Challenges: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
This is a challenge to your software you have to address at compile time. During operations you may want to change the configuration of the device. If you want do to that with re-programming the chip, you need to use an interface of some kind (wireless, SPI/ I2C, or SD card). | This is a challenge to your software you have to address at compile time. During operations you may want to change the configuration of the device. If you want do to that with re-programming the chip, you need to use an interface of some kind (wireless, SPI/ I2C, or SD card). | ||
* Updating device configuration (ie, MQTT/ WLAN) | * Updating device configuration (ie, MQTT/ WLAN) - ideas: via SD Card or via writing config data to EEPROM | ||
* Updating device code | * Updating device code - via ISP, or - ideas - OTA with the Arduino uploading a program to the ESP, followed by the ESP flashing the Arduino | ||
[[IoT with AME|Home]] | [[IoT with AME|Home]] | ||
Revision as of 15:32, 17 July 2017
Challenges - How to Overcome Hardware and Software Limitations
The Arduino hardware is pretty limited - you get 32kB of unmodifiable (at run-time) flash memory for the program, and 2kB of modifiable SRAM memory for variables. That's it.
This is a challenge to your software you have to address at compile time. During operations you may want to change the configuration of the device. If you want do to that with re-programming the chip, you need to use an interface of some kind (wireless, SPI/ I2C, or SD card).
- Updating device configuration (ie, MQTT/ WLAN) - ideas: via SD Card or via writing config data to EEPROM
- Updating device code - via ISP, or - ideas - OTA with the Arduino uploading a program to the ESP, followed by the ESP flashing the Arduino