• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 151 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.

LP-CC2652RB: Bricked XDS110

Julien Devillers
Prodigy 40 points
Part Number: LP-CC2652RB
Other Parts Discussed in Thread: CC2652RB, UNIFLASH, , TM4C1294NCPDT, MSP432E401Y

Tool/software:

Hello,

I'm evaluating CC2652RB with its launchpad.

I wanted to install the sniffer firmware.

I did a first attempt with flash programmer 2. It had to update the probe firmware and it fails (probe firmware update, not CC2652 firmware update)

I tried with uniflash. Same result.

I tried xdsdfu. As a newbee, I typed only "xdsdfu.exe", without any parameters. Of course it fails showing the list of parameters.

I tried with uniflash again. Same result.

From that moment, the board never starts again. No led is lighted. I tried to plug/unplug, change the cable, change the usb port without any more success.

I read this topic:  CC2640R2F: Bricked XDS110 Debug Probe 

Now, in my case, I got this result for enumeration:

C:\ti\uniflash_9.2.0\deskdb\content\TICloudAgent\win\ccs_base\common\uscif\xds110> .\xdsdfu.exe -e

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

Scanning USB buses for supported XDS110 devices...


Found 0 devices.

What should I do with this 50 euros beautiful red board that I was unable to use a single time?  :(

Have a nice day.

Julien

  • 0
    TI__Guru**** 218357 points

    Hello Julien,

    From where did you procure the LP-CC2652RB?  Make sure to use the USB cable which came with the LaunchPad.  What is your OS and have you tried any other computers?  What is it emulating as in your computer's Device Manager (should be two COM Ports)?  If no LEDs are active on the XDS110 side then the bootloader is likely damaged and needs to be re-flashed.  Here are the relevant instructions.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Prodigy 40 points

    Hello Ryan,

    Thanks for your answer.

    LP-CC2652RB is from Mouser. 

    Win10.

    Tried with the provided cable too.

    Nothing emulates in device manager.

    Since, I switched to linux. I succeeded in flashing boot_loader.bin using a tagConnect and a JLink probe. I based my experiments on 

    "XDS110SupportReadme.pdf" file.

    J-Link>loadfile /home/ju/tools/ti/uniflash_9.2.0/uniflash_9.2.0/deskdb/content/TICloudAgent/linux/ccs_base/common/uscif/xds110/boot_loader.bin, 0
'loadfile': Performing implicit reset & halt of MCU.
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading file [/home/ju/tools/ti/uniflash_9.2.0/uniflash_9.2.0/deskdb/content/TICloudAgent/linux/ccs_base/common/uscif/xds110/boot_loader.bin]...
J-Link: Flash download: Bank 0 @ 0x00000000: 1 range affected (16384 bytes)
J-Link: Flash download: Total: 0.384s (Prepare: 0.136s, Compare: 0.013s, Erase: 0.039s, Program & Verify: 0.170s, Restore: 0.024s)
J-Link: Flash download: Program & Verify speed: 94 KB/s
O.K.
J-Link>exit

    Device is still not recognized by xdsdfu, nor as a USB device. 

    I still wanted to try to upload firmware_3.0.0.38.bin but the address is not specified. I downloaded the current firmware and saw that, beside the bootloader at address 0, there was data starting at address 8192. So I uploaded firmware_3.0.0.38.bin at this address. But nothing changed...

    I read your instructions, it looks similar to what I did but with differents tools.

    Both XDS110SupportReadMe.pdf and your instructions deal with TM4C1294NCPDT while my board is populated with an MSP432E401Y. Is it the same binary?

    Thanks

    Julien

  • 0 in reply to Julien Devillers
    Prodigy 40 points

    Correction, I did a mistake. Firmware seems to be at 16384 and not 8192 but the result is the same with those values.

  • +1 in reply to Julien Devillers
    TI__Guru**** 218357 points
    Julien Devillers said:

    deal with TM4C1294NCPDT while my board is populated with an MSP432E401Y. Is it the same binary?

    Same MCU Arm core and pin map, the binary is compatible.

    I've done this procedure in the past and do not recall needed to provide an address.  Grounding TDO before powering the device is a crucial manual step.

    Regards,
    Ryan