• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 83 subscribers
  • Views 636 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.

CCS/TMS320F280049C: CCS/TMS320F280049C

Ramesh Muruganantham
Expert 1410 points

Part Number: TMS320F280049C
Other Parts Discussed in Thread: UNIFLASH,

Tool/software: Code Composer Studio

We have developed a hardware based on TMS320F280049C.  We earlier developed the firmware on the launchpad and was working fine.  I changed the debug probe to XDS200 in the target configuration (.ccxm file). Source listed below.  In the new hardware I am able to flash and the code is also working after flashing through 'uniflash'.   However when I connect through code composer the code is not getting executed.  Please help

?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 XDS2xx USB Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS2xx USB Debug Probe_0" href="connections/TIXDS2XXUSB_Connection.xml" id="Texas Instruments XDS2xx USB Debug Probe_0" xml="TIXDS2XXUSB_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS2xx USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds560icepick_c.xml" id="drivers" xml="tixds560icepick_c.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560c28x.xml" id="drivers" xml="tixds560c28x.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560cla2.xml" id="drivers" xml="tixds560cla2.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds560cs_child.xml" id="drivers" xml="tixds560cs_child.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320F280049C_0" href="devices/f280049c.xml" id="TMS320F280049C_0" xml="f280049c.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>

  • 0
    Expert 1410 points

    In code composer I get this error message while it was flashed successfully in uniflash.

    Texas Instruments XDS2xx USB Debug Probe_0/C28xx_CPU1 : Target must be connected before loading program.

  • 0 in reply to Ramesh Muruganantham
    TI__Guru 50611 points

    Ramesh,

    Open the Target Configuration file, and on the right side (Advanced Setup), can you run the Test Connection. It should give some idea why ccs is not connecting.

  • 0 in reply to Santosh Jha
    Expert 1410 points

    I checked and got the following displayed

    [Start: Texas Instruments XDS2xx USB Debug Probe_0]
    Execute the command:
    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
    [Result]

    -----[Print the board config pathname(s)]------------------------------------
    C:\Users\VDSSUP~1\AppData\Local\TEXASI~1\
        CCS\ccs920\0\0\BrdDat\testBoard.dat
    -----[Print the reset-command software log-file]-----------------------------
    This utility has selected a 560/2xx-class product.
    This utility will load the program 'xds2xxu.out'.
    E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Open::dtc_io
    Failed to open i/o connection (xds2xxu:0)
    An error occurred while soft opening the controller.
    -----[An error has occurred and this utility has aborted]--------------------
    This error is generated by TI's USCIF driver or utilities.
    The value is '-250' (0xffffff06).
    The title is 'SC_ERR_ECOM_EMUNAME'.
    The explanation is:
    An attempt to access the debug probe via USCIF ECOM has failed.
    [End: Texas Instruments XDS2xx USB Debug Probe_0]
  • 0 in reply to Ramesh Muruganantham
    TI__Guru 50611 points

    Ramesh,

    It looks like there is an issue in physical connection between host pc and JTAG debugger.

    Please refer to http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems

    Also, please refer to AppNote on C2000 MCU JTAG connection debug.

     http://www.ti.com/lit/an/spracf0/spracf0.pdf 

  • 0 in reply to Santosh Jha
    Expert 1410 points
    Sorry.  Previously I connected ccs in paralllel to uniflash.   Today I connected only CCS and Test connection displays the below.  However the debugging  is not enabled.  It displays "Texas Instruments XDS2xx USB Debug Probe_0/C28xx_CPU1 : Target must be connected before loading program."
    [Start: Texas Instruments XDS2xx USB Debug Probe_0]
    Execute the command:
    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity
    [Result]

    -----[Print the board config pathname(s)]------------------------------------
    C:\Users\VDSSUP~1\AppData\Local\TEXASI~1\
        CCS\ccs920\0\0\BrdDat\testBoard.dat
    -----[Print the reset-command software log-file]-----------------------------
    This utility has selected a 560/2xx-class product.
    This utility will load the program 'xds2xxu.out'.
    The library build date was 'Aug 26 2019'.
    The library build time was '12:55:28'.
    The library package version is '8.3.0.00003'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '13' (0x0000000d).
    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]-----------------------------
    This emulator does not create a reset log-file.
    -----[Perform the Integrity scan-test on the JTAG IR]------------------------
    This test will use blocks of 64 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]------------------------
    This test will use blocks of 64 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 DR Integrity scan-test has succeeded.
    [End: Texas Instruments XDS2xx USB Debug Probe_0]
  • 0 in reply to Ramesh Muruganantham
    Expert 1410 points

    I tried to play with CCS and did the following and the issue is solved

    Run-->Debug Configuration -->Target --> Auto Run and Launch -->Launch Options --> enabled the 'Connect to the Target on Debugger Startup'.  Now debugging is working.

    I am wondering how this was working for Launchpad?

    Regards,

    Ramesh

  • 0 in reply to Ramesh Muruganantham
    TI__Guru 50611 points

    Ramesh Muruganantham said:
    tried to play with CCS and did the following and the issue is solved

    I am glad it is working now.

    Ramesh Muruganantham said:

    I am wondering how this was working for Launchpad?

    On Launchpad, It has xds110 emulator