ChanServ changed the topic of #rust-embedded to: Welcome to the Rust Embedded IRC channel! Bridged to #rust-embedded:matrix.org and logged at https://libera.irclog.whitequark.org/rust-embedded, code of conduct at https://www.rust-lang.org/conduct.html
Mathias[m] has quit [Quit: Idle timeout reached: 172800s]
starblue has quit [Ping timeout: 244 seconds]
starblue has joined #rust-embedded
ivche has quit [Ping timeout: 244 seconds]
ivche has joined #rust-embedded
starblue has quit [Ping timeout: 276 seconds]
starblue has joined #rust-embedded
pcs38 has joined #rust-embedded
HumanG33k has quit [Ping timeout: 260 seconds]
HumanG33k has joined #rust-embedded
<RobinMueller[m]> thejpster: It is vaguely documented, but there actually is a standard set of things to do. The ARM ref manual recommends doing an exception return. Most vendor code and exception handlers I saw in the wild branch to some (user) provided C handler. Or both combined.. How does your debug script look? I was not sure whether breakpoints in the global assembly even work (at least in the GUI), I tried setting one in the startup
<RobinMueller[m]> routine and I think it did not work.
<thejpster[m]> My scripts are TRACE32 specific and they set breakpoints on the vector addresses.
<thejpster[m]> In GDB it would be break *0x00000008 etc