• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 99 subscribers
  • Views 289 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.

DM365 IPNC-MT5 USB problem

tzvi reznick
Prodigy 130 points

I am trying to configure the USB on the Appro IPNC-MT5 to work as a Host or OTG.

The steps I took are:

1. I configured the kernel to be in OTG or HOST mode:

double checked with this page:

2. opened the case of the Appro cam and probed for voltage on VBUS
    when working in device mode I saw 5v on vbus.
    when configured to be OTG or HOST, did not get any voltage. 

3. The error that I get is : "VBUS error workaround", this error appears only after configuring the board to host or OTG, while I try to connect a device.

4. verified init code in the kernel code using gpio 33 configured as enable for 5v voltage.

    N2 pin should be ok as far as I understand according to the schematics.

5. Read the status from /proc/drivers/musb and sysfs and saw that I am configured as OTG and I am in HOST mode, as far as I understand everything is              configured correctly.

6. reviewed the following posts:

https://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/t/5812

https://e2e.ti.com/support/arm/sitara_arm/f/791/t/299887#pi316653=1

         https://e2e.ti.com/support/embedded/linux/f/354/t/109180 


can you please help with this issue ?

Thanks
Tzvi.

  • 0
    TI__Expert 8920 points

    Hi,

    Follow up questions from the PSP support:

    1. Is this issue seen when you have setup OTG mode and trying to switch to USB host or the basic USB host only mode without OTG is also not working?

    2. Has this issue been tested and observed on EVM also. If yes, we can try to reproduce if the steps are provided.

    3. If this issue is specific to the custom board, we would need the board to check the issue. Meanwhile, it will be helpful if schematics of the custom board is shared.

    regards,

    Anand