Robert, oh right the other bit of information I needed to let you know about . . .
debian@beaglebone:~$ cd /opt/scripts/tools/developers/ debian@beaglebone:/opt/scripts/tools/developers$ git pull Already up-to-date. Where the boot log still says . . . [116467.340818] reboot: Restarting system U-Boot SPL 2017.01-rc2-00002-g52b3c56009 (Dec 23 2016 - 16:22:21) Trying to boot from MMC2 U-Boot 2017.01-rc2-00002-g52b3c56009 (Dec 23 2016 - 16:22:21 -0600), Build: jenk ins-github_Bootloader-Builder-493 CPU : AM335X-GP rev 2.1 So apparently, for now. I'm unable to "play". I'd so an apt-get update. But somehow, I don't think that'd work ;) On Thu, Dec 29, 2016 at 6:12 PM, William Hermans <[email protected]> wrote: > > On Thu, Dec 29, 2016 at 6:05 PM, Robert Nelson <[email protected]> > wrote: > >> You just stumbled on the biggest issue... >> >> Debugging's going to be fun.. Specially if the end user doesn't have >> a usb-serial cable.. >> >> After u-boot patches the device-tree, the kernel will never know.. >> (that's also why things, video/mmc/wl18xx will also just work better) >> >> > Honestly, and obviously just my opinion. But if anyone is truly serious > about using a beaglebone black / green*. They really need a serial debug > cable. Otherwise, they should just "stay home". As far as spending a little > extra time reading a couple logs, versus just one . . .yeah whatever. If > you're serious, you're serious. A small price to pay for such a useful bit > of hardware that can be used in many different ways. > -- 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/CALHSORqn-4-7jb%2BFK5fGY6o-vWsfHtEojNH_E5noDSVVTieLdQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
