#Support Of New Hardware
1 messages · Page 1 of 1 (latest)
I am a new "user" and hopefully developer of the HASSIO. I am on the way to port the OS to a new platform - STM32MP1. Therefore I have a few Questions: Do I have to add the new HW Machine also to the supported machines to the Supervisor? Is there a prefered way for porting new Hardware / Platforms? Are there templates to use?
Thanks for answers.
Generally, new machines need to be added to all parts of the stack (HAOS, Supervisor, as well as Core container). This is mainly to support custom packages in case needed.
We mandate upstream support, but afaik that should not be a big problem with STM32MP1.
What I am a bit worried is if the STM32MP1 is powerful enough. We'd rather prefer adding a bit more powerful system (aarch64, 1GHz+, 2GB RAM+)
I would even suggest at least 1.5GHz, 2 are even better today
We need a System with Secure Boot... RaspberyPi 4 (CM4) do not support a secure boot because of a closeed source bootloader - what about an iMX8 System?
I means our ADR are clear in that point what is needed to get a chance for being a supported device:
The board needs to be available for private customers in most major economic regions
Less power as an RPi4 make no sense for us to maintain such hardware as that is already very limited on memory speed and CPU clock
Toradex Products shall be available for public use and the iMX8 should have enough computational power. Do You know if someone has try to port the HA + Supervisor to Torizon (running in a docker container)?
I guess stefan know this
Supervised used to work on Torizon, not sure if it still does.
Toradex is more geared towards industrial users, they don't typically sell to consumers
FWIW, RPi recently added secure boot to their EEPROM firmware
My Questions why I am serching for secure boot are the following: I have a customer , a PV and Renewable Energy manufacturer which planed to give his customers the possibility to use his PV Data and give his customers the possibility to add via e.g. HA all the users needs ...
Thumb up -- thank You for that Info. This will simplify everything.
Is there a more complete guide somewhere For the haos build process? I would very much like to build for and test HAOS on my Rock5b I have the. I get "Error2" at the End of the build process. It generates. The u-boot files in output/image/ but never anything in the /releases dir.
If a single package fails during the Buildroot build process, the whole process wont finish