We have a BeagleBone Black Industrial board purchased from DigiKey.
I am trying to build and run a Yocto Linux image for this board. The Yocto image builds successfully and boots correctly, but the HDMI display is not working.
To determine whether the problem was specific to my Yocto build, I also tested the board using the stock image downloaded from BeagleBoard.org:
BeagleBone Black Debian 13.7 2026-09-20 Xfce (kernel v6.18.x)
However, HDMI does not work with this image either. The system boots successfully, but I do not get any output on the HDMI display.
My questions are:
Does the BeagleBone Black Industrial require any specific kernel configuration or patch to enable HDMI?
Are any device-tree/DTS changes required for HDMI support on the Industrial version?
Is there anything specific I should check to confirm whether the HDMI hardware is being detected and initialized correctly?
Are there any known differences between the standard BeagleBone Black and BeagleBone Black Industrial related to HDMI support?
Any suggestions on what to check next would be greatly appreciated.
On the non-industrial one, you usually have to intentionally disable HDMI. Make sure in /boot/uEnv.txt that the line like #disable_uboot_overlay_video=1 really is commented out (starts with a #).
@rsr_sam let’s check a couple things.. report sudo beagle-version to make sure the board is loading correctly. But most likely your on a RevD board with IT66122 which still has a lot of fun issues thinking DVI screens are HDMI… BBB RevD (and Industrial) IT66122 issues - #93 by RobertCNelson 7.3.x is better for some users, once that becomes an lts it’ll replace our 6.18.x default..
Thank you. Before I run the U-Boot install script, I just want to make sure I understand correctly.
The system I am currently testing is booted from the SD card:
rsrsam@BeagleBone:\~$ lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS
NAME SIZE TYPE FSTYPE MOUNTPOINTS
mmcblk1 14.6G disk
|-mmcblk1p1 36M part vfat
|-mmcblk1p2 512M part swap
`-mmcblk1p3 14.1G part ext4 zram0 240.5M disk swap [SWAP] mmcblk1boot0 4M disk mmcblk0 119.1G disk |-mmcblk0p1 36M part vfat /boot/firmware |-mmcblk0p2 512M part swap [SWAP] `-mmcblk0p3 118.5G part ext4 /
mmcblk1boot1 4M disk
rsrsam@BeagleBone:\~$
If I remove the SD card, the board boots normally from the factory eMMC image, and HDMI works correctly. i can see teminal outputs in HDMI display.
debian@BeagleBone:\~$ sudo beagle-version
eeprom:\[A335BNLTEID02630SBI00220\]
model:\[TI_AM335x_BeagleBone_Black_rev_D\]
dogtag:\[BeagleBoard.org Debian Bookworm Base Image 2025-05-27\]
bootloader:\[eMMC-(default)\]:\[/dev/mmcblk1\]:\[U-Boot SPL 2022.04-gc6f4cf7d (Apr 24 2025 - 03:22:59 +0000)\]:\[location: dd MBR\]
UBOOT: Booted Device-Tree:\[am335x-boneblack-revd.dts\]
kernel:\[6.12.28-bone25\]
/boot/uEnv.txt Settings:
pkg check: to individually upgrade run: \[sudo apt install --only-upgrade \]
WARNING:pkg:\[bb-cape-overlays\]:\[NOT_INSTALLED\]
pkg:\[bb-customizations\]:\[1.20240119.0-0\~bookworm+20240119\]
pkg:\[bb-usb-gadgets\]:\[1.20250523.1-0\~bookworm+20250527\]
pkg:\[bb-wl18xx-firmware\]:\[1.20230703.0-0\~bookworm+20240703\]
pkg:\[kmod\]:\[30+20221128-1\]
WARNING:pkg:\[librobotcontrol\]:\[NOT_INSTALLED\]
pkg:\[firmware-ti-connectivity\]:\[20230210-5\]
groups:\[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal input render netdev i2c bluetooth gpio admin tisdk weston-launch\]
cmdline:\[console=ttyS0,115200n8 root=/dev/mmcblk1p3 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet\]
dmesg | grep remote
\[ 3.175048\] remoteproc remoteproc0: wkup_m3 is available
\[ 12.130070\] systemd\[1\]: Reached target remote-fs.target - Remote File Systems.
\[ 35.318149\] remoteproc remoteproc0: powering up wkup_m3
\[ 35.336142\] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
\[ 35.336417\] remoteproc remoteproc0: remote processor wkup_m3 is now up
\[ 44.352086\] remoteproc remoteproc1: 4a334000.pru is available
\[ 44.371765\] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pru
\[ 44.352086\] remoteproc remoteproc1: 4a334000.pru is available
\[ 44.371765\] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pinctrl-single
\[ 3.194811\] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
dmesg | grep wlcore
lsusb
Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
lspci
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
END
debian@BeagleBone:\~$ uname -r
6.12.28-bone25
debian@BeagleBone:\~$ lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS
NAME SIZE TYPE FSTYPE MOUNTPOINTS
mmcblk1 14.6G disk
├─mmcblk1p1 36M part vfat /boot/firmware
├─mmcblk1p2 512M part swap \[SWAP\]
└─mmcblk1p3 14.1G part ext4 /
mmcblk1boot0 4M disk
mmcblk1boot1 4M disk
debian@BeagleBone:\~$
could you please help me understand why I need to update the U-Boot on /dev/mmcblk1 (eMMC) as well?
I am hesitant to overwrite the factory eMMC U-Boot because that image currently boots correctly and HDMI is working.
Is updating only the SD-card U-Boot (/dev/mmcblk0) sufficient for this test, or is it necessary for the eMMC and SD card to have the same U-Boot version?
Newer images vs the factory renable uboot_overlay_options:[enable_uboot_overlays=1] in /boot/uEnv.txt i had missed this in the original patch, and you have the industrial, which needs another:
Thanks for your help. After running the install.sh script and rebooting, the system now boots from the SD card with the GUI working correctly on the HDMI display.
beagle-version now shows the correct HDMI overlay:
I am also working on a custom Yocto build for this BeagleBone Black Industrial Rev D board. Do you have a recommended U-Boot branch/patch and device-tree/IT66122 patches that I could use to add the same HDMI support to my Yocto build?
Any pointers to the relevant commits or patches would be greatly appreciated.
I was using the Wrynose Yocto build. The Linux version is 6.18.39-yocto-standard and the U-Boot version is also old. I will rebuild pointing to this branch.
This error did not happen on Debian only on buildroot which is comparable to yocto. I can give you the patch to try (I have not gotten around to upstreaming it yet).
