• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 285 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Linux module debug in CCSv5

Scott Park
Prodigy 110 points

How do I perform Linux module debug in CCSv5?

Specifically, I would like to be able to debug syslink.ko on a TI816x platform using a Spectrum Digital XDS560V2 probe.

I am already successfully performing Linux kernel debug using the above configuation using the instructions at this link:

http://processors.wiki.ti.com/index.php/Linux_Debug_in_CCSv5

However there are no instructions for debugging kernel loadable modules, and I am unable to successfully set breakpoints in them.

Scott

  • 0
    Intellectual 460 points

    This is a good question.  

    Using the information here http://lwn.net/Articles/90913/ I concluded that it should be possible to set breakpoints and examine memory by adding the offset of the module to the symbol.  CCSV5 does this simply by entering base_address + symbol.  However I found the debugger could not read the memory the module was loaded into so was unable to set breakpoints or examine the memory. 

    The memory issue non withstanding gdb can be told where the module is loaded and provide source level debugging. As far as I can tell this is not possible with CCSV5.  So CCSV5 has managed to make kernel module debugging harder.  With no OpenOcd support for DM816x the only other option is kgdb which AFAIK is not compatible with jtag debugging.

    I will link to this thread from the CCSV5 forum and TI can move it if they want.