Bugzilla – Bug 11880
support firmware updates for ip3k players
Last modified: 2011-01-13 22:53:40 UTC
If and only if we support attaching ip3k players to TinySC, then should we support firmware updates for those players? If so, for which players? Including such firmware would significantly increase the size of the downloaded SC (and, presumably, also the Fab4 firmware), unless we add a download-on-demand mechanism for ip3k f/w like we currently have for Jive/Fab4.
We already have a download-on-demand system for NAS vendors, which should already work. Does it not?
but tinysc should not cache the files, rather download to the player from the network on demand.
Michael, any chance that I can pass this to you? Alan.
I can look at this.
Created attachment 5471 [details] Proposed patch Andy, how about this as a solution, with a couple of extra bits: 1. Remove the default attempt to download all firmware for ip3k players in Firmware::init 2. Ship the ip3k Firmware/model.version files for TinySC 3. I think I also need to check that the updates dir gets created in TinySC.
OK so this still downloads the full firmware bin to flash? That should be OK as they are pretty small. I think you would need to add something that deletes the file after it's been sent to the player(s).
Why? Another player of the same type might connect, or the player might bounce back and forth between TinySC and another SC with a different f/w version. Are we that short of flash filesystem space? If one ignores the bouncing scenario, then I guess deleting them on startup would be fine.
OK I guess that's Richard's call.
Change 27634. Implemented so that ip3k f/w is deleted upon SC startup and re-downloaded as required.