LS1043A-SDK Image sdcard boot hangs at Kernel start

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

LS1043A-SDK Image sdcard boot hangs at Kernel start

1,173 Views
tmorrison
Contributor III

I have built with flex-builder a firmware image and loaded it onto a sd card

I have put that into my board and U-boot comes up, and I do the following:

    mmc read a0000000  8000 14000

    bootm a0000000#ls1043argw

This is the result:

   bootargs=console=ttyS0,115200 root=/dev/ram0
   MMC read: dev # 0, block # 32768, count 81920 ... 81920 blocks read: OK
   ## Loading kernel from FIT Image at a0000000 ...
      Using 'ls1043argw' configuration
      Trying 'kernel' kernel subimage
        Description:  ARM64 Kernel
        Type:         Kernel Image
        Compression:  gzip compressed
        Data Start:   0xa00000d0
        Data Size:    9155616 Bytes = 8.7 MiB
        Architecture: AArch64
        OS:           Linux
        Load Address: 0x80080000
        Entry Point:  0x80080000
        Hash algo:    crc32
        Hash value:   c9a6eb85
      Verifying Hash Integrity ... crc32+ OK
   ## Loading ramdisk from FIT Image at a0000000 ...
      Using 'ls1043argw' configuration
      Trying 'initrd' ramdisk subimage
        Description:  initrd for arm64
        Type:         RAMDisk Image
        Compression:  uncompressed
        Data Start:   0xa08bb5d0
        Data Size:    10993748 Bytes = 10.5 MiB
        Architecture: AArch64
         OS:           Linux
        Load Address: 0x00000000
        Entry Point:  0x00000000
        Hash algo:    crc32
        Hash value:   aa44d389
       Verifying Hash Integrity ... crc32+ OK
   ## Loading fdt from FIT Image at a0000000 ...
      Using 'ls1043argw' configuration
      Trying 'ls1043argw-dtb' fdt subimage
        Description:  ls1043argw-dtb
        Type:         Flat Device Tree
        Compression:  uncompressed
        Data Start:   0xa134c864
        Data Size:    28303 Bytes = 27.6 KiB
        Architecture: AArch64
        Load Address: 0x90000000
        Hash algo:    crc32
        Hash value:   975defd9
      Verifying Hash Integrity ... crc32+ OK
      Loading fdt from 0xa134c864 to 0x90000000
      Booting using the fdt blob at 0x90000000
        Uncompressing Kernel Image ... OK
       Using Device Tree in place at 0000000090000000, end 0000000090019e8e
     WARNING: SEC firmware not running, no kaslr-seed

     Starting kernel ...

Thats it?

I know I got past this once, but I need to get past this again...

0 Kudos
4 Replies

1,060 Views
yipingwang
NXP TechSupport
NXP TechSupport

Hello Thomas Morrison,

Which version LSDK are you using? The latest release LSDK 19.09 or  20.04 doesn't support ls1043argw.

Would you please provide your patches applied on  flex-builder LSDK to support ls1043argw?

I uploaded lsdk2004_yocto_tiny_LS_arm64.itb in the following link.

https://drive.google.com/open?id=1Awquuv3lKTc-qAdSFg22C7rkgIPXWWPK 

Please deploy it on your SD card and check whether you could execute the following command to start Linux Kernel.

 mmc read a0000000  8000 14000

bootm a0000000#ls1043ardb

Thanks,

Yiping

0 Kudos

1,060 Views
tmorrison
Contributor III

Hi Yiping,

Thank you for getting back to me so quickly.

We are working with 18.03 (with patches for RGW). I know it's old and

decrepit

but we are only using it for the uboot (which I am trying to port "up" to

modern

OpenWrt)

thank you

tom

0 Kudos

1,060 Views
tmorrison
Contributor III

I tested first by tftp'ing this image over and trying to boot from it - it crashed

(we don't have a NOR flash that it is trying to accessing):

[    3.552968] physmap-flash 60000000.nor: physmap platform flash device: [mem 0x60000000-0x67ffffff]
[    3.562064] SError Interrupt on CPU0, code 0xbf000002 -- SError
[    3.562065] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.3 #1
[    3.562067] Hardware name: LS1043A RDB Board (DT)
[    3.562068] pstate: 60000005 (nZCv daif -PAN -UAO)
[    3.562069] pc : cfi_send_gen_cmd+0xe0/0x158
[    3.562070] lr : cfi_send_gen_cmd+0x7c/0x158
[    3.562071] sp : ffff80001003b960
[    3.562072] x29: ffff80001003b960 x28: 0000000000000000
[    3.562075] x27: 0000000000000000 x26: ffff0008737de580
[    3.562077] x25: ffff0008737de580 x24: 0000000000000000
[    3.562080] x23: 0000000000000000 x22: ffff800012129000
[    3.562082] x21: ffff0008737de680 x20: 0000000000000000
[    3.562084] x19: 0000000000000000 x18: ffffffffffffffff
[    3.562087] x17: 0000000000000007 x16: 0000000000000001
[    3.562090] x15: ffff800012129908 x14: 206d656d5b203a65
[    3.562092] x13: 6369766564206873 x12: 616c66206d726f66
[    3.562094] x11: 0000000000000008 x10: 0101010101010101
[    3.562097] x9 : 0000000000000125 x8 : 0000000000000000
[    3.562099] x7 : 0000000000000002 x6 : 0000000000000002
[    3.562101] x5 : 0000000000000002 x4 : ffff800012129908
[    3.562104] x3 : 0000000000000002 x2 : ffff800018000000
[    3.562106] x1 : ffff800018000000 x0 : 000000000000f0f0
[    3.562109] Kernel panic - not syncing: Asynchronous SError Interrupt
[    3.562111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.3 #1
[    3.562112] Hardware name: LS1043A RDB Board (DT)
[    3.562113] Call trace:
[    3.562114]  dump_backtrace+0x0/0x150
[    3.562115]  show_stack+0x14/0x20
[    3.562116]  dump_stack+0xbc/0x100
[    3.562117]  panic+0x16c/0x37c
[    3.562118]  __stack_chk_fail+0x0/0x18
[    3.562119]  arm64_serror_panic+0x74/0x88
[    3.562120]  do_serror+0x70/0x138
[    3.562121]  el1_error+0x84/0xf8

0 Kudos

1,060 Views
yipingwang
NXP TechSupport
NXP TechSupport

Would you please provide patches for RGW based on LSDK 18.03?

Would you please provide the procedure which you used to generate the itb image?

0 Kudos