• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 29 subscribers
  • Views 259 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS570LS0332: TMS5700432BPZQQ1R: Can’t flash TMS5700432 with JTAG from TMS570LC43x Hercules Development Kit with a XDS100v2 programmer.

Kelvin Sweere
Prodigy 110 points
Part Number: TMS570LS0332
Other Parts Discussed in Thread: TMS5700432

TMS5700432BPZQQ1R: Can’t flash TMS5700432 with JTAG from TMS570LC43x Hercules Development Kit with a XDS100v2 programmer.

 

Hi all,

 

For a school project I’ve to design an embedded system with a TMS5700432 chip and I want to flash it with a TMS570LC43x Hercules Development Kit with an onboard XDS100v2 programmer. But it doesn’t work.

I developed the embedded system with KiCAD and a professional PCB company in the Netherlands made the board.

When the PCB was delivered, I try to verify the connection in Code Composer Studio (see picture), but I got error code 183 back.

Error msg:

[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\30045508\AppData\Local\TEXASI~1\
CCS\ccs930\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 'Feb 13 2020'.
The library build time was '18:30:11'.
The library package version is '9.1.0.00001'.
The library component version is '35.35.0.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 64 32-bit words.

The JTAG IR instruction path-length was not recorded.

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

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

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

This error is generated by TI's USCIF driver or utilities.

The value is '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.

[End]

First I wanted to make sure that the JTAG connection worked on a another board. So, I programmed two development-kits and that worked fine.

I measured the clock on my board, and it gives a stable 10 MHz signal. I use a 12V power supply with TPS562200DDCR step-down converts, to convert it to 3.3V I/O voltage and 1.2V core voltage. The core voltage is a little bit noisy (see picture), but when measured with the multimeter it gives a voltage of 1.21V. Is the noise maybe the cause of the problem?

 

The other point I’m not sure about, is that I didn’t implemented pull-up resistors on the PCB. I didn’t place them on my board because there are already pull-ups from the dev-kit (right?). Can that be a problem? See pictures below:

 

Does anybody know what I did wrong in my design and maybe how to fix it?

 

Kind regards,

Kelvin S.