<JamesMunns[m]>
Maybe here or #rtic:matrix.org if it's specific to RTIC? If the questions are about the project in general, maybe here or the issue tracker.
<scorpion2185[m]>
yes it's general. is RTIC Real Time Interface Coprocessor?
<scorpion2185[m]>
it's the os name right?
marmrt[m] has joined #rust-embedded
<marmrt[m]>
Real Time Interruptdriven Concurrency
sroemer has joined #rust-embedded
sroemer has quit [Changing host]
sroemer has joined #rust-embedded
sroemer has quit [Ping timeout: 248 seconds]
sroemer has joined #rust-embedded
sroemer has quit [Ping timeout: 252 seconds]
dne has quit [Remote host closed the connection]
dne has joined #rust-embedded
<scorpion2185[m]>
* name right? it's in my link but i did not look it in long time ๐
<scorpion2185[m]>
atm is that the only active project for the pientime?
<dirbaio[m]>
lots of people rusting the pinetime :D
vollbrecht[m] has joined #rust-embedded
<vollbrecht[m]>
interesting, a couple weeks ago another kickstarter was launching with a similar watch, featuring the same processor, but also running a esp32s3. It's name was spectra. It doesn't seam there OS is open source, but they focus on "right to repair". At least physically it looks that it would be true. It seams there is a market for this stuff :D
<vollbrecht[m]>
* the same nrf processor, but
<JamesMunns[m]>
Turns out you can make hardware a lot cheaper when you tell the people you sell it to that software is their problem :p
<JamesMunns[m]>
(this is picking more on Pine than Spectra, which I haven't seen before)
<scorpion2185[m]>
>If you want to reflash your sealed PineTime to Watchful, it is possible. But there is a chance to brick your PineTime, so don't do this unless you've tried it a few times on a devkit and feel confident. Also consider the fact that once you go to Watchful, there is no way to go back at the moment.
<scorpion2185[m]>
does that mean that i can brick it in a way that i cannot fix it?
lulf[m] has joined #rust-embedded
<lulf[m]>
Not for the faint of heart
<lulf[m]>
Yes, you'd need to use a heatgun to 'unseal' it to fix it (flash it with a debug probe)
<lulf[m]>
Depending on your skills, you might be able to re-seal it just fine
<scorpion2185[m]>
i ordered a dev kit to mess with it
<lulf[m]>
Yeah, devkit is good for experimenting
<lulf[m]>
FWIW I plan to modify watchful to use trouble instead of nrf-softdevice, which will allow it to re-use the mcuboot that comes ootb with the pinetime, allowing you to try watchful without the risk
<lulf[m]>
But it requires some spare time
<scorpion2185[m]>
since it's already unselead i can fix it if something goes wrogn right?
<lulf[m]>
Yes, it's not a problem with the devkit, where you can just use a debug probe to flash it. The above warning only applies to the sealed pinetime, where you must use a 'reloader' that allows you to 'upgrade' from infinitime to watchful without a debug probe.
<lulf[m]>
For details see the above RustNL talk :P
<scorpion2185[m]>
iiuc there is no simulator i watched the video but not too carefully
<scorpion2185[m]>
while mesozoic simulator shows no apps almost no ui
<cbjamo[m]>
I've used crc several times, works great. Big fan of the pre-cooked crc constants.
<takkaryx[m]>
<JamesMunns[m]> "https://github.com/mrhooray/crc..." <- Huh, so it is, itโs not mentioned anywhere in the README and I made a poor assumption,
<takkaryx[m]>
* poor assumption, thanks!
crabbedhaloablut has quit [Read error: Connection reset by peer]