imx8mm encrypted uboot failed to load linux kernel

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

imx8mm encrypted uboot failed to load linux kernel

2,806 Views
yanghongsing1
Contributor III

I built a encrypted uboot, it can load the kernel image and dtb file, but gave an error of "Could not create optee node.ERROR: system-specific fdt fixup failed: FDT_ERR_NOTFOUND". I hangs there. Please refer to below for details. Could you advise that I used the correct versions of below modules? If not, what are the correct versions?

Uboot version: lf_v2021.04

Optee os: imx_5.4.70_2.3.0

Imx-atf: lf-5.4.y

Imx-mkimage: lf-5.10.y_2.0.0

 

U-Boot SPL 2021.04-dirty (Aug 11 2021 - 17:15:21 +0800)
DDRINFO: start DRAM init
DDRINFO: DRAM rate 3000MTS
DDRINFO:ddrphy calibration done
DDRINFO: ddrmix config done
SEC0: RNG instantiated
Normal Boot
Trying to boot from MMC1

Authenticate image from DDR location 0x401fcdc0...


U-Boot 2021.04-dirty (Aug 11 2021 - 17:15:21 +0800)

alloc space exhausted
CPU: i.MX8MMQ rev1.0 1800 MHz (running at 1200 MHz)
CPU: Commercial temperature grade (0C to 95C) at 36C
Reset cause: POR
Model: NXP i.MX8MM EVK board
DRAM: 2 GiB
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x52]
Power supply on USB2
TCPC: Vendor ID [0x1fc9], Product ID [0x5110], Addr [I2C1 0x50]
MMC: FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
mxs_video lcdif@32e00000: failed to get any video link display timings
probe video device failed, ret -22

[0] lcdif@32e00000, video
[1] mipi_dsi@32e10000, video_bridge
[2] adv7535@3d, panel
adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
mxs_video lcdif@32e00000: failed to get any video link display timings
probe video device failed, ret -22
In: serial
Out: serial
Err: serial
SEC0: RNG instantiated

BuildInfo:
- ATF 7b3389d

switch to partitions #0, OK
mmc1 is current device
flash target is MMC:1
Net: eth0: ethernet@30be0000
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
starting USB...
Bus usb@32e40000: Port not available.
USB is stopped. Please issue 'usb start' first.
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
47412 bytes read in 3 ms (15.1 MiB/s)
Scanning disk mmc@30b50000.blk...
Scanning disk mmc@30b60000.blk...
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
Found 16 disks
No EFI system partition
adv7535_mipi2hdmi adv7535@3d: Can't find cec device id=0x3c
fail to probe panel device adv7535@3d
mxs_video lcdif@32e00000: failed to get any video link display timings
Could not create optee node.
ERROR: system-specific fdt fixup failed: FDT_ERR_NOTFOUND
- must RESET the board to recover.

ERROR: failed to process device tree
switch to partitions #0, OK
mmc2(part 0) is current device
** Unrecognized filesystem type **
Running BSP bootcmd ...
switch to partitions #0, OK
mmc1 is current device
Failed to load 'boot.scr'
30083672 bytes read in 318 ms (90.2 MiB/s)
Booting from mmc ...
47412 bytes read in 3 ms (15.1 MiB/s)

Authenticate image from DDR location 0x40480000...

Secure boot enabled

HAB Configuration: 0xcc, HAB State: 0x99
No HAB Events Found!

Moving Image from 0x40480000 to 0x40600000, end=422b0000
## Flattened Device Tree blob at 43000000
Booting using the fdt blob at 0x43000000
Using Device Tree in place at 0000000043000000, end 000000004300e933
Could not create optee node.
ERROR: system-specific fdt fixup failed: FDT_ERR_NOTFOUND
- must RESET the board to recover.

FDT creation failed! hanging...### ERROR ### Please RESET the board ###

Labels (1)
0 Kudos
5 Replies

2,796 Views
igorpadykov
NXP Employee
NXP Employee

Hi Hong

 

one can recheck optee configuration described on

https://source.codeaurora.org/external/imx/uboot-imx/tree/doc/imx/habv4/guides/mx8m_encrypted_boot.t...

In general using aligned  versions is important, so for v5.10.y recommended to use

https://source.codeaurora.org/external/imx/linux-imx/tree/?h=lf-5.10.y

https://source.codeaurora.org/external/imx/imx-optee-os/tree/?h=lf-5.10.y_2.0.0

 

Best regards
igor

0 Kudos

2,785 Views
yanghongsing1
Contributor III

Dear Igor,

 

Thank you for your advise.

Could you also advise which version of imx-atf and uboot-imx are aligned to lf-5.10.y? There is no lf-5.10.y at link below:

https://source.codeaurora.org/external/imx/imx-atf

https://source.codeaurora.org/external/imx/uboot-imx

Thanks...

 

0 Kudos

2,781 Views
igorpadykov
NXP Employee
NXP Employee
0 Kudos

2,774 Views
yanghongsing1
Contributor III

Hi Igor,

 

I use modules below to build a signed flash.bin and try to generate dek_spl_blob.bin. But I got an error message of "Cannot get OP-TEE device". Could you advise what wrong with me?

uboot-imx: v2021.04

imx-optee-os: lf-5.10_2.2.0.0

imx-atf: lf-5.4.y

imx-mkimage: lf-5.10_2.0.0

0 Kudos

2,698 Views
elginallen
NXP Employee
NXP Employee

Hello Hong,

 

Could you please check that imx-atf was built with "SPD=opteed" as decribed by the U-boot documentation Igor linked above?

elginallen_0-1633028501535.png

That was my issue when I encountered "Cannot get OP-TEE device".

Best,

Elgin

0 Kudos