topic Re: LX2160A RDB uboot log issue in Layerscape

LX2160A RDB uboot log issue

ash_law — Thu, 14 Nov 2019 22:45:12 GMT

I have an LX2160ARDB (just started with it). The system seems to boot up fine from the default load. When I set SW1 to try and boot off the SD card (SW1 set to 1000 1000) I get no uboot log on the terminal. Any ideas would be appreciated.

Thanks

Re: LX2160A RDB uboot log issue

yipingwang — Fri, 15 Nov 2019 09:37:43 GMT

Please download SD firmware image with the following command.

wget https://www.nxp.com/lgfiles/sdk/lsdk1909/firmware_lx2160ardb_uboot_sdboot.img

Under u-boot:

=> tftp a0000000 firmware_lx2160ardb_uboot_sdboot.img
or
=> load mmc 0:2 a0000000 firmware_lx2160ardb_uboot_sdboot.img
Under U-Boot:
=> mmc write a0000000 8 1f000
Under Linux:
$ flex-installer -f firmware_lx2160ardb_uboot_sdboot.img -d /dev/mmcblk0 (or /dev/sdx)

SD Card (SDHC1) SW1:1000 1000 SW2:0000 0110 SW3:1111 1100 SW:41011 1000

Re: LX2160A RDB uboot log issue

ash_law — Fri, 15 Nov 2019 18:16:40 GMT

Thanks. Idid manage to get uboot to show up. You do have to rerun the whole comman because flex-installer wants to reformat the whole SD card

>>flex-installer -b bootpartition_LS_arm64_lts_4.14.tgz -r build/images/rootfs_lsdk1909_LS_arm64_main_201911141047.tgz -f firmware_lx2160ardb_uboot_sdboot.img -d /dev/sdc

But after doing that there's a kernel panic when it tries to boot

[    8.003541] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[    8.011636] VFS: Mounted root (ext4 filesystem) on device 179:3.
[    8.018223] devtmpfs: error mounting -2
[    8.022432] Freeing unused kernel memory: 1344K
[    8.027030] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[    8.041186] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W       4.14.83 #1
[    8.048394] Hardware name: NXP Layerscape LX2160ARDB (DT)
[    8.053779] Call trace:
[    8.056222] [<ffff000008089b80>] dump_backtrace+0x0/0x3c0
[    8.061609] [<ffff000008089f54>] show_stack+0x14/0x20
[    8.066651] [<ffff000008ce7228>] dump_stack+0x9c/0xbc
[    8.071690] [<ffff0000080ce878>] panic+0x11c/0x28c
[    8.076469] [<ffff000008cf980c>] kernel_init+0xf4/0x108
[    8.081682] [<ffff000008084f30>] ret_from_fork+0x10/0x18
[    8.086991] SMP: stopping secondary CPUs
[    8.090905] Kernel Offset: disabled
[    8.094381] CPU features: 0x1802008
[    8.097856] Memory Limit: none
[    8.100905] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

I'm assuming it can't find /sbin/init but I'm not sure why not.

ETA: I checked on the SD card and /dev/sdc4 has an sbin/init file.

Any ideas?

Thanks

Re: LX2160A RDB uboot log issue

yipingwang — Thu, 21 Nov 2019 08:59:10 GMT

Please configure bootargs similar as the following.

console=ttyS0,115200 root=/dev/mmcblk0p4 rw rootwait earlycon=uart8250,mmio,0x21c0500

Re: LX2160A RDB uboot log issue

johan_duque — Mon, 25 Nov 2019 14:20:32 GMT

Hi,

I'm also using the EvalKit LX2160A RDB and:

I don't understand the instructions. When is supposed to move the switch1 to "1000 1000"?

I have done as follow:

In My laptop:

1- Built images using flex-builder

2- Download uboot image with "wget https://www.nxp.com/lgfiles/sdk/lsdk1909/firmware_lx2160ardb_uboot_sdboot.img"

3- Flash all the images with command: flex-installer -b bootpartition_LS_arm64_lts_4.14.tgz -r build/images/rootfs_lsdk1909_LS_arm64_main_201911201102.tgz -f /home/lex/Downloads/firmware_lx2160ardb_uboot_sdboot.img -d /dev/mmcblk0 -> Success

In the EvalKit (UART1):

4- Insert the SD card to the LX2160A,

5- Use command: "load mmc 0:2 a0000000 firmware_lx2160ardb_uboot_sdboot.img"

6- Use command "mmc write a0000000 8 1f000"

7- Use command: "editenv bootargs" clean the values and set these: "console=ttyS0,115200 root=/dev/mmcblk0p4 rw rootwait earlycon=uart8250,mmio,0x21c0500"

