Migrating from RPI3 to Vero V

[casperklein]

Hi!

I received my new Vero V yesterday and I am quite happy with it. Previously I was using a RPI3 with some minor customizations.

Now that I’ve setup the Vero from scratch, I’ve some issues (compared to my old RPI3 setup), I wasn’t able to solve yet:

While booting, I had disabled the OSMC splash screen by removing the “quiet” keyword from /boot/cmdline.txt. However, /bootdoesn’t exist on the Vero. I’ve found this post, but the solution was not publicly shared.

---

When I start the Vero before my AVR / TV, CEC doesn’t work. On the RPI the solution was:

1. Run tvservice -d edid.dat (after booting with TV/receiver powered on first)
2. Copy the edid.dat to the /boot partition
3. Add to config.txt: hdmi_edid_file=1 and hdmi_force_hotplug=1

How can I accomplish that on the Vero?

---

The Vero does have a blue LED which is only on while booting and when in standby. Can this behaviour be change?

I’d like to know, when my Vero has shutdown, to turn the power plug off.

Currently I cannot distinguish between a powered on and a shutdown Vero. To avoid any (filesystem) damage, I want to be sure, that the Vero has stopped gracefully, before turning the power plug off.

---

Please let me know, if you prefer, that I open a separate topic for each question.

Thank you!

[darwindesign]

@casperklein

While booting, I had disabled the OSMC splash screen by removing the “quiet” keyword from /boot/cmdline.txt. However, /bootdoesn’t exist on the Vero. I’ve found this post, but the solution was not publicly shared.

Disable boot messages

Try adding systemd.show_status=0 to the kernel command line in /boot/cmdline.txt (Pi) or /boot/uEnv.txt (Vero)

Regarding the LED you should check out this thread…

Standby blue led

Hi, there is a way to switch off (or decrease the intensity) the blue led during standby?

As for the CEC issue I really don’t know what EDID (ie which display modes are supported) has to do with it. Often CEC can be fixed with powering off the display and any connected AVR/soundbar from the wall for a few seconds. This resets the CEC bus which can sometimes get a bit confused with device assignments.

Additionally, the Vero, like most devices of its type, are designed around being powered on all the time. The power use at idle should be quite low.

[casperklein]

Thank you for your fast reply! 2 of my 3 issues are solved now

1. I’ve created the file /boot/uEnv.txt (it did not exist) and put systemd.show_status=0 in it. However, after rebooting the splash screen is still there.
2. I also stumbled about this thread while looking for solutions. But I didn’t read it to the end, because I thought it was about adjusting the brightness level For reference, this did the trick for me: I’ve put echo 1 > /sys/class/leds/standby/brightness in /etc/rc.local.
3. I’m not sure what the problem was yesterday when I was testing, but today I couldn’t reproduce the CEC issue anymore. Fingers crossed it stays that way.

[casperklein]

@darwindesign

As for the CEC issue I really don’t know what EDID (ie which display modes are supported) has to do with it.

I followed this to fix my CEC issue I was having with my RPI3.

[sam_nazarko]

I will get back to you about these issues shortly.

Sam

[sam_nazarko]

Hi,

Sorry for the delays in getting back to you

@casperklein

How can I accomplish that on the Vero?

Turn on all your equipment and when things run, do:

echo save bin edid | sudo tee /sys/class/amhdmitx/amhdmitx0/edid
sudo mv edid /lib/firmware.

This will now persist.

@casperklein

The Vero does have a blue LED which is only on while booting and when in standby. Can this behaviour be change?

You can control the state of the LED with: echo 1 | sudo tee /sys/class/leds/standby/brightness

@casperklein

I’ve created the file /boot/uEnv.txt (it did not exist) and put systemd.show_status=0 in it. However, after rebooting the splash screen is still there.

This isn’t parsed. You could change the boot arguments with fw_setenv, but you could brick your system and updates can change this environment.

I have been considering for a while to add an equivalent of RPi’s ‘cmdline.txt’ and read it from /boot.
This would allow you to add additional boot arguments, but not necessarily remove existing ones such as ‘quiet’.

If this is something you think would be beneficial and you’re willing to test, I can look at whipping something up. I suspect it’s a good thing to have and may be needed sooner than later, so we might as well do it.

[casperklein]

Hi Sam,

thank you for your detailed answer!

echo save bin edid | sudo tee /sys/class/amhdmitx/amhdmitx0/edid
sudo mv edid /lib/firmware.

This will now persist.

That worked.

You could change the boot arguments with fw_setenv, but you could brick your system and updates can change this environment.

1. Do you mean brick in a way, I can’t recover from? For example with the instructions here
2. I tried fw_printenv | grep quietbut there isn’t a match.

If a solution with `fw_setenv …` would work, I don’t mind if updates would overwrite it. Then I would adjust it again.

This would allow you to add additional boot arguments, but not necessarily remove existing ones such as ‘quiet’.

Ok. But that wouldn’t help me disabling the OSMC splash screen while booting, right?

[sam_nazarko]

@casperklein

If a solution with fw_setenv … would work, I don’t mind if updates would overwrite it. Then I would adjust it again.

Yes but that’s a bit of a pain.

I can think of a post update hook that would help.

Let me think and get back to you about this.

A hard brick of Vero V is impossible as long as you have a USB cable. But I would like to avoid the potential for such a scenario.

[Maaaash32]

Hello casperklein,

I’m just a casual user of Vero 4K+ and Vero V and I would add to that reflection that to control my vero with CEC I use to go to settings → system → input → peripherals → CEC Adapter in KODI interface to configure the actions to do when vero V turn on (turn on TV) and when I turn off my TV (turn off vero).

I hope it will be usefull for you (and others).