Apalis imx8qm container signature

Technical Support
, ,
1

hi everyone, mi using apalis imx8qm where do i find the output of the mkimage recipe so i can use it to sign the container(header offset and signature offset)?

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.

Looking at the mkimage output for Apalis iMX8QM, the header offset and signature offset information is displayed when you run the mkimage command(1).

Finding the Offsets

When you generate the OS Container Image using imx-mkimage, the output will show the offset information you need(1):

$ cd .../imx-mkimage/  
$ make SOC=iMX8QM flash_kernel  
...  
CST: CONTAINER 0 offset: 0x0  
CST: CONTAINER 0: Signature Block: offset is at 0x110  
DONE.  
Note: Please copy image to offset: IVT_OFFSET + IMAGE_OFFSET

(1)

Using the Offsets for Signing

The offset values from the mkimage output are then used in your CSF file for signing(1). For the OS Container Image example, these offsets would be used like this in your csf_linux_img.txt file(1):

[Authenticate Data]
# Binary to be signed generated by mkimage
File = "flash_os.bin"
# Offsets = Container header Signature block (printed out by mkimage)
Offsets = 0x0 0x110

(1)

The key information you’re looking for will be in the terminal output after running the mkimage command - specifically the “CONTAINER 0 offset” and “Signature Block: offset” values(1).

**

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.

3

im using the mkimage as yocto recipe so how do i see the output

4

I’d be glad to help! To provide specific guidance on viewing mkimage output from your Yocto recipe, could you let me know which OS and version you are using?

For example, are you working with:

Hardware: Apalis iMX8QM, Verdin i.MX8M Plus, Verdin AM62, Aquila AM69, or another module?

OS: Yocto 7.2.0, Torizon OS 6, BSP 7, BSP 6, or another version?

You can use the tdx-info command to get detailed information about your setup. More details are available at: Getting Device Information with Tdx-Info | Toradex Developer Center

Integration guidance varies significantly by platform, so confirming your specific setup will help me provide the most accurate instructions for accessing the mkimage recipe output and finding the header/signature offsets you need for container signing.

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.

5

Hi @anmsn44!

I saw you opened three threads about this issue. I’m kindly asking you not to do that, since it makes it difficult to prioritize and organize the support queue.

Not only that, but I saw that one of our engineers already started helping you in this thread. Please continue the support there.

Best regards.