Hello, I'm developping on the TMDX570LS20SUSB kits, uploading with the embedded XDS100v2.
I usually use CCSv4.2.3.00004 (provided on the kit's dvd). Sometimes while I'm working on it, it crashes without any particular reason, I get a windows from the jvm telling "the program exited unexpectedly" with all the jvm arguments. Recently I was uploading, as usual CCS switched to the DebugView, with the progress bar moving, but this time it never ended, I waited, and after more than 10min the whole program disappeared without even a windows message about the jvm...
I ran CCS again and tried to connect to the device, but I got:
Error connecting to the target:
(Error -5008 @ 0xFFFFEC70)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Release 0.0.0.0)
Trying to upload new code I got the same output.
I tried different frequencies up to 488Hz (the lowest allowed by my CCS), it just took more time to get the same result.
I also tried to erase the flash from nowFlash (tried v3.38, 3.39 and 3.40):
nowFlash version 3.40 Build (OFFICIAL)
Config file c:\ti\nowFlash\v340\nowFlash.cfg Revision: 0
Accessing device 0 through port 0x000
User specified emulator type TIXDS100V2.
Using board configuration file c:\ti\nowFlash\v340\brddat\board_tixds100v2_v3_cortex_rxx.dat
Port driver "c:\ti\nowFlash\v340\drivers\tixds510cortexR.dvr" ... LOADED
Port address 0x000 target..initialize..connect....failed
Error 199 - Unable to connect to target on port address 0x000.
**************************************************************
Press Enter to exit
Error connecting to the target:
Unknown error (Error -5008) @ -5008 (0xFFFFEC70)
Dap: Error connecting to the target: Unknown error (Error -5008) @ -5008 (0xFFFFEC70)
I downloaded CCSv4.2.4.00033 and tried it on a new kit, i got it broken the same way :(
I also used CCSv5.1.0.07001 on a 3rd kit and "burned" it again... here is the output from the console:
CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Warning: (Error -1044 @ 0xFFFFEC70) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Release 5.0.429.0)
CortexR4: Warning: (Error -1044 @ 0xFFFFEC70) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Release 5.0.429.0)
CortexR4: Warning: (Error -1044 @ 0xFFFFEC70) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Release 5.0.429.0)
After reading differents posts about similar problems, I tried the dbgjtag tool, but it doesn't help me much:
C:\TI\nowFlash\v340\drivers>xdsprobe.exe -f ..\brddat\board_tixds100v2_v3_cortex_rxx.dat -a
-----[Print the controller-open software log-file]---------------------------
This utility has selected an XDS510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'jioserdesusb.dll'.
The emulator adapter is titled '(null)'.
The emulator adapter is version '(null)'.
The emulator adapter is using 'Normal-Mode'.
The controller has a version number of '4' (0x0004).
The controller has an insertion length of '0' (0x0000).
The cable+pod has a version number of '0' (0x0000).
The cable+pod has a capability number of '0' (0x0000).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '1048576' (0x100000).
-----[Analysing the configure file and the scan-path]------------------------
The configure file indicates 4 JTAG devices should be in the system.
This test indicates zero JTAG devices are actually in the system.
This test cannot analyse the scan-path when the
configure file and the scan-path do not match.
C:\TI\nowFlash\v340\drivers>xdsprobe.exe -f ..\brddat\board_tixds1_rxx.dat -b
-----[Print the controller-open software log-file]----------------
This utility has selected an XDS510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'jioserdesusb.dll'.
The emulator adapter is titled '(null)'.
The emulator adapter is version '(null)'.
The emulator adapter is using 'Normal-Mode'.
The controller has a version number of '4' (0x0004).
The controller has an insertion length of '0' (0x0000).
The cable+pod has a version number of '0' (0x0000).
The cable+pod has a capability number of '0' (0x0000).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '1048576' (0x100000).
-----[Perform the standard path-length test on the JTAG IR and DR]
This path-length test uses blocks of 512 32-bit words.
The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 bits.
The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.
-----[Perform the Broken Path scan-test on the JTAG IR]-----------
This test will use blocks of 512 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
All of the values were scanned correctly.
The JTAG IR Broken Path scan-test has succeeded.
-----[Perform the Broken Path scan-test on the JTAG DR]-----------
This test will use blocks of 512 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
All of the values were scanned correctly.
The JTAG DR Broken Path scan-test has succeeded.
C:\TI\nowFlash\v340\drivers>
I also tried from Linux with CCSv5.0.3.00025:
root@computer:/opt/ti/CCS5.0.3.00025/ccsv5/ccs_base_5.0.3.00025/common/uscif# ./dbgjtag -f BrdDat/ccBoard0.dat -rv -Sgivendata,repeat=10
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioserdesusbv2.so'.
The library build date was 'Jan 3 2011'.
The library build time was '23:12:04'.
The library package version is '5.0.281.0'.
The library component version is '35.34.29.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will now 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 FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 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 Given Data scan-test on the JTAG IR]-----------------------
This test will use blocks of 512 32-bit words.
This test will be applied 10 times.
It uses all of the 10 different test-cases.
Do a test using 0x5533CCAA.
Scan tests: 10, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG IR Given Data scan-test has succeeded.
-----[Perform the Given Data scan-test on the JTAG DR]-----------------------
This test will use blocks of 512 32-bit words.
This test will be applied 10 times.
It uses all of the 10 different test-cases.
Do a test using 0x5533CCAA.
Scan tests: 10, skipped: 0, failed: 0
All of the values were scanned correctly.
The JTAG DR Given Data scan-test has succeeded.
root@computer:/opt/ti/CCS5.0.3.00025/ccsv5/ccs_base_5.0.3.00025/common/uscif# ./dbgjtag -f BrdDat/ccBoard0.dat -A scanpath
-----[Analysing the configure file and the scan-path]------------------------
File: BrdDat/ccBoard0.dat
-------------------------
The configure file indicates 4 JTAG sub-paths should be in the system.
The configure file indicates 3 JTAG devices should be in the system.
Device: 0
---------
The device name is 'ICEPICK'.
The family name is 'ICEPICK_C'.
The product title is 'router'.
The product description is 'scan-path router'.
The device has a subpath count of 2.
The device has a custom JTAG DR register length.
The device has a custom JTAG IR register length.
The JTAG IR register bit length is : 6
The JTAG IR pre-amble bit length is : 0
The JTAG IR post-amble bit length is : 0
The JTAG DR register bit length is : 1
The JTAG DR pre-amble bit length is : 0
The JTAG DR post-amble bit length is : 0
An interrogation routine is not yet available.
Device: 1
---------
The device name is 'DAP'.
The family name is 'CS_DAP'.
The product title is 'router'.
The product description is 'CoreSight memory-map router'.
The device has a subpath count of 1.
The device has a custom JTAG DR register length.
The device has a custom JTAG IR register length.
The JTAG IR register bit length is : 4
The JTAG IR pre-amble bit length is : 0
The JTAG IR post-amble bit length is : 6
The JTAG DR register bit length is : 1
The JTAG DR pre-amble bit length is : 0
The JTAG DR post-amble bit length is : 1
An interrogation routine is not yet available.
Device: 2
---------
The device name is 'CORTEXR4'.
The family name is 'CORTEX_RXX'.
The product title is 'cpu'.
The product description is 'RISC micro-processor'.
The device has a custom JTAG DR register length.
The device has a custom JTAG IR register length.
The JTAG IR register bit length is : 0
The JTAG IR pre-amble bit length is : 0
The JTAG IR post-amble bit length is : 10
The JTAG DR register bit length is : 0
The JTAG DR pre-amble bit length is : 0
The JTAG DR post-amble bit length is : 2
An interrogation routine is not yet available.
root@computer:/opt/ti/CCS5.0.3.00025/ccsv5/ccs_base_5.0.3.00025/common/uscif# ./xdsprobe -f BrdDat/ccBoard0.dat -k
-----[The log-file for the JTAG TCLK output generated from the PLL]----------
There is no hardware for programming the JTAG TCLK frequency.
-----[Measure the source and frequency of the final JTAG TCLKR input]--------
I'm a bit hopeless now, I eventually could connect via the jtag header to check if the cpu is still working, but there is no official support about using it it seems.
Another piece of information, I'm also using the TMDX570LS20SMDK kit, and it also happened that CCS "disappears" suddently, but after restarting it I can still access the cpu and upload new code, so this problem seems to affect only the USB kits.
Any help to get those kits working back would be greatly appreciate!
regards,
Yasuki.
PD: serial number of the chips:
- TMS570LS20216ASPGEQQ1 CA-13A951W G4
- TMP570LS20216ASPGEQQ1 CA-12A943W G4
- TMS570LS20216ASPGEQQ1 CA-13A951W G4
