I am having Custom i.MX6ULL based board(NAND boot) which is currently having 4.1.15 Kernel . Now I am trying to port Latest NXP community BSP(https://www.nxp.com/docs/en/user-guide/i.MX_Yocto_Project_User%27s_Guide_Linux.pdf ). This has following Items :
My plan is to retain older Uboot and just change Linux kernel and Rootfs. For this I ported My device tree(DTB) , defconfig and board file related to my board. But unfortunately Booting stops in "Starting kernel ..."
U-Boot 2015.04 (Jun 17 2019 - 16:13:02)
CPU: Freescale i.MX?? rev1.1 at 396 MHz
CPU: Temperature 45 C
Reset cause: POR
Board: i.MX6UL iW-RAINBOW-G18M-SM
Boot Device: NAND
I2C: ready
DRAM: 256 MiB
PMIC: PFUZE300 DEV_ID=0x31 REV_ID=0x11
NAND: 1024 MiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Board Info:
BSP Version : iW-PRFYB-SC-01-R1.0-REL1.0-Linux4.1.15
SOM Version : iW-PRFYB-AP-01-R1.x
CPU Unique ID : 0x453b91d260435a43
Net: FEC0
Normal Boot
Hit any key to stop autoboot: 0
iWave-G26P> setenv bootcmd 'nand read ${loadaddr} 0xA00000 0x1000000;nand read ${fdt_addr} 0x1A00000 0x1000000;bootz ${loadaddr} - ${fdt_addr}'
iWave-G26P>
iWave-G26P>
iWave-G26P> boot
NAND read: device 0 offset 0xa00000, size 0x1000000
16777216 bytes read: OK
NAND read: device 0 offset 0x1a00000, size 0x1000000
16777216 bytes read: OK
Kernel image @ 0x80800000 [ 0x000000 - 0x49ecf0 ]
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300ab09
Starting kernel ...
I have Few doubts here. I am using older version of Uboot
Thanks in Advance.
Keshava Kumar B
Hi Keshava
>My plan is to retain older Uboot and just change Linux kernel and Rootfs.
this may be issue. Recommendation is to use nxp linux
freescale\dts\boot\arm64\arch - linux-imx - i.MX Linux kernel
and corresponding with it imx_v2017.03_4.9.88_2.0.0_ga uboot
Note, community bsps are not supported by nxp, issue may be posted on
meta-fsl-arm mailing list:
meta-freescale Info Page
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------