While this may have been the problem, be aware that there is an undocumented (AFAIK) chip erratum on the CC430. I had programmed some boards to immediately enter LPM5 on boot; at that point, I could no longer use the FET over JTAG. See the threads titled *Cannot access TI MSP Experimenters board * from this mailing list about three weeks ago for potentially related information. We were able to restore functionality using the BSL over a USB port on our development boards. I have not tried to diagnose this further.
If you left the watch programmed and running and it put itself into LPM5 after some extended idle period, that may have been part of the problem. It's possible that there's something about the code generated by mspgcc vice IAR/CCS that makes it happen. Or it may have just been your Windows problem all along. Peter On Sun, Jun 20, 2010 at 9:17 AM, <p...@sehorne.org> wrote: > It turns out there was never a problem with the build. > I discovered later that I had a Windows 7 problem that > prevented the BM Firmware Update Tool and also TI's > BSL_Scripter tool from accessing the the USB FET. > > I've since rebooted my machine and have repeated flashed > the watch with mspgcc4 project with not problems. > > Paul > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users >
