OpenSDA debugger in S32 project being compiled by diab can't write many EmbSys registers

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

OpenSDA debugger in S32 project being compiled by diab can't write many EmbSys registers

189 Views
kstaroverov
Contributor I

Hi,

I encountered a problem when I can't get write access to many EmbSys registers.

Everything was good with GCC, but after switching to DIAB I get this problem even if I set a breakpoint at very beginning of the startup code.

After an attempt to write, S32 highlights such a register in purple (see attachment)Screenshot 2023-03-17 192046.png

Debug console gives no hint on that.

Tools data:  MPC5748G-DEVKIT rev D, diab 4.7.1, S32 v2.1

Could you advise a direction on where to dig for fixing this? What is the meaning of the purple color?

 Thanks, 

          Kostiantyn.

p.s.

rchw sections for gcc/diab projects and debugger settings are identical

 

0 Kudos
1 Reply

172 Views
stanish
NXP Employee
NXP Employee

Hello,  

Please make sure the execution in debugger is halted when checking embsys register view (P&E cannot read the registers in while code is running). Also please double-click on peripheral register name to disable and re-enable the register to view again - the register value should reflect the latest value.

Also please make sure you enabled the peripheral clock to the peripherals you are writing into. Perhaps there is a diff between diab and gcc init code.

Hope it helps. 

Stan

0 Kudos