BalenaOS boot error

Hey ,

I have two µsom IMX6-Solo and IMX6 Dual Lite like base for my custom board. I try to run ResinOS/BalenaOS with the Development image 2.15 for the humming board.

With IMX6 Solo, ResinOS run correctly. Board is present on my network. However, I don’t detect it with balena-cli command “balena scan”. The balena-cli version is 11.7.3. How can i push a project on my board ?

With IMX6 Dual Lite, there are boot errors. Like indicated, bootloader don’t find “imx6dl-cubox-i-emmc-som-v15.dtb” file. This file is indeed absent on boot partition. Is it normal ?
More over, logs indicate the board is recognized like Cubox-i, whereas my custom board is more similar to HummingBoard. And on boot partition, this file is present for hummingboard. Are there a possibility to force device type ?

Thanks
Ben

Log for IMX6 Dual Lite :

U-Boot SPL 2018.01 (Sep 03 2018 - 10:58:19)
Trying to boot from MMC1


U-Boot 2018.01 (Sep 03 2018 - 10:58:19 +0000)

CPU:   Freescale i.MX6DL rev1.3 996 MHz (running at 792 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 37C
Reset cause: POR
Board: **MX6 Cubox-i (som rev 1.5)**
       Watchdog enabled
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
MMC partition switch failed
*** Warning - MMC partition switch failed, using default environment

No panel detected: default to HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial
MMC partition switch failed
!MMC partition switch failed
Net:   FEC
Hit any key to stop autoboot:  0
Scanning MMC and USB devices 0 1 2
reading resin-image-flasher
24 bytes read in 10 ms (2 KiB/s)
Found resin flasher on mmc 0
Loading resinOS_uEnv.txt from mmc device 0 partition 1
reading resinOS_uEnv.txt
4 bytes read in 14 ms (0 Bytes/s)
Import resinOS_uEnv.txt in environment
reading zimage
9105216 bytes read in 453 ms (19.2 MiB/s)
** Unable to read file imx6dl-cubox-i-emmc-som-v15.dtb **
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree

Anyone can enlighten me for my issues ?

I see on the doc :

In order to use local mode on a device:

The device must be running balenaOS v2.29.0 or higher. 

BalenaOS version for Humming board (Imx-6 ) is 2.15. Do you intend to update you host OS for this board ?

What are my alternatives to deploy project without local mode ? I don’t find documentations for old version of BalenaOS.

Ben

Hi @benat ,

We don’t have current plans to update balenaOS for Hummingbird board.
You could consider providing community support for this board though, which we’ll be happy to accept.

As for your question regarding the local mode functionality, as documentation says, it’s not available on older balenaOS.
But the regular flow (of pushing a release with “balena push” or “git push”) should work for your device if you disable local mode on it.

I tried to push project via BalenaCloud with “git push” but it does not seem to be working.
I have the confirmation with “our friendly unicorn mascot” that the upload of image is Ok. And on the dashboard, I only see the status “online” for the board. Like you can see in the capture, other informations (OS version, Supervision OS ,Ip adress, …) are missing. I don’t see none indicators that inform the image are downloaded and work on the board.

@benat is the supervisor on the device running? The fact that none of the information has been reported back implies there are issues with the device that mean it may not be able to connect to balenaCloud or be aware that there is a release to download.

How can i confirm that the supervisor running ? By logging in via serial port, the OS seems boot correctly.

@benat
Yes, you could use the serial connection if you use the development OS build and login as root (without a password).

Then if you execute

balena-engine ps

you should see a resin_supervisor container running
checking its logs may also be useful

You can use balena-engine logs resin_supervisor to check the logs.

I followed your instructions and like you can see balena-engine command is don’t find.balena_engine_command

@benat sorry, on older OS version balena should be used instead of balena-engine

So, please try balena ps and balena logs resin_supervisor.
Thanks,

After investigating Host OS, I observed resin-init-flasher service was down. with the help of this post Failed to start Resin flasher service , I realized my µsom don’t have internal memory and the os can’t be flashed.

After changing µsom, I am able to flash ResinOS on Humming board and the image is correctly downloaded. When I try it on my custom board, I have this error :

** Unable to read file imx6dl-cubox-i-emmc-som-v15.dtb **

Like indicated in my initial post, my board is recognised like Cubox-i board. Do you know how bootloader get back board informations ? I think if I were able to force board type to Humming Board, I would boot correctly.

U-Boot 2018.01 (Sep 03 2018 - 10:58:19 +0000)

CPU:   Freescale i.MX6DL rev1.3 996 MHz (running at 792 MHz)
CPU:   Commercial temperature grade (0C to 95C) at 37C
Reset cause: POR
Board: **MX6 Cubox-i (som rev 1.5)**
       Watchdog enabled
DRAM:  1 GiB
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
MMC partition switch failed
*** Warning - MMC partition switch failed, using default environment

No panel detected: default to HDMI
Display: HDMI (1024x768)
In:    serial
Out:   serial
Err:   serial

I find a solution. By entering in Uboot I use command setenv to modify board_name
setenv board_name HUMMINGBOARD2
boot

Next steps is to find how to fix board_name variable in base image.

Are you trying to build your own OS image? These modifications are not really recommended. We are checking with the devices team about the device tree overlay.

Your comment is noted. Our team consider to build our OS image with time.

Just for information, to fix board_name variable I use resinos_uent.txt at the racine of boot partition.