Why can't DSP connect? TMS320C6416T+seed-XDS510 PLUS

Aguilera

Why can't DSP connect? TMS320C6416T+seed-XDS510 PLUS [Copy link]

Platform: TMS320C6416T

Emulator: seed-XDS510 PLUS

The most common error: (because there are many kinds of errors, this is the one that occurs most often)

Error connecting to the target:
Error 0x80002262/-116
Fatal Error during: Memory, Execution, Initialization, OCS, Control,
This error was generated by TI's USCIF driver.

SC_ERR_CTL_TRASH <-116>
A bad parameter value was detected within an internal data-structure of Unified-SCIF.
The controller or Unified-SCIF may be in an invalid state.

Sequence ID: 0
Error Code: -116
Error Class: 0x80002262
I/O Port = 240

Board Name: C64xx SEEDXDS510PLUS Emulator_1
Cpu Name: TMS320C6400_0

Abort: Close Code Composer Studio.
Retry: Try to connect to the target again.
Cancel: Remain disconnected from the target
Diagnostic: Run diagnostic utility.

Analysis of the reasons: (The following are some solutions from the Internet, including some of my own opinions. Due to the large number of reference URLs, the sources are not posted one by one. Please understand!)

1. Reinstall CCS

2. Change the computer or
emulator. One reason is that your emulator version is not good. For example, XDS510 is upgraded to XDS510PLUS.
3. EMU0 and EMU1 need to be pulled up. The manual requires 1Kohm.

This should not be strict, because I have two boards on hand, one uses 4.7K and the other uses 10K, and there are no problems.
4. Reinstall the driver, check whether the driver is installed in the device manager, whether the driver is installed in the same path as CCS, and whether the reset program usb20reset can be reset normally.
For the driver, you can check the "xdsfast3.dll" file in the "..CCStudio_v3.3/cc/bin" path. If this file is 160K in size, the driver is not installed. If such a problem occurs, even reinstalling the driver often fails. You need to delete the "xdsfast3.dll" file, then disconnect the PC and the emulator, and reinstall the emulator driver. After installation, check that the "xdsfast3.dll" file size is 352K, which means that the driver has been installed successfully.

5. Some people suspect that it is a JTAG power supply problem

The boards on hand all use 3.3V, so they can be connected, no problem, no need for 5V
6. Check whether the crystal oscillator is oscillating, and check whether there is a waveform output at CLKOUT

I brought out CLKOUT6, which is one sixth of the system clock by default. I used a 50MHz external clock, 20x mode, and the output here is 166MHz
7. Is there a driver buffer chip installed between the JTAG connector and the DSP?

This is okay. I used to use a SN74LVTH244, but now it is useless. You can also connect it.
8. The USB port is not powered enough. If it is a desktop computer, try the USB port on the back of the chassis.
9. Pay attention to the power-on sequence. Connect JTAG and USB first, and then power on the development board.

Ultimately my questions:

First, because the reset of DSP was always in reset state, the reset chip used was MAX705, which was a mistake. This was used under 5V. Alas, what a tragedy. I changed it to ADM706T, OK!

The problem has always existed, and was finally solved as follows:

I checked the configuration of the DSP, mainly some pins on the EMIFB, as shown in the manual:

All the original configurations were configured as high level 1, which is problematic (maybe). I made the following changes:

Try changing BEA18, BEA16, and BEA14 to 0. It still doesn't work.

Remove the configuration resistors on BEA13 and BEA11 to use the default mode. Connection, success!

Of course, this is just my solution. TI products generally have good performance, but are troublesome to use. Sometimes, there are many times when everything is OK but the connection cannot be established.