• Locked Locked
  • Replies 25 replies
  • Subscribers 32 subscribers
  • Views 3794 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DRV8312EVM kit stopped working?

Kustaa Nyholm
Expert 2005 points
Other Parts Discussed in Thread: DRV8312, INSTASPIN-BLDC, CONTROLSUITE, TMS320F28035, DRV8412

I had the DRV8312EVM kit running on my desktop and with my motor. I needed some compressed air to to cool the motor so I unplugged everything and moved over to an other desk and rewired everything, and now I cannot get the Instspin BLDC to connect to the kit. In Windows device manager I see that the kit appears as COM5 (and it disappears if I unplug the USB cable). With the connection Wizard I've tried to create a new connection but that fails with and error message/dialog. I've rechecked everything mentioned in the "DRV8312 InstaSPIN -BLC Quick Start Guide" and only thing that is missing is that the LD3 (Red) on the control card is not blinking but is off. Have I managed to corrupt the Flash on the board or something....?

br Kusti

  • TI__Mastermind 21805 points

    Kusti,

    Please unplug the EVM from both the power supply and the computer. Then switch SW3 on the control card (just change it, it does not matter right now what position it was at). Re-plug in the power, and then the USB. Since SW3 controls how the CC2835 initializes, it may help to change modes.

    You need to have the red light on the control card blinking for the GUI to be able to connect to the EVM.

    Please keep me posted on your progress.

    Thanks,

    Matt

  • in reply to Matt Hein
    Expert 2005 points

    Hi Matt,

    thanks for answering.

    The SW3 was in top position (ON i guess). Did as you said, unpowered / unplugged, changed the switch. Tried both switch orientations

    several times. Nothing change, get no blinking LD3 any which way....

    br Kusti

  • in reply to Kustaa Nyholm
    TI__Mastermind 21805 points

    Kusti,

    Can you re-flash the firmware onto the CC2835 using CCS? I find it unlikely but possible that you corrupted the flash memory. If you need help doing this I can walk you through the steps.

    Thanks,

    Matt

  • in reply to Matt Hein
    Expert 2005 points

    Ok, but need to get back to this on Monday.

    Is the procedure described somewhere, I've got CCS 5xx installed... (free license atm)

    br  Kusti

  • in reply to Kustaa Nyholm
    TI__Mastermind 21805 points

    Kusti,

    In order to re-flash the control card, follow the following steps:

    1) Open CCS and open up the InstaSPIN-BLDC_GUI_DRV8312_v104.out file found in \ti\controlSUITE\development_kits\DRV8312-C2-KIT_v128\~GUI

    2) Select View -> Target Configurations and a side window should open

    3) Right-click on User Defined, select New Target Configuration, and press Finish

    4) Make sure the Connection is set to Texas Instruments XDS100v1 USB Emulator

    5) Select the Board or Device as Experimenter's Kit - Piccolo F28035, and save the configuration

    6) Press Test Connection and verify that the device communicates properly.

    7) Press Debug, if necessary select Run -> Connect Target

    8) Run -> Load -> Load Program

    Thanks,

    Matt

  • in reply to Matt Hein
    Expert 2005 points

    Hi Matt,

    I followed your instructions, and when I get to the point 6 and click the Test Connection I get:

    [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\nyholku\AppData\Local\.TI\213602635\

        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 30 2012'.

    The library build time was '22:52:27'.

    The library package version is '5.0.747.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]

     

    And when I try Connect Target I get:

     

    Error connecting to the target:

    (Error -1041 @ 0xFFFFFF87)

    The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.

    (Emulation package 5.0.747.0)

    Looks like I need a kit or controlCARD, eh? Do you think the problem is with the controlCARD or

    the baseboard?

    br Kusti

  • in reply to Kustaa Nyholm
    TI__Mastermind 21805 points

    Kusiti,

    I don't think the hardware is the problem right now.

    Try unplugging everything, then switching SW3 to the DOWN position.

    I tried on my EVM and found that when SW3 is UP, then I get the same error as you when I Test Connection. Making SW3 DOWN seemed to solve the issue on my computer.

    I'm curious if this is the same problem you are seeing.

    Thanks,

    Matt

  • in reply to Matt Hein
    Expert 2005 points

    Hi Matt,

    thanks but did no change anything, I still get the same failure (see below) when I test the connection.

    BTW The following LEDs are ON (and only them)

    controlCARD

    LD4

    base board

    /OTW (amber)

    /FAULT (red)

    12V (green)

    5V (green)

    PVDD (green)

    br Kusti

    [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\nyholku\AppData\Local\.TI\213602635\
    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 30 2012'.
    The library build time was '22:52:27'.
    The library package version is '5.0.747.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]

  • in reply to Kustaa Nyholm
    TI__Mastermind 21805 points

    Kusti,

    That is very concerning that LD1 is not lit. Even more so, you are throwing both over-temperature and over-current faults at the same time.

    Please unplug the power connector and USB, then remove all outputs (the motor) from the main board. Remove the control card, and plug in the power connector again.

    I want to see if /OTW and /FAULT are still asserted.

    Thanks,

    Matt

  • in reply to Matt Hein
    Expert 2005 points

    Unplugger power and USB cables, removed controlCARD, re-powered the base board, still the same LEDs are on.

    br Kusti

  • in reply to Kustaa Nyholm
    TI__Mastermind 21805 points

    Kusti,

    From what you describe to me, it looks like the IC has suffered a catastrophic ESD event. If LED10 and LED11 are not lit, then you are not getting 3.3V out of the regulator. It seems like there is a PVDD-GND short inside the chip. Can you attach an external supply to the EVM instead of using the provided power source? I am curious regarding the current consumption.

    If you do have a bad IC, I have two suggestions for you:

    1) Order free samples of the DRV8312 (under Sample & Buy), and replace the chip on the EVM.

    2) Attempt to RMA the board here, and please include me under "Send a Copy of This Issue" (m-hein@ti.com) so I can keep track.


    Thanks,

    Matt

  • in reply to Matt Hein
    Expert 2005 points

    Ok, thanks Matt, will try to get a new kit. 

    br Kusti

  • in reply to Kustaa Nyholm
    Expert 2005 points

    Ok, hope this thread is still alive!

    Finally got the new kit but meanwhile I had to move to other tasks. Now back to this project.

    So, got the new kit, followed the instruction to the T on two computers, everything looks good:

    The Insta-SPIN-BLCD software is running, bottom row shows connected,

    the GuiSpeedRPM graph is running/updating, all the correct LEDs are on

    LED1,LED2,LED3,LED10 and LED11on the baseboard are lit green,

    LD1 and LD2 are lit and green on the controller board and

    LD3 is blinking slowly red.

    BUT

    When I enable the motor, nothing happens.

    All the time the DC Bus gauge show full scale red and the number below is 177.61

    Motor speed display shows 70363

    Motor curretn shows -86.28

    So stuck again, I'm afraid.

    br Kusti

  • in reply to Kustaa Nyholm
    TI__Guru 55615 points

    Kusti,

    Your problem is most likely because of a mismatch between the firmware in the micro-controller and version of the GUI.  What is the version of the GUI you are using?

  • in reply to Ryan Kehr
    Expert 2005 points

    Hi Ryan,

    thanks for answering.

    The exetable file name is 'InstaSPIN-BLDC_GUI_DRV83xx_v104.exe'

    and the 'About' dialog shows:

    Interface Designer version: v1.11.7246

    Framework version: v1.11.7295

    Component version: v1.11.7296

    Engine version: v2.2.7294

    Commros version: v.0.0.0

    I think you maybe right about the incompatibility, as firmware is the one thing I've not been able to check

    and which could be different from the previous setup. 

    br Kusti

  • in reply to Kustaa Nyholm
    TI__Guru 55615 points

    Kusti,

    There should be a ".out" file on the memory stick that shipped with your kit.  The filename and version should match the GUI.  Please try to reflash the controlCARD with this version of .out and all should be well.

     

  • in reply to Ryan Kehr
    Expert 2005 points

    Ryan,

    on the memoir in a top level girectory named 'GUI' I have:

    DRV8312GUIv5.exe

    DRV8312GUIv5.out

    InstaSPIN-BLDC_GUI_DRV83xx_v104.exe

    InstaSPIN-BLDC_GUI_DRV8312_v104.out

    readme.txt

    when I run the DRV8312GUIv5.exe I can get the motor running and everything seems

    AFAIU correct, this is not insta spin but proves that the hardware works.

    The read me says:

    GUIv1.out was flashed for kits that shipped with RevF DRV8312 baseboards

    Only the GUIv1.exe will work with this flashed .out

    GUIv2.out and .exe can and should be used with all kits


    To re-flash the controlCARD follow CCSv4HowToFlashcontrolCARDS.txt in

    this same folder InstaSPIN-BLDC added 9/9/11 Requires InstaSPIN-BLDC DRV8312 .out

    Ok, so time to reflash, spent the better part of morning downloading and installing

    CCSV4 but lets no go into that.

    Next I go and read 'CCSv4HowToFlashcontrolCARDS.txt'

    which says

    power board, connect USB JTAG, launch CCSv4

    ----- delete all other projects (right click, delete)

    --- view -> targets -> user defined make sure xds100-f28035[default] make sure no targets under projects folder

    --- launch debug (green bug) connect target target -> load program 2xPM_Motors.out

    ------ terminate all controlCARD is now flashed

    ----- power cycle before connecting GUI

    Try to follow the instructions but they are not quite correct it seems.
    It says "delete all OTHER projects" which seems to imply that I should have
    one project left, which one is that? Try to find a project file that would make
    sense in this context, can't identify one. Never mind, feel my way around
    and create a new target configuration.  Could not find 'xds100-f28035'
    but guessed this is the correct one:
    Connection: Texas Instruments XDS100v1 USB Emulator
    Board or Device:  Experimenterd's Kit - Piccolo F28035 is the correct one. 
    Next it says in the instructions 'connect target' which I presume means
    'go to menu Target/Connect Target' and no physically connect target, as
    the next step 'load program' (presumably menu 'Target/Load Program...") is
    not available.
    Ok, so try the 'Target/Connect Target' but get this error message:
    C28xx: 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. (Release 5.0.429.0) 
    After power cycling the evaluation kit I get:
    C28xx: Error connecting to the target: (Error -1041 @ 0xFFFFFF87) The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation. (Release 5.0.429.0) 
    This is probably something totally trivial but the instructions
    seem a bit loosely worded so I don't seem to be able to get this
    work to be able to re-flash.
    This Code Composer 4.2.4.00033 
    br Kusti
  • in reply to Kustaa Nyholm
    TI__Guru 55615 points

    Kusti,

    There should be a switch in the top, middle of the controlCARD.  It is hard to read, but it is labeled "S3" or "SW3".  Flip that switch to the opposite direction of what it is now and the board should connect.  Flip to back after you program.

    I believe this is the issue. 

    So sorry for your trouble. 

     

  • in reply to Ryan Kehr
    Expert 2005 points

    Hi Ryan,

    good tip, though that did not solve the problem. 

    I've finally managed to solve the issue with a little help from your local distributors.

    The problem was, as I suspect all along, the instructions that were not precise and left room

    for interpretation. I'm sure for anyone who is familiar with this particular tool set and processor

    everything is crystal clear but for the newbie it does not work. Mind you I've used Eclipse for

    ten years daily and have been doing embedded stuff for the past 30 years.

    Ok, for posterity, here is what I need to do to update the Flash:

    First I created a brand new Target Configuration with

    "Connection: Texas Instruments XDS100v1 USB Emulator"
    "Board or Device: TMS320F28035"
    Note that was the only that worked for me and is, I presume, what 
    the instructions mean when they say
    'XDS100v1 and F28035'.
    Next I *right clicked* on that target configuration and selected 
    Launch from *that* pop up menu.
    Then I needed to open the Eclipse Debug view from the View menu,
    it did not appear automatically.
    Next from the displayed target configuration I selected this line:
    "Texas Instruments XDS100v1 USB Emulator_0/C28xx"
    none of the other lines worked for me.
    By right clicking that line and selecting 'Connect Target' from *that*
    menu I was able to get the target to connect after which the
    Load Program menu item in the Target menu was available
    and I was able to Flash the board.
    Now InstaSPIN works and I can hopefully get to work!
    Thanks for the great support but let me express an old
    mans opinion that while there are some good points in IDE
    environments these point and click stuff is responsible
    for a lot of unnecessary work and frustration.
    Instead of this exercise that took four TI employees
    and a week to untangle and sort out,
    not counting the people who created the UI for
    debugger and Eclipse and wrote the not so precise
    instructions for updating the Flash, how about a
    good old shell script or makefile that would have
    done the job in minutes and would have been correct
    because someone had used and debugged it ...
    just saying.
    thanks and cheers Kusti
  • in reply to Kustaa Nyholm
    TI__Guru 55615 points

    Kusti,

    Points well received and the instructions are certainly way over simplified. 

    Glad you are at least on your way.

     

  • in reply to Ryan Kehr
    Prodigy 160 points

    Now that it is mid-2014, it's sad that the kit I just received seems to still have bad instructions and still has the control board programmed incorrectly.  Could you guys at least have the proper instructions added as a drop-in sheet?

    I'm still trying to get past the issues provided by the fact that I'm a very new user to Code Composer, and it's now version 6 not version 4.  Apparently a number of menu items have changed names and locations.

    Is there a set of instructions that are known to work???

  • in reply to Mike Stevens1
    TI__Expert 8885 points

    Steven,

    DRV8312 kit's How to run guide porvides instructions for down-loading and running proejct files from CCS. While it's true that instructions are still showing CCS version-4, but if you follow carefully, you should be able to dwonload the program with latest CCS version.

    Best Regards

    Milan-Motor Applicaiton Team

  • in reply to Milan Rajne
    Prodigy 160 points

    Unfortunately, this response shows that you didn't read my posting in detail, and that you have not tried to run the 8412-c2-kit instructions (either the printed material OR the files on the USB stick OR the information TI has on the web).

    Please get a DRV8412-c2-kit and try to follow the instructions exactly as they are written.  They are incorrect.  They do not work.  It took 4 hours to get it working, and that only because there were 3 great emails from users pointing out the documentation errors and who provided corrections or clues on how to make it work.

    The instructions fail to mention that you MUST upgrade the control board software for it to work with the GUI, you have to change a switch setting on the control board to let the programming instructions work, selection information for setting up the command file are incorrect in that they don't match the choices provided by the software, and the instructions to figure out how to load the *.out file are not correct for CCS version 6.

    Before suggesting that users RTFM, you should try it yourself on a recent product and figure out why we are pointing out that the TI product isn't working "out of the box" like it should.

  • in reply to Mike Stevens1
    TI__Guru 55615 points

    Mike,

    I am sorry for your frustration and misunderstanding on our part.  The original thread you added to was for the DRV8312 kit, so I was also assuming (never a good thing) that you were using that kit instead of the DRV8412 which you mention in your last post. 

    I am glad you are on your way and I couldn't agree with you more on getting a recent kit in our hands and stepping through the instructions to make sure the documentation is updated properly.  This kit should work OTB and the last thing I want any of our customers to do is waste time during their evaluation of our parts.

    Please accept our apologies and let us know if you run into more trouble during your evaluation.

     

  • in reply to Ryan Kehr
    TI__Guru 55615 points

    Mike,

    As a follow-up to my last post, we have ordered a kit and stepped through the instructions.

    As you noted, we discovered that the code image on the C2000 was incompatible with the included Version9 GUI on the USB stick.  The "out-of-the-box" experience was certainly not good.  To resolve this, we are pulling all the kits out of stock and re-flashing the controlCARDs with the correct version 9 GUI.

    Also as you noted, the documentation for re-flashing the ControlCARDs is cryptic and dated.  We are in the process of fixing this documentation as well.

    Thank you for bringing this to our attention.