Hi Daniel,
I am using Segger J-Link. When I perform the reset through the IDE (S32 Design Studio) I get a Software reset, and this bit says:
"Software
Indicates a reset has been caused by software setting of SYSRESETREQ bit in Application Interrupt and
Reset Control Register in the Arm core.
0 Reset not caused by software setting of SYSRESETREQ bit
1 Reset caused by software setting of SYSRESETREQ bit"
Instead, when I use PE Micro Multilink Universal as debugger, I get External Reset Pin, and this bit says:
"External Reset Pin
Indicates a reset has been caused by an active-low level on the external RESET (RESET_b) pin.
0 Reset not caused by external reset pin
1 Reset caused by external reset pin"
This last one (with Multilink debugger) makes more sense for me because the debugger can write on the MCU reset pin and so cause a reset through that pin. But in the case of the J-Link debugger, it just felt weird that a reset cause by a user through the debugger triggers a Software reset, which normally is done programmatically from the code.
The only thing I would like to know if it all makes sense?
Best regards,
Adria