Hello,
we once had the issue that Spinlocks will not reset properly after a "warm" reset, mentioned here: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1008815/processor-sdk-am64x-ccs-cpu-reset-does-not-reset-spinlocks/3728731?tisearch=e2e-sitesearch&keymatch=%25252525252520user%2525252525253A453845#3728731
So we need to manually reset them.
Now the following scenario: We are locking a Spinlock and another core triggers a warm reset of all 4 R5F-Cores (so no SBL involved). After the reset the lock is still active and no core can get the lock again.
We do not know which core will be first and sharing the information about who is first and shall reset the Spinlock is some overhead. We are also not starting our SBL, which can of course reset the Spinlocks, because it would be the only application running at this time.
So a warm reset can lead to a deadlock of the Spinlocks in the worst case, because the lock is still active. What happens if every core tries to reset the Spinlocks? Would this be at least a workaround or even a viable solution?
Best regards
Felix