Re: trashed MSP-FETU430IF

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: trashed MSP-FETU430IF

Fávero Santos
Hello!

Firstly, I would like to thank you guys for all the hints and the help you
gave me. Let me give you a digest on what I did in the last few weeks as I
also would like to share with the mailing list this experience.

As suggested, I programmed my trashed fet. I was able to do that in 2 ways:
1) Using BSL. The BSL application note can be found in Ti website. With
this note, you can use your msp launchpad as a BSL to program other
firmware via serial lines.
2) Using another FET.

Results:
I was able to re-program my trashed FET with a V2 firmware but I found
another problem... When plugging my trashed fet to the computer, it was
initialized as a CDC driver (v3 firmware), not as a VCP driver (v2
firmware) - so I had a V2 firmware in my fet but my PC recognized it with a
V3 driver. I tried to re-install official drivers (used Ti files available
on mspdebug stack's site) but it also didn't work. I also tried removing
all available TI drivers and then letting the FET install it's driver
automatically. It also didn't work but this time I saw my FET couldn't even
supply a driver for the installation process in my PC (as usually it
happens when you plug your FET's for the first time).

I also tried to downgrade/upgrade the firmware hopping that those
procedures could somehow save my FET. I used the steps described in
MSPDebug's website as the program FET-430Pro Lite. No luck with both.

In the last week I've received another FET. This time, as people suggested
me, I stuck with V2 firmware. I'm using uif driver with jtag option. As it
is a demand in my project, I had to use mspdebug and gdb as external
programs to Eclipse in order to debug my firmware (MSP430 Toolchain works
fine - the project I'm working on is imported from a makefile thus some
changes in the path to the .elf program had to be done).

I would like to thank you guys for the effort on helping me and for the
time expended in this situation. Thank you so much for the those helped me!

Cheers,
Fávero

FS

*"If it doesn't starts with you, it dies with you." *
Julian Casablancas


On Mon, Jul 14, 2014 at 9:20 AM, Kees Schoenmakers <[hidden email]>
wrote:

> Hi Favero,
>
> I found your report on the mspgcc mailing list.
>
> One of the files I sent you is the EEROM image that initializes as
> /dev/ttyyUSBx.
>
> I used ponyprog2000 via the parallel port and A MINIMAL INTERFACE to
> access the I2C EEROM. Need only GND, SDA and SCL.
>
> http://www.lancos.com/e2p/easyI2Cbus.gif
>
> So first: re-program the serial EEPROM in the FET
> Second have another jtag tool to write the firmware image.
>
> I believe it would work as normal after this.
>
> I also ran into trouble while trying to update to V3. I managed to
> succeed only once. After downgrading (succesful) I was not able to
> upgrade a second time....
>
> I stuck to V2 for now.
>
> best regards
>
> Kees
>
>
>
> On 7/2/14, Fávero Santos <[hidden email]> wrote:
> > Hello, Kees
> >
> > Thank you so much. I'll get back to you ASAP.
> >
> > Regards!
> >
> > FS
> >
> > *"If it doesn't starts with you, it dies with you." *
> > Julian Casablancas
> >
> >
> > On Wed, Jul 2, 2014 at 8:04 AM, Kees Schoenmakers <[hidden email]>
> > wrote:
> >
> >> Hello Favero,
> >>
> >> Here they are....
> >>
> >> Let me know how it went.
> >>
> >> best regards
> >>
> >> Kees
> >>
> >> On 7/1/14, Fávero Santos <[hidden email]> wrote:
> >> > Hi!
> >> >
> >> > Thx for the hints, Kees. Can you make a copy of your v3 firmware and
> >> > send
> >> > me, pls (.hex format pls)? This way I can flash into my fet430uif...
> >> >
> >> >
> >> > Thanks!
> >> >
> >> > FS
> >> >
> >> > *"If it doesn't starts with you, it dies with you." *
> >> > Julian Casablancas
> >> >
> >> >
> >> > On Tue, Jul 1, 2014 at 11:57 AM, Kees Schoenmakers <[hidden email]
> >
> >> > wrote:
> >> >
> >> >> Hello Friend,
> >> >>
> >> >> I have been in the same boat _but_ I had access to a second device
> :-)
> >> >>
> >> >> In that way I could extract the serial eerom contents from the
> >> >> know-good device and rewrite
> >> >> the serial eerom in the trashed device to start with.
> >> >>
> >> >> Further I took a copy of the MSP430F16something device from the
> >> >> MSP430-FET (good one) and wrote it back in the broken one.
> >> >>
> >> >> For reading the serial EEROM I used Ponyprog2000 which allows for a
> >> >> _very_ simple interface via the parallel port (that's handy on Linux)
> >> >>
> >> >> Just 3 connections (SCL,SDA and GND) are neccesary to have it
> working.
> >> >>
> >> >> For further questions,
> >> >>
> >> >> Kees
> >> >>
> >> >
> >>
> >
>

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck&#174;
Code Sight&#153; - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users