TMDSHVMTRINSPIN and Code Composer, target

Anne-Marie Cressin

Other Parts Discussed in Thread: TMDSHVMTRINSPIN, TMS320F28069, MOTORWARE

Hi,

I just purchased the TMDSHVMTRINSPIN and am trying to experiment with the example labs.

Because I am using different control cards than the ones that are already "pre-loaded" in the example, the last stage, "Debug the imported project", is not working. I am trying to make a new configuration file to "28069MPZT".

I get errors when I do the general setup. Could you please check the settings:

1- the emulator selected is Texas Instruments XDS100v3 USB Emulator

2- the target is TMS320F28069.

This is the error I get: This error is generated by TI's USCIF driver or utilities.

The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:
One of the FTDI driver functions used during
the connect returned bad status or an error.
The cause may one or more of: invalid emulator serial number,
blank emulator EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the emulator can be located.

I may have erased the flash control cards by mistake, could you show me how to flash them to the proper image as well? I tried with the instructions provided "CCSv4HowToFlashcontrolCARDS.txt", but had issues as well, as it involves the same target configuration technique.

Could you please help me?

Thank you,

Anne-Marie

over 12 years ago

0 Anne-Marie Cressin over 12 years ago

Prodigy 155 points

I found the post "Target connection to JTAG of tmdshvmtrpfckit using CCS v5 failed", where they are having the same issues. I will try the suggested solutions of toggling the switches.

However, do you know if I should leave both USB connections on (1- from my computer to the JTAG emulator and 2-from my computer to the control card USB port)?

Also, I will add a jumper for J9 (as recommended in the post mentioned above), any other recommendations for the other jumpers that I may have missed?

Thank you

0 Nicholas Oborny over 12 years ago in reply to Anne-Marie Cressin

TI__Mastermind 21320 points

Hi Anne-Marie,

I am going to move your post to the C2000 forums. They will better be able to assist you.

0 Anne-Marie Cressin over 12 years ago in reply to Nicholas Oborny

Prodigy 155 points

So I have added jumper J9, and toggled SW1 to the down position and I am still unable to test the connection of the target configuration. I get the same error as on this other post "Target connection to JTAG of tmdshvmtrpfckit using CCS v5 failed" http://e2e.ti.com/support/applications/motor_drivers/f/38/t/210004.aspx

Here is the test log:

