On Wed, Aug 04, 2010 at 08:32:53PM -0500, Mark Rages wrote: > On Wed, Aug 4, 2010 at 5:56 PM, Daniel Beer <[email protected]> wrote: > > On Thu, Aug 05, 2010 at 12:15:57AM +0200, Chris Liechti wrote: > >> Am 04.08.2010 23:52, schrieb Daniel Beer: > >> > There is a driver in MSPDebug for accessing the FET bootloader, but so > >> > far I haven't been brave enough to try using it for erasing and > >> > writing. I currently have no other way of debugging the FET if I break > >> > the firmware. > >> > >> make your experiments with a UIF box. it has a JTAG header inside which > >> allows you to upload (and later restore) the current firmware with a > >> second JTAG adapter. > >> > >> chris > > > > Hi Chris, > > > > That had occured to me, but my problem is that I'm _very_ short on > > equipment. Apart from a FET430UIF, the only other debugger I have is > > an eZ430-RF2500, which apparently only does Spy-Bi-Wire (and the > > MSP430F1612 inside the FET only does JTAG). > > > > I do have another JTAG adapter (a fairly dumb one) and I was thinking > > at some stage to implement a raw JTAG driver for MSPDebug. If I manage > > to get this working, this could solve my first problem, assuming I > > don't get more equipment by then. > > > > It would be sweet if you could get MSPDebug working with a GoodFET. > Do you have one?
Yeah, I'd like to do a driver for the GoodFET. I have a blank board, but not the skill or parts to assemble it at the moment. Is there any documentation of the GoodFET protocol aside from the control software's source? - Daniel
