M7 wakeup issue after doing DSM

Technical Support
, ,
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 your M7 wakeup issue after DSM (Deep Sleep Mode). To provide the most accurate guidance, could you clarify a few details about your setup?

Please provide:

  1. Which Toradex module are you using? (e.g., Verdin iMX8M Plus)
  2. Which OS and version are you running? (e.g., Torizon OS 7.1.0, BSP 6.x, etc.)
  3. Kernel version if available

You can get this information quickly by running the tdx-info command on your device. See tdx-info documentation for details.(1)(2)

Initial Observations:

The RemoteProc framework on i.MX8M Plus modules has known constraints regarding firmware loading, particularly:

  • Firmware binaries built with the NXP MCUXpresso SDK can fail to load through the Linux RemoteProc framework when the binary size approaches or exceeds 128 KiB(1)
  • The RemoteProc driver expects firmware in .elf format(1)
  • There’s a required kernel command line argument clk-imx8mp.mcore_booted=1 that must be set for RemoteProc functionality(1)(3)

Relevant Documentation:

For M7 management with RemoteProc on i.MX8M Plus:

Once you provide your platform details, I can offer more specific guidance for your DSM resume scenario.

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.