[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\TDREE~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 'Jan 21 2014'.
The library build time was '12:29:33'.
The library package version is '5.1.402.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 failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

-----[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.
Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF.
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 IR Integrity scan-test has failed.

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

Any help would be much appreciated, I cannot wait to get this kit working.

0 Brett Larimore over 12 years ago in reply to Anne-Marie Cressin

TI__Guru 57255 points

Hi Anne-Marie,

Can you let me know what controlCARD you are plugging into your TMDSHVMTRINSPIN baseboard? In particular I am trying to figure out if it is the standard controlCARD or the ISO controlCARD. It should say on the card itself (or you can let me know the TEX# which should also be written on the secondary layer of the board).

The proper setup is different between the two cards.

Thank you,
Brett

0 Anne-Marie Cressin over 12 years ago in reply to Brett Larimore

Prodigy 155 points

I am using the ISO control card TMS320F28069MPZT.

I have not tried the 28027 ControlCARD yet.

Thank you Brett,

Anne-Marie

0 Maria Todorova over 12 years ago in reply to Anne-Marie Cressin

Guru 13185 points

Hello,

About Texas Instruments XDS100v3 USB Emulator that you have chosen, should it be Texas Instruments XDS100v2 (not v3) USB Emulator?

Best regards,

Maria

0 Anne-Marie Cressin over 12 years ago in reply to Maria Todorova

Prodigy 155 points

Actually I have tried with both XDS100v3 USB Emulator and XDS100v2 USB Emulator, and testing to the connection targets failed both times.

When using the XDS100v2, this is the error I get:

Any help or suggestions would be much appreciated,

Thank you,

Anne-Marie

0 ChrisClearman over 12 years ago in reply to Anne-Marie Cressin

TI__Guru** 119680 points

This looks like a bad install of CCS to me.

I would re-install CCSv5.5

For TMDSHVMTRINSPIN, use TMDSCNCD28069MISO

TMDSCNCD28069MISO use the default switch settings on the controlCARD. U-U, D-D, U-U

From

C:\ti\motorware\motorware_1_01_00_11\docs\guis\hvkits_8312s_8301s\instaspin_foc\qsg_gui_instaspin_foc.pdf

d. HVMTR_r1p1 i. Populate: J3, J4, J5, J8,

ii. Populate: M3-J5 1. (turns OFF on-kit emulation so you can use controlCARD emulation)

iii. J7: Right-Middle (towards capacitors)

iv. Motor Phase Wires to U, V, W

v. J2 1. For DC bus input (recommended): Do NOT Populate J2 and a. connect 50-350V DC supply from BS6 to BS5

2. For AC input: Populate J2 Bridge-Middle

a. connect banana cable from BS5 to BS1

b. connect AC power cord to P1

3. DO NOT APPLY HIGH VOLTAGE AC OR DC UNTIL ALL CONNECTIONS ARE CHECKED, VERIFIED, AND YOU HAVE LAUNCHED THE GUI

vi. 15V DC power supply to JP1 and SW1 ON

0 Anne-Marie Cressin over 12 years ago in reply to ChrisClearman

Prodigy 155 points

Thank you for the response. I finally got the target board working today.

I toggled the switches back to the initial positions as suggested above (unlike what was suggested in a different forum post), and finally it worked after several trials. So I am not sure why it did not work initially but at least I can go on with experimenting with the board.

On a different note, I am having issues with Motorware identifying the AC induction machine, unless I solve that problem soon I post again.

0 ChrisClearman over 12 years ago in reply to Anne-Marie Cressin

TI__Guru** 119680 points

Anne-Marie,

There are known issues with motor ID for ACI motors in existing MotorWare revisions. These have been solved / fixed internally and will be in release _12 at end of February.

If you have a datasheet / nameplate I can post the forumlas which will allow you to update the USER_MOTOR parameters directly in user.h and bypass motor ID. That will allow you to keep working.

I will probably do this anyways on a new post...

0 Anne-Marie Cressin over 12 years ago in reply to ChrisClearman

Prodigy 155 points

Chris, I am using the standard ACI motor sold by TI: the Marathon Electric model 5K33GN2A.

Let me know if you need extra information, and thanks,

Anne-Marie

0 ChrisClearman over 12 years ago in reply to Anne-Marie Cressin

TI__Guru** 119680 points

Anne-Marie,

Ok. Usually that one identifiies ok, but it's not consistent. You can also just set this motor in user.h (the USER_MOTOR is filled out for this motor).

Ideally though you should read this post and go throught the process of double checking the numbers. I will do it myself for your motor (the one we sell as ti.com/tool/hvacimtr ) when I get a chance.

http://e2e.ti.com/support/microcontrollers/c2000/f/902/p/318299/1107337.aspx

0 Kurt Kloesel over 11 years ago in reply to ChrisClearman

Expert 1010 points

TMDSHVMTRINSPIN 'SC_ERR_FTDI_OPEN' error connection failure.

Dear Sir;

I have received a new TMDSHVTRINSPIN HV kit. I also have the following hardware:

TI Experimenter's Kit - Docking-Stn USB-EMU [R3]

TI Peripheral Explorer

Several Control cards:

F2802xx controlCARD (Piccolo-A) Release 1.0 with a F28027PTT chip

F28335 controlCARD Release 2.2 with a F28335ZJZA

F28069 controlCARD Release 1.1 with a F28069UPZPS

F2806x ISO controlCARD Release 0.4 with a F28069MPZT chip

My challenge seems to be the USB interface on the TMDSHVMTRINSPIN kit. I have successfully used the F28027, F28335 and the F28069 and F28069MISO controlCARDS in the Experimenter's kit and the Code Composer Studio, Version: 6.0.0.00190 communicates through the USB interface and I have successfully changed flashing speed on the "flashing light" program on all of these cards. However, the USB interface does not appear to be working on the TMDSHVMTRINSPIN and issues the TMDSHVMTRINSPIN 'SC_ERR_FTDI_OPEN' error connection failure. If I connect a scope to the any of the pins of the functioning Experimenter's kit, JTAG J2 Pins 1,3,7,9 (DIL-14) and run the XDS100v1 (or v2) "Test Connection". I get data signals. This is with the USB connected and SW1 powered by USB. However, if I run the same test on the TMDSHVMTRINSPIN, with the USB plugged in (M3 LD1 is on indicating 3V3_ISO is functioning). M6 is receiving external power (M6 LD1 is ON). The controlCARD (typically F28027 LD1 is also ON. Placing a scope on signals TMS-ISO, TDI-ISO, TDO-ISO, and TCK-ISO via M3-J2 jumper block (Pins 1,3, 7, 9) indicates no data signals at all referenced to the ISO ground. The following message is issued:

The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

I have also gone through the combinations of J9(TRSTn) and M3-J5 with no luck. USB Data-P and Data-M have signals. Can you help?

C2000™︎ microcontrollers

C2000 microcontrollers forum

TMDSHVMTRINSPIN and Code Composer, target