-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic from init (rtic 0.5.5) #361
Comments
Hi, I see the issue. This line is undefined behavior and was fixed in the latest release: https://github.com/quartiq/stabilizer/blob/5d41fa0aa981c68372464c016e9e7a4b222dfc06/src/main.rs#L206 As you have the Tell me if you experience more problems! |
Thanks, it seems to be working now. |
144: Fix syntax for taking core peripherals (required by cortex-m-rtic v0.5.5) r=jordens a=HarryMakes This is to fix a panicking upon initialization problem that is caused by a now undefined behaviour in our code from the perspective of the latest release of the cortex-m-rtic crate. As per conversation in rtic-rs/rtic#361, `context.core` should now be used instead of `cortex_m::Peripherals::take()`, which would cause some unexpected behaviour. On a side note, a similar symptom where the Ethernet PHY does not get reset, as discussed in #141, might have also arisen from this new version of rtic. However, the reset delay still seems a bit too short to me. Co-authored-by: Harry Ho <hh@m-labs.hk>
Hi, I am working on a Cortex-M7-based project that has previously been functional before we update cortex-m-rtic from 0.5.3 to 0.5.5. I suspect that some changes have broken our RTIC implementation (link for reference).
Environment
Error
GDB backtrace:
Using
next
in GDB, the program panics after:The text was updated successfully, but these errors were encountered: