• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 752 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/DRV8312-C2-KIT: What resource should I select in Resource Explorer to support this kit?

Christopher Ingraham
Intellectual 1000 points

Part Number: DRV8312-C2-KIT

Tool/software: Code Composer Studio

I wanted to try to re-flash the CC2803X Control Card that came with my kit to use the "InstaSPIN-BLDC-GUI-DRV8312_v104" so I tried to follow the getting started video for CCS.  Unfortunately, I could not find my kit in the list of kits and boards.  Nor could I find anything that seemed like it would be correct.  Exactly what do I need to do to get CCS7 configured to be able to flash my Control Card?

The kit is up and running properly as I have been able to spin the motor using the DRV8312GUIv5.exe that came with the kit.  So I believe all the drivers and software has been installed, I am just at a loss as to how to get CCS configured to recognize and talk to my kit.

  • 0
    TI__Guru**** 420930 points
    Hello,
    There is no specific target content available for C2000 in the new Resource Explorer. You can use the Resource Explorer Classic (View -> Resource Explorer Classic) to browse examples and documentation that come with controlSUITE (which supports your device): www.ti.com/.../controlsuite

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 1000 points

    Hello Ki,

    Thank you for the quick response!  I tried to use the "View->Resource Explorer Classic".  I browsed to "controlSuite->Development Tools->Motor->Three Phase BLDC Motor Kit with DRV8312 and Piccolo MCU->Example Projects->InstaSPIN-BLDC".  I successfully imported the project into CCS and then built it without error.  The next step "Debugger Configuration" is where I'm stuck now.  I tried all the XDS100 combinations that were available to me but when I try to "Debug the imported project" I get errors saying "Error connecting to the target".  It is acting like I'm not selecting the correct debug interface.

    I assume the only connection I need is the USB Cable connected between my PC and the CC2803x Controller card.


    Please let me know if you have any additional insight into this problem.

    Thanks,

    Chris.

  • 0 in reply to Christopher Ingraham
    TI__Guru**** 420930 points
    I think the Connection is XDS100v1 and the device is some F28035 variant. When you use the "Test Connection" option, what are the results of the test?

    Thanks
    ki
  • 0 in reply to Ki
    Intellectual 1000 points

    Hello,


    When I run the "Test Connection" I get the following output:

    [Start: Texas Instruments XDS100v3 USB Debug Probe_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\CHRIST~1\AppData\Local\TEXASI~1\
        CCS\ti\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 'jioserdesusbv3.dll'.

    An error occurred while soft opening the controller.

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

    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 be one or
    more of: no XDS100 is plugged in, invalid XDS100 serial number,
    blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
    Use the xds100serial command-line utility in the 'common/uscif'
    folder to verify the XDS100 can be located.

    [End: Texas Instruments XDS100v3 USB Debug Probe_0]

    I then tried to run the xds100serial command line utility as suggested, and it reported that No XDS100 emulators were found on the system.

    This is perplexing since my device manager clearly shows "TI XDS100 Channel A" and "TI XDS100 Channel B" under the "Universal Serial Bus Controllers section.  When I unplug the USB cable the TI XDS devices go away and when I plug the cable back in, the TI XDS devices come back.

    Chris.

  • 0 in reply to Christopher Ingraham
    TI__Guru**** 420930 points
    I assume you are using the on-board debugprobe. Are you plugged into the mini-USB connector on the control card? I think there may be some dip switches on the card that dictate which debug probe (onboard or external) you are using. You may want to check that. Sorry I can't give much concrete help - I don't have that target to confirm.
  • 0 in reply to Ki
    Intellectual 1000 points

    Hello Ki,

    Thanks for your help on this.  I did some digging around and, although I couldn't find it documented clearly anywhere, it appears that setting S3 to the down position was needed in order for the debugger to connect and communicate properly with the processor.  Even after I discovered this, there was still a great deal of instability in the connections, both for the debugger and serial connection used by the GUI interfaces.

    So, I decided to switch gears and install everything on my HP Laptop that's running Windows 10.  Up to this point, I've been trying to get things running in Windows 7 running under VMWare Fusion on my Macbook Pro.  Every now and then I run into a situation where some debugger/hardware platform has difficulty working reliably in my standard VM operating mode.

    Once I installed everything on my native Windows 10 machine, and made sure S3 was in the down position, the debugger connected and downloaded perfectly.  And as an added bonus, the GUI applications also worked while the debugger was running.  I could never get that far under my VM configuration.

    So, I'll just have to write this one off as yet another configuration that won't reliably work when running under VMWARE hosted operating systems.

    Thanks again for your help.

    Chris.