On Tue, 11 Dec 2018 19:05:37 -0800 (PST), Marius Strom
<brmariustor@gmail.com> declaimed the
following:
Using the Etcher program suggested by the quick start guide, I've burned a
16GB microSD card once with the image for Debian Linux v9.5 and, after that
failed, with Debian Linux v9.1. Both times, the only change I've done is
to edit /boot/uEnv.txt as directed to make sure
that cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh is
uncommented.
Why "uncommented"? I'd recommend leaving the SD card as a non-flashing
image until you've confirmed the image works -- eg; that command is
/commented out/ (with # at the start). I have no idea what a PocketBeagle
will do with a flasher image -- it doesn't have an eMMC, does it?. Which
image? IoT or LXQT?
*Booting with Debian v9.1*
Upon plugging in the PB to USB, all 4 LEDs light up momentarily. They all
go off, and USR0 starts its heartbeat pattern. USR1 starts to blink
intermittantly and the Octavo chip starts to heat up. After about 5
seconds, all four LEDs light up simultaneously. I let it stay that way for
5-10 more seconds before the Octavo chip gets too warm and unplug the USB.*Booting with Debian v9.5*
1 - Upon plugging in the PB to USB, all 4 LEDs light up momentarily.
2 - They all go off, and USR0 starts its heartbeat pattern and USR2 is on.
USR1 starts to blink intermittantly.
3 - After about 20 seconds, USR2 blinks quickly and intermittently while
being dim, USR1 stays off, and USR0 continues its heartbeat pattern.
4 - The Octavo chip is starting to get warm. I let it stay that way for 30
more seconds and unplug the USB.
It takes a BBB powered from USB and booting from on-board eMMC 47
seconds to when Windows beeps that it has discovered the device. The output
from dmesg indicates that booting completed at 59 seconds.
[ 26.999093] usb1: MAC d0:39:72:18:3e:ea
[ 27.348278] configfs-gadget gadget: high-speed config #1: c
[ 28.135015] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[ 58.981321] pruss 4a300000.pruss: creating PRU cores and other child
platform devices
[ 59.076416] remoteproc remoteproc1: 4a334000.pru is available
[ 59.076544] pru-rproc 4a334000.pru: PRU rproc node
/ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully
[ 59.096145] remoteproc remoteproc2: 4a338000.pru is available
[ 59.096270] pru-rproc 4a338000.pru: PRU rproc node
/ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully
debian@beaglebone:~$
Note the long delay between 28 and 58 seconds...
debian@beaglebone:~$ uname -a
Linux beaglebone 4.14.49-ti-r54 #1 SMP PREEMPT Fri Jun 15 22:14:13 UTC 2018
armv7l GNU/Linux
debian@beaglebone:~$
Booting from SD card to 43 seconds to Windows beep... But 62 seconds to
complete.
[ 25.864069] configfs-gadget gadget: high-speed config #1: c
[ 26.889293] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[ 62.802778] pruss 4a300000.pruss: creating PRU cores and other child
platform devices
[ 62.833125] remoteproc remoteproc1: 4a334000.pru is available
[ 62.833251] pru-rproc 4a334000.pru: PRU rproc node
/ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully
[ 62.860167] remoteproc remoteproc2: 4a338000.pru is available
[ 62.860289] pru-rproc 4a338000.pru: PRU rproc node
/ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully
debian@beaglebone:~$ uname -a
Linux beaglebone 4.14.49-ti-r54 #1 SMP PREEMPT Fri Jun 15 22:14:13 UTC 2018
armv7l GNU/Linux
debian@beaglebone:~$