On Fri, Jun 26, 2015 at 1:32 PM, Dr. H. Nikolaus Schaller <[email protected]> wrote: > I have found in this article that the mapping is well defined: > > http://thethingsystem.com/dev/Bootstrapping-the-BeagleBone-Black-with-Debian.html > > "NOTE: The booted device is always device 0, i.e. mmcblk0. The internal eMMC > always has the mmcblkXboot0 and mmcblkXboot1 entries. If the device is booted > from eMMC the entries will be mmcblk0boot0 and mmcblk0boot1. If the device is > NOT booted from eMMC the entries will be mmcblk1boot0 and mmcblk1boot1.” > > On the OMAP5 EVM it appears that eMMC is always /dev/mmcblk0 and SD card is > /dev/mmcblk1 independently from where I boot. So the “boot device” appears > not to be stable. This makes it a little difficult to write scripts that are > generic for both. > > I use a 4.1 kernel with just different DT files. Otherwise the same binaries. > Well, MLO and u-boot also differ, but my issue is how the kernel does the > mapping. > > Any hints how this is achieved on the BBB? Or is it just good luck (different > boot activity sequence between AM335x and OMAP5)?
Using: /sys/devices/platform/ it maps them by address omap5-uevm: 480b4000.mmc = mmc0 = eMMC 480ad000.mmc = mmc1 = un-used 4809c000.mmc = mmc2 = microSD bbb: 48060000.mmc = mmc0 = microSD 481d8000.mmc = mmc1 = eMMC aka... Always use an initrd with multiple platforms and use uuid's. ;) Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
