Part Number: CCSTUDIO
Other Parts Discussed in Thread: AM2434
Hi,
I am using latest CCS12 and SDK and I am using attributes to place variables at specific memory locations for my am2434 LP. For example:
volatile GENERAL_MEM g_GeneralMemory __attribute__((aligned(4), section(".bss.general_mem"))); // GENERAL_MEM : ORIGIN = 0x070180000, LENGTH = 0x10000
Obviously, there are corresponding linker and syscfg memory configurations to make this work.
The program compiles and runs fine - the data is in the correct location and visible across all cores (the intent of using defined memory locations).
However, if I try to use the g_GeneralMemory variable name in any of the debug tools (expression evaluator, memory viewer, graph etc.), the variable name seems to be unresolvable by the debugger and no data is shown. Using the address directly (e.g. 0x070180000) the data is correctly shown.
Also, removing the attribute allows the debugger to 'see' the variable - but it's obviously now in the 'wrong' location.
I understand the issue with 'dual-address' memory such as ARM TCM or PRU local memory that is invisible to the debugger, but the memory in question is general purpose.
Thanks for your help,
Steve
