Customer is Aurora.
s32g2
They are having trouble with a method to trigger a debug without needing to perform a reset first. So they are wondering if they even need to consider SM1.FCCU.UNINTENDED_DEBUG_MON?
It seems to me a debugger can be "attached" to a running system, so being able to detect this and force a fault to trigger a chip reset would be vital to safety? But they are indicating the test for this fault requires a chip reset, so it wouldn't be the same as a debugger "attach".
-Randy Krakora
