Usb Client (Function) mode in bootloader

Technical Support
1

I have the Ixora board and i’ve configured it for OTG.

I am able to detect the Client mode via id pin and set up the controller. However, as soon as i do a soft reset of it, it kills Ixora completely. Had anyone else seen this kind of issue with Ixora OTG as client?

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

I’d be glad to help troubleshoot this USB OTG client mode issue with your Ixora board! To provide the most accurate guidance, could you let me know:

  • Which OS and version are you running? (e.g., Torizon OS 7.2.0, Yocto BSP 7, etc.)
  • Which Apalis module are you using with the Ixora carrier board? (e.g., Apalis iMX8QM, Apalis iMX6, etc.)

You can get this information by running the tdx-info command on your device. More details are available at: Getting Device Information with Tdx-Info | Toradex Developer Center

Background on Ixora OTG Configuration

Based on the Ixora datasheet, the USB OTG interface (X9) configuration is controlled by jumper JP2(1):

  • JP2 Open: X9 operates as OTG (can switch between host/client based on cable type)
  • JP2 Closed: X9 and X8 bottom connector are configured as HOST only

For client mode detection, the USBO1_ID signal determines the configuration(1):

  • When a Micro-A connector is inserted, ID pin connects to ground (host mode)
  • When a Micro-B connector is inserted, ID pin is unbiased (client mode)

The soft reset issue you’re experiencing during client mode operation could be related to power management, device tree configuration, or bootloader USB controller initialization specific to your module and OS version.

Common platforms to consider:

  • Hardware: Apalis iMX8QM, Apalis iMX6, Ixora Carrier Board
  • OS: Torizon OS 6/7, Yocto BSP 6/7
  • Integration: Device tree, USB OTG, bootloader configuration

Once you provide the platform details, I can offer more specific troubleshooting steps for your configuration.

Best regards, Toradex AI Assistant.

Did you like my answer? :+1: :-1:

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

3

Hi @kurt ,

Could you please specify what Apalis module you are using and version of the bootloader.
Please also describe a steps we can follow to reproduce your issue .
Could you also describe goals you want to achieve using client mode?

4

I am using IMX8QM 2GB IT.
I have a self-written UEFI.
The use of USB Client is as umbilical during board assembly and setup for custom product.
I would like to know what lies between the SoC pins and the Apalis connector, so I know if there are other electrical components on those wires. There is no schematic for the Apalis available publically. If i am under NDA do I get access to that?

5

Kurt,

The schematic of the SoM is proprietary and cannot be shared. However, most of the i.MX8QM signals are routed directly to the SoM X1 connector. You can find details about this in the module datasheet, either in the pin summary table or within the relevant interface chapters.

Alexander Samutin
Toradex