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.
Part Number: EVMK2H
Tool/software: Code Composer Studio
Hello
We are unable to connect the board EVMK2H Rev4.0 through XDS200 with CCS under Ubuntu 16.04
We narrowed the problem to the software release of JTAG xds200 onboard usb adapter on EVMK2H boards :
It is a 1.0.0.2 release ( and the latest is 1.0.0.8 ). We try to update a board following TI instructions with CCSv7.30.00019 :
http://processors.wiki.ti.com/index.php/XDS200#Updating_the_XDS200_firmware
As the xds200 is connected with an external XDS220 and connected to the host, we try to load the last version of the firmware xds200-firmware-v1008.bin obtained from CCV7\ccs_base\uscif\xds200
Message error was displayed as Load Memory Failed Data Verification failed at address 0x80017ff0 (see attached picture)
The distribution CCSV7 only contains am1808.gel
We tried also the procedure with CCSV6.0.1.00040 with the same results
As we checked , all our EVM2KH XDS200 onboard firmware is 1.0.0.2 and are thus unusable on linux for emulation purposes.
Do you have any procedure to make it possible to connect to the board ?
See picture attached
Regards
Clement
Rahul
Thanks for your proposition, it still works on Windows, to connect the target through XDS200 USB Onboard Debug Probe with the gel file on DSP and ARM.
I didn’t try to make the update XDS Firmware from version 1.0.0.2 to 1.0.0.8 because we already destroyed 2 XDS200 USB Onboard Debug Probe.
Please, Have you another solution to upgrade the update XDS Firmware from version 1.0.0.2 to 1.0.0.8 ?
As the note on the Updating XDS200 firmware indicates the procedure works well with windows machines but some folks have run into issues with Unix/Linux machines when performing the update.
One work around for this is that when CCS tries to connect, it provides an option to ignore the firmware update and proceed. You could choose to use older firmware to avoid impacting more Onboard debug probes.
I have looped in the CCS team to comment on additional options that may be available for you.
Regards,
Rahul