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/RM48L952: XDS110 DEBUG PROBE Error

Part Number: RM48L952
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

When downloading the program using XDS110(cTI20), as following error occurs.
The same is true if the TCLK is lowered to 2.5 MHz or less than.
I have used XDS200 before and there were no special errors.
Please help me!
Thank Regards.
  • Hello,

    Can you please re-post the error message? 

  • Dear, Wang

    I re-post error message.

    I was using it well with the XDS200.

    However, the above ERROR is occurring when trying to use XDS110.

    Please advice (CCS configuration and etc...).

    Reards,

    JY Kim

  • Hello,

    Please, Someone reply this post.

    XDS110 Connection Test is OK on CCS.

    But, When downloading out file, erro occurs.

    Regards,

    JY Kim.

  • Hello Kim,

    Can you try the following:

    1. From the View menu in CCS open the Target Configuration View
    2. Find the .ccxml file that is part of your project
    3. Right click on it and choose "Launch selected configuration".  This will start a debug session in CCS but won't connect to anything yet.
    4. When the debug view opens click on the top level node in the tree (it will be the name of the .ccxml file).  Select "Show all cores".
    5. Under "Non debuggable devices" select the one that ends in ICEPick_C.
    6. Click on the connect button on the toolbar. 
    7. Open the registers view.
    8. If you expand core registers. Do the TAP registers have values other than 0 or 1?
    9. Next select the DAP under "Non debuggable devices" and see if you can connect to that.

  • Hello Wang,

    I tried your comment.

    IcePick and DAP was connect.

    And then i tried connect CortexR4.

    But, CortexR4 was disconnect(show error -6311).

    I attach error message.

    Regards,

    JY Kim.

  • Hello Kim,

    The PRSC error is related to reset - TMS570 may be held in reset, or external circuitry may be holding the device in reset. I would strongly check if the TMS570 itself is being held in reset at the time you are trying to connect using CCS.

  • Hello Wang,

    Please check RM48L952.ccxml.

    <?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 XDS110 USB Debug Probe_0">
            <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
            <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
                <instance XML_version="1.2" href="drivers/tixds510icepick_c.xml" id="drivers" xml="tixds510icepick_c.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510cortexR.xml" id="drivers" xml="tixds510cortexR.xml" xmlpath="drivers"/>
                <property Type="choicelist" Value="0" id="Debug Probe Selection"/>
                <property Type="choicelist" Value="1" id="The JTAG TCLK Frequency (MHz)">
                    <choice Name="Fixed with user specified value" value="SPECIFIC">
                        <property Type="stringfield" Value="1.25MHz" id="-- Enter a value from 100.0kHz to 2.5MHz"/>
                    </choice>
                </property>
                <property Type="choicelist" Value="0" id="Power Selection">
                    <choice Name="Probe supplied power" value="1">
                        <property Type="stringfield" Value="3.3V" id="Voltage Level"/>
                    </choice>
                </property>
                <platform XML_version="1.2" id="platform_0">
                    <instance XML_version="1.2" desc="RM48L952_0" href="devices/rm48l952.xml" id="RM48L952_0" xml="rm48l952.xml" xmlpath="devices"/>
                <device HW_revision="1" XML_version="1.2" description="RM48L952 QFP/BGA, 3MB Flash, 256kB RAM, 10/100M Ethernet, USB host and slave" id="RM48L952_0" partnum="RM48L952" simulation="no">
                        <router HW_revision="1.0" XML_version="1.2" desc="IcePick" description="ICEPick_C Router" id="IcePick_C_0" isa="ICEPICK_C">
                            <property Type="choicelist" Value="0" id="bypass"/>
                        <subpath id="Port16">
                                <router HW_revision="" XML_version="1.2" desc="Dap" description="CS_DAP Router" id="CS_DAP_0" isa="CS_DAP">
                                    <property Type="choicelist" Value="0" id="bypass"/>
                                <subpath id="PortR4">
                                        <cpu HW_revision="" XML_version="1.2" description="Cortex_R4 CPU" deviceSim="false" id="Cortex_R4_0" isa="Cortex_R4">
                                            <property Type="filepathfield" Value="..\..\emulation\gel\rm48l952.gel" id="GEL File"/>
                                        <property Type="choicelist" Value="0" id="bypass"/>
                                        </cpu>
                                    <property Type="numericfield" Value="4" id="Port Number"/>
                                    <property Type="choicelist" Value="0" id="Force Configuration"/>
                                    <property Type="choicelist" Value="1" id="Initial Configuration"/>
                                    <property Type="choicelist" Value="1" id="Custom Configuration"/>
                                    </subpath>
                                <property Type="filepathfield" Value="..\..\emulation\gel\rm48l952.gel" id="GEL File"/>
                                <property Type="choicelist" Value="0" id="Device Management"/>
                                </router>
                            <property Type="choicelist" Value="1" id="Custom Configuration"/>
                                <property Type="choicelist" Value="1" id="Initial Configuration"/>
                                <property Type="choicelist" Value="0" id="Force Configuration"/>
                            </subpath>
                        <property Type="filepathfield" Value="..\..\emulation\gel\rm48l952.gel" id="GEL File"/>
                        </router>
                    </device>
                </platform>
            </connection>
        </configuration>
    </configurations>

    Regards,

    JY Kim.

  • Hello Wang,

    I have modified RM48L952.ccxml as fowlling.

    <subpath id="PortR4">

    ....

       <property Type="numericfield" Value="0" id="Port Number"/>

    I tried Target Configuration -> Launch Selected Configuration.

    CortexR4 click and then connect button on the toolbar.

    The result was as follows.

    How can i do next?

    Regards,

    JY Kim.

  • Hi Kim,

    What is the purpose to change "numericfield" Value="4" to "numericfield" Value="0"? I don't know what this number is used for.

    Can you please create a new ccxml using CCS or uniflash for RM48 device?

  • Hi Wang,

    I create a new ccxml using CCS for RM48L952 device.

    <?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 XDS110 USB Debug Probe_0">
            <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
            <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
                <instance XML_version="1.2" href="drivers/tixds510icepick_c.xml" id="drivers" xml="tixds510icepick_c.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
                <instance XML_version="1.2" href="drivers/tixds510cortexR.xml" id="drivers" xml="tixds510cortexR.xml" xmlpath="drivers"/>
                <property Type="choicelist" Value="1" id="The JTAG TCLK Frequency (MHz)">
                    <choice Name="Fixed with user specified value" value="SPECIFIC">
                        <property Type="stringfield" Value="1.25MHz" id="-- Enter a value from 100.0kHz to 2.5MHz"/>
                    </choice>
                </property>
                <platform XML_version="1.2" id="platform_0">
                    <instance XML_version="1.2" desc="RM48L952_0" href="devices/rm48l952.xml" id="RM48L952_0" xml="rm48l952.xml" xmlpath="devices"/>
                </platform>
            </connection>
        </configuration>
    </configurations>

    I try again Target Configuration -> Launch Selected Configuration.

    Then, CortexR4 click and connect button on the toolbar.

    IcePick, Dap and CortexR4 connected.

    But, can't load .out on the CCS or uniFalsh because (Error -242 @ 0x0), (Error -1170 @0x0).

    Please note, Test Connection for XDS110 was OK.

    And, There was no problem in using XDS200.

    Please again check.

    Regards,

    JY Kim.

  • Did you use the same out file and same flash settings for xds110 and xds200?

  • Hi Wang,

    Yes, samed.

    Debug flash setting for XDS110 as following.

    It samed XDS200.

    Regards,

    JY Kim.

  • Hello Wang,

    I repeat,

    Program downloading OK in using XDS100 and XDS200.

    Only XDS110 cannot downloading the program.

    I don't know what problem.

    Can someone help me with this problem?

    Regards,

    JY Kim.

  • I don't know what is wrong with your xds110 debugger. Can you upgrade the firmware of your xds110 debugger?

    You can download the latest driver from ti.com. Or you can reprogram the firmware using xdsdfu which is located ccsxx/ccs_base/common/uscif/xds110.

    In CMD window, type xdsdfu -h to learn how to use it:

    xdsdfu -f firmwarexxx.bin -r

    The firmware is in the same folder.

  • Hello Wang,

    Yes, it is the latest version.

    Have you tried downloading the program using XDS110 on RM48L952?
    Regards,
    JY Kim.
  • Are you using a TI evaluation board for this, or did you design your own board with an XDS110 emulator on it?

    The TI evaluation boards for RM48x do not include an XDS110 emulator.

  • Hello Wang,

    I designed my own board.
    So far, XDS200 has been used.
    However, because the XDS200 is expensive, it was intended to use the XDS110.
    Regards,
    JY Kim.
  • Hi Kim,

    Have you make the xds110 work?

  • Hi Wang,

    It is not the xds110 working yet.

    Please tell me the solution.

    Regards,

    JY Kim.

  • Does your xds110 debugger work on other board? Does your xds110 debugger on TI HDK or launchpad? Is the nTRST signal connected to GND on your target board? xds110 doesn't use this pin, but this pin should be pulled low.

  • Hi Wang,

    I connected the nTRST(pin number 2) signal to GND on my target board.

    But, Test Connection error occur(-233 SC_ERR_PATH_BROKEN) on Target Configuration.

    And, IcePick: Error connecting to the target: (Error -2131 @ 0x0) occurrence when running debug.

    Please check.

    Thanks and Regards,

    JY Kim.

  • Hi JY,

    nTRST should not be connected to GND directly. A resistor (for example 2.2Kohms) is required. 

  • Hi Wang,

    I tried again your recommend.

    My targer board pull-down 2.2k at nTRST.

    The same error occurs( CortexR4: Error: (Error -242 @ 0x0) and CortexR4: Error: (Error -1170 @ 0x0) ).

    Note that, nTRST of RM48L952 is internal pull-down(default pull state). Refer to the datasheet.

    Also, i checked nTRST pull-down resister in xds110.

    I think there should be another soultion.

    Thanks and Regards,

    JY Kim.

  • Hi Wang,

    A new Error has occurred.

    That was 'Could not read register CPSR: target is not connected'.

    Please check error message.

    Thanks & Regards,

    JY Kim.