fleet variables and configuration - automatic?

[shawaj]

we currently use fleet variables such as VARIANT and FREQ and we have configuration info such as:

Define DT parameters
"i2c_arm=on","spi=on"
Define DT overlays
"spi1-3cs", "uart0,txd0_pin=32,rxd0_pin=33,pin_func=7"

ideally, for balena open fleets we would be able to have these auto-populate and/or somehow be set manually - perhaps in diagnostics?

[vpetersson]

It doesn't seem to be possible to do this out-of-the-box in the image creation process at least.

[shawaj]

We do it with the config.txt and a loopback connection.

We could just do the same with a file called like nebra.txt or something and read back the details perhaps? Or if it doesn't break anything, put some custom stuff in config.txt

A custom file is preferable IMO as it's more platform agnostic

[vpetersson]

@shawaj I've scoped out the ticket for migrating VARIANT and FREQ here. I'm still not sure how to solve the SPI configuration, as this is set from within the dashboard. The only way I can think of is having separate fleets per device type (which wouldn't be too big of an issue).

[shawaj]

This has been sorted for open fleets by Balena.yml files

And the rest will be sorted by NebraLtd/hm-diag#444

[shawaj]

Closing as completed