USB-C port not detected on PC when connected to Mallow carrier board

Hardware:

Mallow V1.1C carrier board

Verden iMX95 Hexa 8GB

OS:

Windows 10 (version 22H2)

Issue:

Connected USB-C cable from Mallow board (X8) to PC. Powered on Mallow board. Observed solid green LED. After ~5 seconds, observed 2 solid red LEDs.

There was no port detected on PC. Tried another USB-C cable with same result.

Objective is to Toradex Easy Installer to download a new package.

How do I connect the PC to the Mallow board to use Toradex Easy installer with USB?

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 understand you’re trying to connect your Mallow V1.1C carrier board with Verdin iMX95 to your PC to access Toradex Easy Installer. Let me help you with the proper setup.

USB Connection Setup

The USB-C connector X8 on the Mallow carrier board is the correct connector for recovery mode and Toradex Easy Installer access (1). This connector is linked to the Verdin USB_1 port and operates as a dual-role-port (DRP) for both host and client functions (2).

Recovery Mode Access

To properly enter recovery mode and access Toradex Easy Installer:

  1. Connect the USB-C cable to the DRP (X8) connector on the Mallow carrier board (1)
  2. Connect the other end to your Windows 10 PC
  3. Power on the board - you should see the Toradex Easy Installer interface

Power Supply Requirements

Ensure you’re using proper power supply connections (1):

  • Power input: Use connector X6 with a 12V 2A power supply (7-27V range supported) (1)
  • Check polarity: Ensure the power supply polarity is correct and within rating limits (1)

Troubleshooting Steps

Since you’re seeing solid red LEDs after ~5 seconds, this typically indicates a power or boot issue:

  1. Verify power supply specifications - ensure it meets the 7-27V requirement with sufficient current capacity (1)
  2. Check cable connections - ensure all connections are secure
  3. Try different USB ports on your PC
  4. Monitor the debug console if available for additional diagnostic information

Additional Connection Options

If USB connection continues to have issues, you can also:

  • Connect Ethernet cable to the GBIT ETH (X2) connector for network access (1)
  • Use HDMI output for direct display access (note: HDMI interface is compatible with Verdin iMX8M Plus modules) (1)

The network connection can provide DHCP and internet access for downloading packages through Toradex Easy Installer (1).

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.

What kind of port detection are you referring to? The behavior of this USB port depends on the software running on the module and its configuration.

If you want the USB port to act as a serial downloader for loading the Toradex Easy Installer over USB, the module must be placed into recovery mode. When the Toradex Easy Installer boots, it configures the port as RNDIS so you can access the Easy Installer GUI using VNC.

If any other image is running on the module, the USB port configuration will be determined by that specific image.

I ran the instructions for putting the module in recovery mode. I am still not seeing the any USB enumeration in device manager. I’m also not seeing any question marks around the USB Serial Bus Controllers that would indicate an unknown device is detected.

Do you have access to the Debug UART (X11 on Mallow board)?

We don’t have a cable to connect to X11. So it would need to be made. Is there any other way to get debug messages from the board? I thought the USB could be used for debug.

Yes, you can access the UART debug console through USB on many boards, such as the Dahlia or Verdin Development Board. However, the Mallow board requires a 1.8 V UART-to-USB adapter like this one

Ok, we’ll order this. But is there any other way to talk to the board before this comes in? I can’t get anything on the Mipi display (10.1” Toradex Capacitive Touch), HDMI or USB. So I don’t have a way to talk to the board.

All new Toradex modules are pre-flashed with Toradex Easy Installer. You can use the USB-C (X8) connector in RNDIS mode to access the graphical interface via VNC. Then if you flash Linus or Torizon you can use SSH to access its console.

I tried to connect on Windows side with USB-C (X8). But the connection shows up as UsbNcm Host device. So I need to change it to RNDIS mode. But how do I do this? I can’t do it from the Windows side, and I’m not sure how to do it on the Verdin side since I don’t have an interface to the Verdin side yet.

What software was running on the Verdin module? Was it the Toradex Easy Installer?
What PID/VID values were detected for the USB device?

I haven’t installed anything, so it should have Toradex Easy Installer installed. PID/VID values are:

Please try to update driver and select RNDIS
image

The USB is only showing up as a Composite Device. So I’m not able to select Remote NDIS Compatible device.

Would it make sense to have a call to discuss? What time zone are you in? Let’s set up a time to talk and you can call me at 760-695-8419.

Sorry for the confusion. Yes, when the Verdin iMX95 is running the Toradex Easy Installer, Windows should recognize it as a USB-NCM network device. You can ping it at IP address 192.168.11.1 and use a VNC client to access the Toradex Easy Installer GUI using the same IP address.

We were able to find the UsbNcm Host device and configure it. But now how do we get the Weston VNC backend started on the PC?

By running a VNC client like TightVNC or any other by your choice.

I keep getting multiple windows open when running TightVNC. Have you seen this before? I’m not sure what’s causing it.

Nope.

You mentioned earlier: ‘We were able to find the UsbNcm Host device and configure it.’
Could you describe exactly what configuration you performed?

In my experience, you simply plug in the board and open a VNC viewer — no additional configuration is required.

Could you describe exactly what configuration you performed?

I meant that I updated the driver in Device Manager like you suggested.