Verifying Hash Integrity ... sha256 error!

[dbldevelopers]

Hi,
I tried to build a default demo-distro image with a FIT kernel image and mender update support for Jetson TX2 devkit (TX2 som + carrier board rev. B04), build was successfull but got a problem booting an image on my devkit.

Step by step...

First I cloned the repository of the corresponding branch including the submodules (I want use yocto kirkstone branch for my tx2 and mender support, so I cloned kirkstone-l4t-r32.7.x branch):

git clone --recurse-submodules https://github.com/OE4T/tegra-demo-distro.git -b kirkstone-l4t-r32.7.x
cd tegra-demo-distro

Than I set up my build with mender distro for my machine:
. ./setup-env --machine jetson-tx2-devkit-cot --distro tegrademo-mender

After successfull build I unzipped resulting demo-image-egl-jetson-tx2-devkit-cot-20230222094604.tegraflash.tar.gz and flashed it to my devkit by
sudo ./doflash.sh

Than I connected my pc to the devkit's debug UART to receive early boot messages from devkit. There is my UART output:

[0000.181] I> Welcome to MB2(TBoot-BPMP)(version: 01.00.160913-t186-M-00.00-mobile-f97eef92)
[0000.189] I> Boot-device: eMMC
[0000.197] I> sdmmc bdev is already initialized
[0000.201] I> pmic: reset reason (nverc)        : 0x80
[0000.234] I> Found 18 partitions in SDMMC_BOOT (instance 3)
[0000.254] I> Found 34 partitions in SDMMC_USER (instance 3)
...
[0000.920] I> boot profiler for TOS @ 0x275844000
[0000.924] I> Unhalting SCE
[0000.927] I> Primary Memory Start:80000000 Size:70000000
[0000.932] I> Extended Memory Start:f0110000 Size:1856f0000
[0000.939] I> MB2(TBoot-BPMP) done

NOTICE:  BL31: v1.3(release):9892ce1
NOTICE:  BL31: Built : 09:21:30, Nov 22 2022
ipc-unittest-main: 1519: Welcome to IPC unittest!!!
ipc-unittest-main: 1531: waiting forever
ipc-unittest-srv: 329: Init unittest services!!!
hwkey-agent: 41: hwkey-agent is running!!
hwkey-agent: 347: key_mgnt_processing .......
hwkey-agent: 255: Setting EKB key 0 to slot 14
hwkey-agent: 178: Init hweky-agent services!!
luks-srv: 40: luks-srv is running!!
luks-srv: 157: Init luks-srv IPC services!!
platform_bootstrap_epilog: trusty bootstrap complete
[0001.313] I> Welcome to Cboot
[0001.316] I> Cboot Version: 32.07.03-oe4t-t186-faa90776
[0001.321] I> CPU-BL Params @ 0x275800000
[0001.324] I>  0) Base:0x00000000 Size:0x00000000
...
[0004.317] I> node /plugin-manager/fragment-p3310-c00-camera matches
[0004.344] I> Disable plugin-manager status in FDT
[0004.348] I> Plugin-manager override finished successfully
[0004.353] I> tegrabl_load_kernel_and_dtb: Done
[0004.364] I> Kernel EP: 0x80600000, DTB: 0x80000000


U-Boot 2022.01 (Mar 11 2022 - 15:31:17 +0000)

SoC: tegra186
Model: NVIDIA P2771-0000-500
Board: NVIDIA P2771-0000
DRAM:  7.8 GiB
MMC:   sdhci@3400000: 1, sdhci@3460000: 0
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@2490000
Hit any key to stop autoboot:  0 
41762476 bytes read in 1035 ms (38.5 MiB/s)
## Loading kernel from FIT Image at 90000000 ...
   Using 'conf-1' configuration
   Trying 'kernel-1' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x90000124
     Data Size:    41760776 Bytes = 39.8 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x80080000
     Entry Point:  0x80080000
     Hash algo:    sha256
     Hash value:   05d96dae5a294602372809745b09e5a596fa6a49e6aea53f65e31a548a43b038
   Verifying Hash Integrity ... sha256 error!
Unsupported hash algorithm for 'hash-1' hash node in 'kernel-1' image node
Bad Data Hash
ERROR: can't get kernel image!
Tegra186 (P2771-0000-500) # 

Please help me. What is the reason for the received error? What should I do to successfully boot the system?

[ichergui]

Hey @dbldevelopers
I'm sorry to see that happen for you.
Did you follow our wiki page ?
TBH, I didn't try that with the kirkstone-l4t-r32.7.x branch.
I can do it later and get back to you

[ichergui]

