CCS/TMS320F2812: Uniflash 5.1 - Error -1015: Device is not responding to the request.

James Van Volkenburgh1

Other Parts Discussed in Thread: UNIFLASH

Thanks for the help. I've generated a new standalone package and now longer have the FlashKey0 error...

However, I am now running into another error.

Connecting...
fatal: C28xx: Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request. Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.2.0.00004)
Failed: Operation was aborted

I get this same error when I click the "Unlock" button within Uniflash before creating the standalone command line package - I have verified the Keys are correct.

Probable Issue: Our board has two TMS32f2812 DSPs on it, and we need to flash one of them - I believe this is why we had references to a XDS510; we were attempting to use the f2812.ccxml that originally allowed us to use a XDS510 to flash to one of the two DSPs.

Thoughts?

over 5 years ago

0 James Van Volkenburgh1 over 5 years ago

Prodigy 60 points

We are making progress. We believe we have found a method to flash to the board (with the two DSPs). We use Code Composer Studio to create two .ccxml files, then create New Sessions in Uniflash using those generated .ccxml files. We are technically successful in flashing the board, but it doesn't appear to be flashing the correct DSPs...

OUR THOUGHTS:
We aren't pointing to the correct DSPs; we are either pointing to the same DSP with both .ccxml files or we are pointing to opposite DSPs.

OUR QUESTIONS:
- How do we properly target the correct DSP? - something that has to do with the "choicelist" bypass [value = 0 or 1]?
- What is the .ccxml syntax?

The first .ccxml file that should target the first DSP.

<?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 Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Debug Probe_0" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Debug Probe_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds100v2c28x.xml" id="drivers" xml="tixds100v2c28x.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320F2812_0" href="devices/f2812.xml" id="TMS320F2812_0" xml="f2812.xml" xmlpath="devices"/>
            <instance XML_version="1.2" desc="RXFC" href="devices/f2812.xml" id="RXFC" xml="f2812.xml" xmlpath="devices"/>
                <device HW_revision="1" XML_version="1.2" description="" id="RXFC" partnum="TMS320F2812">
                    <cpu HW_revision="1.0" XML_version="1.2" desc="C28xx_0" description="CPU" id="C2800" isa="TMS320C28XX">
                        <property Type="choicelist" Value="1" id="bypass"/>
                    </cpu>
                </device>
                <device HW_revision="1" XML_version="1.2" desc="RXRF" description="" id="TMS320F2812_0" partnum="TMS320F2812"/>
            </platform>
        </connection>
    </configuration>
</configurations>

The second .ccxml file that should target the second DSP

<?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 Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Debug Probe_0" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Debug Probe_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds100v2c28x.xml" id="drivers" xml="tixds100v2c28x.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
            <instance XML_version="1.2" desc="RXRF" href="devices/f2812.xml" id="RXRF" xml="f2812.xml" xmlpath="devices"/>
                <instance XML_version="1.2" desc="RXFC" href="devices/f2812.xml" id="RXFC" xml="f2812.xml" xmlpath="devices"/>
                <device HW_revision="1" XML_version="1.2" description="" id="RXFC" partnum="TMS320F2812" simulation="no">
                    <cpu HW_revision="1.0" XML_version="1.2" desc="C28xx_0" description="CPU" deviceSim="false" id="C2800" isa="TMS320C28XX"/>
                </device>
                <device HW_revision="1" XML_version="1.2" description="" id="RXRF" partnum="TMS320F2812" simulation="no">
                    <cpu HW_revision="1.0" XML_version="1.2" desc="C28xx" description="CPU" deviceSim="false" id="C2800" isa="TMS320C28XX">
                        <property Type="choicelist" Value="1" id="bypass"/>
                    </cpu>
                </device>
            </platform>
        </connection>
    </configuration>
</configurations>

0 Ki over 5 years ago in reply to James Van Volkenburgh1

TI__Guru**** 464031 points

Hi James,

You got the right idea and your ccxml files look good to me. You are correctly using the bypass option (the first ccxml bypasses the second 28x on the scan chain while the second ccxml file bypasses the first 28x). The '1" value for the bypass simply indicates that you wish to enable the bypass for that CPU.

When you use those ccxml files to launch a debug session in CCS, does it start up a debug session for the correct CPU?

0 Ki over 5 years ago in reply to Ki

TI__Guru**** 464031 points

Hi James,

Just following up to see if the issue still persists and if you have any response to my last question in my previous post.

Thanks

0 James Van Volkenburgh1 over 5 years ago in reply to Ki

Prodigy 60 points

Howdy, Ki!

Our issue has been solved and we are now succesfully able to program each DSP on the board without any issues.

It was only a matter of tinkering with the .ccxml files that got it to work for us.

Thanks a ton for your help!

0 Ki over 5 years ago in reply to James Van Volkenburgh1

TI__Guru**** 464031 points

Great to hear you resolve the issue. Thanks for the update!

Code Composer Studio™︎

Code Composer Studio forum

CCS/TMS320F2812: Uniflash 5.1 - Error -1015: Device is not responding to the request.