Hi,team:
We are debugging the CC2340R5 evaluation board, maybe we burned the wrong file into the chip using XDS110, and now when burning the program, it says that the chip cannot be connected, is there any way to restart the chip? thank you.
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.
Hello Ixy,
I hope you are doing well. Have you tried using Uniflash (UNIFLASH Software programming tool | TI.com) to load or manually erase the device? Sometimes when the device has issues with CCS using Uniflash can help!
Here is a link to the QuickStart guide for Uniflash UniFlash Quick Start Guide (ti.com).
Thanks,
Alex F
Hello Alex Fager ,
Thank you for your reply。I overerased the chip with UNIFLASH as suggested,But the following error will still be reported。Is there any other way to restart the evaluation board?thanks a lot。
Hello Ixy,
So lets try another setting in UniFlash, called "Read Device Info" if successful it should show something like the following (this confirms that UniFlash can actually detect your board):
Next try a "perform blank check" which if the device is programed will show the output:
Next I did "Chip Erase" into another "perform blank check" which confirms device is blank:
You should now try to re-load the project.
From your error the XDS may be acting irregularly, do you happen to have another debugger board on hand to test with? you can alternately try to program/debug the device with another boards XDS through the 10-pin debug connector (LP-XDS110ET Quick Start Guide (ti.com)).
Thanks,
Alex F
Hello Alex Fager ,
Thank you for your reply。I Try it as you suggest,But the following error will still be reported。
In fact, we can burn the program normally before burning the.out file, but burn the program can not burn properly after trying to burn the.out file。Is the chip broken?thanks a lot。
Hello Ixy,
Have you experienced this error, with more than 1 XDS.
To confirm you can perform a chip erase, but after burning the program one time you cannot burn another program after and need to perform another chip erase to burn the device with another program.
Has your XDS been updated already; CCS prompts you to update the XDS when connected and flashing a device.
Thanks,
Alex F
Hello Alex Fager ,
Thank you for your reply。First of all, I just used an XDS burner。Then, when I erase the chip the way you suggested, I get an error。Then, I will report the above error when I erase the chip or read the chip information in the way you suggested。Now that we can't identify the chip, what do we do about it?In addition, other chips can be successfully burned with the XDS burner。thanks a lot。
Hello Ixy,
While the error reporting seems to indicate an issue with the XDS, the issue you describe seems instead to be an issue with the .out file you have flashed. If the .out file flashed (burned) to the device is configured as debug locked, UniFlash would need an authorization password. However, if we do not know the password and cannot perform a chip erase then there is not much we can do to recover the device.
Do you happen to know more about the .out file you had flashed on the device?
Thanks,
Alex F
Hello Alex Fager ,
Thank you for your reply。We generated the.out file after the CCS compiler compiled the official routine, and we wanted to know how to do a forced restart of the chip。thanks a lot。
Hello Ixy,
CCS compiler compiled the official routine
Can you expand on what you mean here? We have many configurable syscfg settings; the one we are interested in looking at is in the Debug Configuration category:
-What SDK and example project did you use initially?
maybe we burned the wrong file into the chip using XDS110
Are you aware if the file you burned was any debug locked project, or if during flashing you disconnected the board/XDS? The current error somewhat points to the device being locked in a debug locked state or having some issue during flashing. If we cannot read/chip erase the device then there is not much we can do to recover the device.
Thanks,
Alex F
Hello Alex Fager ,
Thank you for your reply。Is to burn the general routine, should be burning the wrong file and lead to the chip can not identify, we replace the new chip to operate it。thanks a lot。