Добрый день - помогите пожалуйста разобраться со следующей проблемой:
Поставил CCS 5.1 под windows xp 32 bit. Подключаю эмулятор как описано здесь (драйвера FTDI не ставил - да меня почему-то об этом и не спрашивали - но на всякий случай запустил и их setup - но новых устройств типа USB Serial Converter A и B не появилось). CCS xds100v2 признала и в device managere у меня появились TI XDS100 Channel A, TI XDS100 Channel B и Составное USB устройство
http://processors.wiki.ti.com/index.php/XDS100#Installation_for_Code_Composer_Studio_v5.1.x
Далее пытаюсь подключиться к beagleboard (OMAP3530). Подключаюсь после того как на beagleboard остановил autoboot. Target configuration (.ccxml) и ссBoard0.dat файлы такие же как и в (GEL инициализацию Cortex-A8 не выставлял).
http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/95724.aspx
ccBoard0.dat на всякий случай у меня следующий:
-------------------------------------------------------------------------
# config version=3.5
$ sepk
pod_drvr=jioserdesusb.dll
pod_port=0
$ /
$ product
title="Texas Instruments XDS100v2 USB"
alias=TI_XDS100v2_USB
name=FTDI_FT2232
$ /
$ ftdi_ft2232
usb_vid=0x0403
usb_pid=0xa6d0
gpio_l0="TRSTn,Active_Low"
gpio_l1="EMU_Pin_Enable,Active_Low"
gpio_l2="EMU_Pin_0,Active_Low"
gpio_l3="Adaptive_Clock,Active_High"
gpio_h0="SRSTn,Active_High"
gpio_h1="SRSTn_In,Active_Low"
gpio_h2="Power_Loss_Detect,Active_Low"
gpio_h3="Power_Loss_Reset,Active_High"
gpio_h4="EMU_Pin_1,Active_Low"
gpio_h5="Cable_Disconnect,Active_High"
gpio_h6="Loopback,Active_High"
$ /
$ uscif
tdoedge=FALL
jtagboot_mode=disable
jtagboot_value=hiz
powerboot_mode=disable
powerboot_value=hiz
tclk_program=SPECIFIC
tclk_frequency=1.0
loopback_mode=disable
loopback_value=disable
$ /
@ icepick_c_0 family=icepick_c irbits=6 drbits=1 subpaths=2
& subpath_1 address=19 default=no custom=no force=yes pseudo=no
@ cs_dap_pc_0 family=cs_dap_pc irbits=4 drbits=1 subpaths=2 address=0xD401D030 identify=0x0B6D602F revision=Legacy
& subpath_6 type=legacy address=0 default=no custom=no force=yes pseudo=yes
@ csetb_0 family=cs_etb irbits=0 drbits=0 address=0x5401B000 traceid=0x0
& subpath_2 type=legacy address=0x9000 default=no custom=no force=yes pseudo=no
@ cs_child_2 family=cs_child irbits=0 drbits=0 address=0xD4010000 identify=0x48C6E409
@ cs_child_1 family=cs_child irbits=0 drbits=0 address=0xD401D000 identify=0x48CD0C09
@ cs_child_0 family=cs_child irbits=0 drbits=0 address=0xD4012000 identify=0x48C44C09
@ cortex_a8_0 family=cortex_axx irbits=0 drbits=0 address=0xD4011000
& /
& subpath_0 address=17 default=no custom=no force=yes pseudo=no
@ c64xp_0 family=tms320c64plus irbits=38 drbits=1
& /
# /
--------------------------------------------------------------------------
dbgjtag -f ccBoard0.dat -rv -S pathlength - S integrity пишет:
--------------------------------------------------------------------------
-----[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 'Oct 27 2011'.
The library build time was '17:12:35'.
The library package version is '5.0.520.0'.
The library component version is '35.34.38.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-zero.
The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-zero.
-----[Perform the Integrity 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.
Test 1 Word 0: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 1: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 2: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 3: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 4: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 5: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 6: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 7: scanned out 0xFFFFFFFF and scanned in 0x00000000.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 1, skipped: 0, failed: 1
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.
The JTAG IR Integrity scan-test has failed.
-----[Perform the Integrity 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.
Test 1 Word 0: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 1: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 2: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 3: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 4: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 5: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 6: scanned out 0xFFFFFFFF and scanned in 0x00000000.
Test 1 Word 7: scanned out 0xFFFFFFFF and scanned in 0x00000000.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 1, skipped: 0, failed: 1
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 1
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 2
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 3
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 4
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 5
Some of the values were corrupted - 83.3 percent.
The JTAG DR Integrity scan-test has failed.
--------------------------------------------------------------------------
а dbgjtag -f ccBoard0.dat -rv -S brokenlength пишет:
--------------------------------------------------------------------------
-----[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 'Oct 27 2011'.
The library build time was '17:12:35'.
The library package version is '5.0.520.0'.
The library component version is '35.34.38.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).
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.
The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.
--------------------------------------------------------------------------
В чем тут проблема? - я хочу еще попробывать на виртуалке с CCS 4.0 и FTDI драйверами - но в какой последовательности что ставить. Буду очень признателен если расталкуете что к чему.