From: Peter B. <bi...@ac...> - 2014-07-03 17:25:38
|
Run the firmware update as root. Peter On Thu, Jul 3, 2014 at 5:55 PM, Fávero Santos <fav...@gm...> wrote: > Hello! > > I just did the flashing process on my bricked fet. The only change is that > it initializes normally now. When I try to access tilib with it, the board > requires a fw update. When I insert the cmd, mspdebug tilib > --allow-fw-update, I get stuck when it's trying to initialize the > bootloader. Here the message: > > mspdebug tilib --allow-fw-update > MSPDebug version 0.22 - debugging tool for MSP430 MCUs > Copyright (C) 2009-2013 Daniel Beer <dl...@gm...> > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > MSP430_GetNumberOfUsbIfs > MSP430_GetNameOfUsbIf > Found FET: /dev/serial/by-id/../../ttyACM0 > MSP430_Initialize: /dev/serial/by-id/../../ttyACM0 > FET firmware update is required. > Starting firmware update (this may take some time)... > Initializing bootloader... > Initializing bootloader... > Initializing bootloader... > tilib: MSP430_FET_FwUpdate: MSP-FET430UIF Firmware erased - Bootloader > active (error = 56) > tilib: device initialization failed > > As I said before, the bricked fet do its led initialization (3 red blinks, > 1 red blink sustained and then green sustained). > > Weird... Is it possible that the boostrap loader cannot find my firmware? > Ps. In linux, driver is ACM0 and firmware version is 3. > > Thanks! > > Fávero > > FS > > *"If it doesn't starts with you, it dies with you." * > Julian Casablancas > > > On Wed, Jul 2, 2014 at 8:13 PM, Chris Liechti <cli...@gm...> wrote: > >> Am 02.07.2014 16:58, schrieb Fávero Santos:> 3) Last night I went to a >> friend's lab and managed to get a copy of a >> > v2firm. >> >> i suggest you use your friends JTAG interface to flash yours. >> >> if you open the MSP-FET430UIF, you'll find a connector with one row of 5 >> pins. this is the JTAG interface of the MSP430 in there and it is >> compatible with the 14 pin cable, just plug it in on the correct edge >> (connect pin 1 on 14 pin header). >> >> the USB interface must be plugged in to provide power but then you >> should be able to write the firmware with your friends JTAG box to your >> MSP-FET430UIF, just like you'd program any firmware on a board. >> >> unfortunately does the layout of the MSP-FET430UIF NOT connect the >> ROM-BSL of the contained MSP430 (at least not on previous versions of >> the board, the pins to start the BSL are not connected correctly), so if >> the firmware is broken, there is no other way than using an other JTAG >> interface to recover. >> >> chris >> >> >> ------------------------------------------------------------------------------ >> Open source business process management suite built on Java and Eclipse >> Turn processes into business applications with Bonita BPM Community Edition >> Quickly connect people, data, and systems into organized workflows >> Winner of BOSSIE, CODIE, OW2 and Gartner awards >> http://p.sf.net/sfu/Bonitasoft >> _______________________________________________ >> Mspgcc-users mailing list >> Msp...@li... >> https://lists.sourceforge.net/lists/listinfo/mspgcc-users >> > > ------------------------------------------------------------------------------ > Open source business process management suite built on Java and Eclipse > Turn processes into business applications with Bonita BPM Community Edition > Quickly connect people, data, and systems into organized workflows > Winner of BOSSIE, CODIE, OW2 and Gartner awards > http://p.sf.net/sfu/Bonitasoft > _______________________________________________ > Mspgcc-users mailing list > Msp...@li... > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > |