|
|
включил как-то житаг, а шлейф стал плавиться по 10 ноге. то ли руки у меня кривые были то ли что.. но неважно... я конечно же все отрубил. потом перевключил все, - не плавится. Проверяю тесты . xdsprobe с ключами i и y . вылезают ошибки, что при IR тесте ошибка во втором бите при инверсных данных, а в DRJ тесте ошибка во втором бите СЛЕВА.
Нмже вот они .вопрос - чего сгорело то, чего менять? альтеру? или достаточно перепрошить? дорожки как то XTMS и LVD подплавились немного :( которые от LVD к альтере, но не оторвались. ногами не бейте. (собирал его не я).
c:\CCStudio_v3.1\cc\bin>xdsreset
-----[Select and reset the controller]---------------------------------------
This utility has selected an XDS510 class product.
This utility will load the adapter 'sm510dvr.dll'.
This utility will operate on port address '0x0'.
The emulator adapter is named 'c:\CCStudio_v3.1\cc\bin\sm510dvr.dll'.
The emulator adapter is titled 'SM510PCI POD Adapter'.
The emulator adapter is version '3.3.12'.
The emulator adapter is uses 'Normal-Mode'.
The controller has an insertion length of '16' (0x0010).
The controller has a revision number of '1' (0x0001).
The controller type is 'The venerable TBC (74ACT8990)'.
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '262144' (0x040000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.
c:\CCStudio_v3.1\cc\bin>xdsprobe -i
-----[Select the controller]-------------------------------------------------
This utility has selected an XDS510 class product.
This utility will load the adapter 'sm510dvr.dll'.
This utility will operate on port address '0x0'.
The emulator adapter is named 'c:\CCStudio_v3.1\cc\bin\sm510dvr.dll'.
The emulator adapter is titled 'SM510PCI POD Adapter'.
The emulator adapter is version '3.3.12'.
The emulator adapter is uses 'Normal-Mode'.
The controller has an insertion length of '16' (0x0010).
The controller has a revision number of '1' (0x0001).
The controller type is 'The venerable TBC (74ACT8990)'.
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '262144' (0x040000).
-----[Perform the scan-path length test on the JTAG IR and DR]---------------
This scan-path test uses blocks of 512 32-bit words.
The test for the JTAG IR instruction scan-path length failed.
The many-ones then many-zeros tested length was 47 bits.
The many-zeros then many-ones tested length was -16384 bits.
The test for the JTAG DR bypass scan-path length failed.
The many-ones then many-zeros tested length was 2 bits.
The many-zeros then many-ones tested length was -16384 bits.
-----[Perform the scan-path integrity test on the JTAG IR]-------------------
This scan-path test uses blocks of 512 32-bit words.
Starting an Integrity Test using 0xFFFFFFFF.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0x00000000.
Word 0: scanned out 0x00000000 and scanned in 0x00020002.
Word 1: scanned out 0x00000000 and scanned in 0x00020002.
Word 2: scanned out 0x00000000 and scanned in 0x00020002.
Word 3: scanned out 0x00000000 and scanned in 0x00020002.
Word 4: scanned out 0x00000000 and scanned in 0x00020002.
Word 5: scanned out 0x00000000 and scanned in 0x00020002.
Word 6: scanned out 0x00000000 and scanned in 0x00020002.
Word 7: scanned out 0x00000000 and scanned in 0x00020002.
The details of the first eight errors have been provided.
The utility will not report further errors found by this test.
Some of the 32-bit data values were corrupted - 99.8 percent.
Finished that Integrity Test.
Starting an Integrity Test using 0xFE03E0E2.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0x01FC1F1D.
Word 0: scanned out 0x01FC1F1D and scanned in 0x01FE1F1F.
Word 1: scanned out 0x01FC1F1D and scanned in 0x01FE1F1F.
Word 2: scanned out 0x01FC1F1D and scanned in 0x01FE1F1F.
Word 3: scanned out 0x01FC1F1D and scanned in 0x01FE1F1F.
Word 4: scanned out 0x01FC1F1D and scanned in 0x01FE1F1F.
Word 5: scanned out 0x01FC1F1D and scanned in 0x01FE1F1F.
Word 6: scanned out 0x01FC1F1D and scanned in 0x01FE1F1F.
Word 7: scanned out 0x01FC1F1D and scanned in 0x01FE1F1F.
The details of the first eight errors have been provided.
The utility will not report further errors found by this test.
Some of the 32-bit data values were corrupted - 99.8 percent.
Finished that Integrity Test.
Starting an Integrity Test using 0x5533CCAA.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0xAACC3355.
Word 0: scanned out 0xAACC3355 and scanned in 0xAACE3357.
Word 1: scanned out 0xAACC3355 and scanned in 0xAACE3357.
Word 2: scanned out 0xAACC3355 and scanned in 0xAACE3357.
Word 3: scanned out 0xAACC3355 and scanned in 0xAACE3357.
Word 4: scanned out 0xAACC3355 and scanned in 0xAACE3357.
Word 5: scanned out 0xAACC3355 and scanned in 0xAACE3357.
Word 6: scanned out 0xAACC3355 and scanned in 0xAACE3357.
Word 7: scanned out 0xAACC3355 and scanned in 0xAACE3357.
The details of the first eight errors have been provided.
The utility will not report further errors found by this test.
Some of the 32-bit data values were corrupted - 99.8 percent.
Finished that Integrity Test.
The JTAG IR integrity test has failed.
-----[Perform the scan-path integrity test on the JTAG DR]-------------------
This scan-path test uses blocks of 512 32-bit words.
Starting an Integrity Test using 0xFFFFFFFF.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0x00000000.
Word 0: scanned out 0x00000000 and scanned in 0x40004000.
Word 1: scanned out 0x00000000 and scanned in 0x40004000.
Word 2: scanned out 0x00000000 and scanned in 0x40004000.
Word 3: scanned out 0x00000000 and scanned in 0x40004000.
Word 4: scanned out 0x00000000 and scanned in 0x40004000.
Word 5: scanned out 0x00000000 and scanned in 0x40004000.
Word 6: scanned out 0x00000000 and scanned in 0x40004000.
Word 7: scanned out 0x00000000 and scanned in 0x40004000.
The details of the first eight errors have been provided.
The utility will not report further errors found by this test.
Some of the 32-bit data values were corrupted - 99.8 percent.
Finished that Integrity Test.
Starting an Integrity Test using 0xFE03E0E2.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0x01FC1F1D.
Word 0: scanned out 0x01FC1F1D and scanned in 0x41FC5F1D.
Word 1: scanned out 0x01FC1F1D and scanned in 0x41FC5F1D.
Word 2: scanned out 0x01FC1F1D and scanned in 0x41FC5F1D.
Word 3: scanned out 0x01FC1F1D and scanned in 0x41FC5F1D.
Word 4: scanned out 0x01FC1F1D and scanned in 0x41FC5F1D.
Word 5: scanned out 0x01FC1F1D and scanned in 0x41FC5F1D.
Word 6: scanned out 0x01FC1F1D and scanned in 0x41FC5F1D.
Word 7: scanned out 0x01FC1F1D and scanned in 0x41FC5F1D.
The details of the first eight errors have been provided.
The utility will not report further errors found by this test.
Some of the 32-bit data values were corrupted - 99.8 percent.
Finished that Integrity Test.
Starting an Integrity Test using 0x5533CCAA.
All of the 32-bit data values were scanned correctly.
Finished that Integrity Test.
Starting an Integrity Test using 0xAACC3355.
Word 0: scanned out 0xAACC3355 and scanned in 0xEACC7355.
Word 1: scanned out 0xAACC3355 and scanned in 0xEACC7355.
Word 2: scanned out 0xAACC3355 and scanned in 0xEACC7355.
Word 3: scanned out 0xAACC3355 and scanned in 0xEACC7355.
Word 4: scanned out 0xAACC3355 and scanned in 0xEACC7355.
Word 5: scanned out 0xAACC3355 and scanned in 0xEACC7355.
Word 6: scanned out 0xAACC3355 and scanned in 0xEACC7355.
Word 7: scanned out 0xAACC3355 and scanned in 0xEACC7355.
The details of the first eight errors have been provided.
The utility will not report further errors found by this test.
Some of the 32-bit data values were corrupted - 99.8 percent.
Finished that Integrity Test.
The JTAG DR integrity test has failed.
c:\CCStudio_v3.1\cc\bin>xdsprobe -y
-----[Select the controller]-------------------------------------------------
This utility has selected an XDS510 class product.
This utility will load the adapter 'sm510dvr.dll'.
This utility will operate on port address '0x0'.
The emulator adapter is named 'c:\CCStudio_v3.1\cc\bin\sm510dvr.dll'.
The emulator adapter is titled 'SM510PCI POD Adapter'.
The emulator adapter is version '3.3.12'.
The emulator adapter is uses 'Normal-Mode'.
The controller has an insertion length of '16' (0x0010).
The controller has a revision number of '1' (0x0001).
The controller type is 'The venerable TBC (74ACT8990)'.
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '262144' (0x040000).
-----[Test the emulator's JTAG controller hardware]--------------------------
Starting the Control Register Reset Test.
Finished the Control Register Reset Test.
Starting the Control Register Read-Write Test.
Finished the Control Register Read-Write Test.
Starting the Serial Buffer Normal Read-Write Test.
Finished the Serial Buffer Normal Read-Write Test.
Starting the Serial Buffer Reverse Read-Write Test.
Finished the Serial Buffer Reverse Read-Write Test.
Starting the Status0 Register Test.
Finished the Status0 Register Test.
Starting the Status1 Register Test.
Finished the Status1 Register Test.
Starting the Status2 Register Test.
Finished the Status2 Register Test.
Starting the Status3 Register Test.
Finished the Status3 Register Test.
Starting the Counter Capture Test.
Finished the Counter Capture Test.
Starting the Loop-Back with Reads and Writes Test.
Finished the Loop-Back with Reads and Writes Test.
Starting the Loop-Back Test with All-Ones Test.
Finished the Loop-Back Test with All-Ones Test.
Starting the Loop-Back Test Using All-Zeros Test.
Finished the Loop-Back Test Using All-Zeros Test.
Starting the Loop-Back with Recirculation Test.
Finished the Loop-Back with Recirculation Test.
Starting the Serial Buffer Observe Flag Test.
Finished the Serial Buffer Observe Flag Test.
Starting the State Command's State Machine Test.
Finished the State Command's State Machine Test.
Starting the Counter1 and Counter2 Test.
Finished the Counter1 and Counter2 Test.
None of the test-cases have detected errors.
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver.
The value is `-230' (0xffffff1a).
The title is: `SC_ERR_PTH_MEASURE'.
The explanation is:
The measured lengths of the two JTAG scan-paths
are invalid. This indicates that an error exists
in the configuration of the link-delay or scan-path.
c:\CCStudio_v3.1\cc\bin>
|
|
E-mail: 
info@telesys.ru
