http://beagleboard.org/latest-images/ now has the 2014-05-14 image linked and CircuitCo is making the switch to flashing this on the board thanks to improvements in the flasher. Primarily, the flasher now shuts the board down after boot, so the LEDs will be all off, rather than all on when the flash completes. Note that the next revision will likely also change the LED flashing patterned during the flashing operation.
Urgh. I thought you were copied on the other thread and just realized you weren’t. We need to keep lists in copy rather than allowing anyone to hand-pick people to CC.
After you asked the OpenROV project on Github on what to do to get OpenROV over to debian I had a go at the Debian images.
I tried to get the latest Debian demo image (from http://elinux.org/BeagleBoardDebian) running on the BeagleBone Black (I think its a revision B).
I tested it with both, debian-7.5-console-armhf-2014-05-06.tar.xz and debian-jessie-console-armhf-2014-05-06.tar.xz and wrote it to an SD card with --dtb beaglebone.
But when I put it in the BBB it doesn’t seem to boot up properly.
I can’t get a network connection, not on the LAN port nor if I connect it via USB to my laptop.
I checked the /var/log/messages and /var/log/dmesg afterwards and it ends with a message that the root partition wasn’t cleanly unmounted and should be checked with fsck but nothing more.
The heartbeat is still going on though.
I will try to hook up a second BBB via UART to the serial debug output to see if I can get anything more.
Do you have any hint in what could cause that issue?
After you asked the OpenROV project on Github on what to do to get OpenROV
over to debian I had a go at the Debian images.
I tried to get the latest Debian demo image (from BeagleBoardDebian - eLinux.org) running on the BeagleBone Black (I
think its a revision B).
I tested it with both, debian-7.5-console-armhf-2014-05-06.tar.xz and
debian-jessie-console-armhf-2014-05-06.tar.xz and wrote it to an SD card
with --dtb beaglebone.
This is a long standing bug, that i didn't fix till yesterday..
"--dtb" only choose the generic multi platform kernel, thus the "--dtb
beaglebone" would not have much working.. With the "2014-05-06" use
"--uboot bone"..
Of course, i released a new image last night "2014-06-05" (maybe a
should have waited a few more days so the numbers were so oddly
close)..
Which "--dtb beaglebone" now works thanks to:
But when I put it in the BBB it doesn't seem to boot up properly.
I can't get a network connection, not on the LAN port nor if I connect it
via USB to my laptop.
I checked the /var/log/messages and /var/log/dmesg afterwards and it ends
with a message that the root partition wasn't cleanly unmounted and should
be checked with fsck but nothing more.
The heartbeat is still going on though.
I will try to hook up a second BBB via UART to the serial debug output to
see if I can get anything more.
Do you have any hint in what could cause that issue?