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.

OMAP-L138 TESTMODE register

Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Hi,

My customer is developping  OMAP-L138 for their new professional audio recorder.

Customer will plan to use USB1 port of OMAP-L138. But USB1.1 module does not have TESTMODE register like as USB2.0 module.

So customer asks me how to evaluate compliance test for USB1.1 port.

Does anyone know how to do it?

Best regards,

Michi

  • Dear Michi-san,

    Are you referring to the OHCI host controller available in L138? If so, its totally different from the MUSB controller which supports OTG. 

  • Dear Renjith-san,

    Thank you for your reply.

    My customer would like to know  how to do OHCI compliance test with OMAP-L138. Is that test big different from OTG?

    Could you do compiance test for OHCI controller with L138?

    Best regards,

    Michi

  • Michi-san

    USB 2.0 compliance test is different from USB1.1 compliance test. For example, to do the eye diagram test with USB2.0, you need to generate a certain test packet. For eye diagram test with USB1.1, you just need to capture the FS SOF. Please refer to the USB1.1 compliance test procedure: http://www.usb.org/developers/docs/USB-IFTestProc1_3.pdf.

    Thanks

    David

  • David-san,

    Thank you for your comment.

    I don't know L138 device well. Is the test mode register for USB2.0 used for making  certain test packet for eye diagram test?

    And then, according to your comment, customer does not need to generate eye diagram for USB1.1 compliance test. So L1238

    does not have test mode register for USB1.1.

    Is the above my understanding wright?

    Please advise me more.

    Best regards,

    Michi

  • Michi-san

    There are two USB PHY inside L138, a USB2.0 PHY with Mentor controller and a USB1.1 PHY with OCHI controller. The TESTMODE register is only associated with the USB2.0 PHY. When you want to run USB compliance test of the USB2.0 PHY, you would use TESTMODE register to put the USB2.0PHY into different test configuration such as TEST_PACKET for eye diagram, SE0_NAK, TEST_J, TEST_K, etc. The OHCI register is associated the USB1.1 PHY and responsible for putting the USB1.1 into test configuration for the compliance test. For USB1.1 PHY, you still need to do eye diagram, but eye diagram is based on SOF packet. For USB2.0 PHY, the eye diagram is based on a specified test pattern packet.

    Thanks
    David

  • Dear David-san,

    Thank you for your kindly support.

    I understood using SOF packet for USB1.1.

    I have one more question.

    Is there some sample source code that outputting the eye diagram of SOF packet continuously?

    Please advise me.

    Best regarads,

    Michi 

  • Michi

    I will start with the OMAPL138 StarterWare. Once OMAPL138 successfully enumerates a USB device, then it should generate SOF which can be captured using the scope. Please refer to USB FS compliance procedure for more detail on the test setup: http://www.usb.org/developers/docs/USB-IFTestProc1_3.pdf.

    Thanks

    David