• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Subscribers 59 subscribers
  • Views 2924 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.

CCSv5.02 Debug initialisation error

sreekanth bolloju
Prodigy 20 points

Other Parts Discussed in Thread: EK-TM4C123GXL, AM3358

Hi

I am trying to debug linux kernel on panda board with XDS100v2 USB debugger.

 

I have created the target configuration by selecting Connection as "Texas Instruments XDS100v2 USB Emulator" and Board or Device as "OMAP4430(No STM, ETB only).

After this i associate my kernel project using the debug configurations option in CCS.

I configured the Target connection device as "Texas Instruments XDS100v2 USB Emulator_0/CS_DAP_PC"

and when i run debug i get the following error:

Unable to load /usr/local/CCSv5/ccsv5/ccs_base_5.0.2.00006/emulation/drivers/tixds510CortexM.dvr: /usr/local/CCSv5/ccsv5/ccs_base_5.0.2.00006/emulation/drivers/tixds510CortexM.dvr: cannot open shared object file: No such file or directory

 

Thanks

Sreekanth

  • 0
    TI__Guru**** 173310 points

    Sreekanth,

    This is a known issue with CCS 5.0.2 in Linux. The driver xml file is incorrectly referencing a Windows driver (tixds510CortexM.dvr) instead of the Linux driver (libtixds510cortexm.so). This is fixed in 5.0.3. The final release of 5.0.3 is expected later this month, but there is a release candidate available that you can download and try out:  http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5#Downloads

     

  • 0 in reply to AartiG
    Prodigy 20 points

    Thanks Aarti.

    I have been able to resolve the error by bypassing cortexM CPU from the Advanced tab in the target configurations.

    But after that i was getting a POP up saying that Use of "JTAG debbugers needs license".

     

    I am using the 30-day evaluation version. after a bit of googling i found that the evaluation version does not support XDS100v2 debugger

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

    note on this page says:

    "NOTE: The 30-day trial version language in the CCS installer license agreement applies only for the case of using high-speed JTAG

               emulators (does not apply to use of the XDS100v2 JTAG emulator).  If a debug configuration is used that requires a high-speed

               JTAG emulator, you will be prompted to register your software for a fee.  All use of CCSv5 (excluding use of high-speed JTAG

               emulators) if free and has no 30-day time limit."

     

    Is xds100V2 jtag emulator supported in the 30 day trail version of release candidate that you specified, also can you specify the JTAG emulators the 30 day trail version supports

     

    Thanks

    Sreekanth

     

     

     

  • 0 in reply to sreekanth bolloju
    TI__Guru**** 173310 points

    The wording on that wiki page is a bit confusing. The 30 day evaluation license will work with all emulators (xds100 as well as xds510/xds560 emulators). After the evaluation period ends (30 day + 90 day extension), you will need to have a paid license to use xds510/xds560 class emulators, but can still use it for free with xds100 emulators as long as you wish. CCS 5.0 uses the same license as CCSv4.

    This page provides more details on the licensing options: http://processors.wiki.ti.com/index.php/Licensing_-_CCS

     

     

  • 0 in reply to AartiG
    Prodigy 130 points

    I'm using ccsv5.5, still encountering this problem when I try to debug Piccolo Launchpad.

    Unable to load /opt/TI/ccsv5/ccs_base/DebugServer/drivers/JavaToGtiAdapter.dvr: /opt/TI/ccsv5/ccs_base/DebugServer/drivers/JavaToGtiAdapter.dvr: cannot open shared object file: No such file or directory

  • 0 in reply to Larry Lo
    Prodigy 10 points

    Larry Lo said:

    I'm using ccsv5.5, still encountering this problem when I try to debug Piccolo Launchpad


    Same here with a diffrent board (TrxEB) and ccsv6.0.0.13 under Ubuntu 14.04. The problem seems to be unsolved.

  • 0 in reply to Rene Wuerll
    Prodigy 30 points

    And..... Same here on ccsv6.0.1.00040 with EK-TM4C123GXL (The Tiva C Series TM4C123G) running FC20.

    Debugger Initialization Error
    Unable to load /opt/.../ti/ccsv6/ccs_base/DebugServer/drivers/JavaToGtiAdapter.dvr: /opt/.../ti/ccsv6/ccs_base/DebugServer/drivers/JavaToGtiAdapter.dvr: cannot open shared object file: No such file or directory

  • 0 in reply to Vernon McPherron
    Guru 86865 points

    Hi Vernon,

         Have you tried importing projects at Tivaware to CCS like the blinky example and debug it?

    - kel

  • 0 in reply to Markel Robregado
    Prodigy 30 points

    After messing around with a bunch of things.  Editing xml files and changing path and name to correct libs.  Making sure I had (and ownership and mode was correct) the correct libraries in the correct places.  And USB permissions correct.  I now get the famous "Error connecting to the target:  Frequency is out of range" when I try to debug the BlinkWithoutDelay demo example.

  • 0 in reply to Vernon McPherron
    Guru 86865 points

    Vernon McPherron said:
    "Error connecting to the target:  Frequency is out of range" when I try to debug the BlinkWithoutDelay demo example.

    Possibly that your JTAG debug port has been locked. Use LM Flash Programmer "Debug Port Unlock Utility". On reasons why JTAG debug port would be locked, see sticky at my signature "JTAG Communication Failures".

    I am not familiar with this Blink Without Delay demo example program. Is that from Tivaware examples for Tiva Launchpad?

    - kel

  • 0 in reply to Vernon McPherron
    Guru 92251 points

    Vernon McPherron said:
    I now get the famous "Error connecting to the target:  Frequency is out of range" when I try to debug the BlinkWithoutDelay demo example.

    You might have the problem where CCS can't find libusb-1.0.so - see ccs6 beta 4 unable to access Tiva Launchpad on CentOS 6.5

  • 0 in reply to Chester Gillon
    Prodigy 30 points

    Sorry, didn't mean to hijack this thread!  :S


    You're right, that did the trick.  I just needed to:

    ln -s /usr/lib/libusb-1.0.so.0 /usr/lib/libusb-1.0.so


    THANKS!

  • 0 in reply to Vernon McPherron
    Prodigy 20 points

    Vernon,

    Is it possible for you to discuss what exactly you did to avoid the error you were getting about JavaToGitAdapter.dvr?  I am using CCSv5.5 for the BeagleBoneBlack (AM3358) trying to run some of the examples from StarterWare through the XDS100v2 and getting the same error.  I see the problem is pointing to windows drivers and not Linux drivers but how do I fix it?

    Any help would be very appreciated!

  • 0 in reply to Lynetta Rajkovich
    Intellectual 270 points

    Strangely enough, I'm suddenly getting this error on ONE project, but not on another! That is, the

    Unable to load /opt/ti/ccsv6/ccs_base/DebugServer/drivers/JavaToGtiAdapter.dvr

    on launch of debugger. (EDIT: See post below for a (possible) fix!)

    Can't figure out WTF is going on. Only thing that just came to mind as I'm typing this is that I'm using Git, and I may have made changes on a Windows machine and pushed them back to the repository, thus overwriting the target config??

    I have another project with similar code that is launching no problems... bizarre. However, I think the git thing might be the problem. This would also explain the syntax highlighting problem I'm having as well... Let me see what I can do and I'll post a fix here.

  • 0 in reply to Aurelius Rowsell
    Intellectual 270 points

    FIX:

    This worked for me, may not work for others. If you open the targetConfigs folder and open the .xml file in there, it opens up a window in CCS to configure the connection config. For some reason, my project had a ComPort listed in the alternate connection section. Remove that extra Com Port and it starts working!

    This makes sense, as Linux does not use Com Ports, we use ttyUSB or ttyACM or ttyS. Hence the debug looking for a Windows driver...?

    If this fix doesn't work for you let me know and I'll try and help you more :)