• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 279 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.

LAUNCHXL-CC1352R1: Brand new and XDSdfu cant see it

moshe jacobson18
Expert 2210 points
Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi TI

My CC1352R1 launchpad arrived a few days ago and i was wanting to flash my program into it.

Uniflash came up with the message that the XDS firmware needed updating & proceeded to do it.

It then came up with the message " IcePick_C: Error: (Error -592 @ 0x0) The firmware updater encountered an error and could not finish. The firmware download failed to complete on the XDS110. Unplug and re-plug the XDS110, and try again. If the problem remains, try updating the firmware using the xdsdfu utility found in the .../ccs_base/common/uscif/xds110 directory of the installation. View the XDS110SupportReadMe.pdf file there for instructions. (Emulation package 9.10.0.00080)"

on unpluging & repluging power i noticed that the power LED didn't light...plus unflash couldn't see the launchpad (& neither does windows nor XDSDFU).

i then tried the same process on another board that had arrived today...exact same end result! 

TWO faulty boards is unlikely so i suspect the issue may be in the process i'm following....is it possible that uniflash left the boards in the DFU state rather than the run state & if so how do i get it back into the run state if the XDSDFU program cant see them???

i am using uniflash 8.2.0 the CCS is 10.4.....

is there anything i can try & if not, who do i contact to get return the board (bearing in mind i'm in New Zealand).

thanks

[update - for others in a similar position] i managed to fix the problem...ground TDO of the XDS110, connected to power, loaded the new firmware!!

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

and https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

for reference...

  • 0
    TI__Genius 13095 points

    Hi Moshe,

    It's good to hear that you were able to find a solution for the issue you encountered.

    After recovering the board, are you now able to use it in CCS and UniFlash?

    Thanks,

    Ricky

  • 0 in reply to Ricky Lau
    Expert 2210 points

    Hi Ricky

    Yes...it was very odd that it happened in the 1st instance.

    I used the lauchpad TI hardware cad files to trace where the TDO trace went Then i realised what those jtag looking arranged pins on the underside of the launchpad were for!
    Using the TDO pin at the jtag was much easier than trying to short the pin on the actual debger chip.

    interestingly loading & using the debugger firmware in the ccs10.4 XDS utility folder still didnt help and i had to load & use  the debugger firmware in the utility folder in the XDS8.2 folder itself.

    moshe