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.

msp432 problem with XDS110 and firmware version 2.2.4.2

Making use of the CCS cloud on mac osx and on linux, the msp432 xds110 firmware was upgraded to the 2.2.4.2 version. Afterwards, I have tried to use it with CCS, and it was imposible to connect with the debugger. I tried to downgrade it to 2.2.4.0 using the firmware.bin available in the CCS, but it stills stays in 2.2.4.2.

Is there a solution to downgrade the firmware, or upgrade the CCS driver?

Thanks in advance,

Jose M.

10 Replies

  • Guru 106985 points
    Jose,

    I am able to downgrade the firmware ok on Windows.
    xdsdfu.exe -m
    xdsdfu.exe -f firmware.bin -r

    I will give it a try on MacOS and see what happens.

    John

     


    If my reply answers your question please click the "This resolved my issue" button

  • Guru 106985 points

    In reply to JohnS:

    I am able to downgrade to 2.2.4.1 on MacOS as well.

    Attached is the firmware file I am using.  I have run ./xdsdfu -e afterwards to make sure the firmware was programmed.

    firmware2241.zip

    What error message do you get in CCS?

    Regards,

    John

     


    If my reply answers your question please click the "This resolved my issue" button

  • In reply to JohnS:

    The error that I get is that I have to upgrade manually the using the xdsdfu tool.

    When I program with the tool using the firmware available in the CCS 6.1.1 and check it with the xdsdfu -e, I always get the version 2.2.4.2. I will try with this new firmware.bin to see if the situation changes.

    Thanks for your help,

    Jose M.

  • Guru 106985 points

    In reply to jmgc:

    I had an issue with one of my MSP432 LaunchPads where it was giving me a similar message. It turned out that I had it in firmware update mode and that prevented CCS / CCS Cloud from connecting to it. I had to power cycle the board to get it back into the proper state. Running the utility with the -m, with no update/reset afterwards was what got me into that state.

     


    If my reply answers your question please click the "This resolved my issue" button

  • In reply to JohnS:

    It seems that it is necessary to downgrade the firmware to the version 2.2.4.0:

    Answer on Linux CCS v 6.1.1.

    Error connecting to the target:
    (Error -260 @ 0x0)
    An attempt to connect to the XDS110 failed.
    The cause may be one or more of: invalid firmware update, invalid
    XDS110 serial number, or faulty USB connection. The firmware and
    serial number may be updated using the xdsdfu utility found in
    the .../ccs_base/common/uscif/xds110 directory of your
    installation. View the ReadMe.txt file there for instructions.
    (Emulation package 6.0.14.5)

    The console shows that there is one device with version 2.2.4.1:

    [xds110]$ ./xdsdfu -e

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 with CMSIS-DAP
    Version: 2.2.4.1
    Manufacturer: Texas Instruments
    Serial Num: 00000000
    Mode: Runtime

    Found 1 device.

    Following the instructions with the firmware available in CCSv6.1.1

    [xds110]$ ./xdsdfu -m

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 with CMSIS-DAP
    Version: 2.2.4.1
    Manufacturer: Texas Instruments
    Serial Num: 00000000
    Mode: Runtime

    Switching device into DFU mode.
    [xds110]$ ./xdsdfu -e

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x1cbe PID: 0x00ff
    Device Name: Tiva Device Firmware Update
    Manufacturer: Texas Instruments Incorporated
    Serial Num: 00000000
    Mode: DFU

    Found 1 device.
    [xds110]$ ./xdsdfu -f firmware.bin -r

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...

    Downloading firmware.bin to device...
    [xds110]$ ./xdsdfu -e

    USB Device Firmware Upgrade Utility
    Copyright (c) 2008-2015 Texas Instruments Incorporated. All rights reserved.

    Scanning USB buses for supported XDS110 devices...


    <<<< Device 0 >>>>

    VID: 0x0451 PID: 0xbef3
    Device Name: XDS110 with CMSIS-DAP
    Version: 2.2.4.2
    Manufacturer: Texas Instruments
    Serial Num: 00000000
    Mode: Runtime

    Found 1 device.

  • Guru 106985 points

    In reply to jmgc:

    I don't think downgrading the firmware manually to 2.2.4.0 is going to work.  CCS is just going to force you to update it to 2.2.4.2 when you launch the debugger.

    I get that exact same error message you are seeing when my XDS110 is in DFU mode instead of runtime mode.

    If I have it in runtime mode then CCS launches fine (Win/Lin/Mac).

    The VID and PID of yours are the same as mine.

    USB Device Firmware Upgrade Utility

    Copyright (c) 2008-2015 Texas Instruments Incorporated.  All rights reserved.

    Scanning USB buses for supported XDS110 devices...

    <<<< Device 0 >>>>

    VID: 0x0451    PID: 0xbef3

    Device Name:   XDS110 with CMSIS-DAP

    Version:       2.2.4.2

    Manufacturer:  Texas Instruments

    Serial Num:    00000000

    Mode:          Runtime

    Found 1 device.

    Maybe your 2242 firmware files is corrupted.  Here is a copy of mine.  Try updating with this one.  Then run the utility with -e to make sure it is in runtime mode and then try connecting with CCS.  If that doesn't work I am going to need to pull in someone else to try to get to the bottom of what is going on.

    firmware2242.zip

     


    If my reply answers your question please click the "This resolved my issue" button

  • In reply to JohnS:

    I have made a diff with the firmware I've got with CCS 6.1.1 on Linux and both are equal.

    Also, a college has made an upgrade of his computer to windows 10, and now he is having similar problems, and this has also make me remind that some students have had also problems with windows 10.

    Thanks in advance for your help,

    Jose M.
  • Guru 106985 points

    In reply to jmgc:

    Jose,

    I am going to pull in an expert on the 110. In the mean time lets enable some logging. Go to Help -> CCS Support and enable the Debug Server Log. Also if you could enable logging in the debug probe stack following these instructions that would be great: processors.wiki.ti.com/.../Troubleshooting_CCSv6

    I don't think there will be much in the debug server log other than the error message but maybe the other logs might have something for the expert to look at.

    Regards,
    John

     


    If my reply answers your question please click the "This resolved my issue" button

  • In reply to JohnS:

    The debug software will not allow connection to a different version of the firmware than was packaged with it. If you downgrade the firmware, then the auto-update feature will attempt to update to the correct version.  This would be why you see that the XDS110 reverts to version 2.2.4.2 of the firmware each time.

    At the moment, I'm not exactly sure what might be wrong.  The XDS110 is able to communicate over the USB connection, otherwise the update and the xdsdfu utlity would not be able to work.  The -m switch is executed by sending a message over the debug endpoint, so that endpoint is functional, or at least is receiving commands. So many of the common problems with OS drivers, permissions, or the like aren't the problem here.

    Can you supply some more information?  Please upload the .ccxml file you are using.  And trying using the Test Connection button from CCS and post the results.  I don't expect it to work, but it will include more info that might give a hint as to what is happening.

  • In reply to Edward Fewell:

    Dear Edward,

    I do not know how to upload a file in e2e. I have just copied both files, the ccdxml and the resulting log from the test button.

    In any case, my guess is that for some reason, the library that is available in the CCS6.1.1 is not compatible with the firmware 2.2.4.2. I think the library is older than the firmware, so the firmware was upgraded but not the library. So if the firmware is upgraded in another computer, CCS is not able to return to the correct firmware because the one available is too new.

    Best

    ----------------------------------------------------------------------------------------------------

    <?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/tixds510cs_dap.xml" id="drivers" xml="tixds510cs_dap.xml" xmlpath="drivers"/>
    <instance XML_version="1.2" href="drivers/tixds510cortexM.xml" id="drivers" xml="tixds510cortexM.xml" xmlpath="drivers"/>
    <platform XML_version="1.2" id="platform_0">
    <instance XML_version="1.2" desc="MSP432P401R_0" href="devices/msp432p401r.xml" id="MSP432P401R_0" xml="msp432p401r.xml" xmlpath="devices"/>
    </platform>
    </connection>
    </configuration>
    </configurations>

    ---------------------------------------------------------------------------------------------------

    [Start: Texas Instruments XDS110 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)]------------------------------------

    /home/chema/.ti/ti/0/0/BrdDat/testBoard.dat

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

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'libjioxds110.so'.
    The library build date was 'Sep 4 2015'.
    The library build time was '21:51:07'.
    The library package version is '6.0.14.5'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.

    An error occurred while hard 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 '-260' (0xfffffefc).
    The title is 'SC_ERR_XDS110_OPEN'.

    The explanation is:
    An attempt to connect to the XDS110 failed.
    The cause may be one or more of: invalid firmware update, invalid
    XDS110 serial number, or faulty USB connection. The firmware and
    serial number may be updated using the xdsdfu utility found in
    the .../ccs_base/common/uscif/xds110 directory of your
    installation. View the ReadMe.txt file there for instructions.

    [End: Texas Instruments XDS110 USB Debug Probe_0]

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.