Facing issue in booting Balena OS

#1

I have downloaded the Balena OS for Beaglebone green wireless.

I have an sd card with a single partition ( Format Fat32 )

I am using Balena Etcher to Flash the operating system.

Now when I boot the Operating System I get the following error:

U-Boot SPL 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500)
Trying to boot from MMC2
Loading Environment from EXT4...
** Unable to use mmc 0:1 for loading the env **


U-Boot 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build: jenkins-github_Bootloader-Builder-65

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: 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
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
Model: SeeedStudio BeagleBone Green Wireless:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net:   eth0: MII MODE
Could not get PHY for cpsw: addr 0
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] ...
board_rev=[GW1A] ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
btrfs_read_superblock: invalid checksum at superblock mirror 0
btrfs_read_superblock: No valid BTRFS superblock found!
** Unrecognized filesystem type **
btrfs_read_superblock: invalid checksum at superblock mirror 0
btrfs_read_superblock: No valid BTRFS superblock found!
** Unrecognized filesystem type **
btrfs_read_superblock: invalid checksum at superblock mirror 0
btrfs_read_superblock: No valid BTRFS superblock found!
** Unrecognized filesystem type **
** Invalid partition 7 **
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
** Invalid partition 4 **
** Invalid partition 5 **
** Invalid partition 6 **
** Invalid partition 7 **
starting USB...
USB0:   scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
musb-hdrc: peripheral reset irq lost!
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-98-5d-ad-35-f9-6c
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A80102
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A8010
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A801
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A80
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.=>

I am following this documentation

#3

Hi @Sharvin26 could you try using the Beaglebone Black .dev image instead of the Green. This Beaglebone Black image will work on all variants of the beaglebone (except pocketbeagle) and is a newer version of the OS.

#5

Which one should I use production or development?

#6

While you are testing and developing I would recommend the development image. Also just to make sure, i are you just looking to use balenaOS with out the cloud service? or do you intend to use balenaCloud as well?

#8

Right now I am just exploring the platform.

#9

Cool, welcome! If you are interested in the remote update and deployment side of things, you can look at this getting started as well https://www.balena.io/docs/learn/getting-started/beaglebone-black/nodejs/

#10

Thanks

#11

No problem! let us know if you have any more questions

#14

I downloaded the Beaglebone black image and flashed it directly on the sd card using Balena etcher. I am still facing the issue

My Boot logs

U-Boot SPL 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500)
    Trying to boot from MMC2
    Loading Environment from EXT4...
** Unable to use mmc 0:1 for loading the env **


U-Boot 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build: jenkins-github_Bootloader-Builder-65

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: 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
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
Model: SeeedStudio BeagleBone Green Wireless:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net:   eth0: MII MODE
Could not get PHY for cpsw: addr 0
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] ...
board_rev=[GW1A] ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
btrfs_read_superblock: invalid checksum at superblock mirror 0
btrfs_read_superblock: No valid BTRFS superblock found!
** Unrecognized filesystem type **
btrfs_read_superblock: invalid checksum at superblock mirror 0
btrfs_read_superblock: No valid BTRFS superblock found!
** Unrecognized filesystem type **
btrfs_read_superblock: invalid checksum at superblock mirror 0
btrfs_read_superblock: No valid BTRFS superblock found!
** Unrecognized filesystem type **
** Invalid partition 7 **
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
Checking for: /uEnv.txt ...
Checking for: /boot.scr ...
Checking for: /boot/boot.scr ...
Checking for: /boot/uEnv.txt ...
** Invalid partition 4 **
** Invalid partition 5 **
** Invalid partition 6 **
** Invalid partition 7 **
starting USB...
USB0:   scanning bus 0 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
musb-hdrc: peripheral reset irq lost!
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-98-5d-ad-35-f9-6c
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A80102
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A8010
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A801
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A80
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A8
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0A
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C0
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/C
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/default-arm-am33xx
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/default-arm
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Retrieving file: pxelinux.cfg/default
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.Config file not found
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
MAC 98:5d:ad:35:f9:6c
HOST MAC de:ad:be:af:00:00
RNDIS ready
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
The remote end did not respond in time.=>
#15

