• State Resolved
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 97 views
  • Users 0 members are here
Support feedback
Options
Options
Related

LAUNCHXL-F280049C: Trouble Halting Target CPU: (Error -1156 @ 0x0) whenUniFlash connects to LAUNCHXL-F280049C

Vladimir Pavlovic
Prodigy 50 points
Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: UNIFLASH, , TMS320F280049C

Tool/software:

Hi,

Very often when connecting to the LAUNCHXL-F280049C with UniFlash tool, I got the error:

" Texas Instruments XDS110 USB Debug Probe/C28xx_CPU1
Trouble Halting Target CPU: (Error -1156 @ 0x0) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 20.1.0.3372)"

After that, i got a pop-up window with options to Cancel, Retry it (yes), or not (no).

If I press the reset button roughly at the same time as the YES, the connection is established.

After that I can work normally, which in mine case means that I can unlock the device.

It seems that if the device is not locked, this error happens but less frequently.

My concern is that the connection to the TMS320F280049C may be flaky and get in a way of programming it.

The device is out of the box, and only the XDS110 driver is updated as per the request. UniFlash is version 9.1.

The similar error happens with the code composer studio.

Nothing is changed on the development kit board, which includes S2 switch.

Regards,

Vlad Pavlovic

  • 0
    TI__Genius 13795 points

    Hi Vlad,

    The method you are using is one workaround. Is this issue resolved by erasing the entire flash of the device? Some possible steps to take:

    • View ->Target configurations
    • Right click on target config -> launch selected configuration
    • In Debug perspective -> Menu Run -> Connect Target
    • Then setting a breakpoint at 0x80000 (in disassembly view)
    • Free run until breakpoint is hit
    • Menu Tools -> On-Chip Flash -> Erase entire flash
    • After erasing -> Stop debug -> cycle power of board

    Other things to check would be the ccxml file that is being used to connect to the device (if you could show the settings for it).

    Thanks and regards,

    Charles

  • 0 in reply to Charles Roberson
    Prodigy 50 points

    Thanks Charles. 

    Yes, after the erasure of the whole flash the problem disappeared.

    Here is the content of the ccxml file that is used;

    ?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <configurations XML_version="1.2" id="configurations_0">
    <configuration XML_version="1.2" id="configuration_0">
    <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
    <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe">

    <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/tixds510c28x.xml" id="drivers" xml="tixds510c28x.xml" xmlpath="drivers"/>

    <instance XML_version="1.2" href="drivers/tixds510cla2.xml" id="drivers" xml="tixds510cla2.xml" xmlpath="drivers"/>

    <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>


    <property Type="choicelist" id="dataFileRequired" desc="Board Data File" Value="0">
    <choice value="auto generate with extra config file">
    <property Type="filepathfield" Value="0" id="dataFileExtraConfig" desc="Extra Config File" Extensions="Config Files (*.dat)|*.dat|All Files (*.*)|*.*||"/>
    </choice>
    <choice value="specify custom">
    <property Type="filepathfield" Value="0" id="dataFile" desc="Custom Board.dat file" Extensions="Config Files (*.dat)|*.dat|All Files (*.*)|*.*||"/>
    </choice>
    </property>

    <property id="Power Selection" Type="choicelist" Value="0">
    <choice Name="Target supplied power" value="0">
    <property id="Voltage Selection" Type="choicelist" Value="0">
    <choice Name="User specified value" value="1">
    <property id="Voltage Level" Type="stringfield" Value="0"/>
    </choice>
    </property>
    </choice>
    <choice Name="Probe supplied power" value="1">
    <property id="Voltage Level" Type="stringfield" Value="0"/>
    </choice>
    </property>

    <property id="SWD Mode Settings" desc="JTAG / SWD / cJTAG Mode" Type="choicelist" Value="4">
    <choice Name="cJTAG (1149.7) 2-pin advanced modes" value="enable">
    <property id="XDS110 Aux Port" desc="Auxiliary COM Port Connection" Type="choicelist" Value="1"/>
    </choice>
    </property>

    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="TMS320F280049C" href="devices/f280049c.xml" id="TMS320F280049C" xml="f280049c.xml" xmlpath="devices"/>
    </platform>
    </connection>
    </configuration>
    </configurations>

  • +1 in reply to Vladimir Pavlovic
    TI__Genius 13795 points

    Ok that's great. Will consider this problem resolved for now.

    Regards,

    Charles

  • 0 in reply to Charles Roberson
    Prodigy 50 points

    Sure, i will look into the application itself and the booting of it. Thanks Charles. That was a quick answer.