One thing I figured out is that merely writing into POWMAN_TIMER does not trigger this issue, as in my code at the start I currently read POWMAN_TIMER, and it by $FFFF (because it contains upper bits that we need to clear out before setting it), or it by POWMAN_TIMER_NONSEC, or it by $5AFE0000 (the "password"), and then set POWMAN_TIMER to the resulting value without a problem. So I really think it is probably setting POWMAN_TIMER_RUN in particular that could cause the problem (even though in theory setting POWMAN_TIMER_ALARM, which is write-clear, or clearing POWMAN_TIMER_ALARM_ENAB could cause it; I haven't tested it this far).
Statistics: Posted by tabemann — Mon Sep 02, 2024 7:05 pm