Amazing looks to all be working now! eMMC is viewable when booting off the micro SD and I was able to eventually get my 3.14.X image onto the eMMC of the newer BBB's
An alternative work around suggested by arno01, for the dpkg-deb error I was having, can be found at the very bottom of the link https://github.com/aptly-dev/aptly/issues/655 <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Faptly-dev%2Faptly%2Fissues%2F655&sa=D&sntz=1&usg=AFQjCNERdhwM6d0NoI3VZKrd7MJeoVoPKA> can also fix this issue. Run the following commands within your directory that contains the .deb files of interest to gzip the .deb file instead of xz'ing it. Hopefully no one will need it, as Robert has updated the repo dpkg-deb -R package.deb tmp rm package.deb fakeroot dpkg-deb -Zgzip -b tmp package.deb rm -rf tmp One final note, for anyone else experiencing issues flashing these 3.14.x patched images, is that I found flashing this image to the eMMC first https://debian.beagleboard.org/images/bone-debian-7.11-lxde-4gb-armhf-2016-06-15-4gb.img.xz Then booting into it and uncommenting out the last line of /boot/uEnt.txt to enable the eMMC flasher ##enable BBB: eMMC Flasher: cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh Before flashing my 3.14.x patched image worked well. This image contains kernel 3.8.13-bone80, which also has the eMMC patch backported to it. When I tried flashing my 3.14.x patched image while an image with say a 4.X version kernel was already on the eMMC, then the contents of my SD card would get erased (instead of the eMMC) during the flashing process On Wednesday, 19 February 2020 11:48:25 UTC+11, RobertCNelson wrote: > > On Tue, Feb 18, 2020 at 6:37 PM Untitled X <[email protected] > <javascript:>> wrote: > > > > Hey thanks again Robert for going out of your way to provide a procedure > for 3.14.x , and especially for replying while away on your holiday! > > > > Following the procedure for the dpkg method, in which the file > "0001-mmc-Allow-forwar-compatibility-for-eMMC.patch" in placed in > /yakbuild/patches/local_patches/ and then running ."/build_sh" seems to > work ok on my Ubuntu 19.10 VM, it yielded me the following files in the > /yakbuild/deploy/ > > > > linux-firmware-image-3.14.77-ti-r90_1xross_armfhf.deb > > linux-headers-3.14.77-ti-r90_1xross_armhf.deb > > linux-image-3.14.77-ti-r90_1xross_armhf.deb > > linux-libc-dev_1xross_armhf.deb > > > > Placing the file "linux-image-3.14.77-ti-r90_1xross_armhf.deb" on my BBB > attempting to run the command "sudo dpkg -i > linux-image-3.14.77-ti-r90_1xross_armhf.deb" however gave me the following > error: > > > > dpkg-deb error: archive 'linux-image-3.14.77-ti-r90_1xross_armhf.deb" > contains not understood data member control.tar.xz, giving up > > dpkg: error processing linux-image-3.14.77-ti-r90_1xross_armhf.deb > (--install): > > subprocess dpkg-deb --control returned error exit status 2 > > Errors were encountered while processing: > > linux-image-3.14.77-ti-r90_1xross_armhf.deb > > Ah crap, so we had a workaround for "3.8.13" to detect this, but it > got ignored on "3.14.x"... This should fix it: > > > https://github.com/RobertCNelson/yakbuild/commit/991c2f18f94d490861776a92424fba2d560660b1 > > > Just run: > > git pull ; ./build_deb.sh > > and it "should" work this time.. fingers crossed.. > > 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/402558c3-61da-4ba4-b5d8-da31232db4df%40googlegroups.com.
