Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
The NVFlash hanging issue you’re experiencing with your Apalis T30 V1.1b can be caused by several factors. Based on the information available, here are the main potential causes and solutions:
Recovery Mode Connection Issues
First, ensure proper recovery mode setup (1):
- USB Connection: Make sure you’re using a USB 2.0 High-Speed (480Mbps) connection (1). The recovery mode only works with USB 2.0 High-Speed (1).
- USB_DET Pin Issue: The USB_DET pin (SODIMM Pin 137) needs to be very close to 3.3V when entering recovery mode (1). If your customer board has high impedance voltage dividers, this can cause the recovery mode to fail (1).
Known NVFlash Issues
RAM Timings Problem
If you’re using NVFlash version 2.1 or 2.2, there’s a known RAM timings issue with Colibri T30 modules (2). While your issue is with Apalis T30, similar problems could occur. The issue was fixed in NVFlash version 2.3 (2).
Bootloader Initialization Hang
The fact that NVFlash hangs after “waiting for bootloader to initialize” suggests the bootloader is not responding properly after being downloaded to RAM.
Troubleshooting Steps
-
Verify Recovery Mode Entry: Ensure the module is properly in recovery mode by checking if it appears as an NVIDIA device:
lsusb | grep -i nvidia
Bus 002 Device 033: ID 0955:7130 NVidia Corp.
(3)
-
Check USB Connection: Use a different USB cable and ensure you’re connected to a USB 2.0 port (1).
-
Hardware Recovery Mode: Try entering recovery mode using the hardware mechanism by shorting the recovery pads on the module during power-on (1).
-
Update NVFlash: Use the latest NVFlash version (2.6 appears to be what you’re using, which should be fine) (2).
Possible Hardware Issues
Given that the module “suddenly stopped working,” there could be hardware damage:
- eMMC corruption or failure (4)
- Power supply issues
- Physical damage to the module
The fact that the chip information is being read correctly (chip id: 0x30, chip uid, etc.) suggests the SoC is functional, but there might be issues with the eMMC or other components.
Next Steps
- Try the hardware recovery mode method as described in the recovery mode documentation (1)
- Test with a different carrier board if available
- Verify the power supply is stable and within specifications
- If the issue persists, the module may have hardware failure and require replacement
The hanging at bootloader initialization typically indicates either a communication issue between the host and module, or internal module hardware problems.
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.
