thumbv8 targets (like the RP2350!) start with their memory marked as "non-sharable" at boot, meaning that atomics between the processors *don't actually work*, until you either set the regions sharable in the MPU, or set a global "everythings sharable" flag.
thumbv8 targets (like the RP2350!) start with their memory marked as "non-sharable" at boot, meaning that atomics between the processors *don't actually work*, until you either set the regions sharable in the MPU, or set a global "everythings sharable" flag.
1. Always Keep Interrupts Vectored in a Safe direction
2. Treat All Interrupts as Though They are Enabled
3. Keep Your Event Sources Disabled Until You are Ready to Handle Them
4. Always Be Sure of Your Vector Target and What’s Beyond It
1. Always Keep Interrupts Vectored in a Safe direction
2. Treat All Interrupts as Though They are Enabled
3. Keep Your Event Sources Disabled Until You are Ready to Handle Them
4. Always Be Sure of Your Vector Target and What’s Beyond It
(This is sadly not a joke. That sbemail debuted 1/13/03. We are old).
(This is sadly not a joke. That sbemail debuted 1/13/03. We are old).