Quantcast

QUESTION: How to start /dev/mmcblk0 device after yocto boot from NAND?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

QUESTION: How to start /dev/mmcblk0 device after yocto boot from NAND?

rdixey@comcast.net

Hello Gumstix Users,


When booting Yocto Linux overo 3.18.18-custom from NAND, if there is no MicroSD card inserted in the drive while booting, then I have no access to the MIcroSD drive if i insert it after fully booted. There are no /dev entries such as /dev/mmcblk0, etc.


It appears as though there is no driver initialized for the mmcblk0 device. How do I start it up?

I tried experimenting with modprobe and systemctl but no success. 

Is there a driver or service that needs to be started?


root@overo:~# dmesg | grep mmc
[ 0.997528] pbias_mmc_omap2430: 1800 <--> 3000 mV at 3000 mV
[ 3.137054] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@4809c000[0]'
[ 3.137084] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@4809c000[0]'
[ 3.138549] omap_hsmmc 4809c000.mmc: unable to get vmmc regulator -517
[ 3.146026] platform 4809c000.mmc: Driver omap_hsmmc requests probe deferral
[ 3.153930] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@480b4000[0]'
[ 3.153961] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@480b4000[0]'
[ 3.154785] omap_hsmmc 480b4000.mmc: unable to get vmmc regulator -517
[ 3.161895] platform 480b4000.mmc: Driver omap_hsmmc requests probe deferral
[ 3.800994] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@4809c000[0]'
[ 3.801025] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@4809c000[0]'
[ 3.844665] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@480b4000[0]'
[ 3.844696] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@480b4000[0]'
[ 3.931854] mmc1: new SDIO card at address 0001
[ 15.148376] libertas_sdio mmc1:0001:1 (unnamed net_device) (uninitialized): 00:19:88:14:84:0b, fw 9.70.20p0, cap 0x00000303
[ 15.207763] libertas_sdio mmc1:0001:1 wlan0: Marvell WLAN 802.11 adapter
root@overo:~# dmesg | grep mmcblk0

root@overo:~#


***************ON THE OTHER HAND**********************************************************************************

If I insert the MicroSD card just after the u-Boot count down right as Yocto starts booting from NAND then these devices are present after fully booted. And I can use mount to mount the devices to files as specified in /etc/fstab. 


overo login:
Poky (Yocto Project Reference Distro) 1.8 overo ttyO2

overo login: root
root@overo:~# dmesg | grep mmcblk0
[ 4.074005] mmcblk0: mmc0:b368 7.45 GiB
[ 4.085845] mmcblk0: p1 p2 p3
[hidden email]


root@overo:~# ls /dev/mmc*
/dev/mmcblk0 /dev/mmcblk0p1 /dev/mmcblk0p2 /dev/mmcblk0p3


root@overo:~# mount /dev/mmcblk0p2 /media/fsroot
[ 805.249053] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
root@overo:~#
root@overo:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
ubi0:rootfs 463488 97824 365664 22% /
devtmpfs 241328 0 241328 0% /dev
tmpfs 249728 0 249728 0% /dev/shm
tmpfs 249728 4520 245208 2% /run
tmpfs 249728 0 249728 0% /sys/fs/cgroup
tmpfs 249728 0 249728 0% /tmp
tmpfs 249728 8 249720 1% /var/volatile
tmpfs 49948 0 49948 0% /run/user/0
/dev/mmcblk0p2 3998400 1488072 2287508 40% /media/fsroot


------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Loading...