Hi NXP,
my environment is jlink v11 and s32DS. it works until yesterday, when starting debug, it can stop at main entry, then run step into, or any other operation, it goes to unknown state. the abnormal as attached.
1. debug can't halt CPU.
2. read sram failed.
but with the same hardware and elf file, i use ozone , it works normally.
here my debug cofig. it's same compare to it's working time.
i dont know what cause this problem, after totally reinstall S32DS , solved. but after few days use, S32DS debuger seems responses slower than normal.
currently, use OZone to program and debugger instead.
Ozone is software on PC, my board and jlink are the same. i just use it instead of S32DS debug function, all others are same.
I don't find any problem with your configuration, and your other debuggers (ozone) can burn and debug your hardware normally, so the possible reason may be your J-LINK tool or the link problem.