CCS/DRV8312-C2-KIT: Load Program Errors during Example Programs

Hi Anil,

It looks like the MCU (microcontroller unit) is not powered or in reset. Can you describe your setup a bit more? Which CCS version are you using?

I would highly encourage you to download and install controlSUITE. In there you will find useful information about this kit. The folder path is given below.

C:\ti\controlSUITE\development_kits\DRV8312-C2-KIT_v128\~Docs

Read through the How To Run Guide in the ~Docs folder and follow the steps to setup the board. When you get to the step 6, there should be a "Test Connection" button which you can use to verify if CCS can talk to your board. If it cannot, then we may need to debug further.

Hi Gus,

I already had controlSUITE installed and was using the examples in there to try out the board. I followed the steps described by controlSUITE but it led me to that error. I did test The connection but it did not give back any errors. I tried running the same BLDC_sensorless and was given the same errors as stated originally. I am currently using the lastest version of CCS.

Anil

Hi Anil,

>>The configured device (TMS320F28035), does not match the detected device ()

Can you confirm which controlCARD you are using?

Anil Sinha said:

I followed the steps described by controlSUITE but it led me to that error

Can you confirm LD4 (isolated JTAG) and LD1 (5V) on controlCARD, and LED1/LED2/LED3 on the DRV board are turned on?

Anil Sinha said:

I did test The connection but it did not give back any errors.

Can you post the results of the test?

Gus Martinez said:

Can you post the results of the test?

[Start: Texas Instruments XDS100v1 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\anils\AppData\Local\TEXASI~1\CCS\
ccs1010\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 'May 7 2020'.
The library build time was '21:10:18'.
The library package version is '9.2.0.00002'.
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 succeeded.
The JTAG IR instruction path-length is 38 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 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.
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 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 XDS100v1 USB Emulator_0]

Gus Martinez said:

Can you confirm which controlCARD you are using?

The controlCARD is Piccolo TMDSCNCD28035MISO controlCARD.

Gus Martinez said:

Can you confirm LD4 (isolated JTAG) and LD1 (5V) on controlCARD, and LED1/LED2/LED3 on the DRV board are turned on?

That is kinda interesting cause LED1 is solid green, LED2 randomly turns solid red (I haven't figured out the conditions for when the 2nd one turns on), LED3 is flashing red. I just checked the controlCARD and whatever has a switch, is flipped to ON.

Hi Anil,

Anil Sinha said:

That is kinda interesting cause LED1 is solid green, LED2 randomly turns solid red (I haven't figured out the conditions for when the 2nd one turns on), LED3 is flashing red. I just checked the controlCARD and whatever has a switch, is flipped to ON.

There is more information on the LEDs and switches of the controlCARD in the F28035 Info Sheet.

C:\ti\controlSUITE\development_kits\~controlCARDs\CC2803xISOHWdevPkg\F28035_ISOcontrolCAR-InfoSheet.pdf

LD2/LD3 are controlled by GPIOs on the DSP. So if these LEDs are flashing it could mean the DSP is running some code out of flash.

Can you set SW2 to "Wait Mode"? That is Position_1 = 0, and Position_2 = 1. This should put the DSP in a loop & (maybe) LD2/L3 will stop flashing. Also, again verify that SW3 is set to ON position.

Hi Gus,

Spent basically the whole day trying various fixes from all over the internet. 

Gus Martinez said:

Can you set SW2 to "Wait Mode"? That is Position_1 = 0, and Position_2 = 1. This should put the DSP in a loop & (maybe) LD2/L3 will stop flashing. Also, again verify that SW3 is set to ON position.

I can confirm SW3 is ON. I flipped SW2 to "Wait" by position_1 = 0 and position_2 = 1.... It's still flashing....

I am starting to get a bit frustrated.... I spent nearly 3 weeks trying to fix this issue... Do you know if another board or method or something that will be better than trying to figure out this issue?

Anil,

So sorry that you haven't been able to get this board to work. One possibility is that the controlCARD may be damaged. Is this a new board or used? 

As a last resort I would recommend you check the DSP voltage, reset, and clock. The schematics for the controlCARD are included in the controlSUITE installation, but here are the relevant test points:

- TP1: 5V

- TP2: GND

- U9 pin 16: 3.3V

- C19/C20/C21: 1.2V

- R1: XRSN (reset, should be 3.3V)

- R4: 20 MHz Clock

You can use an oscilloscope (if you have one) to check all these signals. If not, a voltmeter can at least help you check the voltages.