DRV8301-HC-C2-KIT: GUI not connecting

Thanks for the suggestion.

InstaSPIN-BLDC_GUI_DRV83xx_v104.exe looks to be the same version in both locations (flash drive and in controlSUITE location.)

Tried the one in controlSUITE with the same results.

Connecting the USB cable makes the sound as if it's connected and I can see it in Devices as Texas Instruments XDS100+R232 V1.0. The GUI is not recognizing that it's there. The instructions say that you can set it up manually by telling it which COM port it is set up as, but I am unable to get it from the device. If I click on it, it only gives me an option to remove it.

I was under the assumption that the .out was already preloaded. I'm new to how this works. I'm not sure how to load the .out. Help in that regard would be helpful.

I had to unhide hidden devices to see the COM port. Looks like it's COM9.

In doing some checking, it looks like the driver is not installing correctly. I have Windows 10, 64 bit machine. Tried uninstalling and reinstalling and still getting an error. "Windows found drivers for your device but encountered an error while attempting to install them."

The documentation says to: Do not let Microsoft search for the driver, instead browse to the following location on the USB stick shipped with the kit <Drive Name:\Drivers>,\

there is not a 'drivers' folder on the USB stick (flash drive).

I've tried finding the appropriate Windows driver on the ti web site with no avail.

Please help?

The UniFlash tool can't find the port either. I'm not sure why the USB port is not finding and/or installing the Windows driver. The first screen shot shows 3 Texas Instruments USB ports, the COM7 device is the one that goes with a LAUNCHXL device that I have and it works correctly. The COM9 device, I have now idea what it is associated with. The device with the error is the one associated with the device I'm trying to get up and running.

I removed both the COM9 device and the errored device and reattached the CRV8301-HC-C2-KIT USB, the results are shown in the second screen shot.

The COM9 was just showing up as a TI device. Not sure where it came from. It didn't seem to be the one I was having trouble with.
I haven't had the LP plugged in at the same time.
I will look at the other post that Tommy posted.

I am using CCS version 8.

Tried the MPROG tool and I am attaching a screen shot of the parsed data. Reprogrammed it, it gave a new serial number. Unplugged and plugged it back in. I am having the same problem. It makes a new device show up, but it still is not accepting the windows driver and generating a virtual COM port.

In the events tab for the device in my windows Device Manager is the following message:
Driver Management concluded the process to install driver xds100port.inf_amd64_0aa290ede59862c8 for Device Instance ID FTDIBUS\VID_0403+PID_A6D0+DR3HB1N0B\0000 with the following status: 0x2.
I don't know if this helps chase down what is going on.

Scott,

Whitney asked me to look into this some more from the emulations side; I'd like to make extra sure that the FTDI has the correct programmation.  I have attached a .txt file to this post, please rename the extension to .ept after you download it and then use it to re-program the XDS100v1 on the control card.  The method described by Tommy assumed that the correct v1/v2 driver was programmed but the COM port was wrong.  I'm wondering if you have the incorrect driver i.e. XDS100v2 driver was incorrectly programmed from the factory to begin with.  Let me know if this works.

[Basic Details]
Device Type=5
VID PID Type=1
USB VID=0403
USB PID=A6D0
[USB Power Options]
Bus Powered=1
Self Powered=0
Max Bus Power=200
[USB Serial Number Control]
Prefix=TI
Use Fixed Serial Number=0
Fixed Serial Number=12345678
[USB Remote WakeUp]
Enable Remote WakeUp=0
[Windows Plug and Play]
Enable Plug and Play=1
[USB String Descriptors]
Manufacturer=TI
Product=Texas Instruments XDS100+RS232 V1.0
[Programming Options]
Only Program Blank Devices=1
[BM Device Specific Options]
USB Version Number=1
Disable Serial Number=0
IO Pin Pull Down in Suspend=1
[Dual Device Specific Options A]
RS 232 mode=1
245 FIFO mode=0
245 CPU FIFO mode=0
OPTO Isolate mode=0
High Current Drive=1
[Dual Device Specific Options B]
RS 232 mode=1
245 FIFO mode=0
245 CPU FIFO mode=0
OPTO Isolate mode=0
High Current Drive=0
[Dual Device Driver Options A]
Virtual Com Port Driver=0
D2XX Driver=1
[Dual Device Driver Options B]
Virtual Com Port Driver=1
D2XX Driver=0
[R Device Specific Options]
Invert TXD=0
Invert RXD=0
Invert RTS#=0
Invert CTS#=0
Invert DTR#=0
Invert DSR#=0
Invert DCD#=0
Invert RI#=0
C0 Signal=-1
C1 Signal=-1
C2 Signal=-1
C3 Signal=-1
C4 Signal=-1
Enable Ext Osc=0
High Current I/O=0
Load D2XX Driver=0
In EndPoint Size=0

Just a quick note on SW3;   If you are only using the GUI to connect via the serial link SW3 = OFF is fine; but if we do manage to get the COM port in Windows device manager resolved and you still have communications issues then we may need to re-program the flash image on the F28035.

This would require connecting to CCS and to do so putting SW3 in the down/on is required, those steps are detailed in the How to Run Guide here: C:\ti\controlSUITE\development_kits\DRV830x-HC-C2-KIT_v105\~Docs\ if needed.

Best,
Matthew

Matthew,

I loaded in the ept file you gave me. It didn't make any difference. When plugging back in the USB cable, the windows notification popup in the lower right corner informing me that it's installing a driver and that it was successful. But in looking at the Device Manager, it shows that there was an error and no virtual COM port.

It looks like the only difference between what I had before and the new one was the serial number prefix.

Thanks for helping, but I don't think we're there, yet.

Scott

TMDSCNCD28035ISO.ccxmlScott,

No worries, will walk  you through it:

1)Under "View" select "Target Configurations" in the bottom section of the drop down

2)Right click in the Target Configurations window that just opened up and select "Import Target Configuration" and load the attached .ccxml

3)Right click on the TMDSCNCD28035ISO.ccxml you just loaded and select "Lauch Selected Configuration"

4)If the emulator portion of the FTDI is working this should bring up the Debug view with your .ccxml listed at the top and both a C28xx_CPU and CPU1_CLA debug probed listed below.  If this works then the emulation path is good

5)Now right click on the C28xx_CPU1 and click "connect"  

6)As long as there is no pop up error we are good(you should see the C28xx_CPU1 change from "Disconnected" to "Suspended".

Best,

Matthew

Matthew,

It worked as you described. What's next?

Scott

Scott,
Great, open this file: C:\ti\controlSUITE\development_kits\DRV830x-HC-C2-KIT_v105\~Docs\InstaSPIN-BLDC_Lab_sprabn7.pdf

This should guide you through some of what we already did, but the relevant section starts with step 11 on page 4. This is where we are going to "Reflash" the image on the device. The next steps after this attempt to connect with the GUI, so let's see if that fixes things.

Matt

Matt,
I don't have a 'Target' menu item. I've looked around in the menu system and can't find anything that looks like 'Load Program' either.
Thanks,
Scott

P.S. I did a search and found it. Trying it.