Hi Dmitry,
Thanks for the feedback. So the normal MSP430 branch doesn't support this
micro, ok. I take it the 55xx is not a MSP430X device ...

Does your comments regarding JTAG still apply if I just use SpyByWire?

Is the GoodFet the same as the TI programmer, i.e can you use it for
SpyByWire also?

I take it the main problem in getting the GdbProxy tool to work, is to
obtain the windows version under wine and using the latest *.dll's shipped
with IAR etc

I could probably hack the headers and linker scripts supplied with IAR or
CCE to use with the mspgccc tools.

If all of the above doesn't work, then like you say, I can resort to CCE ...

Cheers,
Bernie

On Fri, Sep 11, 2009 at 3:27 PM, Dmitry Zuikov <[email protected]> wrote:

> Hi,
>
> I have no idea about the msp430F5529 support, we use 5418, but probably
> the situation for 55XX is similar.
>
> My experience with both MSP430 and MSP430X branches is following:
>
> 1) 'Cause there is an changes in JTAG for X2 architecture, using the
> mspgcc toolchain for programming/debugging thouse MCUs is not possible.
>
> We use the GoodFET board's clone with our own firmware/clients (it's  an
> opensource) for programming those devices. The original board with the
> original client software and firmware now should also work with X2
> MCU's.
>
> 2) The headers for 54XX MCU's use wrong registers definitions.
>
> There is two possible solutions:
>
> Gerald Lutter has made an attempt to write an alternative headers for
> mspgcc. His solution works for MSP430X branch and need probably some
> minor changes to work on MSP430 branch.
>
> I used some ad-hoc scripts to parse a datasheet and generate custom
> header file for 5418 and used it instead of the standard msgpcc
> headers.
>
> 3) The MSP430 branch (that unable to generate the extended instructions
> and access higher flash memory) use some hardcodings and generate wrong
> code for MPY at least for 5XXX devices.
>
> 4) The MSP430X branch looks unstable and has a number of problems:
> typo in setjmp/longjmp and our firmware just does not work when it's
> compiled by msp430x branch for 54XX --- some crashes, memory corruption
> and so on.
>
> Finally, I moved to wine + CCE + GoodFET in order to continue
> development of our product.
>
> ---
> Regards,
> Dmitry
>
>
> On Fri, 2009-09-11 at 15:01 +1200, Bernard Mentink wrote:
> > Anyone?
> > If this is not yet supported in mspgcc, is it possible to grab the
> headers
> > etc from the Free CodeComposer-Eclipse tools provided by TI?
> > But then we still have to have a gdbproxy that will work with the device.
> >
> > Thanks,
> > Bernie
> >
> > On Thu, Sep 10, 2009 at 5:03 PM, Bernard Mentink <[email protected]>
> wrote:
> >
> > > HI All,
> > > Does anyone know if their is a version of mspgcc that supports the
> latest
> > > USB MSP430's. I would like to use the msp430F5529
> > > in a project. Is there header/lib and gdb support for this micro yet?
> > >
> > > I ask, because the download version for Windows has a 2008 date ..
> > >
> > >
> > > Many Thanks,
> > > Bernie
> > >
> >
> ------------------------------------------------------------------------------
> > Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day
> > trial. Simplify your report design, integration and deployment - and
> focus on
> > what you do best, core application coding. Discover what's new with
> > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> > _______________________________________________ Mspgcc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Mspgcc-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>

Reply via email to