Our board was modeled after the Development board and this has always worked. At first i thought it was Threatlocker because it stops everything, and there was a blockage, but that is not it as it was removed. Then I thought it was windows 11, but I tried a Windows 10 device and it still doesn’t work.
It used to be when the device was in recovery mode, you could hear the device show up in device manager and see the USB change. But now that only happens if i use a USB-C cable end to end. But it doesn’t make any difference, other than you see it show up in device manager. Is there a new driver I need to make this work?
Steve
Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
Recovery Mode USB Connection Issues
Based on your description of the USB connection issues in recovery mode, there are several factors to consider for proper recovery mode operation.
USB Cable and Connection Requirements
For recovery mode to work properly, you need to ensure you’re using the correct USB connection method (1). The recovery mode functionality requires USB 2.0 High-Speed (480Mbps) operation (1).
Important USB Cable Considerations:
- Many USB-C cables are missing data lines or are of poor quality (2)
- Try using a different USB-C cable to rule out cable issues (2)
- Ensure the cable supports data transmission, not just power delivery
Driver Requirements for Recovery Mode
For Tegra-based modules (Txx series), recovery mode requires specific APX drivers (1). When the module successfully enters recovery mode, it will show up as an APX device in Device Manager (1).
Driver Installation Process:
- Download the NVFlash / Recovery mode package which contains the required APX drivers (1)
- The driver works on both 32-bit and 64-bit Windows systems (1)
- When you see the APX device in Device Manager, update the driver by pointing to the usbpc_driver_32_64 folder inside the NVFlash package (1)
Recovery Mode Entry Methods
Ensure you’re properly entering recovery mode using one of these methods (1):
Hardware Method:
- Power off the board completely
- Short the appropriate recovery pins/pads
- Power on the board while maintaining the short circuit
- Remove the short circuit only after power-on
Software Method (if bootloader is accessible):
- Connect via serial console
- Enter the bootloader prompt
- Use the
enterrcm command for U-Boot (1)
USB Connection Verification
For proper recovery mode detection:
- Remove any SD cards from the carrier board (1)
- Ensure no other devices are connected to conflicting USB ports
- Check that the USB client port is properly connected to your development PC
Troubleshooting Steps
- Verify Hardware Setup: Compare your custom board design with the Development Board design resources (3)
- Test Cable: Use a known-good USB cable with confirmed data line connectivity
- Driver Check: Ensure the APX drivers are properly installed and associated with the device
- Recovery Method: Try both hardware and software recovery entry methods
If the device appears in Device Manager when using USB-C end-to-end but recovery functionality still doesn’t work, this suggests a driver association issue rather than a hardware detection problem.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
