Apalis iMX8QM Asynchronous SError Kernel Panic because of dm-verity secure boot and mender ota

I understand this is a critical situation. If the module won’t enter recovery mode and the UART console is completely blank, this suggests the bootloader may be corrupted or the module is in a locked state.

Recovery Mode Entry for Apalis iMX8QM

Based on the Apalis iMX8X documentation (which shares similar recovery procedures with iMX8QM), here’s what you need to do(1):

Hardware Recovery Method

  1. Locate the recovery mode pads on the bottom of the Apalis iMX8QM module(1)
  2. Power off the module completely
  3. Short the recovery mode pads using tweezers, scissors, or a jumper wire(1)
  4. While keeping the pads shorted, power on the module(1)
  5. Hold the short for 1-2 seconds after power-on, then release(1)

Important: The recovery mode pads must be shorted during the initial power-on (cold boot) of the module(1). Using reset won’t work.

Alternative Recovery Method (If Supported)

On some Apalis modules, you can also enter recovery mode by pulling up pin 63 (type-specific area) with a 1kΩ resistor while booting(1). However, this is not guaranteed to work on all modules.

USB Connection

Ensure you have the USBO1 interface (USB OTG) connected to your PC(1)(2). This is the interface used for recovery mode flashing.

Troubleshooting Your Specific Issue

Based on your screenshot showing the module is detected but not entering recovery properly, and the community experience with similar issues(3):

1. Verify Hardware Version

Check your Apalis iMX8QM hardware revision. According to a community report, hardware version 1.0B is not officially supported(3). You mentioned you have V1.1, which should be fine, but verify this on the module label.

2. Try Linux Host Instead of Windows

Multiple users have reported that Windows 10 does not work reliably with recovery mode on iMX8 modules(3). Try using a Linux machine instead:

./recovery-linux.sh

3. Check for SD Card

Ensure there is no SD card inserted in the carrier board(1). The presence of an SD card can prevent proper recovery mode entry.

4. Verify USB Connection

  • Use the correct USB port (USBO1/OTG on Ixora carrier board)
  • Try a different USB cable
  • Try a different USB port on your PC
  • Ensure the USB connection is USB 2.0 High-Speed compatible

5. Power Cycle Completely

Since you erased the eMMC boot partitions, the module may be in an undefined state. Try:

  1. Disconnect all power (including USB)
  2. Wait 30 seconds
  3. Short the recovery pads
  4. Connect power via the main power supply (not just USB)
  5. Then connect USB
  6. Release the recovery pads after 2 seconds

If Recovery Mode Still Fails

If the module absolutely won’t enter recovery mode and the UART is blank, this suggests:

  1. The SCFW (System Controller Firmware) may be corrupted - This is the lowest-level firmware and if damaged, the module won’t boot at all
  2. The module may be in a locked state - Though you mentioned you haven’t fused yet, some secure boot operations can lock the module

Last Resort Options

  1. Contact Toradex Support directly - They may have specialized recovery tools for completely bricked modules
  2. Check if RMA (Return Merchandise Authorization) is necessary - If the module is truly unrecoverable, Toradex support can evaluate replacement options

Critical Reminder

For future development with Secure Boot and dm-verity, always test on a separate development module first before deploying to production hardware. Keep at least one module in a known-good state for recovery purposes.

Could you confirm:

  • Which exact hardware revision is printed on your Apalis iMX8QM module?
  • Are you using a Linux or Windows host for recovery?
  • Do you see any LED activity on the module when you attempt recovery mode?
  • Is the UART console completely silent, or do you see any output at all during power-on?

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.