This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Debugger vs code register address discrepancy

Other Parts Discussed in Thread: CONTROLSUITE, CODECOMPOSER

Hello,

I have found that the debugger's register view is looking at different addresses than what I think it should.  I'm seeing this on multiple M-core projects that once worked but now don't.  I even reloaded a TI example, and I'm seeing the same problem.

I'm using CCSv5.1.0.09, Concerto F28M35H52C1 (here I'm talking about the ARM core), configuration file is set for the right chip, and linker command file is the original C:\TI\ccsv5\Workspace\enet_lwip_m3\lwip.cmd

According to C:\TI\controlSUITE\device_support\f28m35x\v110\MWare\inc\hw_sysctl.h

#define SYSCTL_MWRALLOW                     0x400FB980 // M3 Configuration Write Allow

When I hover my mouse over the HWREG marco in my code, it confirms that it's using that address.

HOWEVER, in the debugger, if I right-click the register in the registers view SYSCTL -> MWRALLOW, and select "View Memory At Address", then it takes me to 0x400FE26C

As I step through the code, I see 0xA5A5A5A5 get written to 0x400FB980, and the Register View still shows MWRALLOW equal to zero.  I've also confirmed the register address discrepancy for other registers, like the value shown in the Registers View for SYSPLLMULT is showing up in the Memory Browser at address 0x400FE004, but the .h file says it should be at 0x400FB804.

Where can I find the absolute addresses of the registers?

What maps the register for the debugger view?

Thanks,
-Will