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 support file and its format

Hi,

I'm working on creating an automated test script system to regression test our code.

This system will need to access the CPU (F280049) memory directly to 'peek & poke' global variable values.

From CCS C compiler output .MAP files I get the address of variables which is helpful and enabling,

however variable type information is missing.

Obviously this information (in great detail) is some where available because CCS Expressions view can

show the value of any global variable and very nicely too because it understands enumerations and C structs and stuff.

So I would like to learn where I can find this information programmatically and in which format.

Our device is at the end of a longish communication path through  UPD and a Linux intermediary so I cannot

use any CCS Scripting or some such that relies on having a JTAG debugger attached to the device.

I guess I could find a C parser and parse our headers to the get the type information but I would still have to

mimic the C compiler to get the offsets to struct fields and stuff. This is at best a longish path my goal and

at worst a nightmare. Any little discrepancy in the parsers or TI standard libraries may choke a C parser....

cheers Kusti