ERROR: mmcblk0p1 not found | eeprom writed

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
,
22

I guess the issue is due to you write the emmc based board sku to the eeprom.

So that the plugin-manager here modifies your dts.

[ 0.407690] node /plugin-manager/fragement@0 match with board >=3448-0002-100
[ 0.408240] node /plugin-manager/fragment@1 match with board >=3448-0002-101
[ 0.408705] node /plugin-manager/fragment@3 match with board >=3448-0002-100
[ 0.409484] node /plugin-manager/fragement@7 match with odm-data enable-pmict
[ 0.409731] node /plugin-manager/fragement@8 match with odm-data enable-pmict
[ 0.410346] node /plugin-manager/fragement@10 match with board >=3448-0002-30
[ 0.412333] node /plugin-manager/fragement@13 match with board >=3448-0002-30

I don’t see above log in my boot up log.

A method here is you can disable those fragment in hardware/nvidia/platform/t210/porg/kernel-dts/porg-plugin-manager/tegra210-porg-plugin-manager.dtsi.

Rebuild the dtb and put it during your flash process. I guess the key is fragment@3 because it disables your sdhci controller so sdcard is not able to get run.

23

it work! i’ve use the modifications on #2 and commit all te fragment@3 in the tegra210-porg-plugin-manager.dtsi

1 Like
24

Please restore the eeprom value to the correct one if possible. Thanks.

1 Like
26

hi Wayne,

Now, I have the same iusse, i flashed jetson-nano-4gb-jp441-sd-card-image to sd card with nano B01，i don’t know how to restore the eeprom value to default?

could you help me ?

Thanks.

27

Is your case related to the original post? If not, file a new topic.