S
simon
Greets,
Has anyone used the GaoTek USB510 jtag emulator with a C6713 baseboard? I
am getting errors on starting CCS 3.3, as follows:
=====
Error connecting to the target:
Error 0x00000202/-1024
Error during: Memory, OCS,
PTI_ERR_PREV_IROP_CMD Error Occured at 0x01BC0028
I/O Port = 240
Board Name: AHW1-671X emulator
Cpu Name: TMS320C671x_0
=====
=====
Error connecting to the target:
Error 0x00000202/-2140
Error during: Memory, OCS,
Cannot access memory address at 0x01840004
I/O Port = 240
Board Name: AHW2-671X
Cpu Name: TMS320C671x_0
=====
I've been running tests with xdsprobe and get errors when doing scan and
data path tests...the bits on the wire are literally correct (write out
0x5533CCAA and 0xF32A954C in binary to see this) but the word boundaries
are offset so the end result is an RX error.
xdsprobe -F gao.dll -p0x240 -g -c
....
Test 1 Word 7: scanned out 0x5533CCAA and scanned in 0xF32A954C.
The details of the first eight errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 83, skipped: 32, failed: 51
Some of the values were corrupted - 99.8 percent.
===
Any advice would be appreciated.
Cheers,
Simon
Has anyone used the GaoTek USB510 jtag emulator with a C6713 baseboard? I
am getting errors on starting CCS 3.3, as follows:
=====
Error connecting to the target:
Error 0x00000202/-1024
Error during: Memory, OCS,
PTI_ERR_PREV_IROP_CMD Error Occured at 0x01BC0028
I/O Port = 240
Board Name: AHW1-671X emulator
Cpu Name: TMS320C671x_0
=====
=====
Error connecting to the target:
Error 0x00000202/-2140
Error during: Memory, OCS,
Cannot access memory address at 0x01840004
I/O Port = 240
Board Name: AHW2-671X
Cpu Name: TMS320C671x_0
=====
I've been running tests with xdsprobe and get errors when doing scan and
data path tests...the bits on the wire are literally correct (write out
0x5533CCAA and 0xF32A954C in binary to see this) but the word boundaries
are offset so the end result is an RX error.
xdsprobe -F gao.dll -p0x240 -g -c
....
Test 1 Word 7: scanned out 0x5533CCAA and scanned in 0xF32A954C.
The details of the first eight errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 83, skipped: 32, failed: 51
Some of the values were corrupted - 99.8 percent.
===
Any advice would be appreciated.
Cheers,
Simon
