Hi, Moving this to tinyos-help, as I'm sure it is is a more appropriate location for this question.
In practical terms, for those of us who use msp430-gcc, but are not platform maintainers, what does this change to watchdog timer behaviour mean? Is there some change needed to the core platform files before this version of msp430-gcc can be used? The package manager on my linux box just updated the msp430-gcc version to 4.x when I wasn't paying attention, so, what do I need to do to stop the watchdog timer from breaking all my apps? Is there a flag I can add to the makefile re-disable the watchdog timer if it proves problematic, or do I need to disable it in Boot.booted() (and if so exaclty how), or if I did want to tickle it, what is the easiest way to do this? I'll go read through the msp430f1611 user guide in the morning, but i'm on a fairly tight deadline at the moment so any advice is welcome. Incidentally, if it matters, I'm primarily using telosbs and tmotes, with a few shimmers scattered around. I could revert back to the version 3.x msp430-gcc, but the hardware multiplier fix could be fairly compelling for me. Thanks in advance, Kevin On Thu, Aug 18, 2011 at 5:51 PM, Peter Bigot <[email protected]> wrote: > To save time and questions, I'd like to remind those responsible for > MSP430-based platforms that watchdog is NOT disabled on startup > anymore<https://www.millennium.berkeley.edu/pipermail/tinyos-devel/2011-June/004952.html>, > and that hardware multiply support should be fully > stable<http://www.mail-archive.com/[email protected]/msg09978.html>and > -mdisable-hwmul should be removed from any Makefiles or other places > they might be hiding. > > There is a bug in the original LTS-20110716 mspgcc release that affects > multiplication when using emulation instead of the hardware multiplier (in > other words, -mdisable-hwmul will generate bad code while removing it will > not). This was discovered in the last few days and is probably not in the > uploaded toolchain packages. > > The fix for this and all other known LTS-20110716 releases are available > as > patches<https://sourceforge.net/projects/mspgcc/files/Patches/LTS/20110716/>. > If you browse up a directory from that link you'll see instructions for > using git to track the current set of LTS patches. > > If you determine that the new mspgcc generates bad code, please report the > problem here or on the mspgcc bug > tracker<https://sourceforge.net/tracker/?group_id=42303&atid=432701> > . > > Peter > > On Thu, Aug 18, 2011 at 9:40 AM, Philip Levis <[email protected]>wrote: > >> The first step for the 2.1.2 release is updating the compiler toolchains >> to support newer microcontrollers (and fix many bugs!). Specifically, the >> TinyOS Ubuntu repository on tinyos.stanford.edu will include new compiler >> toolchains for the AVR, MSP430, and SAM3 Cortex M3. >> >> The new MSP430 and AVR toolchains are up in the repository now. I'd >> suggest that everyone switch over: 2.1.2 may not work with the old tools >> (e.g., the old MSP430 compiler requires hardware multiply to be disabled or >> it generates bad assembly sometimes, 2.1.2 will not disable it). As a >> short-term benefit, you should generally see smaller code when using the new >> compilers. >> >> Once Thomas and Razvan have the SAM3 packages ready, I'll tag the TinyOS >> tree for 2.1.2 and we'll start testing. >> >> Phil >> _______________________________________________ >> Tinyos-2.0wg mailing list >> [email protected] >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-2.0wg >> > > > _______________________________________________ > Tinyos-devel mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel > >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
