Red light on Vero 4K+ if booted with HDMI connected

[sam_nazarko]

I’ve taken a belts and braces approach to solving this problem, and the solutions should be in the next update.

Firstly, I’ve ensured that re-installing OSMC in the future will configure the UBoot environment to match the defaults provided by the bootloader that is packaged:

[installer] [target] Vero 4K/4K+: ensure that we reset the UBoot environment on install to match the shipped bootloader. This breaks customer logo support for B2B but these users are on legacy versions for now.

[package] [vero3-bootloader-osmc] Remove persistence of UBoot environmeent across installs by adding support for osmc_defenv parameter to reset all UBoot environment variables. This allows the system environment to match the UBoot version that is installed. This can prevent issues introduced by customising UBoot environment variables as well.

So in your case onwards, if you were missing that hdmimode parameter, it would be reinstated automatically after reinstalling, which would solve your issue.

I’ve also got a patch to solve the original crash which occurred when that parameter wasn’t set. It’s been verified by a user but I’ll wait for a bit more testing before pushing it to the development repository.

Thanks for the report

Cheers

Sam