I'm trying to play around with the Ubuntu snappy core image for BeagleBone Black from here: https://developer.ubuntu.com/en/snappy/start/#try-beaglebone
I downloaded the image and wrote it to a 32GB microSD card, then inserted into a BBB that would otherwise be running Debian Wheezy from the eMMC, using the following steps: 1. Shutdown BBB (sudo halt) 2. When powered off, Insert microSD card 3. Push and hold User/Boot button, then reapply power 4. After a few seconds let go of User/Boot button The image will not boot at all after this - none of the LEDs come on. (I'm assuming that they would also come on in the standard order on the Ubuntu image if everything were going right.) What's even more puzzling, when I insert the microSD card into the BBB while it is booted from eMMC (into Debian Wheezy) to inspect it, the system freezes within about 1-2 minutes. Upon rebooting from eMMC, the syslog suggests that the system ran into out of memory and the OOM killer was active. I'm stumped as to why and how this can happen simply from inserting the card. The card otherwise works fine - I can put Debian Wheezy images on it and boot them just fine. When the Ubuntu snappy image is flashed on the card, the FAT boot partition with which it mounts on MacOSX looks OK. The uEnv.txt file on there is zero bytes, but based on what I can find online, Ubuntu has moved away from using the uEnv.txt file, so I think this being zero bytes may well be a red herring. This being the one official image for the BBB for Ubuntu snappy core, I feel I must have done something wrong, but I don't see what and where. Any suggestions would be much appreciated. -hilmar -- 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.
