[2020-04-06] How to add HDMI back into BBB image after init-eMMC-flasher-v3.sh

General Discussion
,
1

I have a BeagleBone Black that I have just flashed with Buster IoT (without graphical desktop): AM3358 Debian 10.3 2020-04-06 4GB SD IoT from BeagleBoard.org - latest-images. I did the flashing via /opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh.

After flashing, the HDMI no longer works… the external monitor is blank.

Per BB Black not displaying on reboot - #9 by daithi76, I have tried:

sudo /opt/scripts/tools/update_kernel.sh
sudo /opt/scripts/tools/developers/update_bootloader.sh

And it didn’t work in making the HDMI work and the screen show a terminal prompt.

Here is some information on my BeagleBone Black (I made a few tweaks to add U-Boot Overlays for I2C and UART serial):

> uname -r
4.19.94-ti-r73
> cat /etc/debian_version
10.13
sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46]
eeprom:[A335BNLT00C02218SBB18564]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-00002-g07d5700e21]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0.bb.org-overlays]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0.bb.org-overlays]
UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0.bb.org-overlays]
UBOOT: Loaded Overlay:[BB-I2C1-FAST-00A0]
UBOOT: Loaded Overlay:[BB-UART1-00A0]
UBOOT: Loaded Overlay:[BB-UART2-00A0]
UBOOT: Loaded Overlay:[BB-UART4-00A0]
UBOOT: Loaded Overlay:[BB-UART5-00A0]
kernel:[4.19.94-ti-r73]
nodejs:[v10.24.0]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C1-FAST-00A0.dtbo]
uboot_overlay_options:[uboot_overlay_addr5=/lib/firmware/BB-UART1-00A0.dtbo]
uboot_overlay_options:[uboot_overlay_addr6=/lib/firmware/BB-UART2-00A0.dtbo]
uboot_overlay_options:[uboot_overlay_addr7=/lib/firmware/BB-UART4-00A0.dtbo]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
uboot_overlay_options:[dtb_overlay=/lib/firmware/BB-UART5-00A0.dtbo]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.14.20210821.0-0~buster+20210821]
pkg:[bb-wl18xx-firmware]:[1.20211222.2-0~buster+20211222]
pkg:[kmod]:[26-1]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]
pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal bluetooth netdev i2c gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai cloud9ide]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[   44.507419] remoteproc remoteproc0: wkup_m3 is available
[   44.599025] remoteproc remoteproc0: powering up wkup_m3
[   44.599059] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
[   44.599355] remoteproc remoteproc0: remote processor wkup_m3 is now up
[   47.249119] remoteproc remoteproc1: 4a334000.pru is available
[   47.277863] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pru
[   47.249119] remoteproc remoteproc1: 4a334000.pru is available
[   47.249276] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed successfully
[   47.277863] remoteproc remoteproc2: 4a338000.pru is available
[   47.278057] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed successfully
dmesg | grep pinctrl-single
[    0.957750] pinctrl-single 44e10800.pinmux: 142 pins, size 568
[    1.465448] pinctrl-single 44e10800.pinmux: pin PIN48 already requested by 481aa000.serial; cannot claim for 0-0070
[    1.476070] pinctrl-single 44e10800.pinmux: pin-48 (0-0070) status -22
[    1.482665] pinctrl-single 44e10800.pinmux: could not request pin 48 (PIN48) from group nxp_hdmi_bonelt_pins  on device pinctrl-single
dmesg | grep gpio-of-helper
[    0.971105] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 002: ID 04f2:0833 Chicony Electronics Co., Ltd KU-0833 Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

How can I get my external monitor to start working again? I want it to show a terminal for logging in.

2

Just use one of the the latest snapshots… (from 2 days ago)…

https://forum.beagleboard.org/tag/latest-images

Regards,

1 Like
3

Hello RobertCNelson,

Thank you for pointing me there! There seems to be a regression?

With am335x-debian-11.5-minimal-armhf-2022-11-01-2gb.img.xz (Debian 11 newest monthly) from Debian 11.x (Bullseye) - Monthly Snapshots, there is 1.7G space on /dev/mmcblk0p1:

> df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            214M     0  214M   0% /dev
tmpfs            49M  1.4M   47M   3% /run
/dev/mmcblk0p1  1.7G  836M  790M  52% /
tmpfs           242M     0  242M   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs            49M     0   49M   0% /run/user/1000

With bone-debian-10.13-iot-armhf-2022-11-01-4gb.img.xz (Debian 10 newest monthly) from Debian 10.x (Buster) - Monthly Snapshots, there is 3.4G space on /dev/mmcblk0p1:

> df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            214M     0  214M   0% /dev
tmpfs            49M  1.7M   47M   4% /run
/dev/mmcblk0p1  3.4G  1.9G  1.4G  58% /
tmpfs           242M     0  242M   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           242M     0  242M   0% /sys/fs/cgroup
tmpfs            49M     0   49M   0% /run/user/1000

With AM3358 Debian 10.3 2020-04-06 4GB SD IoT (old) from BeagleBoard.org - latest-images, there is 3.4G space on /dev/mmcblk0p1:

> df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            215M     0  215M   0% /dev
tmpfs            49M  1.6M   47M   4% /run
/dev/mmcblk0p1  3.4G  1.9G  1.4G  57% /
tmpfs           242M     0  242M   0% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           242M     0  242M   0% /sys/fs/cgroup
tmpfs            49M     0   49M   0% /run/user/1000

The thing is, this is the same BeagleBone Black. Why does the 11.5 image see half the space available?

4

Reboot… The auto partition resize takes a reboot to finish…

There’s a few commands to fix it, easier to just say use the new image… ( old uboot, location of overlays,)

Regards

1 Like
5

You’re right with a reboot it can now see the full storage, yay!

For Debian 11.5, where has /opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh gone to? I see /opt/scripts is no longer a directory, and sudo find . -name init-eMMC-flasher-v3.sh -type f returns nothing. How does one do microSD → eMMC flashing with Debian 11?

6

Documented on the page you downloaded…

eMMC Flasher

Copy board specific configuration files, example:

sudo enable-beagle-flasher
sudo reboot
1 Like
7

Alright the results are in! With both the Debian 10.13 and 11.5 versions (both are linked above), the display works with both! Victory!!

Also, @RobertCNelson this sudo enable-beagle-flasher is a big improvement, excellent work!

  • With Debian 10 I have an Ansible script to invoke sudo /opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh
  • With Debian 11 I have no Ansible script… I just insert the flash drive and it runs!

Note that after imaging with Debian 10 it takes 3.2 GB of storage, but with Debian 11 it takes 2.4 GB of storage, so there seems to be substantially more compression.

Thank you Robert for your answers, case closed!