Posted in the linux forum but probably more relevent here.
http://e2e.ti.com/support/embedded/linux/f/354/p/167281/680398.aspx#680398
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.
Posted in the linux forum but probably more relevent here.
http://e2e.ti.com/support/embedded/linux/f/354/p/167281/680398.aspx#680398
Graham,
I never performed module debugging using either kgdb or CCS, therefore my knowledge on the subject is very limited. Since the original post references Sys/Link, I would suggest you to get help from the BIOS forum, as one of their experts there may have already experimented with that.
Regards,
Rafael
I have had another go at this. By setting up a normal linux kernel debug session. Once the module is loaded from the module load address I can work out an address to set a breakpoint. Set the breakpoint. Run the code and lo and behold the breakpoint is hit.
However all you get is a disassembly and the registers. The rest you have to go figure yourself.
All the CCV5 needs to do is to be able to load extra symbols at a specified offset and it would work!
CCSV5 release notes suggests that module debugging can not be done because Linux aware debugging is not supported in CCSV5.
Graham,
It is possible to load symbols with an offset. There are a couple ways to do it. The most common way is to open the Modules View (View -> Modules). When this view opens it will show you all the symbol files that are loaded. Along the top are a set of buttons. The load symbols and add symbols buttons allow you to specify an offset.
These actions are also available from the Run -> Load menu. However I like the modules view since it shows you everything that is loaded.
Regards,
John