Thanks much for your efforts. For one, your results were the final nudge I needed to buy a USB to TTL serial debug cable. It’s possible that I didn’t have enough patience with LEDs all dark and not being able to see any indications of it actually booting. From booting the BeagleBoard Debian Wheezy images from uSD I was used to seeing the LEDs come on very quickly, so I was apparently mistaken to assume this would be the same for the Snappy Core image.
Second, the fact that booting the image flashed your eMMC is not cool. I was in fact wondering whether it would or not. The documentation is silent about this question, and the file name of the image contains no suggestion that it flashes the eMMC. On AskUbuntu, someone actually asked whether there is a flasher image: http://askubuntu.com/questions/713604/snappy-on-beaglebone-black-or-green The answer basically repeats the documentation from developer.ubuntu.com (which does not say anything about flashing versus not), and upon being specifically asked in the comments by people for whom the image failed to flash the eMMC, the poster admits they don’t know about that part. I also tried to glean the answer from the snappy-boot.txt file that it uses instead of the uEnv.txt, but there’s nothing in there that obviously indicates that the eMMC will be flashed. To me, whether booting the image will or will not flash your eMMC is a rather important distinction, so to me this is a red flag. On top of that, based on what I can find 15.04 is *only* available as Snappy Core for armhf systems, which means that even just basic things such as installing apache become a huge hassle: http://askubuntu.com/questions/694397/how-to-install-apache-on-a-raspberry-pi-2-ubuntu-snappy-core Based on this experience, while they have nice looking websites, I’m afraid the Ubuntu folks don’t have their act together for Ubuntu on BBB, and as a consequence I’ll stay away from them and their images for now. -hilmar > On Jan 1, 2016, at 11:57 PM, doog <[email protected]> wrote: > > for whatever reason I could not get it to boot back into the uSD and it > started to go back to flashing(cylon eyes). I looked at the partitions and > there were only 2. After re-imaging the uSD card, I saw 4 partitions. And > while I was re-imaging I tried to boot from eMMC and it would not, the failed > flashing left the eMMC goofed up. > > But the good news is, once I finished re-imaging, I booted and got back into > Ubuntu Snappy Core. Another thing of interest is that while I held down the > S2/User/Boot button I didn't get any LEDs lit but it started booting into the > uSD card so I let go of the button. It took a minute of booting/testing > before it went to town and started loading from uSD(ie LEDs ablaze). > > I don't know why the 32G Samsung didn't work but I may have forgot what's the > max uSD size for BBB is. > > -- > For more options, visit http://beagleboard.org/discuss > <http://beagleboard.org/discuss> > --- > You received this message because you are subscribed to a topic in the Google > Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/6_I1Ox9-sms/unsubscribe > <https://groups.google.com/d/topic/beagleboard/6_I1Ox9-sms/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- Hilmar Lapp -:- lappland.io -- 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.
