This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMDSHVMTRPFCKIT: TMDSHVMTRPFCKIT

Part Number: TMDSHVMTRPFCKIT

使用官方TMDSHVMTRPFCKIT高电压电机控制和 PFC 开发者套件调试level3时突然出现这样,请问是什么原因,该如何解决?(Piccolo TMDSCNCD28035 controlCARD只有LED1亮)

这是Debug error:

这是Test  Connection 的结果:

[Start: Texas Instruments XDS100v2 USB Emulator_0]

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\27683\AppData\Local\TEXASI~1\CCS\
INSTAL~1\5\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 'Feb 18 2015'.
The library build time was '23:56:50'.
The library package version is '5.1.641.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: 0
Do 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: 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.
Scan tests: 1, skipped: 0, failed: 0
Do 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: 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.

[End: Texas Instruments XDS100v2 USB Emulator_0]

  • 检查一下物理连接,以及板子有没有掉电

  • 板子给ControlCARD15v供电正常,仿真器在电脑那边显示有端口号,烧录就会显示这样。我讲述一下我的经过:我在调试level3时候给板子供的是DC电源,大概20几伏,操作顺序是按照手册来的,程序正常运行,我调小了一下DC电源,大概17、8伏,然后电机突然抖了一下,CCS软件Debug界面那个暂停程序运行键变成灰色了,Connect to target 变成了Disconnect  ,还有窗口看变量那个小界面所有变量变成不识别状态,我一着急,就点击terminate,电机还在转(按理说程序暂停了电机不会转的),于是我关了DC电源(15v给ControlCARD供电还在,卡上LED1绿色,LED3变成红色),然后断了所有电,重新开始烧录就成这样显示了,猜测会不会程序跑飞,芯片锁住了?

    如果是可以找谁维修或者更换ControlCARD中间的TMS320F28035PNT芯片?

  • 你可以尝试自己更换MCU,或者直接换一块新的ControlCard。

  • 你好,大佬,我换了controlCARD中间的MCU芯片还是出现这样问题(此外有套件有两张controlCARD,我用另外一张,也显示上面Debug错误以及test connection连接失败),所以我想应该不是controllCARD的问题,然后我使用第三方XDS100v2仿真器(因为用它官方配的那根仿真线会出现同样的错误),test connection显示可以连接的上,但是一Debug还是出现上面的错误,此外controlCARD上sw1在off状态    sw2 都在on状态   sw3都在off状态    我在想会不会插仿真器这块M3电路有问题?

  • 首先,如果你有这个控制卡的-->基板<--的话,可以用基板随便调试一个例程,来排除/确定控制卡是否有问题。

    你之前调试一直用的是高压电机套件板上的JP1吧?按照你之前的描述,这一部分确实有可能损坏。

    你可以对着原理图,分别在加电以及不加电的情况下,用万用表检查一下这块的参数。比如不加电的时候可以检查一下电路的通断、各个元器件的参数,加电的时候检查一下各点的电压。M3的原理图在该文件的最后一张:

    file:///C:/ti/controlSUITE/development_kits/HVMotorCtrl+PfcKit_v2.1/~HVMotorCtrl+PFC-HWdevPkg/HVMotorCtrl+PFCKit-R1.1/HVMotorCtrl+PFC-SCH[R1.1].pdf

  • 另外控制卡上的SW1和SW3与调试没有关系。

    SW2的话建议放在0-1(下-上)(wait mode)位置。这个时候LD1是绿色(power on),LD3是红色。

  • 谢谢,已经解决,由于串口芯片跟光耦隔离有问题,更换之后就没问题了

  • 好的,感谢反馈