LS1043a-rdb for ARM 32bit keeps resetting ...

Showing results for 
Search instead for 
Did you mean: 

LS1043a-rdb for ARM 32bit keeps resetting ...

Contributor I


I have compiled the the u-boot version (u-boot-fsl-sdk-v2.0-1701) using  the CROSS_COMPILE=aarch64-linux-gnu- and ARCH=arm64 and for an SD-card and also made fsl-ls1043a-rdb.dtb.

Than I compiled linux-fsl-sdk-v2.0-1701 using the CROSS_COMPILE=arm-linux-gnueabihf- and ARCH=arm, was able to compile that too and than using the mkimage create kernel.itb file which i than copied it  to the SDcard.

When i boot the LS1043a-rdb board this is the output i get

U-Boot SPL 2016.09 (Mar 27 2017 - 14:14:12)
Initializing DDR....
Trying to boot from MMC1

U-Boot 2016.09 (Mar 27 2017 - 14:14:12 -0700)

SoC:  unknown (0x87920410)
Clock Configuration:
       CPU0(A53):1600 MHz  CPU1(A53):1600 MHz  CPU2(A53):1600 MHz  
       CPU3(A53):1600 MHz  
       Bus:      400  MHz  DDR:      1600 MT/s  FMAN:     500  MHz
Reset Configuration Word (RCW):
       00000000: 08100010 0a000000 00000000 00000000
       00000010: 14550002 80004012 60040000 c1002000
       00000020: 00000000 00000000 00000000 00038800
       00000030: 00000000 00001100 00000096 00000001
Model: LS1043A RDB Board
Board: LS1043ARDB, boot from SD
CPLD:  V1.4
PCBA:  V3.0
SERDES Reference Clocks:
SD1_CLK1 = 156.25MHZ, SD1_CLK2 = 100.00MHZ
I2C:   ready
DRAM:  Detected UDIMM Fixed DDR on board
2 GiB (DDR4, 32-bit, CL=11, ECC off)
SEC0: RNG instantiated
PPA Firmware: Version 0.1
Using SERDES1 Protocol: 5205 (0x1455)
Flash: 128 MiB
NAND:  512 MiB
In:    serial
Out:   serial
Err:   serial
MMC read: dev # 0, block # 2080, count 128 ...
Fman1: Data at 00000000ffc12ff0 is not a firmware
PCIe0: pcie@3400000 disabled
PCIe1: pcie@3500000 Root Complex: no link
PCIe2: pcie@3600000 Root Complex: x1 gen1
e1000: 6c:b3:11:0f:0f:5d
Warning: e1000#0 MAC addresses don't match:
Address in SROM is         6c:b3:11:0f:0f:5d
Address in environment is  00:04:9f:04:6c:51

Hit any key to stop autoboot:  0
97497839 bytes read in 4327 ms (21.5 MiB/s)
## Loading kernel from FIT Image at a0000000 ...
   Using 'config@1' configuration
   Trying 'kernel@1' kernel subimage
     Description:  ARM32 Linux kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0xa00000e0
     Data Size:    7056616 Bytes = 6.7 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x80008000
     Entry Point:  0x80008000
   Verifying Hash Integrity ... OK
## Loading ramdisk from FIT Image at a0000000 ...
   Using 'config@1' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  LS1 Ramdisk
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0xa06bc704
     Data Size:    90433698 Bytes = 86.2 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: unavailable
     Entry Point:  unavailable
   Verifying Hash Integrity ... OK
## Loading fdt from FIT Image at a0000000 ...
   Using 'config@1' configuration
   Trying 'fdt@1' fdt subimage
     Description:  Flattened Device Tree blob
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0xa06bae78
     Data Size:    6155 Bytes = 6 KiB
     Architecture: ARM
   Verifying Hash Integrity ... OK
   Loading fdt from 0xa06bae78 to 0x90000000
   Booting using the fdt blob at 0x90000000
   Loading Kernel Image ... OK
   Using Device Tree in place at 0000000090000000, end 000000009001480a
couldn't find /cpus
WARNING: Missing crypto node
WARNING: fdt_path_offset can't find path /soc/msi-controller: FDT_ERR_NOTFOUND

Starting kernel ...

"Synchronous Abort" handler, esr 0x02000000
ELR:     90000000
LR:      ffd082a8
x0 : 00000000ffffffff x1 : 0000000080008000
x2 : 0000000000000000 x3 : 0000000090000000
x4 : 0000000000000000 x5 : 0000000000000008
x6 : ffffffffffffffff x7 : 0000000000000000
x8 : 00000000ffc01fb0 x9 : 0000000000000000
x10: 0000000000000000 x11: 0000000000000000
x12: 0000000000000002 x13: 00000000ffffffff
x14: 000000009001480a x15: 00000000ffd0899c
x16: 000000001000f5f4 x17: 0000000000000001
x18: 00000000ffc04d70 x19: 0000000000000400
x20: 00000000ffd9eeb0 x21: 0000000000000400
x22: 0000000000000000 x23: 00000000ffc0d308
x24: 0000000000000000 x25: 00000000ffd91ae0
x26: 00000000a00000e0 x27: 00000000ffd0b658
x28: 0000000080008000 x29: 00000000ffc02110

Resetting CPU ...

resetting ...

U-Boot SPL 2016.09 (Mar 27 2017 - 14:14:12)
Initializing DDR....
Trying to boot from MMC1

Its not starting the kernel and keeps on resetting ...

Could any please advice on how to solve this problem.

Thank you


0 Kudos
1 Reply

NXP TechSupport
NXP TechSupport

NXP SDK 2.0 -1701 supports 64-bit and 32-bit Linux image.

Usually bitbake is used for image compilation. See the SDK 2.0-1703 documentation:


We usually use the following command sequence for SDK installing under Ubuntu 14.04 and Ubuntu 16.04:

  1. sudo apt-get install ubuntu-minimal ubuntu-standard patch vim-common sed wget subversion git-core coreutils libbonobo2-common unzip texi2html texinfo libsdl1.2-dev docbook-utils gawk python-pysqlite2 diffstat make gcc build-essential xz-utils g++ desktop-file-utils chrpath libgl1-mesa-dev libglu1-mesa-dev autoconf automake groff libtool xterm libncurses5-dev cvs tofrodos


  1. a) command: ls -l /bin/sh

                Message:  /bin/sh -> dash

  1. b) command: sudo dpkg-reconfigure dash

                Answer after password – No


                Removing 'diversion of /bin/sh to /bin/sh.distrib by dash'

                Adding 'diversion of /bin/sh to /bin/sh.distrib by bash'

                Removing 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by dash'

                Adding 'diversion of /usr/share/man/man1/sh.1.gz to /usr/share/man/man1/sh.distrib.1.gz by bash'

  1. c) command for checking: ls -l /bin/sh

                Message: /bin/sh -> bash

  1. mount SDK .iso file
  2. install SDK
  3. cd <sdk-install-dir>.
  4. ./sources/meta-freescale/scripts/

Usually Linux recommends also run the following command: sudo usr/sbin/visudo

  1. bitbake fsl-image-minimal

Have a great day,
Pavel Chubakov

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

0 Kudos