On 11 April 2014 17:54, Doyle, Alan <[email protected]> wrote: > I'm working on remotely upgrading the application code within our > MSP430F2616 based board. > > Does anyone have an example of how to download a new executable and reboot > from the new location in flash. >
In TinyOS you'll want to have a look at using TosBoot (tos/lib/tosboot) as a boot loader. As for getting the new executable onto the board you have a few options. The Deluge protocol is the "normal" way I believe, though I have never used it myself. A quick google turns up http://www.tinyos.net/tinyos-2.x/doc/html/deluge-t2-manual.html . Back when I was actively working on TinyOS for $work, we had our own mechanism of sending out new firmware, which essentially meant that our application was responsible for seeding the standby "partition" on the flash. We are using the MSP430F2616 chip, TinyOS and nesC; and I was hoping to > split the flash code memory in two. So that once the new code has been > received and validated, the start code pointer (and maybe vector values) > are modified so that when a reboot is invoked the new code would be used. > I've never used TinyOS on an MSP430, but I'm currently working on the F2618 chip for a non-TinyOS project here at $work. This chip family doesn't offer a lot in terms of boot flexibility - in particular it does not offer an alternate vector location, so you'd likely want to install some trampolines that can redirect the ISRs to the active "partition", based on a flag you've set somewhere (e.g. INFO area). I have been looking at various documentation but I have not been > successful in finding out whether this is possible. If it is; what > registers need to be modified? > It's technically possible, but unless there's already good platform support in TinyOS it's likely to take a bit of work, especially as the chip itself doesn't provide much help. Another issue you're likely to encounter is that once you've divided the flash into two, there's not a lot of space left for an application once the upgrade support has gone in. People who've worked with TinyOS on the MSP430s probably have better info, but I hope this gives you a couple of leads at least. Cheers, /Johny -- Johny Mattsson Senior Software Engineer DiUS Computing Pty. Ltd. *where ideas are engineered *
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
