Other Parts Discussed in Thread: HALCOGEN, TMS570LC4357, TMS570LS3137
When implementing the SafeTI SDL PSCON selftest "PSCON_PMA_TEST" I am noticing a bug, similar to the related thread.
When in user mode, the test writes to GLOBALCTRL1.AUTO_CLK_WAKE_ENA expecting an abort, then compares the value of the register before the bad write and after to ensure it was not modified.
In testing, writing to the register does not change the value, however no data abort or otherwise is triggered. The test passes because the register was unmodified, but this fails to test the actual abort behaviour.
Is there any reason why this would happen?