Hi Jose, I don't know if you're using a custom device tree or not, but I ran into this issue and solved it by disabling write protection in the device tree:
https://github.com/kratsg/meta-l1calo/blob/master/recipes-bsp/device-tree/files/gfex-prototype4/gfex-prototype4.dts#L48-L51 &sdhci1 { disable-wp; }; Giordon On Sun, Mar 4, 2018 at 8:20 PM Jose David Bravo Alvarez < [email protected]> wrote: > I'm building a image using Yocto rocky and Xilinx for my zynq-702 board. > > > But for some reason my root file system can only be mounted as a read > only. If I put rw in the u-boot load command it fails. I'm booting from a > SD card, that doesn't have any lock switch. > > > And if I boot using other kernel different than the one generated by yocto > it does mount the file system as read write... the problem is somewhere in > my image and not physical in the SD card or in the controller. > > > If generate my yocto image using a qemux86 machine, it does work good and > mount the partition as rw. > > > This is the latest part of my boot log: > > Waiting for root device /dev/mmcblk0p2... > > mmc0: new high speed SDHC card at address aaaa > > mmcblk0: mmc0:aaaa SL08G 7.40 GiB (ro) > > mmcblk0: p1 p2 > > VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2): error > -30 > Please append a correct "root=" boot option; here are the available > partitions: > 0100 16384 ram0 (driver?) > > 0101 16384 ram1 (driver?) > > 0102 16384 ram2 (driver?) > > 0103 16384 ram3 (driver?) > > 0104 16384 ram4 (driver?) > > 0105 16384 ram5 (driver?) > > 0106 16384 ram6 (driver?) > > 0107 16384 ram7 (driver?) > > 0108 16384 ram8 (driver?) > > 0109 16384 ram9 (driver?) > > 010a 16384 ram10 (driver?) > > 010b 16384 ram11 (driver?) > > 010c 16384 ram12 (driver?) > > 010d 16384 ram13 (driver?) > > 010e 16384 ram14 (driver?) > > 010f 16384 ram15 (driver?) > > b300 7761920 mmcblk0 driver: mmcblk > > b301 1048576 mmcblk0p1 9d7a9d10-01 > > b302 6712320 mmcblk0p2 9d7a9d10-02 > > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(179,2) > CPU1: stopping > > CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.9.0-xilinx-v2017.3 #1 > > Hardware name: Xilinx Zynq Platform > > [<c010e3ac>] (unwind_backtrace) from [<c010a5f0>] (show_stack+0x10/0x14) > > [<c010a5f0>] (show_stack) from [<c02dcce4>] (dump_stack+0x80/0xa0) > > [<c02dcce4>] (dump_stack) from [<c010cb58>] (ipi_cpu_stop+0x3c/0x70) > > [<c010cb58>] (ipi_cpu_stop) from [<c010d388>] (handle_IPI+0x64/0x84) > > [<c010d388>] (handle_IPI) from [<c0101420>] (gic_handle_irq+0x80/0x8c) > > [<c0101420>] (gic_handle_irq) from [<c010b00c>] (__irq_svc+0x6c/0xa8) > > Exception stack(0xde471f70 to 0xde471fb8) > > 1f60: 00000000 00000000 1e29c000 > debde9c0 > 1f80: 49d2e7a1 00000000 debdde40 00000001 47add66a 00000000 00000000 > 00000001 > 1fa0: 00000015 de471fc0 c04af5dc c04af600 60000013 ffffffff > > [<c010b00c>] (__irq_svc) from [<c04af600>] > (cpuidle_enter_state+0xe4/0x1b4) > [<c04af600>] (cpuidle_enter_state) from [<c014cdb4>] > (cpu_startup_entry+0x18c/0) > [<c014cdb4>] (cpu_startup_entry) from [<001014cc>] (0x1014cc) > > ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-bl) > > Thanks for your help! > > > Jose Bravo > -- > _______________________________________________ > yocto mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/yocto > -- Giordon Stark
-- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