Did you hold down the small black button marked s2 (located near the SD card slot) and power up the device by inserting the power or USB cable? You need to hold the button down to ensure the BB boots from SD card rather than internal eMMC.

#17

It is booting when holding the s2 switch.

Is there any way I can tell the Beaglebone to boot from Sd card ( like adding configuration in uEnv.txt )

#18

No unfortunately the way the OS is currently designed is that it will initially boot from SD card (when s2 button) is held down, it will then flash the balenaOS onto the devices internal eMMC and shut itself down, all the leds will go off. Then next time you power it on, it will be running balenaOS from eMMC.

#20

Okay, and what’s the default login credentials?
And everytime I add a sd card with balena os will it reflash the eMMC?

#21

on a development OS the default login creds are root and no password. It is designed to be used in a lab and obviously not for production use. On the production versions you can add a ssh key to the SD card before provisioning or you have access via the web dashboard on balenaCloud.

#23

When I ping the device I get following logs

➜ ping balena.local
  ping: cannot resolve balena.local: Unknown host

These are my serial logs:

root@balena:~# hostname
balena

Also, I cannot ssh into the OS. Logs:-

➜ sudo balena local ssh balena.local --host

#24

If your laptop is running linux can you do a avahi-browse -a to try discover the device? Or alternatively try sudo balena local scan it might be that it has a slightly different name for some reason.

#26

I am facing trouble in some configurations on balena os:

Question 1:
By default, the system is mounted as read-only. Is there any way I can mount the system as read-write both.

Question 2:
I could successfully load the overlays dtbo that are present in the Balena OS by enabling them in uEnv.txt
Now I want to load a overlays dtbo file that doesn’t exist in Balena OS by default.
I have the dtbo with me How can I add that dtbo into /boot/overlays directory. As the root file system is mounted as read-only. I tried adding the dtbo by the mounting image from SD card and adding the DTBO in flash-rootfs partition ( /dev/sdc2 ) in /boot/overlays/myoverlay.dtbo
But When the image was flashed on the eMMC that dtbo was not present in that directory.

Question 3:
According to the documentation, balena os has a network manager. I have use connman previously for managing my network connections.

Now I have a use case:
I want my Beaglebone to have its own hotspot. For example, When I was having connman configured on my beaglebone my beaglebone AP was available in the network. I couldn’t find a solution to this situation.

Question 4:

Right now according to my understanding this command sudo balena local ssh mydevice.local --host ssh the beaglebone over a wireless network. How can I ssh using a usb for development purpose?

#27

Hi,

Answers to your questions:

  1. mount -o remount,rw /

  2. Now that you can mount the fs as RW you can copy your custom dtbo after flashing in the /boot folder. Please note that if you do a hostOS update, your custom dtbo will get vanished after update.

If you need the custom dtbo in the OS you can either build your own OS from sources and customize it, or sign-up for a custom device type.

  1. https://www.balena.io/docs/reference/OS/network/2.x/#creating-a-hotspot

  2. Not sure what you mean by ssh using a USB. Connect an USB to ethernet adapter to your board? Make the board act as a USB network interface?

Regards!

#30

Question 1:

first I remounted the partition as writeable using mount -o remount,rw /

After that, I added the dtbo in /boot/overlays

