On Tue, Nov 22, 2011 at 08:06:13AM +0100, Kuba wrote: > Thanks for the info. That sounds a bit better than the chip replacement > (though I will try that if nothing else works, thanks Crazy Casta). > > Did you come across an instruction to follow this procedure? Can it be done > with mspdebug? > As far as I read this morning about BSL operations, the mass erase deletes > both program and information data. Isn't loss of information data going to > bring me more trouble? :)
Hi Kuba, It can be done with mspdebug (flash-bsl driver), but I haven't needed to do it myself. There is some documentation available from TI about the bootstrap loader ("MSP430 Memory Programming User's Guide", I think). You'll also need to check the chip datasheet to see which pins you need for BSL communication and entry. You'll probably want to check this, but I'm fairly sure that a mass erase won't touch the Info A segment, which is the one containing calibration data. The other info segments are for user data. Cheers, Daniel -- D.L. Beer Engineering www.dlbeer.co.nz ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users