Re: [Mspgcc-users] Problems with erasing MSP-EXP430FR5739 and then "Security fuse blown" error

2011-11-21 Thread Daniel Beer
On Sun, Nov 20, 2011 at 02:34:05PM +0100, Kuba wrote: > I am new to the list, trying to dive into the world of MSP430 and I > already thank you for the great work around mspgcc/mspdebug. Thanks! > > After playing a bit with the original Launchpad I also purchased the > FRAM experimenters board ( M

Re: [Mspgcc-users] MSPDebug version 0.18

2011-11-21 Thread Daniel Beer
On Sun, Nov 20, 2011 at 11:16:11AM +0100, Stephan Goldenberg wrote: > Am Samstag, den 19.11.2011, 16:57 -0300 schrieb Sergio Campamá: > > Hello, sorry to interrupt, but I have a (maybe) similar problem. I also > > have the 1.4a JTAG programmer, and when I connect it to Ubuntu (11.04), it > > says

[Mspgcc-users] MSP430.DLL v3 for Linux

2011-11-21 Thread Daniel Beer
If anyone's interested in using the new v3 FET firmware on Linux via the TI MSP430 library, I've prepared a patch series for TI's source package which is available here: http://mspdebug.sourceforge.net/tilib.html There are build instructions on the page. I've tested it using an MSP430F2274 vi

Re: [Mspgcc-users] MSP430.DLL v3 for Linux

2011-11-21 Thread Sergio Campamá
Hello Daniel, Thanks! I have a 1.4a UIF JTAG programmer, with this new work, could I update it's firmware to the V3 one? Is that what the last command in the guide does? Best regards, --- Sergio Campamá sergiocamp...@gmail.com On Nov 21, 2011, at 10:38 PM

Re: [Mspgcc-users] MSP430.DLL v3 for Linux

2011-11-21 Thread Sergio Campamá
Wait, so instead of using the TI3410 driver, it uses the CDC one? I've been using the RF2500 modules for a while now (Ubuntu Server 11.04) , and that driver sucks. It works 1 in 10 tries when opening minicom... --- Sergio Campamá sergiocamp...@gmail.com On

Re: [Mspgcc-users] MSP430.DLL v3 for Linux

2011-11-21 Thread Daniel Beer
On Mon, Nov 21, 2011 at 10:56:27PM -0300, Sergio Campamá wrote: > Wait, so instead of using the TI3410 driver, it uses the CDC one? I've been > using the RF2500 modules for a while now (Ubuntu Server 11.04) , and that > driver sucks. It works 1 in 10 tries when opening minicom... Yep, new firmwa

Re: [Mspgcc-users] Problems with erasing MSP-EXP430FR5739 and then "Security fuse blown" error

2011-11-21 Thread Kuba
Hi Daniel, 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

Re: [Mspgcc-users] Problems with erasing MSP-EXP430FR5739 and then "Security fuse blown" error

2011-11-21 Thread Eric Decker
On Mon, Nov 21, 2011 at 11:06 PM, Kuba wrote: > Hi Daniel, > > 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 mspde

Re: [Mspgcc-users] Problems with erasing MSP-EXP430FR5739 and then "Security fuse blown" error

2011-11-21 Thread Daniel Beer
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? > A

Re: [Mspgcc-users] Problems with erasing MSP-EXP430FR5739 and then "Security fuse blown" error

2011-11-21 Thread Kuba
Dear Eric, Daniel, I see. Indeed if the INFO section contains only "useful" data and not "critical" data, then I can safely erase the device. Sorry for asking silly questions, but though being an electrical engineer I come from the analog side of the world. I guess cannot achieve the mass-erase u

Re: [Mspgcc-users] Problems with erasing MSP-EXP430FR5739 and then "Security fuse blown" error

2011-11-21 Thread Eric Decker
On Mon, Nov 21, 2011 at 11:34 PM, Kuba wrote: > Dear Eric, Daniel, > > I see. Indeed if the INFO section contains only "useful" data and not > "critical" data, then I can safely erase the device. > Not silly at all. How many of us have bricked a device accidentally. Understanding is good and