Телесистемы
 Разработка, производство и продажа радиоэлектронной аппаратуры
На главную   | Карта сайта | Пишите нам | В избранное
Требуется программист в Зеленограде
- обработка данных с датчиков; ColdFire; 40 тыс.
e-mail:jobsmp@pochta.ru

Телесистемы | Электроника | Конференция «Цифровые сигнальные процессоры (DSP) и их применение»

есть вопрос по SM510pci

Отправлено Barton 14 августа 2008 г. 13:25


доброго времени суток.

имею железки: sm510, и таргет с vc5509a. композер 3.1

вопрос такой:

эмулятор както интересно подглюкивает, т.е.

xdsprobe -r,

потом при первом (после -r) запуске xdsprobe -i -- тест проходит либо на 100%, либо 99,8%(см.ниже)

при повторном запуске xdsprobe -i приводит к появлению ошибки -270 (SC_ERR_SCN_LENGTH_CONTROL)


логи:-------------------------->>>>

c:\CCStudio_v3.1_full\cc\bin>xdsprobe -rv

-----[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 controller does not use a programmable FPGA.
The emulator adapter is named 'c:\CCStudio_v3.1_full\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.

-----[Print the reset command log-file]-------------------------------

The controller has been hardware reset via its support logic.
The controller has been software reset via its support logic.
The software is configured to use only TBC features.
The software is configured for slower clock operation.
The controller has a logic ZERO on its EMU[0] input pin.
The controller has a logic ZERO on its EMU[1] input pin.
The controller will use rising-edge timing on output pins.
The controller may use rising edge timing on input pins.
The support logic has not previously detected a power-loss.
The scan-path will be reset by toggling the JTAG TRST signal.
The scan-path link-delay has been set to exactly '4' (0x0004).

c:\CCStudio_v3.1_full\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_full\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 succeeded.
The JTAG IR instruction scan-path length is 38 bits.

The test for the JTAG DR bypass scan-path length succeeded.
The JTAG DR bypass scan-path length is 1 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.
All of the 32-bit data values were scanned correctly.
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.
All of the 32-bit data values were scanned correctly.
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 0x56AB30CD.
Word 1: scanned out 0xAACC3355 and scanned in 0x56AB30CD.
Word 2: scanned out 0xAACC3355 and scanned in 0x56AB30CD.
Word 3: scanned out 0xAACC3355 and scanned in 0x56AB30CD.
Word 4: scanned out 0xAACC3355 and scanned in 0x56AB30CD.
Word 5: scanned out 0xAACC3355 and scanned in 0x56AB30CD.
Word 6: scanned out 0xAACC3355 and scanned in 0x56AB30CD.
Word 7: scanned out 0xAACC3355 and scanned in 0x56AB30CD.
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.
All of the 32-bit data values were scanned correctly.
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.
All of the 32-bit data values were scanned correctly.
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 0x031F3D81.
Word 1: scanned out 0xAACC3355 and scanned in 0xD56619AA.
Word 2: scanned out 0xAACC3355 and scanned in 0xD56619AA.
Word 3: scanned out 0xAACC3355 and scanned in 0xD56619AA.
Word 4: scanned out 0xAACC3355 and scanned in 0xD56619AA.
Word 5: scanned out 0xAACC3355 and scanned in 0xD56619AA.
Word 6: scanned out 0xAACC3355 and scanned in 0xD56619AA.
Word 7: scanned out 0xAACC3355 and scanned in 0xD56619AA.
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_full\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_full\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 JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass scan-path length succeeded.
The JTAG DR bypass scan-path length is 32 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.

-----[An error has occurred and this utility has aborted]-------------

This error is generated by TI's USCIF driver.

The value is `-270' (0xfffffef2).
The title is: `SC_ERR_SCN_LENGTH_CONTROL'.

The explanation is:
The length of the scan is too large for the emulators controller.


манипуляции с разными кабелями от пода к таргету ни к чему не привели, всякие -tck, -sld, и т.д. - тоже не помогают
еще... xdsprobe -y -- без проблем проходит всегда
xdsprobe -g [data] -c -- без ошибок с разными данными, но только один раз после -r.

на другом таргете (с таким же процом) таже фигня, только почемуто в первом запуске xdsprobe -i длина IR instruction scan-path length is 6 bits. но тест проходит...

куда смотреть?..спасибо)


Составить ответ | Вернуться на конференцию

Ответы


Отправка ответа
Имя*: 
Пароль: 
E-mail: 
Тема*:

Сообщение:

Ссылка на URL: 
URL изображения: 

если вы незарегистрированный на форуме пользователь, то
для успешного добавления сообщения заполните поле, как указано ниже:
прибавьте тройку к двум:

Перейти к списку ответов | Конференция | Раздел "Электроника" | Главная страница | Карта сайта

Rambler's Top100 Рейтинг@Mail.ru
 
Web telesys.ru