LS1046, How to load Linux kernel without using SEC Firmware? (HELP!)

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

LS1046, How to load Linux kernel without using SEC Firmware? (HELP!)

ソリューションへジャンプ
2,278件の閲覧回数
nekarose
Contributor II

Hi, experts

I am trying to port ATF/Uboot/linux using the ls1046 CPU custom board that does not support secure mode. I checked that it boots up to ATF and Uboot, but when I download the kernel as tftp and try to boot, the following error occurs.

Verifying Hash Integrity ... OK
Loading fdt from 0xa23b46f4 to 0x90000000
Booting using the fdt blob at 0x90000000
Uncompressing Kernel Image
Loading Ramdisk to 8eb0c000, end 8ffff53f ... OK
Loading Device Tree to 000000008eaef000, end 000000008eb0b7f4 ... OK
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
fdt_update_ethernet_dt:Invalid SerDes prtcl 0x3333 for LS1046AFRWY
NOTICE: SEC is disabled.
WARNING: No random number to set kaslr-seed
"Synchronous Abort" handler, esr 0x96000004
elr: 0000000082032444 lr : 0000000082032394 (reloc)
elr: 00000000f7b7e444 lr : 00000000f7b7e394
x0 : 0000000000000000 x1 : 00000000f7a098a8
x2 : b27e0063d2800043 x3 : 0000000000000068
x4 : 00000000f7a0be70 x5 : 00000000f7a0cb60
x6 : 0000000000000042 x7 : 000000008eaf89d3
x8 : 0000000000000004 x9 : 0000000000000008
x10: 00000000000007d4 x11: 00000000f7a097fc
x12: 00000000000007a0 x13: 00000000f7a09898
x14: 000000008eaef000 x15: 0000000000000002
x16: 00000000f7b8c874 x17: 00000000f7a269b0
x18: 00000000f7a0bdb0 x19: 000000008eaef000
x20: 00000000f7bd58c8 x21: b27e0063d27fffcb
x22: 00000000f7bd58d0 x23: 00000000f7bc4355
x24: 00000000f7bcf2df x25: 00000000f7bd7a30
x26: 0000000000000000 x27: 00000000f7b517f0
x28: 00000000a00000d0 x29: 00000000f7a098e0

It is presumed to be a problem caused by not using SEC, and when I set the CONFIG_ARMV8_SEC_FIRMWARE_SUPPORT item in the Uboot config item to n, the lsdk2108_yocto_tiny_LS_arm64.itb file loaded as tftp is not recognized with an error "wrong Image Format for bootm command" when booting.
If the SEC Firmware is not supported, does the itb image not load? So, what linux kernel image should I use when not using SEC Firmware?

Please, Help me!

 

 

0 件の賞賛
返信
1 解決策
2,261件の閲覧回数
nekarose
Contributor II

When CONFIG_ARMV8_SEC_FIRMWARE_SUPPORT=n and INCLUDE_FIT=y are applied, it loads normally.

元の投稿で解決策を見る

0 件の賞賛
返信
1 返信
2,262件の閲覧回数
nekarose
Contributor II

When CONFIG_ARMV8_SEC_FIRMWARE_SUPPORT=n and INCLUDE_FIT=y are applied, it loads normally.

0 件の賞賛
返信