TMS320F28335: xds110 as standalone flash programmer

hi Vamsi

thanks about your help

i have 2 different development envirnonment:

first is my PC. it use a windows 7 system, where i installed CCS6, uniflash 3.4.1 and uniflash 4.1.2

using CCS6 "test connection" i obtain following result

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\w.mei\AppData\Local\TEXASI~1\CCS\
    ti\1\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Jul 27 2016'.
The library build time was '18:31:37'.
The library package version is '6.0.407.3'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End]

using uniflash 3.4.1 i obtain

[09:47:20] Begin Launching session operation.
[09:47:23] Operation Launching session returned. 
[09:47:23] Loaded target configuration from: C:\Users\w.mei\AppData\Local\TEXASI~1\CCS\ti\2\0\/temptargetconfiguration.ccxml
[09:47:23] Settings purged.
[09:47:47] Erasing flash sectors on Core 0 < Texas Instruments XDS110 USB Debug Probe/C28xx > ...
[09:47:47] Begin Erase Flash operation.
[09:47:47] ERROR >> C28xx: Error connecting to the target: (Error -1040 @ 0x0) A firmware update is required for the debug probe. Click the "Update" button to update the firmware and connect to the debug target. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 6.0.83.1) 
[09:48:03] ERROR >> C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.83.1) 
[09:48:18] Operation Erase Flash returned. 

while using uniflash 4.1.2 i obtain

[19/6/2017 09:52:34] [WARNING] C28xx: Warning: A firmware update is required for the debug probe. Click the "Update" button to update the firmware and connect to the debug target. DO NOT UNPLUG THE DEBUG PROBE DURING THE UPDATE. (Emulation package 6.0.576.0)
[19/6/2017 09:52:49] [SUCCESS] C28xx: Warning: The firmware update completed successfully. (Emulation package 6.0.576.0)
[19/6/2017 09:54:23] [SUCCESS] Program Load completed successfully.

summarizing CCS said it's all ok, uniflash 3.4.1 don't work, uniflash 4.1.2 works properly

my objective is to use xds110 in test laboratory where PC use windows XP. there i don't wanto to use CCS (perhaps i can not use ccs6 or superior) and both unflash releases don't work

in sds110 documentation, and uniflash too, there aren't informations about windows XP. they simply say they work with "windows". do you know something about?

regards

Walter

Walter,

As mentioned in UniFlash V4 release notes (processors.wiki.ti.com/.../CCS_UniFlash_v4.1.2_Release_Notes), UniFlash V4 is supported only on Windows 7/8/10 and not on XP.

Regarding the UniFlash V3 CLI error message: Looks like UniFlash V3 CLI is not handling the XDS110 firmware update dialog properly. To fix this, instead of CLI, can you start up the UniFlash V3 GUI and try to connect to the device? This should bring up the firmware update dialog for you. After updating, the firmware should be correct when using CLI.

Thanks and regards,
Vamsi

hi Vamsi,

thanks about v4 information, i lost it

there should be a misunderstanding because i 'm just using GUI interface

firmware update work properly, in fact it try with the following phase in sequence

after firmware updating i disconnected the probe and reconnect it. trying with a new flash erasing i obtain the same error

[09:22:16] Erasing flash sectors on Core 0 < Texas Instruments XDS110 USB Debug Probe/C28xx > ...
[09:22:16] Begin Erase Flash operation.
[09:22:16] ERROR >> C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.83.1) 

[09:22:31] Operation Erase Flash returned.

(these informations appare in "debug console" window)

in your opinion, what does it mean "confirm debug probe configuration and connections"? how can i reset debug probe other than disconnect it from target and usb?

thanks and regards

EDIT

i tried to update xds firmware, and i used that one found in ccsv6 directory

at the end i obtained (xdsdfu -e in terminal) a firmware version 2.3.0.2 but uniflash gui request a firmware update that bring version to 2.2.5.1 (an older one)

why should uniflash require a specific firmware versione without the possibility to update it?

RE-EDIT

perhaps is simply an uniflash update problem. i checked it on windows7 (it works) and i'm trying to do the same with XP. "see you" tomorrow

uniflash 4.1 upgrade to emulation package 6.0.628.1 works properly both on windows 7 and xp

thanks about your courtesy