• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 624 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.

TM4C1290NCPDT: Help debugging USB interface.

Doug Broadwell
Expert 1175 points

Part Number: TM4C1290NCPDT

I have taken the usbserialdevice_DK_TM4C129X_TI example program and migrated it to my CPU.  When I run it the PC emits the error:

Log Name:     System

Source:       Microsoft-Windows-Kernel-PnP

Date:         6/19/2019 2:50:02 PM

Event ID:     219

Task Category: (212)

Level:         Warning

Keywords:    

User:         SYSTEM

Computer:     Dell-Server

Description:

The driver \Driver\WUDFRd failed to load for the device USB\VID_04A9&PID_3274\5&347fa542&0&3.

Event Xml:

<Event xmlns="schemas.microsoft.com/.../event">

<System>

   <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />

   <EventID>219</EventID>

   <Version>0</Version>

   <Level>3</Level>

   <Task>212</Task>

   <Opcode>0</Opcode>

   <Keywords>0x8000000000000000</Keywords>

   <TimeCreated SystemTime="2019-06-19T21:50:02.747124400Z" />

   <EventRecordID>14900634</EventRecordID>

   <Correlation />

   <Execution ProcessID="4" ThreadID="64" />

   <Channel>System</Channel>

   <Computer>Dell-Server</Computer>

   <Security UserID="S-1-5-18" />

</System>

<EventData>

   <Data Name="DriverNameLength">36</Data>

   <Data Name="DriverName">USB\VID_04A9&amp;PID_3274\5&amp;347fa542&amp;0&amp;3</Data>

   <Data Name="Status">3221226341</Data>

   <Data Name="FailureNameLength">14</Data>

   <Data Name="FailureName">\Driver\WUDFRd</Data>

   <Data Name="Version">0</Data>

</EventData>

</Event>

When I run the app on the DK_TM4C129X board it connects and works correctly.   My electronics is copied directly from the K_TM4C129X schematic.  Any ideas on tools/procedures to debug this would be appreciated.

Thanks.

  • 0
    TI__Guru*** 135355 points

    Hello Doug,

    I am not entirely following what you are trying to do, so let me clarify that first.

    You mention on one part that you migrated the example to your CPU and at another part that you have copied the DK kit schematics - do you mean then that you are trying to use this example with another TM4C device on a custom board you've had made - is that an accurate summary of the hardware setup?

  • 0 in reply to Ralph Jacobi
    Expert 1175 points

    Hi Ralph.

    Yes, I'm bringing up my board which has a TM4C1290NCPDT CPU.  The hardware USB interface I used is a copy of that used on the DK board.

    Doug

  • 0 in reply to Doug Broadwell
    TI__Guru*** 135355 points

    Hello Doug,

    Okay thank you for the clarification.

    It looks like you are using different descriptors than TivaWare's. If so, it may be your descriptors aren't being recognized as valid by the default Windows USB drivers. To check if this is the case, can you try using the TivaWare descriptors first? If they work, then we know the issue is with the descriptors.

    Keep in mind that you may need to manually direct the Device Manager to the latest TivaWare USB drivers when you make that adjustment to get the device to fully enumerate.

  • 0 in reply to Ralph Jacobi
    Expert 1175 points

    Hi Ralph,

    I haven't touched the descriptors, in fact have made very little changes to the software.  I know very little about USB, don't know whether to be looking at a hardware problem or a software problem.

    Doug

  • 0 in reply to Doug Broadwell
    TI__Guru*** 135355 points

    Hello Doug,

    Then the logs you posted aren't for your TM4C board.

    This line shows the VID/PID:

     <Data Name="DriverName">USB\VID_04A9&amp;PID_3274\5&amp;347fa542&amp;0&amp;3</Data>

    But if the descriptor wasn't changed, the VID should be 0x1CBE not 0x04A9.

    From googling, it looks like that is for a device called PowerShot G16: https://usb-ids.gowdy.us/read/UD/04a9?sort=rid

  • 0 in reply to Ralph Jacobi
    Expert 1175 points

    My apologies.  I assumed that the error message was from my board as I never see an error when I plug in my G16.  It seems that Win7 will display an error on the desktop but doesn't log any detail about the error.  I'll have to come up to speed on USB, check that the signals are correct, and go from there.

    Thanks,

    Doug