This is probably obvious, but what is the right way to set dtparam and dtoverlay values when using local dev mode?
Running a multi-container app and testing a i2c based HAT and running into some issues so I wanted to try some different params and overlays.
Actually I don’t know and never really found an answer to that.
I normally tend to change the config.txt before(!) the first boot and include everything there.
Be advised that after the first boot, the config.txt will be “checkum controlled” by the supervisor, meaning if you change something by hand (e.g. when the RPi is off and you reboot), the supervisor will find that change, replace the config.txt with the last known value from its sqlite database and trigger a reboot, undoing your change. You have to manipulate the entry directly in the sqlite database to make it happen, at least that was the case when I did it the last time… But maybe some of the balena Wizards got a more obvious way of doing that or at least a less cumbersome 
So perhaps there is no elegant way of doing so in local mode?
I’d rather not re-flash since flashing the CM4 emmc is a bit of a pain.
That was my old “solution”, but maybe something better is now available:
If the device is in local mode then I think this should work, where you can define your own local target state Interacting with the balena Supervisor - Balena Documentation
Try it out, do let us know if it work.
@vipulgupta2048 that seems to work. Though to be honest, I’ve discovered it’s just easier to set the correct params in the UI in non local mode before switching to local. Easy peazy.
Hi, thanks for your feedback, I’ll record it internally and discuss how we can ease it for local-mode as well.