Debian 9.3 - BBB ver 5AC repeatedly doesn't boot on µSD card unless boot button is pushed each time.

GoogleGroups
1

Hello,

I installed the following image on a BBB version 5AC:#### microSD/Standalone: (stretch-iot) (All BeagleBone Variants & PocketBeagle)

bone-debian-9.3-iot-armhf-2018-02-18-4gb

Everyting is running fine (at least what I tested: node-red).

The BBB boot button was pushed at startup right at the beginning ( boot on the µSD card ).

The problem is that it has to be repeated (button pushed) after a power outage (in case of a clean shutdown (UPS) after power outage), Otherwise the BBB doesn’t simply boot up. That can be a problem in case of remote installation. I don’t see any warning in the wiki about this behavior

It may be a hardware problem on my rather old BBB ver 5AC. Does anybody encountered the same issue ?

Maybe an addtionnal configuration is needed ?

Any suggestion?

Michel.

PS: I also tried the following version with same result: Debian 9.3 2018-01-28 4GB SD IoT

2

On Fri, 23 Feb 2018 03:27:35 -0800 (PST),
mich.gerin@gmail.com declaimed the following:

Hello,

I installed the following image on a BBB version 5AC:
*microSD/Standalone: (stretch-iot) (All BeagleBone Variants & PocketBeagle)
**bone-debian-9.3-iot-armhf-2018-02-18-4gb*

  <SNIP>

The problem is that it has to be repeated (button pushed) after a power
outage (in case of a clean shutdown (UPS) after power outage), Otherwise
the BBB doesn't simply boot up. That can be a problem in case of remote
installation. I don't see any warning in the wiki about this behavior

It may be a hardware problem on my rather old BBB ver 5AC. Does anybody
encountered the same issue ?

  More likely, it is an antique image on the eMMC.

  I believe it was only about a year or so ago that images were
configured so that the eMMC boot-loader would look at and boot an installed
SD card without needing the boot button.

  Second, newer images are expecting u-Boot device tree (overlay)
handling, whereas the older images put-off device tree overlay handling
until Linux had booted.

  You will probably need to obtain a 2GB image (I presume the "5AC" in
your subject meant "A5C" version), verify that boots from SD card (using
the button), convert to flasher image, flash the eMMC, remove SD card and
verify unit boots from eMMC.

  THEN install your 4GB SD card image and see if the board now detects
and boots from it without holding down the button.

3

Robert covered this last month search list

4

Run:

sudo /opt/scripts/tools/version.sh

Then we will know what your dealing with:

Regards

5

Okay, i was expecting a 2nd entry here..

For kicks try this to clear out the first 10mb of the eMMC..

sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10

if that doesn't solve it, do you have a serial cable to plug into j1?

i'd like to see what's up on bootup, when the boot button is not pressed..

Regards,

6

Probably an Old MLO / uboot.img on the eMMC. If the newer is flashed to the eMMC, this problem would probably go away. I’ve experienced this on many boards myself as / when I forget to update the eMMC.

7

eMMC is read first by the bootrom, if something is there that isn't
suppost to be their it can get stuck..

Regards,

8

Ok thank you again

Michel