Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 28 replies
  • Answers 6 answers
  • Subscribers 59 subscribers
  • Views 2196 views
  • Users 0 members are here
Related

Anything special to get USB to work on the side of the case?

garengllc

I have a Moto Z and was hoping to connect an RTL-SDR dongle to the side of the proto case.  I attempted to setup the dip switches to enable the USB 3.1 interface and connected a USB OTG cable, but the phone is still not recognizing the device (I am using the middle USB connection).  Is there something else that I am missing?

Parents
  • 0

    after fixing the app clear issue with MDK (so MDK works again) I can also not see the microOTG memory stick connected to microUSB B connector, do not know why.

     

    EDIT:

     

    moto-Z USB-C to usb host, USB3 Stick works (without MDK)

    moto-Z MDK mid USBC same cable same usb stick does not work

    moto-Z usb stick in microUSB does not work

     

    I guess the manifest may have to be changed??

  • 0 in reply to anttibrain

    Some notes on USB to try and answer several of the questions here.

    USB3 is literally just that, the USB3 PHY.  It does not include the additional lines for USB2 (those have their own dedicated interface).  You *may* look and find a device that will route USB2 traffic over USB3 for you, which would be handy in a dock type configuration.  Additionally, when using USB3.0, the MDK does not support reversible cables.  If your device does not enumerate, try flipping the cable.  The existing 'compute' example firmware has support for attaching USB3.0 devices to the middle port on the MDK.
    If it enumerates when attached to the Moto Z with an OTG cable, it should work through the MDK.  Please take a look at the new usb2 sample firmware posted for basic connectivity.  Please note that the MDK does not support hot plug detect for USB2.
    So if you didn't write any firmware with the USB-Ext protocol, that's probably a big reason why USB isn't working.  It's always good to attempt a direct connection to Moto Z with an OTG cable to ensure you understand that devices behavior when it enumerates.
  • 0 in reply to flowflow25

    Thank you and Christian!

     

    I realized that I was having issues with my Aukey USB-C to uUSB adapter -> uUSB OTG to USB -> thumbdrive USB 2.0 connection.  When I changed to a USBC USB OTG to USB -> thumbdrive USB 2.0 it was happy when plugged directly into the phone with no MDK.  So thank you for helping me to realize some sort of hardware issue on my side.

     

    I still have had no luck getting the thumbdrive to enumerate on the side of the MDK.  I have not touched the firmware on the MDK at all, is that necessary for just routing USB 2.0 through the MDK to the side, or only if I try to access the USB from the protoboard personality card?

  • 0 in reply to garengllc

    Read the response, the MDK USB connectors DO NOT AUTO DETECT usb devices !!!

     

    so you need to change the firmware!

  • 0 in reply to garengllc

    OK, it was still unclear to me before, but I think I've got it now (been reading up on it this morning).  I see the example talked about here: https://developer.motorola.com/build/examples/misc , but I don't see where the download that example.  I guess I am missing an SDK or something, I will go hunting for that now.

Reply Children
  • 0 in reply to garengllc

    The example is in nuttx/nuttx/configs/hdk/muc/

    You'll see the usb2 project here, and the stm32_usbext_usb2.c file in the src directory.

    You may need to do a 'git pull' on the nuttx repository, it was just pushed last weekend.

  • 0 in reply to flowflow25

    Thanks. I posted something on FRI about my steps, but it got attached further up in the thread where it is easy to overlook.  I managed to build and install the usb2 project to the MDK.  Through a lot of trial and error, I can get the USB 2.0 to work on the 3rd USB port on the side (the uUSB connector) if I set A3=ON and A4=OFF.  I thought that if I set A3=OFF and A4=ON that the middle USB port would work for USB 2.0, but I guess not...

  • 0 in reply to garengllc

    Actually that looks correct.

    USB on TypeC: A3 = off, A4 = on

    USB on microB: A3 = on, A4 = off

     

    1. Are you using an OTG cable with the TypeC port?  If not, you may try a Hub.

    2. Have you tried flipping the cable?

     

    I just verified here with the usb2 firmware and a USB2 device attached to a hub attached to USB2 (middle TypeC).  You may also use an OTG cable instead of a hub.  Did you move away from using USB3.1, or that was overkill?

  • 0 in reply to flowflow25

    I just tried A3 = off, A4 = on again and still no dice.  The USB-C on the bottom of the phone works, but the missdle USB port on the side does not.

     

    I am using an OTG cable with the TypeC port.

     

    I tried flipping the cable, still no love.....

    I moved away from 3.1.  I have a 2.0 device, so I needed to go that path. I was thinking that in 3.1 it would be backwards compatible, so I was interested in that route, but you explained why that isn't so.

     

    I obviously got the usb2 project loaded properly, but I cannot for the life of me figure out why the middle USB port won't work.

  • 0 in reply to flowflow25

    I also got the USB2 device to work using the USB2 firmware. However, when using the compute firmware on a USB3.0 type C flash drive it doesn't seem to detect it in the middle port no matter which way I turn it. Is there some way to debug it?

  • 0 in reply to kingstu

    I had the wrong dip switch settings. The USB 3.0 worked when I changed them appropriately.

  • 0 in reply to kingstu

    Stuart, I am curious.  Did you ever try (and succeed) at getting USB 2.0 to work on the type C connector on the side?  I for some reason never was able to accomplish that even though I could get it to work in the uUSB connector.

  • 0 in reply to garengllc

    I don't have any usb 2.0 devices with a type c connection. I have not had good luck with adapters so I try to match the device with the connector without adapters.

  • 0 in reply to kingstu

    Pretty sure I figured out the problem.  Long story short, there isn't power being applied to the TypeC port in the usb2 example firmware.  The microB always has power, hence isn't an issue.  And compute actually contains full support for hotplug detect through the fusb302 driver.  I dug through compute, and found that after performing the hotplug detect they explicitly enable power out Vbus.

     

    I realize when I tested this last week, because I didn't have a TypeC OTG cable I used an external hub...which was powered.  The easy fix for this is in the usb2_probe function, to enable VBus power out the USB Type C.  This is controlled by GPIO_MODS_VBUS_PWR_EN (PA11), and gpio_set_value(GPIO_MODS_VBUS_PWR_EN, 1) should provide power.  The best indication I have for this is my memory stick has a little light when it sees power.

     

    In stm32_usbext_usb2.c, add the following:

    #include <arch/board/mods.h>

     

    In usb2_probe()

        gpio_direction_out(GPIO_MODS_VBUS_PWR_EN, 0);

        gpio_set_value(GPIO_MODS_VBUS_PWR_EN, 1);

     

    In usb2_remove()

        gpio_set_value(GPIO_MODS_VBUS_PWR_EN, 0);

     

    This will turn on power to the external device on Mod attach, and turn it off on Mod detach.  In your actual application, it is important to keep in mind that USB is power hungry.  Only plan on having your USB-Ext device "attached" when it's actually functional.