Operational issues of XDS100V3.0 emulation motoware built-in project

alan000345

Operational issues of XDS100V3.0 emulation motoware built-in project [Copy link]

The core is 28069+DRV8301, the JTAG interface of 14P is reserved, and the emulator is XDS100V3.0

After power-on, the chip can be downloaded and read through UniFlash, indicating that the hardware connection is OK;

The project uses the built-in project of motoware, such as proj_lab5.0, etc., and it cannot be connected during debugging, and it prompts that it is not recognized. As shown in the figure

查看详情

Next, open TMS320F28069_xds100v2.ccxml in the project, add XDS100V3.0, and add 28069 device under it, click "Test Connection", the test process and test results are normal, as follows:

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 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.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS100v3 USB Debug Probe_0]

However, when I click debug again, I still cannot connect. What should I do?

Workaround

After creating a new physical device (XDS100V3.0) and adding the corresponding devices under it, delete the existing XDS100V2 and save it, then you can debug. If you do not delete V2, you will always try to use V2. Even if you perform the "UP" operation on V3.0, V2 will still return to the first position.