HDMI CEC support

[Robbrad]

Hi Guys

My first post here so be kind. ☺

As you probably know the raspberry pi has hardware support to control devices via CEC commands. This is an incredibly useful method to control HDMI devices like TVs and HiFis etc anything that supports it, allowing the user to adjust the power state of the device and the source.

I'm running piCorePlayer which runs on the Tinycore port to the raspberry pi. It's fantastic because of its low resource footprint.

My question, what would it take to include Libcec in this port to allow the control. I have permission from the Pulse-Eight the LibCEC developers to include it. (https://github.com/Pulse-Eight/libcec)

Initial investigation shows HDMI is controlled through the video core.

Thanks
Rob

[bmarkus]

Thanks for advice, I added it to the todo list for piCore 7.0 However it is not a high priority task, so can't promise any date.

[Robbrad]

Thanks bmarkus !

I don't have much money, but im happy to donate what I can to include this, if that has any bearing. If not im also happy to wait as this is just a personal project not work related.

Im also happy to be involved in any testing required.

Thank you so much, again 

[bmarkus]

Hi Rob

it is not about donation but how does it fit to the development workflow. In general you can help with testing releases and reporting what is missing, what is buggy. Than I add them to the todo list.

Regards

Béla

[Robbrad]

Great thanks Béla - great work btw

I will help as much as I can

Thanks
Rob

[nkcfan]

Hi Rob

it is not about donation but how does it fit to the development workflow. In general you can help with testing releases and reporting what is missing, what is buggy. Than I add them to the todo list.

Regards

Béla

Is there any progress or is it still in the todo list?

[curaga]

Bela hasn't been active for a while, but extensions are user contributed, and compiling libcec is probably simple. Maybe you could build it?

[Paul_123]

I know folks that have done it, while libcec is easy to build, the raspi HDMI implementation is not complete, functionality was spotty.  So they gave up.  The pi4 was close, not sure about the pi5.

They were using RaspiOS, if it doesn't work there, then its going to be difficult here.  You might try a quick RaspiOS image and see what happens.

[Yleisajattelija]

I need a display for Rasberry 3. I have already several add-on cards on I/O-expansion bus, so I consider HDMi-connector and touch-screen.

Currentlly I need only simple industrial control panel with few strings, so I don't need graphics. Main goal is simplicity, easy graphics library and TinyCore support.

Now I'm ordering displays from China and try to guess best type for this Tinycore use. Does anyone have a recommendation?

Simple character type library interface is one option, and Qt and full graphics software stack is another option, too.

[Yleisajattelija]

https://www.waveshare.com/wiki/4inch_RPi_LCD_(C)

Is FBCP software driver supported on Rasberry TC?

https://www.waveshare.com/wiki/4.3inch_HDMI_LCD_(B)

I suppose HDMI driver is currently not working on Rasberry TC?

[Paul_123]

Those screens should work, but you cannot use the scripts that wave share provides.  You need to read the scripts and perform the functions in the TC methods.

[Yleisajattelija]

Those screens should work, but you cannot use the scripts that wave share provides.  You need to read the scripts and perform the functions in the TC methods.

With HAT eeprom I think that means bootloader and device tree blob hacking...

...does TC prefer U-boot?

[Paul_123]

We use the same bootLoader as RaspiOS.  The is no hacking involved.  Files are just in a different location, and commands used in the scripts may not be present on piCore, or different due to busybox.

[mocore]

...does TC prefer U-boot?

the only version in the tc repo is @ /4.x/x86/tcz/uboot-tools.tcz.info
which is likely to be removed soon ish 

[patrikg]

Those screens should work, but you cannot use the scripts that wave share provides.  You need to read the scripts and perform the functions in the TC methods.

With HAT eeprom I think that means bootloader and device tree blob hacking...

...does TC prefer U-boot?

The ordenary bootcode have to chainload u-boot if you want to boot with u-boot.