From now I have tried the next two options:

Option 1:

Without reboot/poweroff

8- Use command boot, this fails with a kernel panic since it doesn't find any init:

"[    7.079874] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[    7.094030] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W       4.14.83 #1
[    7.101238] Hardware name: NXP Layerscape LX2160ARDB (DT)
[    7.106623] Call trace:
[    7.109066] [<ffff000008089b80>] dump_backtrace+0x0/0x3c0
[    7.114453] [<ffff000008089f54>] show_stack+0x14/0x20
[    7.119494] [<ffff000008ce7228>] dump_stack+0x9c/0xbc
[    7.124534] [<ffff0000080ce878>] panic+0x11c/0x28c
[    7.129313] [<ffff000008cf980c>] kernel_init+0xf4/0x108
[    7.134526] [<ffff000008084f30>] ret_from_fork+0x10/0x18
[    7.139835] SMP: stopping secondary CPUs
[    7.143748] Kernel Offset: disabled
[    7.147224] CPU features: 0x1802008
[    7.150700] Memory Limit: none
[    7.153748] ---[ end Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
"

Option 2:

- 8 After Step 7, poweroff the board,

-9 Move the Switch1 to "SW1:1000 1000" the other switches keep as default

-10 Power on the EvalKit

- 11 No output from the UART1

What am I doing wrong? How did you manage to make it work @Ash Law?

Thank you.

Re: LX2160A RDB uboot log issue

ash_law — Tue, 26 Nov 2019 12:10:00 GMT

I never did manage to get the unit to work by building an image. I used the installer to install the pre-built package, which is vey rudimentary but let’s things get done.

Please download LSDK 1909 user manual from Layerscape SDK | NXP <https://community.nxp.com/external-link.jspa?url=https%3A%2F%2Fwww.nxp.com%2Fdesign%2Fsoftware%2Fembedded-software%2Flinux-software-and-development-tools%2Flayerscape-software-development-kit-v19.09%3ALAYERSCAPE-SDK%3Ftab%3DDocumentation_Tab> , please refer to the section "4.1.2 Download and deploy LSDK images with flex-installer”.

That’s what worked for me.

Re: LX2160A RDB uboot log issue

johan_duque — Tue, 26 Nov 2019 14:22:22 GMT

Thank you ash.law@sigintsystemsllc.com‌ , can you please help us to boot the board from SD card with instructions only detailed for this purpose yipingwang‌ ? We really need since it's necessary to modify the kernel and userspace.

Re: LX2160A RDB uboot log issue

johan_duque — Tue, 26 Nov 2019 14:53:49 GMT

Hi,

I'm at same step than ash.law@sigintsystemsllc.com‌ , I'm able to boot only to u-boot, I'm getting the same error of init not found.

I have switch1 configured to: 10001000

I have built the images and flashed them with command: "flex-installer -i auto -m lx2160ardb -b bootpartition_LS_arm64_lts_4.14.tgz -r build/images/rootfs_lsdk1909_LS_arm64_main_201911201102.tgz -f /home/lex/Downloads/firmware_lx2160ardb_uboot_sdboot.img -d /dev/mmcblk0" -> Output: "Installation completed successfully"
I have modified the bootargs variable as said yipingwang‌

But the rootfs is not starting, what else must I we do yipingwang‌ ? Have you tested this on your development kit?

Re: LX2160A RDB uboot log issue

ash_law — Tue, 26 Nov 2019 15:08:48 GMT

I think the problem may lie in a mismatch between the kernel rev level and other software in there. You might have to check and see what packages are actually being drawn in.

Re: LX2160A RDB uboot log issue

johan_duque — Wed, 27 Nov 2019 16:16:17 GMT

I was able to boot the board, It seems I was following an outdated user guide. Thank you very much

Re: LX2160A RDB uboot log issue

ash_law — Tue, 03 Dec 2019 19:30:27 GMT

Can you send me a link to the guide you did end up using to get the board to boot up.

Re: LX2160A RDB uboot log issue

johan_duque — Wed, 04 Dec 2019 10:32:13 GMT

The url is: Layerscape SDK | NXP you need to comment the tools where ldconfig is called, I used flex-builder like this:

source setup.env

flex-builder -i mkrfs -a arm64

flex-builder -c linux -a arm64

flex-builder -m lx2160ardb

Then flashed in the SD all the images inserted and all works fine.

Re: LX2160A RDB uboot log issue

ash_law — Wed, 04 Dec 2019 11:47:02 GMT

Thanks.