Reference Minimal Images don't boot on AM62S

Technical Support
, , ,
1

Hello,

I’m using a Verdin AM62S 512MB v1.1A with a Dahlia Board v1.1C.
Using the Easy Installer, I’ve tried loading several minimal reference images, including versions 6.8.2, 7.2.0 and 7.3.0, but none of them are booting.

You can find serial port output after resetting.

Are there any known compatibility issues with the hardware versions I’m using?

Thank you.

image
image633×506 96.4 KB

Reference Minimal Image (UPSTREAM) 7.2.0 (2025-04-02):

~ # [  251.251948] reboot: Restarting system

U-Boot SPL 2024.04-ti-g944dcad43b6c (Mar 28 2025 - 08:55:24 +0000)
k3_system_controller sysctrler: k3_sysctrler_start: Boot Notification response failed. ret = -110
Firmware init failed on rproc (-110)

resetting …

Reference Minimal Image 7.2.0 (2025-04-02)

U-Boot SPL 2024.04-ti-g944dcad43b6c (Mar 28 2025 - 08:55:24 +0000)
k3_system_controller sysctrler: k3_sysctrler_start: Boot Notification response failed. ret = -110
Firmware init failed on rproc (-110)

resetting ...

Reference Minimal Image 6.8.2 (2025-04-01)

~ # [  215.965823] reboot: Restarting system

PS: I have replaced the Verdin AM62S 512MB v1.1A with Verdin AM62D 1GB ET v1.1A (15190493).
AM62D boots as expected but ethernet port not functioning in Easy Installer nor Minimal Images. Anyway this is another issue. I need to work with SOLO version which I have no solution right now.

2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello,

Thank you for providing the details of your hardware and the serial output.

Based on the hardware version you provided (Verdin AM62S 512MB v1.1A with Dahlia Board v1.1C), these are known to be compatible and supported as long as you are using BSP 6.4.0 or newer, and Toradex Easy Installer 6.4.0 or newer. This applies to both the Verdin AM62 SoM and the Dahlia carrier board (Compatibility Guide).

The error you are encountering:

k3_system_controller sysctrler: k3_sysctrler_start: Boot Notification response failed. ret = -110
Firmware init failed on rproc (-110)
resetting ...

indicates a problem during the early initialization stage, likely related to device tree or firmware configuration.

Here are a few recommended checks and troubleshooting steps:

  1. Device Tree Configuration
    Ensure that the correct device tree is being used by your image for the AM62S + Dahlia board. For your configuration, you should see U-Boot set to use the Dahlia device tree, typically named:

    k3-am625-verdin-wifi-dahlia.dtb

    You can enforce this in the U-Boot prompt using:

    setenv fdt_board dahlia
setenv fdtfile k3-am625-verdin-wifi-dahlia.dtb
saveenv
boot

    (Device Tree Troubleshooting)

  2. Image Compatibility
    Double-check that the images you are installing are targeted for the AM62S SoM family, and specifically for the 512MB variant if there are multiple options.

  3. Image Version
    While you are using BSP 7.x images, ensure that you are not mixing old (pre-6.4.0) device trees or images in your boot media or recovery media.

  4. Erase and Reflash
    If you modified the boot environment or loaded other images previously, try using the Toradex Easy Installer to erase any persistent environment by flashing a “Blank” image first, then re-try flashing the reference minimal image.

  5. Carrier Board Placement
    Ensure the Verdin module is properly seated in the Dahlia carrier board.

If you follow the steps above and still observe the same error, please let me know if you made any custom modifications to the images or boot environment.

You can find all compatibility information here:

The device tree troubleshooting steps are further discussed here:

Let me know if you need guidance for setting device tree values or accessing the U-Boot prompt.

Best regards,
Toradex AI Assistant.

3

Hello @Fide,

Some of the very early Verdin AM62 Solo modules were equipped with a General Purpose SoC, which is not secure-boot capable.
This means that they need a different boot container (tiboot3) to boot.

As very few of these modules were shipped, we changed the default boot container selection to use the HS-FS (secure boot capable) on all AM62 modules.

You can still use the current images with your board, but you need to:

  • Download the image you want to install
  • Decompress it
  • Edit the image.json file, so that the 0071 entry under mmcblk0boot0 has the tiboot3-am62x-gp-verdin.bin filename:
                    {
                        "filename": "tiboot3-am62x-gp-verdin.bin",
                        "dd_options": "seek=0",
                        "product_ids": "0071"
                    },

This should work regardless of reference image used or Torizon OS.

Best Regards,
Bruno

1 Like
4

Hi Bruno,

Thank you for the instructions.
I will try them next week and let you know how it goes.

We are also expecting to receive two new Solo v1.1C units by next week.
Do these v1.1C units require the same modification, or are they already fine as they are?

Thanks.

5

Hello @Fide,

The V1.1C modules already have the HS-FS SoC, so they should work with images without the need for any modifications.

Best Regards,
Bruno

1 Like