• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 547 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.

CCS/OMAPL138B-EP: RNDIS initialization for a composite device

Arun M R
Prodigy 175 points
Part Number: OMAPL138B-EP


Tool/software: Code Composer Studio

I'm trying to develop an RNDIS device over USB (USB code got from starterware). I used  wireshark to understand the signal flow. After SEND_ENCAPSULATED_COMMAND Request is received from the host, I removed stall condition of USB and an acknowledgement is sent from the device. A response named RESPONSE_AVAILABLE should be sent from the device after acknowledging the SEND_ENCAPSULTAED_COMMAND Request. I tried to send response by calling a function USBDCDCSendDataEP0(which is used to send data to he host when a custom command is issued or non standard descriptor has been requested on endpoint0). By using wireshark I took the signal flow. But I notice that  RESPONSE_AVAILABLE is not sent.

How can I send that Response? Which function should be used to send these responses? Is there any more changes I should do in order to initialize RNDIS?

  • 0
    TI__Mastermind 27355 points

    Hello,

    We’re looking into this, but please note Starterware is legacy software so support may be limited.

  • 0 in reply to Sahin Okur
    Prodigy 175 points

    Sir,

    Thanks for the reply.

    I sent RESPONSE_AVAILABLE signal through interrupt transmission and a GET_ENCAPSULATED_RESPONSE request from host is received. But the problem now I'm facing is that this Non_standard request(GET_ENCAPSULATED_RESPONSE request) is not decoded properly inside the code. When verified through Wireshark the data was correct, but when debugging the code the data in END_POINT_0, inside the function "USBDReadAndDispatchRequest" is incorrect..

    Am I doing the correct way? What could I do to overcome this problem?

    Any advice is appreciated.

    regards,

    Arun M R

  • 0 in reply to Arun M R
    TI__Guru* 95265 points

    Arun,

    Sorry, this is a requirement of Ethernet over USB interface. It is typical done by USB CDC (communications device class) class. This is a new feature development. We don’t have USB CDC supported in the Processor SDK RTOS and can't provide further support of develop an RNDIS device from Starterware.

    Regards, Eric