Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

LAUNCHXL-F28377S: Problem with usb_dev_bulk example on the F28377S

$
0
0

Part Number:LAUNCHXL-F28377S

Hello!

I am trying to get the usb_dev_bulk-example with the LaunchpadXL-F28377S to work on Windows 10 x64. I should also note that  I am using a modified cable where D+,D- and GND are directly connected to Pin 9 (GPIO43), Pin 10 (GPIO42) and GND.

So far I can get Windows to recognize that something has been plugged in but it gets only identified as "Unknown USB Device (Device Descriptor Request Failed". While looking through this forum I have encountered various other threads about the same issue but with different devices. Most issues seem to boil down to driver related stuff. Here is a list of things that i have tried until now:

  • Turn off driver signature enforcement

  • device in device manager -> update driver -> pick folder "...\device_support\F2837xS\v210\F2837xS_common\windows_drivers". Result: Windows says that the best driver is already isntalled.

  • update driver and specifically pick usb_dev_bulk.inf. Result:

  • press windows+R, open open hdwwiz and open usb_dev_bulk.inf. Result: It is now possible to install the driver and after that it appears in the Device Manager but its still not working.

  • I have also tried the things above with the TivaWare 2.1.3 driver package from ti.com/tool/SW-TM4C

  • Accodring to this thread (e2e.ti.com/support/microcontrollers/c2000/f/171/t/554848) there is a bug in the v210 version of the dual core variant of my chip. However even after applying the suggested fix and also trying v200, v190 and v160 it still does not work

  • I can set a breakpoint rigth at the start of uint32_t RxHandler(void *pvCBData, uint32_t ui32Event, uint32_t ui32MsgValue,void *pvMsgData). After plugging the device in the breakpoint gets triggered only once and the data is as follows:

pvCBData = 0x8400

pvMsgData = 0x0

ui32Event = 7 (USB_EVENT_SUSPEND)

ui32MsgValue = 0xA53C

To me this looks like that data actually gets sent and the cable and hardware ports should be fine. 

  • I have also tried to run it on two other PCs (one with Win10 x64 and the other Win8 x64). Unfortunately rigth now I do not have access to run it on a x86 Machine because i am beginning to suspect, that the drive ris just not compatible on x64 or am I missing something else?


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>