Debugging Issue with S32K144 MCU Using SEGGER J-Link and S32DS IDE

[Gowtham_768]

Sure, Gowtham! Here's a clear and technical version of your question that you can post in a community group (like NXP forums, Stack Overflow, or embedded systems groups):

Hi everyone,

I'm working on S32K144 and currently developing custom MCAL drivers. I'm using the SEGGER J-Link debugger along with S32 Design Studio (S32DS) for development.

While trying to debug my code, I’m encountering a continuous stream of errors and warnings related to register and memory access. Below are the key error messages:

ERROR: Cannot read register 26 (FAULTMASK) while CPU is running  
ERROR: Cannot read register 27 (CONTROL) while CPU is running  
...
ERROR: Cannot read register 64 (FPS31) while CPU is running  
WARNING: Failed to read memory @ address 0xDEADBEEE  

Observations:

• These errors appear as soon as the target starts running.

• It seems like the debugger is unable to access system or floating-point registers while the CPU is in execution mode.

• The memory warning is pointing to an invalid address: 0xDEADBEEE.

Current Setup:

• MCU: NXP S32K144 (ARM Cortex-M4F)

• IDE: S32 Design Studio

• Debugger: SEGGER J-Link (SWD mode, 1 MHz)

• Application: Bare-metal, developing and testing custom MCAL drivers

• Debug Mode: Connected via GDB server and flashing/debugging through S32DS

Questions:

1. Why am I getting these register access errors while the CPU is running?

   • Is there a setting to allow register reads during execution or must the CPU be halted?

2. What could be the root cause for memory access at 0xDEADBEEE?

   • Is this a common default value used for uninitialized pointers in NXP drivers or MCAL?

3. Any recommended way to handle these debugger limitations when developing low-level MCAL drivers?

I'd really appreciate help from anyone who has worked with S32K1xx MCUs, MCAL development, or SEGGER J-Link tools. Let me know if you need more logs or setup details.

Thank you

[Julián_AragónM]

Hi @Gowtham_768,

Sorry to reply with more answers, but please help me confirm this information:

Is this the first time you are trying to connect to the board, or were you able to debug and connect before?

Are you using S32DS v3.6? If not, which version? Also, please share if you are implementing SDK or RTD drivers, and which version as well.

1. Why am I getting these register access errors while the CPU is running? Is there a setting to allow register reads during execution or must the CPU be halted?
   
   The CPU must be halted.
   
2. What could be the root cause for memory access at 0xDEADBEEE? Is this a common default value used for uninitialized pointers in NXP drivers or MCAL?
   
   The 0xDEADBEEE value mainly indicates an error. It's not a standard memory location but rather a value used to indicate that a memory section is uninitialized/has an error. I believe that in your case; it simply states that it cannot connect to the MCU 
   
3. Any recommended way to handle these debugger limitations when developing low-level MCAL drivers?
   
   The first and more obvious thing to say will be to double check that the connection is correct. If you were able to connect before but not now, then there are a couple of things that could be preventing from that:

• Device was using security features when performing mass erase.
• Device is secured.
• Flash Configuration Field was compromised.

Please check the following application note where this issues are detailed described: AN12130: Production Flash Programming Best Practices for S32K1xx MCUs – Application Note

Best regards,
Julián