HAB_INV_ADDRESSS when booting with HAB enabled in iMX8M Mini

[jmmorenog]

Hello, i am suffering some problems when i try to enable HABv4 on a Variscite iMX8M Mini board. I've manually build u-boot from the scratch following the full pipeline to generate the .csf files and attaching it to a flash.bin file. Despite that, I am getting this 2 hab events: 

U-Boot SPL 2022.04-64033-gf6390c6805 (Jan 29 2024 - 14:08:56 +0100)
SEC0: RNG instantiated
Normal Boot
Trying to boot from MMC1
hab fuse not enabled

Authenticate image from DDR location 0x401fcdc0...

U-Boot 2022.04-64033-gf6390c6805 (Jan 29 2024 - 14:08:56 +0100)

CPU: i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 49C
Reset cause: POR
Model: Variscite VAR-SOM-MX8M-MINI
DRAM: 2 GiB
Core: 73 devices, 23 uclasses, devicetree: separate
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
PTN5150: Vendor ID [0x3], Version ID [0x1], Addr [I2C1 0x3d]

Part number: VSM-MX8MM-501
Assembly: AS206185882
Production date: 2022 Aug 02
Serial Number: f8:dc:7a:8b:14:de
switch to partitions #0, OK
mmc1 is current device
flash target is MMC:1
Net: ADIN1300 PHY detected at addr 4
eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
u-boot=> hab_status

Secure boot disabled

HAB Configuration: 0xf0, HAB State: 0x66

--------- HAB Event 1 -----------------
event data:
0xdb 0x00 0x14 0x43 0x33 0x22 0x33 0x00
0x00 0x00 0x00 0x0f 0x00 0x7e 0x0b 0xc0
0x00 0x03 0xf8 0x00

STS = HAB_FAILURE (0x33)
RSN = HAB_INV_ADDRESS (0x22)
CTX = HAB_CTX_TARGET (0x33)
ENG = HAB_ENG_ANY (0x00)

--------- HAB Event 2 -----------------
event data:
0xdb 0x00 0x14 0x43 0x33 0x22 0x33 0x00
0x00 0x00 0x00 0x0f 0x00 0x7e 0x0b 0xc0
0x00 0x03 0xf6 0x60

STS = HAB_FAILURE (0x33)
RSN = HAB_INV_ADDRESS (0x22)
CTX = HAB_CTX_TARGET (0x33)
ENG = HAB_ENG_ANY (0x00)

Any ideas of why is this happening? thanks

[ricciolino]

Hi Jmmorenog,

I just reply to myself into this post.

I was suffering of your issue too and I was able to solve it by adding CONFIG_LTO=y to my defconfig.

You can check details in the post.

Hope this help you and others

[jmmorenog]

It seems there is a problem with the u-boot version of varisicite (lf2022), I've just tried to generate the flash.bin with the 2023 version and I got No hab events found message... may be a memory collision problem?

[ivan_choo]

Were you successful in resolving this issue?

[jmmorenog]

I updated the U-boot version to 2023 and the problem went away

[ivan_choo]

Did you end up using any Yocto build? And other such things from Variscite?

[jmmorenog]

I builded Linux kernel, rootfs, dtb and other non uboot related stuff with variscite yocto build. I builded uboot with variscite 2023 source code separatedly from yocto.

[storeopinion-ca-me]

The HAB events indicate a failure in secure boot, specifically HAB_INV_ADDRESS. This points to an issue with the addresses specified during the authentication process. Verify that the addresses in your Configuration Sequence File (CSF) align with the actual locations of the images in memory. Additionally, ensure the memory addresses used in the CSF match the addresses where the images are loaded.

Check if there are any discrepancies in the memory addresses or offsets in the CSF, and confirm that the images are correctly loaded into the specified locations in DDR memory. Also, verify the correctness of the CSF generation pipeline, ensuring it accurately reflects the memory layout.

If the problem persists, review the Habv4 documentation and seek support from Variscite or the community forums for more targeted assistance with your specific board and setup.