Hi,
I am using CCS Version: N201105110900
With TMDXEVM6678L Rev 1.0
I have set the switches for no boot position:
SW3: Off on on on
sw4: on on on on
sw5: on on on on
sw6: on on on on
sw9: on on
shunts set for serial port: pins 3-5 and 4-6 jumped
In Device manager TIXDS100 Channel A and TIXDS100 Channel B are displayed.
The properties tab shows
Manufacturer: FTDI
Driver provider: FTDI
status: The device is working properly.
Datails tab / Hardware Ids: USB\VID_0403&PID_A6D0&REV_0700&MI_01
I use the gel file “..\..\emulation\boards\evmc6678l\gel\evmc6678l.gel”
Which Has been added ti “initialization script” of all 8 cores. Also core # 7 is marked as slave.
I do a “Launch selected configuration” and the console displays :
C66xx_0: GEL Output: Setup_Memory_Map...
C66xx_0: GEL Output: Setup_Memory_Map... Done.
When I try to connect to target say core # 0, I get the error message:
Error connecting to the target:
Cannot access register at 0x00000000
(Error -2131) @ 0 (0x0)
I have applied the update to the ccs and I get:
Error connecting to the target: (Error -154 @ 0x0) This utility failed to use the adapter for a custom emulator to perform a write to a controller register. The adapter returned an error. (Emulation package 5.0.470.0)
I have gobe through the forum and do not see any solution.
I did a dbgjtag with following results:
C:\Texas Instruments\ccsv5\ccs_base_5.0.3.00023\common\uscif>dbgjtag -f C:\Users\shojati\AppData\Local\.TI\917832140\0\BrdDat\ccBoard0.dat -rv -Spathlength -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 'jioserdesusb.dll'. The library build date was 'Aug 24 2011'. The library build time was '12:16:50'. The library package version is '5.0.470.2'. The library component version is '35.34.33.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 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 failed. The JTAG IR instruction scan-path is stuck-at-ones.
The test for the JTAG DR bypass path-length failed. The JTAG DR bypass scan-path is stuck-at-ones.
-----[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. Test 1 Word 0: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 1: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 2: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 3: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 4: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 5: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 6: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 7: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. The details of the first 8 errors have been provided. The utility will now report only the count of failed tests. Scan tests: 10, skipped: 0, failed: 10 Some of the values were corrupted - 100.0 percent.
The JTAG IR Given Data scan-test has failed.
-----[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. Test 1 Word 0: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 1: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 2: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 3: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 4: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 5: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 6: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. Test 1 Word 7: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF. The details of the first 8 errors have been provided. The utility will now report only the count of failed tests. Scan tests: 10, skipped: 0, failed: 10 Some of the values were corrupted - 100.0 percent.
The JTAG DR Given Data scan-test has failed.
