Device not booting

[sbender]

Any ideas why my Beaglebone is not booting and connecting to balenaCloud?

Trying to boot from MMC1
Loading Environment from EXT4…
** Unable to use mmc 0:1 for loading the env **

U-Boot 2018.11 (Jan 14 2019 - 10:13:08 +0000)

CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver ‘omap_hsmmc’
No match for driver ‘omap_hsmmc’
Some drivers were not found
Reset Source: watchdog reset has occurred.
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4…
** Unable to use mmc 0:1 for loading the env **
Board: BeagleBone Black
Model: SanCloud BeagleBone Enhanced
not set. Validating first E-fuse MAC
BeagleBone Black:
Model: SanCloud BeagleBone Enhanced:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x54:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x55:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x56:
Timed out in wait_for_event: status=0000
Check if pads/pull-ups of bus are properly configured
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net: eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[BBEN] …
Scanning MMC and USB devices 0 1 2
24 bytes read in 1 ms (23.4 KiB/s)
Found resin flasher on mmc 0
Loading resinOS_uEnv.txt from mmc device 0 partition 1
** Unable to read file resinOS_uEnv.txt **
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
** Unable to read file uEnv.txt **
switch to partitions #0, OK
mmc0 is current device
debug: [enable_uboot_overlays=] …
uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to enable…
SD/MMC found on device 0
13820416 bytes read in 875 ms (15.1 MiB/s)
loading /boot/am335x-sancloud-bbe.dtb …
** File not found /boot/am335x-sancloud-bbe.dtb **

Starting kernel …

[gelbal]

Hello @sbender, first of all welcome to the balena community!

How do you trying booting? Are you using an SD card? If so, have you verified that SD card is flashed fine?

As far as I understand, Beaglebone Black has a rather different booting method. I saw other users having boot issues as well and they resolved it by making sure that their board boots from the SD card for the first time:

Booting Beaglebone Black failing

OK I need to learn to RTFM. When redownloading the image again I read that I have to hold the button to flash it to the eMMC - I had assumed it was booting from the SD card and when seeing the errors just assumed it was an image/write problem. Held the button on boot and, lo and behold, it has sprung into life.

Could you please check this and make sure you follow the recommended steps?

[sbender]

Yes, I’m using an SD card. I’ve verified that the image is fine and I am holding down the boot boot button.

[gelbal]

Which balenaOS version are you using for this? Is it development or production variant?

And did you use balenaEtcher to flash the SD card? (Just checking if you saw Etcher’s validation stage)

[sbender]

I was using the latest, 2.29.2+rev3, Ive tried both dev and prod. I’m using balenaEtcher and I do see the validation stage. I can re-insert the SD card in my mac and mount it and see all files.

I just tried with 2.15.1+rev1 and it works, so seems like something is off with the latest version.

[sbender]

Note that 2.29.0+rev1 works also

[spanceac]

Hi,

Your board is detected as “SanCloud BeagleBone Enhanced” (https://beagleboard.org/enhanced), which we don’t support.

The image you are using is for BeagleBone Black.

Starting from v2.29.0+rev2 we switched to using mainline u-boot and that’s why your board doesn’t work anymore.

Regards!

[sbender]

Ah, ok. I wasn’t sure since this it is based on the “Black” board.

thanks!