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.

Debugging early code in Linux boot on OMAP-L137

Does anyone have experience in symbolic debugging early Linux boot code on the L137. If so, what is suggested? I have an evaluation copies of CCSv3.3 and CCSv5, but I am mostly familiar with GDB server/client using emacs etc. I also have a TI USB100v2 JTAG emulator. I would prefer to debug from a Linux environment, but I do have a copy of Windows XP as a last resort.

Any help in getting started would be much appreciated.

 

  • David,

    Here are a couple of related posts that should point you in the right direction. Although they are not for the specific processor you are using, the general idea and procedure would be the same:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/94214/336605.aspx#336605
    http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/p/59474/335642.aspx#335642

     

  • Thanks for your quick reply. Unfortunately I am now having a more basic problem installing CCSv5. I just purchased a Blackhawk USB100v2 Emulator but unfortunately the kernel module supplied in CCSv5 does not install on my Linux (Ubuntu based) system:

    insmod: error inserting 'Bh560v2/linux.ko/2.6.32-21-generic/h_dtc.ko': -1 Invalid module format


    I am guessing this is due due to kernel version differences as my version is: 2.6.35-28-generic. Is there a repository for an updated version of this driver?

     

     

  • David,

    The device driver you mentioned is for BH560v2 and not for BH USB100v2 - which one did you purchase? The BH560v2 does not yet have USB device drivers for Ubuntu 10.04LTS, while the USB100v2 does not require any additional step for loading its device driver - i.e., it should simply work. 

    Depending on what's your hardware you have few options:

    - If you have a BH560v2, use the Ethernet interface instead of the USB - it works like a charm for me (I have the same emulator)

    - If you are using a OMAPL137 EVM from Spectrum Digital you may be able to use the board's embedded emulator (a XDS510USB+) - I recall using it sometime in the past, but I would need to confirm this.

    - If you have a XDS100v2, it has complete device driver support and it also works very well. 

    Hope this helps,

    Rafael

  • Blackhawk expects to post a fix (via a download link) for the invalid .ko file today.

  • Thanks. I have a USB-100v2 so that driver did not apply. Anyway I upgraded to CCSv5.1 and now I have a problem on "Associating the Kernel Project with the Target" on page 11 of the "Linux Debug in CCSv5" document. It states "Select Run -> Debug Configurations to bring up the dialog". Unfortunately there does not appear to be a "Run" in the top row. It reads "File Edit View Navigate Project Tools Scripts Window Help" but no "Run". Is there an alternative path to associate the kernel Project with the Target?
  • Another small issue I think I might have spotted is that the filter in some dialogs for "All files" is "*.*" and not "*". This means that vmlinux will not show, but vmlinux.o will.
  • I don't know what I did, but eventually the "Run" menu appeared and I was able to associate the project to the target. Unfortunately now I am faced with another error: ICEPICK_C: Error connecting to the target: (Error -151 @ 0x0) This utility failed to open the adapter for a custom emulator. The adapter returned an error. (Release 5.0.353.0)
  • David,

    The page you are following was created with the CCSv5.0.x version, the version that officially supports Linux debugging. CCSv5.1 is beta and is still undergoing some interface changes, therefore the menu Run was removed.

    You can re-enable it. Open the CCS Edit perspective and go to menu Window --> Customize Perspective --> tab Menu Visibility --> select the check box Run.

    David Lambert said:

    Unfortunately now I am faced with another error: ICEPICK_C: Error connecting to the target: (Error -151 @ 0x0) This utility failed to open the adapter for a custom emulator. The adapter returned an error. (Release 5.0.353.0)

    I get the exact same error if I disconnect my emulator from the PC and try to connect to the target. If you open a terminal and type lsusb do you see an entry for Future Technology Devices International, Ltd? 

    Try to connect the emulator to another USB port or restart the PC (sometimes Ubuntu strangely refuses to detect some USB devices on my system, but I am using 64-bit 10.04). 

    If that is not the case, what is the exact version of CCS you are using? 
    Hope this helps,
    Rafael

  • desouza said:

    You can re-enable it. Open the CCS Edit perspective and go to menu Window --> Customize Perspective --> tab Menu Visibility --> select the check box Run.[

    Thanks!

    Unfortunately now I am faced with another error: ICEPICK_C: Error connecting to the target: (Error -151 @ 0x0) This utility failed to open the adapter for a custom emulator. The adapter returned an error. (Release 5.0.353.0)

     

    I get the exact same error if I disconnect my emulator from the PC and try to connect to the target. If you open a terminal and type lsusb do you see an entry for Future Technology Devices International, Ltd? 

    Try to connect the emulator to another USB port or restart the PC (sometimes Ubuntu strangely refuses to detect some USB devices on my system, but I am using 64-bit 10.04). 

    If that is not the case, what is the exact version of CCS you are using? 
    Hope this helps,
    Rafael

     

    [/quote]

    lsusb shows:

    ...

    Bus 001 Device 045: ID 0403:a6d0 Future Technology Devices International, Ltd

    ...

    Changes Device ID on unplug/plug

    CCS version: 

    Code Composer Studio 

     

     Version: N201103281800 

    I still get the error:
    ICEPICK_C: Error connecting to the target: (Error -151 @ 0x0) This utility failed to open the adapter for a custom emulator. The adapter returned an error. (Release 5.0.353.0) 

     

     

  • I have now tried this on 2 machines, one HP laptop, and one Dell desktop, both running Ubuntu 10.10. Both give the same symptoms. Could someone please advise m e on which version of CCSv5 is preferred.