Other Parts Discussed in Thread: CC1312R, UNIFLASH, SEGGER
Hi
I have just updated my debugger software and now cant get it to work, please see attached error.
Regards
David
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.
Hi
I have just updated my debugger software and now cant get it to work, please see attached error.
Regards
David
Hi
I failed to mention that the problem I have is with the 2 new CC1312R launchpads not the old one's, when I looked at the device drivers I notice there are only 2 entry's in the device table on the old boards (these work) when I try the new boards I get 4 entry's in the device table please see attached, can someone please assist.
Regards
David
Hi David,
Please refer to this E2E thread: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/887212/faq-launchxl-cc1352p-debugger-firmware-upgrade-failure/3281522#3281522
Regards,
Nikolaj
Hi
These are brand new boards never used and all have the same problem, As I explained the older boards I have, work fine ,these new ones directly out of the box , none work, if there is a problem then I can send them back. In the link you have sent it mentions not seeing the boards? but as shown in the device table it shows 4 connections not 2. I have also tried to use the command prompt but keep getting directory errors although the directory is correct, surely you don't expect people having brought new boards to go through this.
I really need to get these working can you please get back asap.
Regards
David
Hi
I have now tried to update the firmware file according to the PDF please see attached
As you can see I can put it into DFU mode but as soon as I add the next line it tells me its not in DFU mode???????????
Regards
David
Hi David,
I understand that this is not something you want to experience when receiving a new board. Unfortunately upgrading the firmware on the XDS110 can sometimes fail, as indicated in my previously shared E2E thread.
From your screen shot it definitely looks like the device is in a wrong state (most likely as a result of the failed firmware upgrade) since device name, manufacturer and serial number are unknown.
Can you please try to follow the instructions, for installing the bootloader and upgrading the firmware, in the E2E thread linked to earlier? This is the best advice we have for you.
Regards,
Nikolaj
HI Nikolaj
Do I need to solder wires to the board as in your previous link. Can you please point to the section you wish me to follow.
Regards
David
Hi David,
Yes, I will suggest following the "Installing Bootloader" section followed by "Upgrading firmware" section of the post marked as resolved. I assume that you do not have a 10 pin TAGCONNECT connector, so you will have to solder wires to the corresponding pins.
Regards,
Nikolaj
Hi Nikolaj
I have brought a 10 pin TAGCONNECT but it only comes with the larger header (please see attached) so I am unable to connect to the programmer on the launch pad and it seems you cant use a different programmer with uniflash IE my J-Link Segger so can you please send me details on how to do this with the Segger programmer.
Thank you
David
Hi David,
Can you please try to find a way to connect an XDS-110 to the TAGCONNECT? Alternatively, you can try to use the Segger forum (https://forum.segger.com/), if you want to use your J-Link Segger.
Regards,
Nikolaj