Open neilh10 opened 5 years ago
I'm going to close this too. I think anything related to changing the bootloader is beyond the scope of this library.
@aufdenkampe
Similar to my comments for #219...
@neilh10, I really like these ideas! @SRGDamia1, I also fully agree that we don't want to make this ModularSensors library rely on a non-standard boot loader.
Let's think about creating a new repo for the development and testing of a new boot loader. @neilh10, Let me know if you would like me to do this within the EnviroDIY GitHub organization.
So let' keep this issue open, so we don't loose track of this goal, even if such and effort will largely be done in a new repo.
I'm documenting discussion elsewhere to put it in the context of an "OTA Upgrade". I've no idea whether these features make sense in terms of Modular Sensors , and it maybe easy if there are libs that perform some or all of the sub-features. https://github.com/EnviroDIY/ModularSensors/issues/198
Using a layered architecture - if a file can be downloaded to the SD card, and there is a "ModularSensors" boot program, then when the ModularSensors reboots it would upgrade itself. https://github.com/EnviroDIY/ModularSensors/issues/219
One way of having a new image downloaded (.pioenvs\mayfly\firmware.hex ~206Kb), is for a message to be sent to the ModularSensors to ftp a specific file onto the SD card, that way it can do it when the right conditions exist (good strong signal, power...) {I didn't think of this first - its the way one of the new CATM modems can be upgraded}
One way of supporting messaging from a Cloud to ModularSensors maybe to implement an MQTT subscribe, and have a corresponding cloud location to be able to initiate messages and also place upgrade able files on a ftp server (drive.google... box..) https://learn.adafruit.com/mqtt-adafruit-io-and-you/more-on-subscriptions
There maybe otherways of doing it - and sometimes it takes some "chewing it" before it gets simple enough to make it workable :)