Hi All,
we are doing kernel migration from kernel-4.14.98 to 5.10.72_2.2.0 to our custom board based out of IMX8DX.
Source version: linux-imx-5.10.72_2.2.0
we are facing the issue regarding the eMMC mount ,for reference i have attached the logs and defconfig below, please have a look and Kindly help on this issue.
[ 1.384161] VFS: Cannot open root device "mmcblk0p1" or unknown-block(0,0): error -6
[ 1.389124] platform regulatory.0: Falling back to sysfs fallback for: regulatory.db
[ 1.396854] Please append a correct "root=" boot option; here are the available partitions:
[ 1.412938] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 1.421165] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.10.72-lts-5.10.y+ga68e31b63f86 #1
Seems the mmcblk0 is not exist.
Please check the emmc setting in the dts file.
Thanks for reply,
yes , we have add mmc related changes in dts file.
Below are the changes related to eMMC. please have a look.
Included DTSI files are:
#include "imx8dx.dtsi"
#include "imx8x-mek.dtsi"
This is the USDHC1 node which we are adding into our dts file.
&usdhc1 {
pinctrl-names = "default", "state_100mhz", "state_200mhz";
pinctrl-0 = <&pinctrl_usdhc1>;
pinctrl-1 = <&pinctrl_usdhc1_100mhz>;
pinctrl-2 = <&pinctrl_usdhc1_200mhz>;
bus-width = <8>;
non-removable;
status = "okay";
};
Kindly let me know is something we are missing in our dts file.
In the imx8x-mek.dtsi, there are already usdhc1 setting for the EMMC.
Hi Jimmy,
I agree that the node USDHC1 is already present in imx8x-mek.dtsi. And we have removed the the duplicated node USHDC1 from our dts file.
we tried with these changes also , but still facing the issue.
can you help us here,
Do you use the UUU to program the rootfs image to the mmcblk0p1?
yes , we use UUU tool to program the rootfs image.
please check the partition mmcblk0p1 is well created.