ACME-revB.dtbo			   BB-UART5-00A0.dtbo
AM335X-20-00A0.dtbo		   BB-VIEW-LCD4-01-00A0.dtbo
AM335X-PRU-RPROC-4-4-TI-00A0.dtbo  BB-VIEW-LCD7-01-00A0.dtbo
AM335X-PRU-RPROC-4-9-TI-00A0.dtbo  BB-W1-P9.12-00A0.dtbo
AM335X-PRU-UIO-00A0.dtbo	   BEAGLEBOY-0013.dtbo
BB-ADC-00A0.dtbo		   DLPDLCR2000-00A0.dtbo
BB-BBBMINI-00A0.dtbo		   DVK530-LCD4-01-00A0.dtbo
BB-BBBW-WL1835-00A0.dtbo	   GHI-DB-NH5C-00A0.dtbo
BB-BBGW-WL1835-00A0.dtbo	   GHI-LCD-00A0.dtbo
BB-BONE-4D4C-01-00A1.dtbo	   GHI-TH-NH43C-00A0.dtbo
BB-BONE-4D4N-01-00A1.dtbo	   GHI-TH-NH43R-00A0.dtbo
BB-BONE-4D4R-01-00A1.dtbo	   GHI-TH-NH7C-00A0.dtbo
BB-BONE-4D5C-01-00A1.dtbo	   M-BB-BBG-00A0.dtbo
BB-BONE-4D5N-01-00A1.dtbo	   M-BB-OSD3358-SM-RED-00A0.dtbo
BB-BONE-4D5R-01-00A1.dtbo	   NL-AB-BBBC-00D0.dtbo
BB-BONE-4D7C-01-00A1.dtbo	   NL-AB-BBCL-00B0.dtbo
BB-BONE-4D7N-01-00A1.dtbo	   OSD3358-00A0.dtbo
BB-BONE-4D7R-01-00A1.dtbo	   PB-I2C1-MPU-9DOF-CLICK.dtbo
BB-BONE-AUDI-02-00A0.dtbo	   PB-I2C1-RTC-6-CLICK.dtbo
BB-BONE-BACONE-00A0.dtbo	   PB-I2C1-RTC-CLICK.dtbo
BB-BONE-CRYPTO-00A0.dtbo	   PB-I2C1-WEATHER-CLICK.dtbo
BB-BONE-DVID-01-00A3.dtbo	   PB-I2C2-MPU-9DOF-CLICK.dtbo
BB-BONE-LCD3-01-00A2.dtbo	   PB-I2C2-RTC-6-CLICK.dtbo
BB-BONE-LCD4-01-00A1.dtbo	   PB-I2C2-RTC-CLICK.dtbo
BB-BONE-LCD5-01-00A1.dtbo	   PB-I2C2-WEATHER-CLICK.dtbo
BB-BONE-LCD7-01-00A1.dtbo	   PB-SPI0-ETH-CLICK.dtbo
BB-BONE-LCD7-01-00A2.dtbo	   PB-SPI0-ETH-WIZ-CLICK.dtbo
BB-BONE-LCD7-01-00A3.dtbo	   PB-SPI0-RTC-5-CLICK.dtbo
BB-BONE-NH7C-01-A0.dtbo		   PB-SPI0-THUNDER-CLICK.dtbo
BB-BONE-REACH-00A0.dtbo		   PB-SPI1-ETH-CLICK.dtbo
BB-BONE-REACH-00B0.dtbo		   PB-SPI1-ETH-WIZ-CLICK.dtbo
BB-BONE-REPLICAP-00A4.dtbo	   PB-SPI1-RTC-5-CLICK.dtbo
BB-BONE-REPLICAP-00B1.dtbo	   PB-SPI1-THUNDER-CLICK.dtbo
BB-BONE-REPLICAP-00B2.dtbo	   RoboticsCape-00A0.dtbo
BB-BONE-REPLICAP-00B3.dtbo	   SDS-CAPE-00A0.dtbo
BB-BONE-REPLICAP-0A4A.dtbo	   am33xx_pwm-00A0.dtbo
BB-BONE-REPLICAP-0B3A.dtbo	   bb-justboom-amp-00A0.dtbo
BB-BONE-SERL-03-00A1.dtbo	   bb-justboom-dac-00A0.dtbo
BB-BONE-WL1837-00A0.dtbo	   bb-justboom-digi-00A0.dtbo
BB-BONE-WTHR-01-00B0.dtbo	   beaglelogic-00A0.dtbo
BB-BONE-eMMC1-01-00A0.dtbo	   bone_eqep0-00A0.dtbo
BB-CAN0-00A0.dtbo		   bone_eqep1-00A0.dtbo
BB-CAN1-00A0.dtbo		   bone_eqep2-00A0.dtbo
BB-CAPE-DISP-CT4-00A0.dtbo	   bone_eqep2b-00A0.dtbo
BB-GATEWAY-WL1837-00A0.dtbo	   cape-CBB-Serial-r01.dtbo
BB-GREEN-HDMI-00A0.dtbo		   cape-bone-ibb-00A0.dtbo
BB-HDMI-TDA998x-00A0.dtbo	   cape-univ-audio-00A0.dtbo
BB-I2C1-00A0.dtbo		   cape-univ-emmc-00A0.dtbo
BB-I2C1-MCP7940X-00A0.dtbo	   cape-univ-hdmi-00A0.dtbo
BB-I2C1-PCA9685-00A0.dtbo	   cape-universal-00A0.dtbo
BB-I2C2-00A0.dtbo		   cape-universala-00A0.dtbo
BB-I2C2-PCF8523-00A0.dtbo	   cape-universalh-00A0.dtbo
BB-I2C2N-00A0.dtbo		   cape-universaln-00A0.dtbo
BB-NHDMI-TDA998x-00A0.dtbo	   dev-USB-PWR-CTL-00A1.dtbo
BB-PWM0-00A0.dtbo		   uio_pruss_enable-00A0.dtbo
BB-PWM1-00A0.dtbo		   univ-all-00A0.dtbo
BB-PWM2-00A0.dtbo		   univ-bbb-EVA-00A0.dtbo
BB-RELAY-4PORT-00A0.dtbo	   univ-bbb-EVx-00A0.dtbo
BB-RTC-01-00A0.dtbo		   univ-bbb-Exx-00A0.dtbo
BB-SPI0-ADS8688-0A00.dtbo	   univ-bbb-xVA-00A0.dtbo
BB-SPI0-MCP3008-00A0.dtbo	   univ-bbb-xVx-00A0.dtbo
BB-SPIDEV0-00A0.dtbo		   univ-bbb-xxx-00A0.dtbo
BB-SPIDEV1-00A0.dtbo		   univ-bbgw-00A0.dtbo
BB-SPIDEV1A1-00A0.dtbo		   univ-bbgw-EW-00A0.dtbo
BB-UART1-00A0.dtbo		   univ-bbgw-Ex-00A0.dtbo
BB-UART2-00A0.dtbo		   univ-bbgw-xW-00A0.dtbo
BB-UART2-RTSCTS-00A0.dtbo	   univ-bbgw-xx-00A0.dtbo
BB-UART3-00A0.dtbo		   univ-emmc-00A0.dtbo
BB-UART4-00A0.dtbo		   univ-hdmi-00A0.dtbo
BB-UART4-RS485-00A0.dtbo	   univ-nhdmi-00A0.dtbo
custom_overlay.dtbo

