- This topic has 3 replies, 2 voices, and was last updated 11 years, 5 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Hi Radu,
Reading through the other posts regarding firmware updates. Perhaps if you added an SPI or I2C (depending on what IO is left and available on the ATMega) SRAM chip you could use the new json api to push a hex file into the sram verify it then hand off to the bootloader to read the SRAM and flash it.
You could also use the SRAM for temp storage when not being used to buffer firmware images.
Only downside is adding a couple of dollars to the BoM in the SRAM and passives.
Not a bad idea and would make the updates so much easier!
You could use the SRAM as a limited buffer for lost web updates. For example my ADSL2+ connection can get very unstable and loosing updates while the connection is offline gets very real, so buffering the lost updates would be advantageous.
Also retrofitting the SRAM on a piece of proto board would be pretty straight forward. From what i can see you could tap the SPI lines off the Ethernet module and go straight to a spare I/O line on the ATMega for the chip select