Hello: Gunther Lemm wrote:
> Hi, > > I'm stuck with mspgcc + F248 - so I just subscribed to this list to ask > for some help. > > I've got a product based on a F149. In the new design I've switched to > F248. Now I've got the hardware, but no toolchain that supports the > processor. > Some weeks ago I've checked out the toolchain from the CVS and managed > to add support for F248. Binutils and gcc tell me that they support this > processor and I get my test code compiled and linked (I've got no clue > if the generated code is correct though). > > When I tried to flash the F248 with good old msp430-gdbproxy via a > parport FET it tells me > > error: msp430: Could not read device memory (6) > > Ok, so I need a new gdbproxy. I've been using the procedure in > packaging/README-MAINTAINER.txt but the included makefile does not > compile any gdbproxy. > Yesterday I tried to check out the current version of the toolchain from > the CVS because I thought there may have been someone adding support for > new processors. CVS got stuck telling me: > > cvs checkout: Updating msp430-libc4/include/msp430 > cvs checkout: [13:34:46] waiting for root's lock in > /cvsroot/mspgcc/msp430-libc4/include/msp430 > > I guess there's something wrong with the repository ... > > So here are my questions: > > - is there a list of officially supported devices? or do I have to > compile and ask my gcc-binary? > - are MSP430F24x already supported (as they are JTAG-devices, there > shouldn't be any spy-by-wire related issues - or did something else > change?)? > - is there another (maybe official) way to build the toolchain (except > for the way explained in README-MAINTAINER.txt)? > - where do I get a gdbproxy that supports the F248? > - could anyone please fix the CVS repository? > > Please, look into the archives, there have been recent discussion on that topic. -- Raúl Sánchez Siles
