Questions relative to porting of the HA OS to Beagle Bone Black

[Didifred]

I'm quite advanced in porting HA OS to Beagle Bone Black, i have several questions before to do a pull requests if the community is interested ...

• It seems mandatory ( initialization fails in others cases) to have packages BR2_PACKAGE_RPI_RF_MOD and BR2_PACKAGE_RPI_RF_MOD_DTS, it shall concerns obviously only RPI hw ?
• I have one warning at initialization of Home Assistant application that concerns pulsaudio, in *_defconfig the package is not compiled (BR2_PACKAGE_PULSEAUDIO). It sounds every install has this warning so ?
• I've setup BR2_PACKAGE_HASSIO_MACHINE="tinker" and BR2_PACKAGE_OS_AGENT_BOARD="Tinker", since i need something close. Why the supervisor and os agent are dependant to the board BSP, naively i was thinking that HA OS provided APIs independant of the board ? Using it for beagle bone seems work ok, it do not appear to be dependant of board in fact.
• In order to flash the EMMC, i simply dd the image from a SD card bootup debian 12 ( the haos-data expansion is about 3G and the OS itself about 450M shrinking the partition mapping a bit, i'm near to the 3.6G available ...). Then i move data to external media (SD or SSD) via HA web application. Running OS on EMMC give reasonable starting time of the application comparing SD. Maybe i can even remove the haos-data partition from the image, flash it in EMMC and burn the data.ext4 on external media, and first start like this ? Does OS will scan automatically for the partition in external media at first start ?

[sairon]

Hey, sorry for replying this late but maybe my answers would still have some use :)

It seems mandatory ( initialization fails in others cases) to have packages BR2_PACKAGE_RPI_RF_MOD and BR2_PACKAGE_RPI_RF_MOD_DTS, it shall concerns obviously only RPI hw ?

It shouldn't be needed - while it's not exclusively for RPi HW (there's support for some more boards), some of our targets don't use it at all, e.g. Green. I'm not sure what you mean by failed initialization.

I have one warning at initialization of Home Assistant application that concerns pulsaudio, in *_defconfig the package is not compiled (BR2_PACKAGE_PULSEAUDIO). It sounds every install has this warning so ?

Again, not sure what warning you mean but PulseAudio is normally running in a separate container (https://github.com/home-assistant/plugin-audio), it shouldn't be needed to have it in the base OS.

I've setup BR2_PACKAGE_HASSIO_MACHINE="tinker" and BR2_PACKAGE_OS_AGENT_BOARD="Tinker", since i need something close. Why the supervisor and os agent are dependant to the board BSP, naively i was thinking that HA OS provided APIs independant of the board ? Using it for beagle bone seems work ok, it do not appear to be dependant of board in fact.

OS Agent has some device-specific features that are depending on a compile-time flag. Maybe it is something that could be done differently but right now it's a historical decision that needs to be taken as a fact. Similarly, HASSIO_MACHINE is used to determine what Docker images would be used by the Supervisor, which may have some specific extra packages installed, etc.

Maybe i can even remove the haos-data partition from the image, flash it in EMMC and burn the data.ext4 on external media, and first start like this ? Does OS will scan automatically for the partition in external media at first start ?

No need to remove anything from the image. Simply use the data disk feature and the eMMC will be used only for the other partitions: https://www.home-assistant.io/common-tasks/os/#using-external-data-disk