Hello @dbldevelopers
Please follow our wiki page. It should work
I tried the kirkstone-l4t-r32.7.x branch and it is working properly.

Kindly see below logs from the Serial UART

U-Boot 2022.01 (Mar 11 2022 - 15:31:17 +0000)

SoC: tegra186
Model: NVIDIA P2771-0000-500
Board: NVIDIA P2771-0000
DRAM:  7.8 GiB
MMC:   sdhci@3400000: 1, sdhci@3460000: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@2490000
Hit any key to stop autoboot:  0 
Saving Environment to MMC... Writing to redundant MMC(0)... OK
41762694 bytes read in 1028 ms (38.7 MiB/s)
## Loading kernel from FIT Image at 90000000 ...
   Using 'conf-1' configuration
   Verifying Hash Integrity ... sha256,rsa2048:dev+ OK
   Trying 'kernel-1' kernel subimage
     Description:  Linux kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x90000124
     Data Size:    41760776 Bytes = 39.8 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x80080000
     Entry Point:  0x80080000
     Hash algo:    sha256
     Hash value:   05d96dae5a294602372809745b09e5a596fa6a49e6aea53f65e31a548a43b038
   Verifying Hash Integrity ... sha256+ OK
## Flattened Device Tree blob at 80000000
   Booting using the fdt blob at 0x80000000
   Loading Kernel Image
ERROR: reserving fdt memory region failed (addr=0 size=0 flags=4)
ERROR: reserving fdt memory region failed (addr=0 size=0 flags=4)
   Using Device Tree in place at 0000000080000000, end 0000000080060997
copying carveout for /host1x@13e00000/display-hub@15200000/display@15200000...
copying carveout for /host1x@13e00000/display-hub@15200000/display@15210000...
copying carveout for /host1x@13e00000/display-hub@15200000/display@15220000...

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] Linux version 4.9.299-l4t-r32.7.3+gff65a92ec55e (oe-user@oe-host) (gcc version 11.3.0 (GCC) ) #1 SMP PREEMPT Fri Dec 2 12:17:09 UTC 2022
[    0.000000] Boot CPU: AArch64 Processor [411fd073]
[    0.000000] OF: fdt:memory scan node memory@80000000, reg size 80,

You can see that we are performing the signature verification of the FIT image, which is working as expected.

The device boots successfully. Please see logs below

[   13.019971] eqos 2490000.ether_qos eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[   13.037235] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

OE4Tegra Demonstration Distro with Mender 4.0.7-9db9d34-icg jetson-tx2-devkit-cot ttyS0

jetson-tx2-devkit-cot login: 
jetson-tx2-devkit-cot login: 
jetson-tx2-devkit-cot login: 
jetson-tx2-devkit-cot login: root
[   25.972736] audit: type=1006 audit(1677110477.916:2): pid=5202 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=1 res=1
root@jetson-tx2-devkit-cot:~# 
root@jetson-tx2-devkit-cot:~# 
root@jetson-tx2-devkit-cot:~# 
root@jetson-tx2-devkit-cot:~# 
root@jetson-tx2-devkit-cot:~# hostnamectl 
 Static hostname: jetson-tx2-devkit-cot
       Icon name: computer
      Machine ID: f37ba44243f34eef94818874d8629c1e
         Boot ID: b72d96fccebe43ec87ccf196a58f7430
Operating System: OE4Tegra Demonstration Distro with Mender 4.0.7-9db9d34-icg
          Kernel: Linux 4.9.299-l4t-r32.7.3+gff65a92ec55e
    Architecture: arm64
root@jetson-tx2-devkit-cot:~# 
root@jetson-tx2-devkit-cot:~# tegra-eeprom-tool 
tegra-eeprom-tool> show
partnumber[nvidia]: 699-83310-1000-D02 K.0
factory-default-wifi-mac: 48:b0:2d:1b:b4:c5
factory-default-bt-mac: 48:b0:2d:1b:b4:c6
factory-default-wifi-alt-mac: 00:00:00:00:00:00
factory-default-ether-mac: 48:b0:2d:1b:b4:c7
asset-id: 1420221003449
vendor-wifi-mac: 48:b0:2d:1b:b4:c5
vendor-bt-mac: 48:b0:2d:1b:b4:c6
vendor-ether-mac: 48:b0:2d:1b:b4:c7
tegra-eeprom-tool> quit
root@jetson-tx2-devkit-cot:~# 

[dbldevelopers]

Hello @ichergui,
I rebuilt the system without FIT image signing enabled and with it enabled. FIT image without signing doesn't boot. Image with signing booted successfully.