On Sun, Feb 9, 2020 at 6:20 PM <[email protected]> wrote: > > > Hi guys > > I am having an issue where I am unable to flash the eMMC of newer Beaglebone > black boards that ship with the Kingston EMMC04G-M627 eMMC (and probably a > newer kernel version), with our Debian 7.11 image, that uses kernel > 3.14.77-ti-r90. In the past, we have had no issue flashing the older > Beaglebone black boards that use Kingston EMMC04G-S100 eMMC with this > image/kernel combination and it works quite well for our application. > > > I have been able to flash other images through the usual method of > uncommenting the last line of boot/uEnv.txt > (#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh) to use the > eMMC flasher, but in this case, it fails since the eMMC can’t be seen. > > > Putting the image on an SD card and booting off the SD seems to work fine, > but unfortunately my bosses will not accept this solution. Additionally, I > noticed that when booting this image from the SD card, the eMMC can’t be seen > when using the “blkid” command. I am a bit confused since I thought the > unrecognized eMMC issue was fixed on June 15, 2016, and kernel 3.14.77 was > released after this.
Sorry, that's not how the kernel development works, just because a patch was committed to the master branch, does not mean it will be automatically pushed to the older stable branches. Someone needs to go thru the effort of testing and requesting to have it back-ported. So yes, while it was "fixed" before v3.14.77 was released, it was never back-ported to the v3.14.x branch.. Here is the patch in question: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/drivers/mmc/core/mmc.c?h=v3.17 mmc: Allow forward compatibility for eMMC https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/mmc/core/mmc.c?h=v3.17&id=03a59437ef6b6ad7fb0165cb9b96c08d6bf057fc If you guys are stuck on v3.14.x, do you need me to write up a procedure similar to what i did for 3.8.x users stuck on ancient kernels too: aka like this: https://gist.github.com/RobertCNelson/39faf80ddc9fcefae74dce2c6ca2eb45 > So far, I’ve attempted the following: > > -Run the update kernel script found in /opt/scripts/tools/update_kernel.sh, > but of course it seems that the release is so old that this no longer works, > even with the --no-check-certificate, as detailed in posts made by other > members Wheezy (with armhf) went EOL on May 31st 2018: https://wiki.debian.org/LTS Wheezy's wget doesn't fully 100% support "https".. > -Install the kernel 3.8.13-bone84_1wheezy, which can be seen here > https://groups.google.com/forum/#!topic/beagleboard/IgnJB-vATTU In this case > installing any 3.8.X kernel caused my image to no longer boot, but installing > other 3.14.XX kernels listed on > http://repos.rcn-ee.net/debian/pool/main/l/linux-upstream/ seemed to boot ok, > but this still rendered the eMMC unviewable. I was able to however install > kernel 3.8.13-bone84 to a Debian 8.7 image on eMMC > (bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz), which I got from the > official beaglebone download page, which comes with a version 4.X kernel. Show us your "serial" boot log over the J1 connector.. > > https://www.element14.com/community/thread/61956/l/flash-old-debian-79-image-from-usd-to-newer-bbb-debian-83?displayFullThread=true. > I do know however that we use a custom cape to run some additional hardware > in conjuction with our image, perhaps this is why it doesn't boot after > installing the 3.8.13-bone84 kernel? > > > > Apologies is anything I’m asking is silly, I am still an embedded linux > newbie. I do think that if I am able to have the eMMC viewable, when booting > off the SD, then I can use something like > https://github.com/RobertCNelson/tools/blob/master/scripts/beaglebone-black-copy-microSD-to-eMMC.sh > or the command "dd if=/path/to/your_image.img of=/dev/mmcblk0 bs=1M" to > copy the SD contents to the eMMC. Or initiate the usual eMMC flasher, etc > > > Let me know if you guys require any further information! > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYj1rjj8o4T4ODBFK%3DXwBqn6Q33WZh%3D63v7igL%2BzNs_s6A%40mail.gmail.com.
