# Uboot error - Humming board

**URL:** <https://forums.balena.io/t/uboot-error-humming-board/28463>\
**Category:** balenaOS\
**Created:** [August 28, 2019, 12:48pm UTC](https://forums.balena.io/t/uboot-error-humming-board/28463 "2019-08-28T12:48:17Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![benat](https://avatars.discourse-cdn.com/v4/letter/b/ac91a4/32.png) [@benat](https://forums.balena.io/u/benat)\
**Post date:** [August 28, 2019, 12:48pm UTC](https://forums.balena.io/t/uboot-error-humming-board/28463/1 "2019-08-28T12:48:17Z")

</div>

Hey,

I try to build latest BalenaOS image for HummingBoard2. From this (balena-fsl-arm)[[https://github.com/balena-os/balena-fsl-arm/](https://github.com/balena-os/balena-fsl-arm/)] repo I build image with Yocto Project. I flash resin-image-flasher-solidrun-imx6.img with BalenaEtcher on SD card. When I boot on SD card, I have followed Uboot error:

```
U-Boot SPL 2018.01 (Aug 13 2019 - 08:36:47)
Trying to boot from MMC1

U-Boot 2018.01 (Aug 13 2019 - 08:36:47 +0000)

CPU: Freescale i.MX6DL rev1.3 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 53C
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
*** Error - default environment is too large

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
env_buf [32 bytes] too small for value of "preboot"
syntax error
env_buf [32 bytes] too small for value of "bootcmd"
Hit any key to stop autoboot: 0
### ERROR ### Please RESET the board ###

```

Are there an particular setting to do to boot corectly ?

Thanks,  
Ben

---

<div class="post-metadata">

**Author:** ![floion](https://avatars.discourse-cdn.com/v4/letter/f/45deac/32.png) [@floion](https://forums.balena.io/u/floion)\
**Post date:** [August 28, 2019, 1:40pm UTC](https://forums.balena.io/t/uboot-error-humming-board/28463/4 "2019-08-28T13:40:25Z")

</div>

Hi. You would need to patch u-boot and allow for a bigger env for your particular board. An example on how we did this for other boards can be found here: [https://github.com/balena-os/balena-jetson/blob/2486c8d3507942b25417fc2b4166372b8098e79f/layers/meta-balena-jetson/recipes-bsp/u-boot/u-boot-tegra/0001-Increase-default-u-boot-environment-size.patch](https://github.com/balena-os/balena-jetson/blob/2486c8d3507942b25417fc2b4166372b8098e79f/layers/meta-balena-jetson/recipes-bsp/u-boot/u-boot-tegra/0001-Increase-default-u-boot-environment-size.patch)

---

<div class="post-metadata">

**Author:** ![benat](https://avatars.discourse-cdn.com/v4/letter/b/ac91a4/32.png) [@benat](https://forums.balena.io/u/benat)\
**Post date:** [August 28, 2019, 2:46pm UTC](https://forums.balena.io/t/uboot-error-humming-board/28463/6 "2019-08-28T14:46:58Z")

</div>

Image must be re-built ? Or can I modify my image with new uboot files ?

---

<div class="post-metadata">

**Author:** ![wrboyce](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/wrboyce/32/374_2.png) [@wrboyce](https://forums.balena.io/u/wrboyce)\
**Post date:** [August 28, 2019, 2:49pm UTC](https://forums.balena.io/t/uboot-error-humming-board/28463/7 "2019-08-28T14:49:46Z")

</div>

I believe you will need to rebuild the image with the patch applied.

---

<div class="post-metadata">

**Author:** ![benat](https://avatars.discourse-cdn.com/v4/letter/b/ac91a4/32.png) [@benat](https://forums.balena.io/u/benat)\
**Post date:** [August 29, 2019, 7:58am UTC](https://forums.balena.io/t/uboot-error-humming-board/28463/9 "2019-08-29T07:58:19Z")

</div>

Thanks for you help. I patched u-boot and I rebuilded image and I am able to boot and run BalenaOS. I have a few questions.

With Yocto project, I build BalenaOS v2.38 production image. Is-it possible to build a development image ? How do this ?

In my Dashboard, I see HummingBoard is discontinued and on [FAQ](https://www.balena.io/docs/faq/troubleshooting/faq/#what-does-it-mean-when-a-device-type-is-discontinued) is noted :

> In addition, it will no longer be possible to create applications for these device types, although existing applications and their devices will still function.

If I build latest BalenaOS for the board, I will able to use BalenaCLoud services ?

Thks,  
Ben

---

<div class="post-metadata">

**Author:** ![dfunckt](https://sea2.discourse-cdn.com/balena/user_avatar/forums.balena.io/dfunckt/32/56_2.png) [@dfunckt](https://forums.balena.io/u/dfunckt)\
**Post date:** [August 29, 2019, 1:06pm UTC](https://forums.balena.io/t/uboot-error-humming-board/28463/10 "2019-08-29T13:06:43Z")

</div>

Hello, see “Build Flags” about building a development image: [https://github.com/balena-os/meta-balena#build-flags](https://github.com/balena-os/meta-balena#build-flags)

It’s okay to deploy devices with your custom build using a supported device type and will most likely work just fine, but you won’t be able to perform host OS updates.