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.

USB Enumeration not working

Hi,

I want to develop USB firmware on 6748 . I have the sample code for the same. But going through the enumeration process I found the following sequence.

Reset signal from host then followed by Get_descriptor request again reset signal ,next the host send a set address request .

i hope this sequence is correct , but after getting the set address request the above sequence is repeating. Can anyone help me to solve the problem...?

Thank you.

  • Hi Tinu,

    The USB firmware for C6748 was already existing, you need not develop. It is enclosed in the C6748 starterware package. The enumeration sequence followed in the example is correct. You can refer to it for clarity.

    From the below link, you can download the  C6748 starterware package

    http://www.ti.com/tool/starterware-dsparm

    After you install the package, you will find the USB firmware sample example at path: "..\ti\C6748_StarterWare_1_20_04_01\usblib" and "C:\ti\C6748_StarterWare_1_20_04_01\examples\lcdkC6748"

    If you still have any questions, please do come back, I will help you.

     

    Regards,

    Shankari

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------

  • Hi ,

    Thank you for the replay. I got the code from the above link .

    In enumeration procedure its mentioned that after getting a SET_ADDRESS request we should wait for the Status stage to complete to the address. And for completring this stage we need to send a zero length  DATA1 packet, in response to the IN packet.

    while going through the sample code i cant see such a situation handling . I am asking bcz I am not getting a response after a SET_ADDRESS command.

    Thank you.

     

     

  • Hi,

    Thank you for your replay ,

    I installed the driver that mentioned in the above link. 

    I got the sample code from the above link. while running the code on my board my PC detecting the device. But by looking in the device manager its showing that  unable to load the Driver. why its showing like this..?

  • Hi,

    Thank you for your replay ,

    I installed the driver that mentioned in the above link.

    I got the sample code from the above link. while running the code on my board my PC detecting the device. But by looking in the device manager its showing that unable to load the Driver. why its showing like this..?
  • Hi Tinu,

    It is Good that you are able to detect the device bypassing the enumeration problem.

    Actually, in that package you will find three examples for Host side and three examples for Device Side.
    On which mode, you are using the C6748 LCDK board? either host or device? . Mention the name of the Host /device side driver.

    For example, consider you are using the C6748 LCDK board as Mass storage device ( running usb examples of mass storage ) and when you connect to a Host PC, the device manager of the host PC will detect the C6748 board as a removable media.

    Likewise, it depends on which USB example you are using on the C6748 LCDK board with appropriate jumper settings for Host and device mode.


    Regards,
    Shankari

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.
    --------------------------------------------------------------------------------------------------------

  • Hi ,
    thank you for the replay. I am using my board as device. Should I need to install any other driver..? If not where I should change the Name..? or what change i should make in my code.?


    Thank You.