latest testing images incompatible with existing u-boot
Created by: mvduin
The latest images made subtle changes to /boot/uEnv.txt and how u-boot works that causes the combination of old u-boot + new system (i.e. the typical situation when people boot from SD card) to seem to boot normally except
- pru overlay doesn't load
- cape-universal doesn't work (it loads the non-univ base dts for some reason)
snippet of version.sh in this situation:
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-gc9b3922522]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.01-rc1-00002-g9b09b2]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot.dts]
UBOOT: Loaded Overlay:[AM335X-20-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]
UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0]
kernel:[4.19.94-ti-r50]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
After the last major breakage of a similar kind (caused by the introduction of u-boot overlays) this has been the single most frequent problem people run into and "are you booting from SD card?" is usually the first question I ask people who come into chat with problems, problems they've often been trying to solve for days. This problem was finally starting to subside as most people have beaglebones with a sufficiently recent u-boot, and now it looks like the pain will start all over again?
rcn, please! I beg you, please don't unnecessarily break backwards compatibility with widely deployed u-boot versions.