dalekuhn

Hi Charles, I must have used the wrong image because I noticed later that fresh builds of focal were still having the same issue. However, the issue seemed to be fixed in Hirsute. Thanks, Dale

I just made a fresh Focal desktop build and it is working again. The GUI comes up again after a reboot now. Sorry to waste your time. Thanks, Dale

Hi, I just wanted to confirm that I see the same issue on recent builds of both Focal and Buster desktops for the Cubox-i (specifically, I'm using a Hummingboard Edge). On first boot, the HDMI display comes up and prompts me to set the root password and create a new user. After doing this, the XFCE GUI comes up on the HDMI display. However, after rebooting, I see some messages from U-Boot, but then the display goes blank and stays that way. I'm not a Linux expert by any means, but I would think if this was caused by a missing driver the desktop GUI would not load at all. However, it does come up after the first boot (and only on the first boot). Does anyone have any ideas of what I can do to help troubleshoot what's causing the HDMI display to remain blank after a reboot? Thanks in advance for your help, I really appreciate it. Thanks, Dale

Hi KennyM64, I just had to figure this out for myself on the Hummingboard Edge. The Solidrun article on boot jumpers is a little misleading. Removing the jumpers (at least on an unfused system) boots into USB recovery mode. That's not the same as actually booting from USB. Instead, the board will sit there and wait for SDP (serial download protocol) commands to come in over the USB OTG port. 1. Make a custom cable following instructions here. I used a 1 ohm resistor. 2. Connect the cable to the top USB port next to the ethernet port. (This is the only port with OTG functionality) 3. Follow the instructions here to download and build the imx_usb_loader. 4. Generate SPL and u-boot images or use the attached files. Drop them into the imx_usb_loader folder or adjust the path in the commands below. 4. Run ./imx_usb SPL (if you haven't adjusted your udev rules, you have to use sudo for this and the next command) 5. Once SPL is loaded, run ./imx_usb u-boot.img You can build Armbian with the CREATE_PATCHES=yes option to adjust U-Boot to include ums support. The changes required are outlined in the link from step 3. Alternately, I've attached my SPL and u-boot.img. My u-boot has ums enabled and activates mmc 1 by default so you shouldn't need a serial cable, although it is nice to see that things are working without the need for a monitor. Once mmc 1 is activated by ums, you should see the board's eMMC flash show up as a USB drive. From here you can flash an image using Etcher, dd, or whatever method you prefer. If the board is actually fused, this may not work. However I saw a Solidrun document somewhere that shows how to hold the eMMC in reset at powerup. In this case, if the board can't boot from eMMC because it's held in reset, that should cause the board to fall back to recovery mode. Either way, once you're in recovery mode, the above steps should work. I hope this helps. Good luck, Dale SPL u-boot.img

Thank you, Igor. I appreciate your feedback. I will look into what options I have at this point. By the way, the Armbian images have all worked very well. Thank you for your hard work. Dale

Hello. I have been running Armbian_5.41_Cubox-i_Ubuntu_xenial_next_4.15.7_desktop.img with no issues on my Hummingboard Edge which consists of rev 1.4 Hummingboard2 carrier and rev 1.5 SOM. I decided to try the legacy image (Armbian_5.41_Cubox-i_Ubuntu_xenial_default_3.14.79_desktop.img) to gain support for the hardware video decoder. However, I have been unable to get the legacy version to boot properly. Initially, the board is detected as having a rev 1.5 SOM and there is a message about not being able to find the right dtb file (imx6q-hummingboard2-som-v15.dtb). Looking under /boot/dtb there are no dtb files for the rev 1.5 SOM in the legacy image. So I copied the default imx6q-hummingboard2-som-v15.dtb from my 'next' image into the dtb folder of my legacy image. Now I no longer see the message about the missing dtb file, but the boot process stops at "Starting kernel ..." Does anyone have any ideas what may be the problem? Is the legacy image compatible with the rev 1.5 SOM? Thanks in advance to anyone that can help. I sure appreciate it. Thanks, Dale