bootm error using nxp lsdk tiny kernel on LS1088ARDB

[holder]

Folks,

 Target is LS1088ARDB.

Following directions in LSDK_REV1809 documentation section 4.3 Step 2.

I downloaded the pre-built linux image from nxp site:

wget http://www.nxp.com/lgfiles/sdk/lsdk1806/lsdk_linux_arm64_tiny.itb

I transfer this file from tftp server and boot as directed in LSDK_REV1809 section 4.3 Step 2.

==> bootm a0000000#ls1088ardb

I get following error:

## Loading kernel from FIT Image at a0000000 ...
   Using 'ls1088ardb' configuration
   Trying 'kernel' kernel subimage
     Description:  ARM64 Kernel
     Created:      2018-06-23   8:35:51 UTC
     Type:         Kernel Image
     Compression:  gzip compressed
     Data Start:   0xa00000d0
     Data Size:    9004198 Bytes = 8.6 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x80080000
     Entry Point:  0x80080000
     Hash algo:    crc32
     Hash value:   6e2e1026
   Verifying Hash Integrity ... crc32+ OK
## Loading ramdisk from FIT Image at a0000000 ...
   Using 'ls1088ardb' configuration
   Trying 'initrd' ramdisk subimage
     Description:  initrd for arm64
     Created:      2018-06-23   8:35:51 UTC
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0xa0896658
     Data Size:    10842127 Bytes = 10.3 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x00000000
     Entry Point:  0x00000000
     Hash algo:    crc32
     Hash value:   b67ed0d0
   Verifying Hash Integrity ... crc32+ OK
## Loading fdt from FIT Image at a0000000 ...
   Using 'ls1088ardb' configuration
   Trying 'ls1088ardb-dtb' fdt subimage
     Description:  ls1088ardb-dtb
     Created:      2018-06-23   8:35:51 UTC
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0xa12f7500
     Data Size:    15864 Bytes = 15.5 KiB
     Architecture: AArch64
     Hash algo:    crc32
     Hash value:   2227f976
   Verifying Hash Integrity ... crc32+ OK
   Loading fdt from 0xa12f7500 to 0x90000000
   Booting using the fdt blob at 0x90000000
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 000000009fff9000, end 000000009ffffdf7 ... OK
WARNING: fdt_fixup_stdout: could not read serial0 alias: FDT_ERR_NOTFOUND

fdt_fixup_smmu: WARNING: no SMMU node found
fdt_fixup_board_enet: ERROR: fsl-mc node not found in device tree (error -1)
ERROR: fsl-mc: DPL is not applied
ERROR: board-specific fdt fixup failed: <unknown error>
 - must RESET the board to recover.

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

Any suggestions?

bob

[yipingwang]

Hello bob holder,

According to the error log, the dpl is not applied, I am not sure whether the DPL image is deployed on QSPI flash, please refer to the following procedure to deploy the pre-built QSPI u-boot image on the alternate bank. 

For QSPI boot (programming from altbank):
=> sf probe 0:1
=> tftp 0xa0000000 firmware_ls1088ardb_uboot_qspiboot.img
=> sf erase 0 +$filesize
=> sf write 0xa0000000 0 $filesize
=> i2c mw 0x66 0x50 20;i2c mw 66 10 20;i2c mw 66 10 21

Then apply MC, DPC and DPL images as the following.

=> sf read 0x81000000 0xA00000 0x05000
device 0 offset 0xa00000, size 0x5000
SF: 20480 bytes @ 0xa00000 Read: OK
=> sf read 0x82000000 0xE00000 0x7000
device 0 offset 0xe00000, size 0x7000
SF: 28672 bytes @ 0xe00000 Read: OK
=> fsl_mc start mc 0x81000000 0x82000000
fsl-mc: MC is already booted
=> sf read 0x83000000 0xD00000 0x06800
device 0 offset 0xd00000, size 0x6800
SF: 26624 bytes @ 0xd00000 Read: OK
=> fsl_mc apply DPL 0x83000000
fsl-mc: Deploying data path layout ... SUCCESS

Then execute the following command.

=> bootm a0000000#ls1088ardb

Note:

DPAA2 MC or PFE firmware 3MB 0x00A00000 0x05000

DPAA2 DPL 1MB 0x00D00000 0x06800

DPAA2 DPC 1MB 0x00E00000 0x07000

fsl_mc start mc <MC FW Address> < MC DPC Address>

fsl_mc apply DPL <MC DPL Address>

Have a great day,
TIC

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------