Then I added the overlay into my uEnv.txt under /mnt/boot/

uboot_overlay_addr1=/boot/overlays/custom_overlay.dtbo

And rebooted the system then I get the following logs:

uboot_overlays: unable to find [mmc 1:2 /boot/overlays/custom_overlay.dtbo]...

Question 2:

Is there any guide for Beaglebone to build balena os from source with the custom dtbo? And can you share more about

sign-up for a custom device type.

Question 3:

https://www.balena.io/docs/reference/OS/network/2.x/#creating-a-hotspot

When I turn on the hotspot it disconnects the wifi connection. I don’t want this behavior. I want Beaglebone to have its own access point and it can connect other wifi networks simultaneously.

Question 4:

Not sure what you mean by ssh using a USB. Connect a USB to ethernet adapter to your board? Make the board act as a USB network interface?

When I was using Debian on beaglebone I could ssh using command ssh debian@192.168.7.2. According to my understanding, IP was assigned to the USB interface. Can I do the same for the Balena OS?

Question 5:

I didn’t see anything related to logrotate and cron in my Host OS. Do I need to add this functionality in the container for the application that needs logrotate and cron jobs?

#33

Hi,
WRT Question 2,
you can contact our sales team for more information about custom device support from https://www.balena.io/contact-sales .
Let me check with the team about the rest of your questions.