F28M35xx ControlCard won't work with DRV8312EVM

Hi Mitch,

I am moving your question to the C2000 microcontroller thread. The team there is best suited to assist you.

Hi Mitch,

There are few thing that you'll have to take care of:

1. The hardware i.e. is it proper and wrt to design sheets provided by TI esp. the JTAG portion.

2. The voltage levels at specific TP (test points)

Before doubting the software portion (i.e. CCS) please check out the hardware part thoroughly.

Also try one more thing, try programming the custom board using CCS Uniflash utility.

Regards,

Gautam 

This is a T.I. designed controlcard plugged into a T.I. designed evaluation board on which I am running (in the case of the blinky code and other examples I've tried) T.I. evaluation software.  This should plug and play and I should not have to debug hardware, unless it is to set switches that may be in the wrong position.   Since for code download and debug purposes the DRV8312EVM board is really only supplying power,  It seems that it comes down to a question of what is wrong with the controlcard.   I see no user settable switches on the control card so it must be a matter of firmware/software, or the card is bad, in which case I need T.I. to replace the card. 

Mitch

Mitch,

I know this combination works as VisSim has a really nice demonstration of a hosting a web page on the M3 side which allow UI to send commands to the 28x side for PM Sensorless control of the DRV8312.  I've sent this post over to the guys who use the 28M35 controlCARD more often than I do.

Mitch,

I would make sure the left-most switch on SW3 in toggled up on the controlCARD.  This will enable the JTAG connection to the device. 

I would also make sure that both LD4 and LD1 on the controlCARD are on as you are trying to connect (both the mini-USB connector on the cCARD and the baseboard must provide power to the cCARD in order for everything to work.

A document describing the cCARD, its schematics and its design data can be found in controlSUITE:
\controlSUITE\development_kits\~controlCARDs\CCF28M35xxHWdevPkg_v2\


Thank you,
Brett

Brett,

Left most switch in SW3 is up; LD4 and LD1 are on.  

When I run click 'Test Connection' in the .ccxml file of my custom code it runs through the test and appears to complete successfully, suggesting the communication with JTAG is there.  I'll list the output at the end of this post.  However, when I try to debug my code, it hangs at 'OnTargetConnect()'. 

As mentioned before, when I try to debug one of the example programs such as blinky_c28, it fails with the following message (repeated from earlier but with additional detail):

Error connecting to the target:
(Error -1135 @ 0x0)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.

When I try to run blinky_m3 it says: "the project blinky_m3 is not compatible with any CPU in the target system"

Can someone at T.I. replicate this setup and verify that your F28C35xx controlCard plugs and plays and runs blinky_c28 and blinky_m3?  If it won't run these, can you please detail what you had to do to get it to run these.  If it will run these, then I'll conclude I have a bad card. 

Here is the result of pressing the 'Test Connection' button in the target configuration:

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\MITCHH~1\AppData\Local\.TI\693494126\
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 'Apr 1 2013'.
The library build time was '23:55:08'.
The library package version is '5.1.73.0'.
The library component version is '35.34.40.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 512 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 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 512 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 512 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.

OK, it works now.  The previous controlCard (F28069) required only building the code and then running from debug.  By following all the steps in the UG I have it working.  Thanks for the help.

Mitch