HAB4_IMAGE_VERIFIER(1)

💖 HAB4_IMAGE_VERIFIER(1) 💖

okay bestie so this is the i.MX CST documentation page for ahab_image_verifier and hab4_image_verifier — two tools that literally parse and verify AHAB and HABv4 images for secure boot on NXP i.MX processors. secure boot core, no cap 🔐✨

---

🌸 NAME 🌸

ahab_image_verifier, hab4_image_verifier — parse and verify AHAB and HABv4 images for secure boot on NXP i.MX processors 🦋

---

✨ SYNOPSIS ✨

AHAB

ahab_image_verifier [-h] [-b] image_file offset

HABv4

hab4_image_verifier [-h] [-b] image_file offset

---

📌 NOTE 📌

Heads up bestie, this manpage is just a short description of NXP's ahab_image_verifier and hab4_image_verifier. If you want the full deep-dive tea, go read the Code Signing Tool User Guide UG10106, sections 5.6 and 5.7 for usage, and the High Assurance Boot Version 4 API Reference Manual RM00298 section 4 for the structures contained in image_file. Both of those can be obtained from www.nxp.com and — plot twist 😭 — they're excluded from Debian for copyright reasons. so yeah, you gotta go get them yourself.

also, real talk: the ahab_image_verifier and hab4_image_verifier tools are intended solely for experimentation and debugging purposes. they are not the moment for production, okay? 💅

---

🫶 DESCRIPTION 🫶

So ahab_image_verifier and hab4_image_verifier parse and verify an AHAB or HABv4 binary image_file, where that image_file was previously generated with the cst tool. it's giving forensic detective energy 🔍

Then it prints out a readable representation of the IVT, the HAB commands, the SRK table, signatures, and verification errors if there are any.

offset specifies the offset in bytes from the beginning of image_file to the Image Vector Table (IVT). the IVT is the entry point for all the further processing — it's the main character of this whole operation, honestly 👑

---

💅 OPTIONS 💅

• -h — display a help message. your little cry-for-help button, love that for you 🎀
• -v — display version information. know which era of the tool you're in ✨

---

🚨 EXIT STATUS 🚨

ahab_image_verifier and hab4_image_verifier exit with 0 if the image is valid, or 1 otherwise. simple as that, no drama 🌈

---

🔥 EXAMPLES 🔥

say you wanna parse and verify an ELE firmware container in an i.MX 95 A0 AHAB image, where the image starts immediately with an IVT — here's the move:

ahab_image_verifier mx95a0-ahab-container.img 0

periodt. that 0 at the end is the offset, in case you were wondering 👀

---

👀 SEE ALSO 👀

cst(1), hab_csf_parser

---

and that's the whole page bestie!! this was the i.MX CST Documentation version of HAB4_IMAGE_VERIFIER(1), dated 2026-09-02 💜 go verify something and slay 💅✨🦋