• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 54 subscribers
  • Views 839 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/LAUNCHXL-CC1312R1: Launchpad not detected after firmware update

Jan Ingwer Baer
Expert 1205 points
Part Number: LAUNCHXL-CC1312R1


Tool/software: Code Composer Studio

After the SensorControllerStudio updated the Firmware of the LaunchpadXL-CC1312R1 it is not longer  recognized by SCS, CCS and SmartRF-Studio.

After connection the launchpad is listed in the Windows Devicemanager as

USB-Verbundgerät :
  • HID,
  • XDS110 Class Application/User UART (COM4)
  • XDS100 Class Auxiliary Port (COM3)
  • XDS Class Data Port
  • CDS Class Debug Probe

and in USB-Device Tree Viewer :

USB-Verbundgerät - HID, COM3, COM4
XDS110 (02.03.00.18) Embed with CMSIS-DAP

After some time i get an error from Windows : Device is not recognized

Windows has stopped this device because it has reported problems. (Code 43)

Fehler bei einer Anforderung des USB-Gerätedeskriptors.

The xdsdfu utility does not find a supported XDS110 device.

How to unbrick the Launchpad? Any chance to set the Launchpad to dfu-mode?

SCS : Version 2.5.0.84 with patches 1,2,3

CCS :  Version: 9.2.0.00013 

OS : Win 10 64bit

  • 0
    Expert 1205 points

    Even after setting the device to dfu-mode with grounding the TDO pin it is not recognized by xdsdfu.

    Then i tried to use another PC with older Version of CCS (9.0.1) installed. With this older version xdsdfu found the device and i could flash the firmware version 2.3.0.18.

    But this is not recognized by the CCS9.2 tools. After transfering the firmware file of CCS 9.2 to the other PC i could flash the firmware version 3.0.0.5. Now the launchpad is again accepted from CCS 9.2 and i can start the debugger.

    But SensorController-Studio wants to update the debugger firmware. Because the last firmware update from SCS made the debugger unusable i will not do it again.

  • 0 in reply to Jan Ingwer Baer
    TI__Guru**** 171309 points

    Hi,

    Thanks for the detailed post. 

    Jan Ingwer Baer said:
    After transfering the firmware file of CCS 9.2 to the other PC i could flash the firmware version 3.0.0.5. Now the launchpad is again accepted from CCS 9.2 and i can start the debugger.

    I am not sure if I understood correctly; did the launchpad start to be acknowledged by the host with the newer software after updating the firmware on the "older" host? 

    If so, I suspect that your "newer" host may have a problem with the install of the DFU device drivers of the TM4C device present on the XDS110 Debug Probe of your launchpad. This device driver is instantiated when the probe is put in "manual" (DFU) mode and a screenshot is shown in the section "Flashing the bootloader" of the XDS110 page below. 

    https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html 

    These drivers are automatically installed with CCS is installed, but perhaps something got corrupt in your system. You can try to reinstall and point to the directory C:\ti\ccs920\ccs\ccs_base\emulation\drivers\stellaris\icdi

    An exact root cause for why this got corrupt is hard to explain, but if the issue persists even after installing the derivers, I would start suspecting a USB port with problems, which could be either logical (a faulty controller) or mechanical (flimsy USB socket, etc.) - that is assuming you are using the same USB cable with the two hosts, otherwise keep the cable as a possible root cause as well. 

    This would explain the inability of updating the probe only on one host, but otherwise the probe works well for debugging UART, etc. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Expert 1205 points

    Hi,

    all the trouble started because CCS and SCS wants different versions of the Launchpad-FW. And each time i changed from CCS to SCS for debugging/Task-testing and back to CCS both tools started to 'update' the launchpad firmware. CCS programmed FW-version 03.00.00.05 and SCS programmed FW-Version 02.03.00.18.

    And after some times switch the FW-version forth and back it stopped working (see previous post). The device is shown in the Windows Devicemanager but not recognized by TI-tools. The instructions for (Re-)Flashing the XDS did not worked because it could not detect the device.

    The only way to re-animate the Launchpad was to use the tools from the older CCS 9.0.1 version together with the instructions from the emu_xds110.html document.

    The root of the problem was that SCS wants a FW-version different then that from CCS. 

    How to unify the FW-version between the different TI-tools (CodeCompoer-Studio, SensorController-Studio, SmartRF-Studio) to avoid the same trouble in the future?

    Is there a simple way to change the wanted FW-version in the configuration of SensorController-Studio and SmartRF-Studio?

    Regards

    Jan

  • 0 in reply to Jan Ingwer Baer
    TI__Guru**** 171309 points

    Jan,

    Jan Ingwer Baer said:
    all the trouble started because CCS and SCS wants different versions of the Launchpad-FW.

    Yes, unfortunately this is a transitional problem when the various products are out of sync. Details about the rules for re-flashing are shown on this post. 

    Jan Ingwer Baer said:
    Is there a simple way to change the wanted FW-version in the configuration of SensorController-Studio and SmartRF-Studio?

    Unfortunately no. Until a new software release of the SensorController Studio and SmartRF Studio are released, the firmware dance continues. 

    You could potentially hack your way into circumventing the older firmware installed with the tool by replacing the contents of the subdirectories "emulation" and "common" of the offending tools with the ones provided in CCS (these are under Sensor Controller Studio\drivers or SmartRF Tools\SmartRF Studio 7\config\xds). There is also a possibility that the only thing needed is to replace the file <firmware.bin> (located in the directory Sensor Controller Studio\drivers\common\uscif\xds110 or SmartRF Tools\SmartRF Studio 7\config\xds\common\uscif\xds110)

    Try this at your own risk. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Expert 1205 points

    Replacing the directory 

    Sensor Controller Studio\drivers\common\uscif

    with the directory 

    SmartRF Studio 7\config\xds\common\uscif

    from latest version (2.15.0) of SmartRF Studio seems to work.

    No more request to update/downgrade the Launchpad-FW and 'Task Testing' in SCS works.

    Using the uscif-directory from CCS 9.2 does not work. 'Task Testing' can not connect to debugger.

    Thank you for this hint. 

    I think TI should find a way to reduce the coupling between the different tool versions and the board-FW-versions.

    Regards

    Jan