On Sat, May 4, 2019 at 2:08 AM <[email protected]> wrote: > > Thank you! I found your response helpful. > > I tested bbxm-debian-9.9-lxqt-xm-armhf-2019-04-28-4gb.img.xz image with my > existing card and it booted reliably. I tested both cold boot and restart > multiple times. I did not even see the mmc issue come up once with that image. > > I'm still considering buying a better SD card. I found this thread discussing > the issue from 2015 > https://github.com/RobertCNelson/armv7-multiplatform/issues/25 . As far as I > understand, the issue is not read/write speed, but rather SD-card's boot time > which is not typically specified for SD-cards and might not correlate with > the card's price range - that makes an informed choice more difficult. I > think I'll first try Strontium Nitro 16 GB Class 10 card. Do you have any > recommendations with regard to SD-card products or brands that have worked > for you in the past?
I just use Sandisk refurbished units, i go thru so many when testing boards.. it's just cheaper to get reburb's when i know they will burn out in a few months. ;) But this mmc -110 has been an odd issue since 2015, as long as it boots, you should be good to go now.. > > *** > > As a side note, I successfully moved the image to SD-card using dd. However, > I noticed the image build directory had a *.bmap file so out of curiosity I > tried using bmaptool to flash the card, however it failed. Was I doing it > right? (bmaptool version 3.2 on Ubuntu 16.04) > > $ sudo bmaptool copy > https://rcn-ee.net/rootfs/bb.org/testing/2019-04-28/stretch-lxqt-xm/bbxm-debian-9.9-lxqt-xm-armhf-2019-04-28-4gb.img.xz > /dev/sdc > bmaptool: info: discovered bmap file > 'https://rcn-ee.net/rootfs/bb.org/testing/2019-04-28/stretch-lxqt-xm/bbxm-debian-9.9-lxqt-xm-armhf-2019-04-28-4gb.bmap' I've also never had any luck having bmaptool directly down the image/bmap.. But note, on the xM, you'll want to dd the start of the microSD before you run bmaptool, as it doesn't zero out the first couple MB.. Which could cause the xM's bootrom to get confused, expecially if it had a BeagleBone image on the microSD.. For example: (if you have a BeagleBoard Black and xM) Burn microsd for BeagleBoard Black.... Black boots.. Take that same card and using bmaptool to write the xM image, the xM will fail to boot, as bmaptool didn't erase the BeagleBoard Black's version of u-boot at the start of the microSD. Which then confuse the xM boot rom, (which doesn't support raw boot, but still get's stuck..) 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/CAOCHtYgkMuaYQqZY31GSWWmFd61LygL1j2YS%3DXp15x5JEFaCCg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
