Like I wrote: with "small modification" Isn't smbus simpler than usb? CEC part is done, rainshadow protocol is done. Only communication must be changed. Still betetr than writing everything. And implementation must be standardized.
There's a lot more to it as the STM32 needs to support FAN + wakeup + CEC + IR, furthermore the STM32F100R4H6B is low spec 16K flash + 4K RAM. So some parts of the CEC protocol may need to be implemented further up the stack with additional custom drivers.
maybe I'm unfair with my limited exposure, but it seems like cec is a common problem with SBC. How is it so easy to implement on the RPi on arm, but difficult on x86? Any insight from someone who works on code for both platforms?
It looks like ektor5 of the UDOO team is working again on this feature (https://github.com/ektor5/secocec). Can we have an official ETA?
As already discussed, it's not OS-side only, a proper firmware for the STM32 has to be in place. If this is already the case, it's not documented at all. The new firmware update 1.03 (which was due some weeks ago) could provide something, given it already needs some modifications to the STM32 firmware (for factory reset and waking the CPU from the Curie core), yet @Laura seems to be avoiding all these issues. As an aside, in the Kickstarter campaign the UDOO team advertised the UDOO x86 to be open hardware and software, but the only actual "software" is the STM32 firmware, which was never released (but apparently they're now "evaluating" wether to release the code).
I am currently awaiting an update on the 1.03 firmware progress for the SoC. The original estimated time frame that I gave you all has since passed, and I would like the next update that I provide to be accurate and final. Regarding the open sourcing of the STM32 firmware, we are looking into this.
Nothing new here. What I was really hoping for was an official statement on CEC (and IR) support, possibly related to the STM32 firmware.
After a month and a half since I opened a ticket on this issue I finally got an answer, but it's not good news. There is no ETA for the CEC (and IR) driver and they don't plan to open source the STM32 firmware in the foreseeable future. I'm really disappointed
I suspect (although I could be wrong) the STM32F100R4 is too low spec to add features like CEC (and IR) on top of what it already has do.
This really sucks! Udoo x86 was also promoted on KS as a mediaplayer. Not having CEC / IR really limits the user-friendlyness. Udoo should at least open-source the firmware!
There might be more work happening towards this soon, now that the 1.03 firmware is now available: https://www.udoo.org/forum/threads/any-estimate-when-firmware-1-03-will-be-available.7464/page-2
damn this sucks... this was one of the main reasons i bought it -.- but the kodi remote is a good idea thx... i will use this also for now... but did u heard about the pulse eight cec adapter? shouldnt this also work? do u think hdmi cec will ever be supportet ? i dont understand why they say its working...https://www.udoo.org/docs-x86/Hardware_&_Accessories/CEC-HDMI.html
