httpstapxcardio[ has left #rust-embedded [#rust-embedded]
<JamesMunns[m]>
yep, waiting for the bot to 🔨
<JamesMunns[m]>
(for some reason the "redact all recent messages for user" command is much slower than the "ban user from all rooms" command, but now that user has been banned and all messages redacted 🙂 )
dav1d9 has joined #rust-embedded
dav1d has quit [Ping timeout: 245 seconds]
dav1d9 is now known as dav1d
dngrs[m] has quit [Quit: Idle timeout reached: 172800s]
dirbaio[m] has quit [Quit: Idle timeout reached: 172800s]
ivmarkov[m] has quit [Quit: Idle timeout reached: 172800s]
thejpster[m] has quit [Quit: Idle timeout reached: 172800s]
Emkanea[m] has joined #rust-embedded
<Emkanea[m]>
I am trying to implement some time/timer logic on top of embedded-time. After struggling with durations and conversion I also found some behavior (checked_duration_since not working for overflow cases) which I do not understand. I also saw that there is no more activity in the repo in the last 4 years. So I came here to ask if building on top of it is a bad idea? Or is it still the standard?
dirbaio[m] has joined #rust-embedded
<dirbaio[m]>
yeah don't use it
<Emkanea[m]>
so embassy-time then?
<dirbaio[m]>
alternatives are embassy-time, rtic v2 monotonics, or fugit
<dirbaio[m]>
or if your needs are really simple, the embedded-hal/embedded-hal-async 1.0 DelayNs trait
<dirbaio[m]>
(it only allows waiting for a certain amount of time, not measuring time. it can still be quite flexible especially with async, for example you can use it to implement a timeout with select())
KevinPFleming[m] has joined #rust-embedded
<KevinPFleming[m]>
that's useful to know. it's unfortunate that embedded-time didn't make any progress.
<GrantM11235[m]>
I'm using probe-rs 0.29.0, I have debug = 2 in my cargo toml, and I enabled the "print-defmt" feature in panic-probe. defmt is working fine up until the panic
<dirbaio[m]>
your firmware is panicking
<dirbaio[m]>
and probe-rs is incapable of unwinding past the panic call so you don't see the full stacktrace :(
<dirbaio[m]>
is the panic message missing also?
<GrantM11235[m]>
Yeah
<dirbaio[m]>
yeah I have also seen that happen with 0.29 😭
<GrantM11235[m]>
I just installed the git version, now I can see the panic message
<dirbaio[m]>
would be helpful if you could find which patch fixes it
<dirbaio[m]>
maybe it's the one I linked
<dirbaio[m]>
if we find what it is we might do a 0.29.1 (or 0.30.0?) since not showing panic messages is quite bad
<dirbaio[m]>
* because if we
<GrantM11235[m]>
Its weird, I'm pretty sure I was correctly seeing the same panic message before on 0.29.0 at some point earlier today, I don't know why it stopped working
<GrantM11235[m]>
I just finished compiling the revision from that pr, and it seems to work
<dirbaio[m]>
must be that, then
<dirbaio[m]>
it was made almost after the 0.29 release so not much in between
GuineaWheek[m] has quit [Quit: Idle timeout reached: 172800s]
d34db33f has joined #rust-embedded
<i509vcb[m]>
So uhh 5V microcontroller in 2025 anyone?