CCS/TMS320F2812: Error Connecting with the TMS320F2812 for Programming the DSP

Tool/software: Code Composer Studio

Hello,

I have been attempting to program the TMS320F2812 DSP. I am using a development board from Spectrum Digital referred as the eZdsp for F2812. I am using the XDS100v2 or XDS200 (JTAG device) in attempt to program the device. I am stuck at the point when verifying communication with the F2812 with either JTAG device. The communication verification tool I am referring is the verify function when you start a CCS project (CCS 10). No matter what I try it gives me an error during the verification process. Below is a list of things I have tried and confirmed. Error found by both JTAGs listed below. Any help would be greatly appreciated.

Things tried or confirmed:

1. Two different JTAG programmers (XDS100v2 and XDS200)
2. Confirm both JTAG programmers work by programming the TMS320F28335
3. Tried two different computers (both running Windows 10)
4. Tried different CCS versions (CCS 10, CCS 4.2, and CCS 3.3) [Development board came out when CCS 3.3 was around]
   1. Couldn't run CCS 3.3 on my Windows 10 computer due to operating system incompatibility
      1. Tried Compatibility mode feature within Windows 10 to fix with no luck
   2. Had to use an example code within CCS 4 to attempt to program, good chance there is a bad setting
      1. That said, I was successful doing the exact same thing with the TMS320F28335 which worked
5. The eZdsp development board is brand new, just ordered from Spectrum Digital
6. Have tried programming a SM320F2812 with exact error.
   1. The board is custom, so circuit error is possible
   2. Had to select TMS320F2812 within CCS 10 since the SM320F2812 version is not there
7. Have communicated with Spectrum Digital with the following reasoning of error
   1. “Invalid scan length errors would indicate a problem with the emulator, target, or interconnection between the two.”
   2. “If it is a hardware failure in the scan chain, it could be a problem with the F2812 board hardware or maybe the connection between the emulator and board.”
   3. “You can look at the configuration settings in the project you are using in case there is something there causing a timing issue on the JTAG.”
8. Tried to use Parallel to USB adapter
   
   1. Cannot use because it "requires a standard LPT1 port address which cannot be assigned with a USB adapter"

eZdsp TMS320F2812
http://www.spectrumdigital.com/ezdsp-f2812-for-tms320f2812-dsp-power-supply-code-composer-studio-for-c28xx/

Error List:

****************Error message that was received using the XDS100v2***********************************

[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\aawrigh\AppData\Local\TEXASI~1\

    CCS\ccs1000\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 test for the JTAG IR instruction path-length failed.
The many-ones then many-zeros tested length was 32 bits.
The many-zeros then many-ones tested length was -2048 bits.
The test for the JTAG DR bypass path-length failed.
The many-ones then many-zeros tested length was 2048 bits.
The many-zeros then many-ones tested length was -2037 bits. 

-----[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.
Test 1 Word 0: scanned out 0xFFFFFFFF and scanned in 0xFA800000.
Scan tests: 1, skipped: 0, failed: 1
Do a test using 0x00000000.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFC003.
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.

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: 2
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 3
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 4
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 5
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 6
Some of the values were corrupted - 83.6 percent. 

The JTAG IR Integrity scan-test has failed.

-----[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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xE3EA0000.
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]

****************Error message that was received using the XDS200*********************************** 

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\aawrigh\AppData\Local\TEXASI~1\

    CCS\ccs1000\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Feb 13 2020'.
The library build time was '17:48:35'.
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 '13' (0x0000000d).
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]-----------------------------

This emulator does not create a reset log-file.

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

This error is generated by TI's USCIF driver or utilities.
The value is '-230' (0xffffff1a).
The title is 'SC_ERR_PATH_MEASURE'. 

The explanation is:
The measured lengths of the JTAG IR and DR scan-paths are invalid.
This indicates that an error exists in the link-delay or scan-path. 

[End]