[R32.2.1] kernel boot failed

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

Hi,
I have developed a product using R32.2.1.
When writing firmware to Jetson TX2 in recovery mode
In rare cases, the following issues occur.

[issue]
boot does not start.
The log at that time is as follows.

[0002.927] I> T18x: Authenticate boot.img (bin_type 24), max size 0x4000000
[0002.935] I> T18x: Authenticate tegra194-p2888-0001-p2822-0000.dtb (bin_type 21), max size 0x100000
[0002.944] E> AES verification failed for header 1
[0002.949] E> Kernel-dtb: authentication failed
[0002.953] E> kernel boot failed

This issue does not usually occur.
Is this a hardware issue with the Jetson TX2?
Or is it a bootloader issue?
Could you please tell me the cause?

I will attach the UART log when a issue occurs.
ng_log.txt (12.0 KB)

3

No, just you flashed the wrong board config to your board… tegra194-p2888 is jetson AGX…

4

thx reply.

your board… tegra194-p2888 is jetson AGX…

The board is definitely Jetson TX2.
Below is the log of burning the same firmware on different Jetson TX2.

I> Kernel hdr @0x80400000
I> Kernel dtb @0x80000000
I> T18x: Authenticate boot.img (bin_type 24), max size 0x4000000
I> T18x: Authenticate tegra194-p2888-0001-p2822-0000.dtb (bin_type 21), max size 0x100000
I> Checking boot.img header magic … [0002.707] I> [OK]
I> Valid boot.img @ 0x80400000
I> decompressor handler not found
I> Copying kernel image (477378 bytes) from 0x80400800 to 0x80800000 … [0002.724] I> Done
I> Move ramdisk (len: 0) from 0x80475800 to 0x94830000

In the same way, [tegra194-p2888-0001] is displayed.

5

  1. Can you try to flash the board with sdkmanager?

  2. Is it a custom board or devkit?

  3. Rel-32.2.1 is kind of an old release, why do you have to use it? Is it possible to use some latest one?

6

1.Can you try to flash the board with sdkmanager?

No.
I’m running fhas.sh directly.

2.Is it a custom board or devkit?

Custom board.

3.Rel-32.2.1 is kind of an old release, why do you have to use it? Is it possible to use some latest one?

We are considering using the new L4T, but development has not started yet.
So I am using 32.2.1.
We plan to use the new L4T in the future.

7

Please move this module to devkit and flash with sdkmanager and see if it can boot up fine.

8

Okay,
I will try the testing.

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.