• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 739 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 Aware Debug in CCSv5 5.1.0.09000

Danny Cullen
Intellectual 510 points

Hi, recently downloaded CCSv5 5.1.0.09000 for use with our newly acquired DM814x EVM.

I can connect using the JTAG port and XDS100v2 USB emulator, view the kernel symbols/source etc but when I enable OS debugging I can't see currently running processes and no options to turn on this part of the view (like there were in CCSv4), "Debug configurations -> Code Composer Studio - Device Debugging -> <config_name> -> Target -> OS Aware Debug Options".

Does anyone know how to enable the viewing of the currently running processes in order to attach and debug when using CCSv5?

Thanks, Danny

  • 0
    Intellectual 510 points

    Some further information, according to this post (circa 03/11): http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/t/99130.aspx

    The Linux Aware Debugging part of Eclipse used in CCSv4 has not been ported to CCSv5.  Presumeably, this is still the case as of 5.1.0.09000?  Could somebody please confirm?  Is this feature on the roadmap for CCSv5 at some point?

    For our usage of the DM814x, we would not have a serial port or network port on the board so debugging using the JTAG  stop-mode and GDB server/client method would not be possible.

    As a second point, using CCSv4, I get the following error when trying to enable OS debugging:

    CortexA8: Can't initialise TLD Driver: per_cpu__runtime.curr - not found

    I am assumming that this is because I'm using kernel version 2.6.37 from the DM814x EZSDK v5.3.1.15 and PSP version 4.1.0.6?  We don't think we can move back to a previous PSP version as the feature we require, such as using the DM814x as a PCIe endpoint are not supported.

    Thanks, Danny

  • 0 in reply to Danny Cullen
    TI__Guru**** 171094 points

    Danny,

    Sorry for the delay, but I was trying to get a confirmation from the development team regarding Linux Thread Aware debug. Unfortunately the news is that this feature was not ported to CCSv5.1 due to compatibility break with the standard Eclipse (required significant changes that would penalize other debug features), lack of popularity and overall performance (speed and memory usage to refresh and store all processes at every breakpoint).


    To date we don't have an estimate to implement an "add-on" tool to CCSv5.1. Sorry.

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 510 points

    Hi Rafael,

    I suspected this may be the case, and although not completely a deal-breaker for our usage of the DM814x it does provide a headache as we're planning on using the chip on a PCIe card and as such reserving board real-estate for a network switch or second serial port for use with GDB server/client is not very appealing.

    Thanks for the confirmation though!  We're still prototyping on the EVM at the minute.

    Regards,

    Danny

  • 0 in reply to Danny Cullen
    TI__Guru**** 171094 points

    Danny,

    If you have an ethernet connection in your board, you don't need to have an additional one just for debugging, as CCS/GDB/GDBserver can connect to it directly provided the board and the PC are in the same network. 

    If you have a JTAG connector in your board (highly recommended) and a XDS560v2 emulator, in addition to the standard debugging you can also try to use STM to redirect Linux standard I/O console (among other things). Check:

    http://e2e.ti.com/blogs_/b/mobile_momentum/archive/2011/01/03/how-omap-software-developers-use-system-trace-to-boost-performance.aspx

    http://processors.wiki.ti.com/index.php/Using_System_Trace_%28STM%29

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 510 points

    Thanks again Rafael for your comments, unfortunately, the PCIe board we are designing will not have any network port (it will be a dedicated product for encoding MPEG4/H264 content) in a host PC.  So that is why our preferred application debugging platform would have been the Linux Aware Debug (via JTAG).  It was a struggle to get the hardware department to include a single serial port to view the Linux console :)

    We are desiging in a JTAG port for our product and I will follow your suggestion for using STM,  We are pleased that we can debug the Linux kernel and modules through this interface too.

    Regards,

    Danny.