GrantM11235[m] has quit [Quit: Idle timeout reached: 172800s]
oneDragon[m] has quit [Quit: Idle timeout reached: 172800s]
starblue has quit [Ping timeout: 264 seconds]
starblue has joined #rust-embedded
Guest7282 has joined #rust-embedded
IlPalazzo-ojiisa has joined #rust-embedded
crabbedhaloablut has quit []
crabbedhaloablut has joined #rust-embedded
vollbrecht[m] has quit [Quit: Idle timeout reached: 172800s]
Ralph[m]1 has quit [Quit: Idle timeout reached: 172800s]
starblue has quit [Ping timeout: 252 seconds]
starblue has joined #rust-embedded
kenny has joined #rust-embedded
starblue has quit [Ping timeout: 268 seconds]
wyager[m] has joined #rust-embedded
<wyager[m]>
What's the consideration between ending a panic handler with udf (panic_probe) vs cortex_m::peripheral::SCB::sys_reset()(panic_persist)?
<JamesMunns[m]>
udf escalates into a hardfault, reset resets
<JamesMunns[m]>
IIRC hardfaults in cortex-m-rt default to an endless loop?
<JamesMunns[m]>
(technically what UDF does is a little different between M0 and other M3/4/7+ targets, but it'll trigger an exception, which if you aren't handling, will by default go into an endless loop. If you don't have a watchdog, it'll just spin forever instead of rebooting)