仿真器连接不上

想问一下，自己作的6748板子，参照 TI6748 LCD原理图，dsp电源没有问题，仿真器连接不上，测量复位引脚是1.1V,现在找不到原因

Nancy Wang：

复位部分是参考原理图设计的吗？请问此时VDD电压多少呢？如果vdd是3.3v的话，reset高电压也应该为3.3v。

user6258583：

回复 Nancy Wang:

谢谢您的回复，DVDD18接1.8V ,DVDD3318接3.3V.复位部分电路现在都拆了，电压有时是1.1 V，有时就变成0.8V，我想问下dsp6748正常工作的话功耗是多大，我dsp 供5V电压，电流，147mA，这能说明DSP运行了吗？

user6258583：

回复 Nancy Wang:

量到JTAG口的EMU0和EMU1是2.68V

Nancy Wang：

回复 user6258583:

典型的功耗值请参考：
www.ti.com/…/sprabf9.pdf

Tony Tang：

#1.共有几块板子,都有这个问题吗?

#2. 电源没问题,是指电压没问题吧,上时时序符合要求吗? 1.1V->1.8V->3.3V. 

#3. 间接判断一下DSP是否工作了: 将启动模式改到UART boot, 从串口看是否能收到BOOTME输出.

RESET是输入脚,外部可以加一个上拉电阻. 通过将RESET手动捅一下GND来手动复位DSP.

user6258583：

回复 Tony Tang:

上电顺序没有问题，dsp 启动应该也没问题，JTAG连接到板卡后，RTST引脚没有被驱动成高电平

Tony Tang：

回复 user6258583:

看清楚我的问题，按顺序回答。

user6258583：

回复 Tony Tang:

1.共有5块板子，测了三块都有这个问题

2.电源上电顺序没有问题，用的TPS650250电源芯片1.3->1.8->3.3

3.间接判断DSP工作:用UART2启动模式串口的收发如下

RESET外部上拉到3.3V后JTAG口的电压都正常，但是还是连接不上仿真器，提示如下错误：

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

—–[Print the board config pathname(s)]————————————

C:\Users\Administrator\AppData\Local\.TI\ 2526794187\0\0\BrdDat\testBoard.dat

—–[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 20 2013'.The library build time was '22:56:19'.The library package version is '5.1.232.0'.The library component version is '35.34.40.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 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).

—–[The log-file for the JTAG TCLK output generated from the PLL]———-

There is no hardware for programming the JTAG TCLK frequency.

—–[Measure the source and frequency of the final JTAG TCLKR input]——–

There is no hardware for measuring the JTAG TCLK frequency.

—–[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 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.Scan tests: 1, skipped: 0, failed: 0Do a test using 0x00000000.Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 7: scanned out 0x00000000 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: 2, skipped: 0, failed: 1Do a test using 0xFE03E0E2.Scan tests: 3, skipped: 0, failed: 2Do a test using 0x01FC1F1D.Scan tests: 4, skipped: 0, failed: 3Do a test using 0x5533CCAA.Scan tests: 5, skipped: 0, failed: 4Do a test using 0xAACC3355.Scan tests: 6, skipped: 0, failed: 5Some 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.Scan tests: 1, skipped: 0, failed: 0Do a test using 0x00000000.Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF.Test 2 Word 7: scanned out 0x00000000 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: 2, skipped: 0, failed: 1Do a test using 0xFE03E0E2.Scan tests: 3, skipped: 0, failed: 2Do a test using 0x01FC1F1D.Scan tests: 4, skipped: 0, failed: 3Do a test using 0x5533CCAA.Scan tests: 5, skipped: 0, failed: 4Do a test using 0xAACC3355.Scan tests: 6, skipped: 0, failed: 5Some of the values were corrupted – 83.3 percent.

The JTAG DR Integrity scan-test has failed.

[End]

Tony Tang：

回复 user6258583:

55 AA是什么？你发送的，还是接收到从板子上发出来的？

user6258583：

回复 Tony Tang:

是我发送的