Beaglebone kernel debugging with CCS v5.1


I'm using a Beagle bone REV4 with all software installed on an VMWare.Ubuntu 11.04. I can compile my kernel and use it with a tftp/nfs boot. I can use the CCSV5 to debug in RUN MODE (user space application).

BUT I fail trying to begin with Kernel debuging with CCS. I've tried the sitara support package documentation or such tutorial below but no way.

THe main problem i think ? is that I never can have a connection such as XDS100V2 USB Emulator ? I think i need this connection ... but not sure.

The BBone should embed necessary hardware  but noway, I never have any other "connections" than "Data snapshot viewer". and indeed the directory "ccs_base/common/targetdb/connections" does nt contain anything else than "DataSnapshotViewer.xml".

Please help ?

  • In reply to desouza:

    HI all,

    My problem is not solved but i got a workaround.

    In fact, none of my available Windows Desktops (Vista or 7 32 bits) would work with the BeagleBone except one : An old XP one !!!

    Then i could modify the VID/PID get back to my Linux and ... ouf ... connect to the JTAG/USB emulator ! cool !

    I've to go further trying the "STOP MODE" debugging on my Kernel.

    Thanks for all your suggestions.

  • In reply to peg:


    Thanks for reporting back the solution... It is indeed really strange you couldn't access the board from a Win7/Vista PC.

    Quick question: what is the brand/model of the PCs you used? This information could help other developers that experience similar issues...



  • In reply to desouza:

    Failed to discover Beaglebone RevA3 or A4:

    Mine: is PAckard-BELL,imedia X9234 / Windows vista famillial premium SP2 / CPU Intel core2 Quad Q6600 / 32 bits
    Other: DELL dimension 500 / Windows 7 edition famillial premium SP1 / CPU Intel core2 Quad Q8300 / 32 bits
    Other: DELL vostro 420/ Windows 7 edition famillial premium SP1 / CPU Intel core2 Quad Q8300 / 32 bits

  • In reply to peg:

    HI again,

    Ouups, i forgot to mention the computer on which it has worked correctly: Laptop SAmsung X22 / XP pro 2002 SP3 / Intel Core 2 duo T7500

    Anyway, I'm still struggling to make run my debug "stop mode" for Jtag/USB Kernel debugging.

    Now i can create a "Target configuration" file that can correctly connect and "test connection" seems OK (see below).

    But when i launch my "Debug configuration" (see joined screenshots) my CCS immediately return with the following error :

    Hips .... if anyone has got an idea ?

    Here are the screen-shots of my debug configuration:

    Here is my configuration file:

    (Notice that i've replaced all the beginning "<" chars by a "^" as i could never preview the XML code with e2e forum HMI ?)

    ^?xml version="1.0" encoding="UTF-8" standalone="no"?>
    ^configurations XML_version="1.2" id="configurations_0">

    ^configuration XML_version="1.2" id="Texas Instruments XDS100v2 USB Emulator_0">
            ^instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Emulator_0" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Emulator_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
            ^connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Emulator_0">
                ^instance XML_version="1.2" href="drivers/tixds100v2icepick_d.xml" id="drivers" xml="tixds100v2icepick_d.xml" xmlpath="drivers"/>
                ^instance XML_version="1.2" href="drivers/tixds100v2cs_dap.xml" id="drivers" xml="tixds100v2cs_dap.xml" xmlpath="drivers"/>
                ^instance XML_version="1.2" href="drivers/tixds100v2cortexM.xml" id="drivers" xml="tixds100v2cortexM.xml" xmlpath="drivers"/>
                ^instance XML_version="1.2" href="drivers/tixds100v2cs_child.xml" id="drivers" xml="tixds100v2cs_child.xml" xmlpath="drivers"/>
                ^instance XML_version="1.2" href="drivers/tixds100v2cortexA.xml" id="drivers" xml="tixds100v2cortexA.xml" xmlpath="drivers"/>
                ^instance XML_version="1.2" href="drivers/tixds100v2csstm.xml" id="drivers" xml="tixds100v2csstm.xml" xmlpath="drivers"/>
                ^instance XML_version="1.2" href="drivers/tixds100v2etbcs.xml" id="drivers" xml="tixds100v2etbcs.xml" xmlpath="drivers"/>
                ^instance XML_version="1.2" href="drivers/tixds100v2pru.xml" id="drivers" xml="tixds100v2pru.xml" xmlpath="drivers"/>
                ^property Type="choicelist" Value="0" id="Emulator Selection">
                    ^choice Name="Select by serial number" value="0">
                        ^property Type="stringfield" Value="ttyUSB0" id="-- Enter the serial number"/>
                ^platform XML_version="1.2" id="platform_0">
                    ^instance XML_version="1.2" desc="AM335x_0" href="devices/AM335x.xml" id="AM335x_0" xml="AM335x.xml" xmlpath="devices"/>
                    ^device HW_revision="1" XML_version="1.2" description="AM335x" id="AM335x_0" partnum="AM335x" simulation="no">
                        ^router HW_revision="1.0" XML_version="1.2" description="ICEPick_D Router" id="IcePick_D_0" isa="ICEPICK_D">
                            ^subpath id="subpath_11">
                                ^router HW_revision="1.0" XML_version="1.2" description="CS_DAP Router" id="CS_DAP_M3" isa="CS_DAP">
                                    ^subpath desc="M3_wakeupSS_0" id="M3_wakeupSS">
                                        ^cpu HW_revision="1.0" XML_version="1.2" desc="M3_wakeupSS_1" description="Cortex_M3 CPU" deviceSim="false" id="M3_wakeupSS" isa="Cortex_M3"/>
                            ^subpath id="subpath_12">
                                ^property Type="numericfield" Value="0xc" desc="Port Number_0" id="Port Number"/>

    Here is the result of the "test connection":

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity


    -----[Print the board config pathname(s)]------------------------------------


    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter ''.
    The library build date was 'Feb 13 2012'.
    The library build time was '22:40:23'.
    The library package version is '5.0.623.0'.
    The library component version is ''.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the FTDI FT2232 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for FTDI FT2232 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    -----[The log-file for the JTAG TCLK output generated from the PLL]----------

    There is no hardware for programming the JTAG TCLK frequency.

    -----[Measure the source and frequency of the final JTAG TCLKR input]--------

    There is no hardware for measuring the JTAG TCLK frequency.

    -----[Perform the standard path-length test on the JTAG IR and DR]-----------

    This path-length test uses blocks of 512 32-bit words.

    The test for the JTAG IR instruction path-length succeeded.
    The JTAG IR instruction path-length is 6 bits.

    The test for the JTAG DR bypass path-length succeeded.
    The JTAG DR bypass path-length is 1 bits.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 512 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

  • In reply to desouza:

    Back to my problem ...

    Even if the board can now be seen on XP PC with 0403/6010 VID/PID it is still not visible from any of my Vista or 7 !!!

    I'm desesperate with that can't even us the board on any of my regular PC. Is ther any requirement about vista or XP to recognize the FT232H device ????

    Please help !

  • In reply to peg:

    So it seems that it works with 64 bits Windows not on 32 bits ones .... is ther any palliative please ?

  • In reply to peg:


    Whenever you connect your BeagleBone to the Windows 7 / 32 bits, does it show the "new hardware found" window? If so, make sure you install the standard FTDI drivers on this OS - the boards with the updated VID/PID do not use the TI XDS100 drivers that are installed with CCSv5.

    A link for download is shown at this FAQ.

    Hope this helps,


  • In reply to desouza:


    Yes it does but the recognized VID/PID is weird !! See screenshot.

    Not that connected to my XP the same board shows correct VID/PID and use correct FTDI drivers.

    Yes i've already used the FAQ to pass my VID/PID form 403/A6D0 to 403/6010. Done on XP !

    But any of the programmed VID/PID the recognized VID/PID on 32 bits Windows vista and 7 is the one shown on the screenshot.


  • In reply to peg:

    Hi all,

    The problem is solved, and is so simple !

    In fact it seems that beaglebone has also a USB HUB on board [USB\VID_0424&PID_2412&REV_0;;2USB\VID_0424&PID_2412]

    and this one was definitly not correctly installed on driver side of my Windows 32 bit PCs.

    Here is a driver that has worked for my windows vista premium 32 bits. And thereafter the the two FT2232H dirvers are correctly installed.

    Thanks all

  • In reply to peg:

    Thanks for reporting this; I imagine the fact you were using a virtual machine can influence this yet unreported behaviour (at least on the BeagleBone mailing lists).

    Thank you,