boot fitImage on i.MX8mp

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

boot fitImage on i.MX8mp

202 Views
francesco_giust
Contributor II

Hi,

I build fitImage for u-boot, but I am not able to boot image.

During boot I get this error:

[ 3.291520] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[ 3.299048] Please append a correct "root=" boot option; here are the available partitions:
[ 3.307436] 1f00 32768 mtdblock0
[ 3.307442] (driver?)
[ 3.314004] b300 30621696 mmcblk2
[ 3.314007] driver: mmcblk
[ 3.320830] b301 85196 mmcblk2p1 076c4a2a-01
[ 3.320834]
[ 3.327658] b302 1299318 mmcblk2p2 076c4a2a-02
[ 3.327662]
[ 3.334499] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

Do I miss some configurations into u-boot?

I tested build with official kirkstone and scarthgap, for i.MX8mp evaluation board, but I get same error

Thanks,

Francesco

0 Kudos
Reply
5 Replies

171 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hello,

Did you append the bootargs in its file? Can you share your fitimage setting?

Best Regards,
Zhiming

0 Kudos
Reply

155 Views
francesco_giust
Contributor II

Hello,

I use 

KERNEL_CLASSES += "kernel-fitimage"
KERNEL_IMAGETYPES += " fitImage "

in local.conf to enable fitImage.

Is there a specific field in its file to add bootargs ? I didn't find this information anywhere, could you send me an example ?

 

BR,

Francesco

0 Kudos
Reply

133 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hello,

Is there any other steps? I tried it on L6.6.52, there is no such issue. Please check if the rootfs mout point is correct.

The key logs:

[    0.000000] Kernel command line: console=ttymxc1,115200 root=/dev/mmcblk2p2 rootwait rw
[    2.191335] mmcblk2: mmc2:0001 DG4032 29.1 GiB
[    2.200753]  mmcblk2: p1 p2
[    2.204079] mmcblk2boot0: mmc2:0001 DG4032 4.00 MiB
[    2.210023] mmcblk2boot1: mmc2:0001 DG4032 4.00 MiB
[    2.213232] [drm] Initialized vivante 1.0.0 20170808 for 40000000.mix_gpu_ml on minor 0
[    2.216800] mmcblk2rpmb: mmc2:0001 DG4032 4.00 MiB, chardev (234:0)



Best Regards,
Zhiming

0 Kudos
Reply

117 Views
francesco_giust
Contributor II

I have an empty botoargs

[ 0.000000] Kernel command line:

is it not taken from u-boot environment ? 

I have 

console=ttymxc1,115200

mmcroot=/dev/mmcblk1p2 rootwait rw

mmcargs=setenv bootargs ${jh_clk} ${mcore_clk} console=${console} root=${mmcroot}

 

Regards,

Francesco

0 Kudos
Reply

94 Views
Zhiming_Liu
NXP TechSupport
NXP TechSupport

Hello,

Can you try to boot without fitImage to verify if there is any issue in your uboot?

The Uboot should give bootargs to kernel under normal circumstances.

Best Regards,
Zhiming

0 Kudos
Reply