(a) For a ticketing approach, might be better to create tickets on the
sourceforge project instead of emailing everybody with each one. Though I
don't know if anybody's going to maintain the how-to for the existing mspgcc
infrastructure; my preference is to leave packaging to downstream and just
Thanks for your input. (Note: Detailed discussion of the mechanics of
reconciling mspgcc/mspgcc4/msp430x is intended to be held on mspgcc-devel.
Please subscribe to that list if you're specifically interested in this
topic.)
Re errata: to whatever extent binutils or mspgcc{3,4} already supports
I'm not convinced that presence of a single far pointer requires that every
address kick up to 32 bits. If near/far is maintained as an attribute on
the symbol, as apparently IAR uses a __data20 qualifier, it should be
possible to manage things properly. Whether GCC+binutils makes it
reasonably
Hi,
I have moved to mspgcc4, I like it.
This should have nothing to do with the move. I'm using Eclipse to
debug. When I have the USB debugger plugged in with a 149 everything
works fine. When I plug in the EZ-430 I can do everything but set a
breakpoint. The breakpoint usually gets a
That's https://lists.sourceforge.net/lists/subscribe/mspgcc-devel, by
the way - it doesn't show up on the list-of-mailing-lists at
http://sourceforge.net/mail/?group_id=42303.
From: Peter Bigot [mailto:p...@peoplepowerco.com]
Sent: donderdag 12 augustus 2010 2:29
To:
Thanks for your help Peter. I didn't realise that the root PATH would be
different to the user PATH, so after trying to learn how to work around
that, I took you advice, at (c), and tried building mspgcc4, from the
procedure at http://mspgcc4.sourceforge.net/ What could go wrong? It's
only 3
Von: Peter Bigot
Gesendet am: 30 Dez 1899 00:00:00
Re errata: to whatever extent binutils or mspgcc{3,4} already supports
chip-specific errata I'll have to retain that. To whatever extent I can
come up with a way to add support, I'll do so. But I expect this'll be an
on-demand sort of
People will turn away from a product when it doesn't fit their purpose
now, or in the foreseeable future.
(If I could ever get it built, I might be able to pass judgement.)
Errol Kowald
On Thu, 2010-08-12 at 12:42 +0200, JMGross wrote:
Von: Peter Bigot
Gesendet am: 30 Dez 1899 00:00:00
Von: Peter Bigot
Gesendet am: 12 Aug 2010 03:04:29
I'm not convinced that presence of a single far pointer requires that every
address kick up to 32 bits. If near/far is maintained as an attribute on
the symbol, as apparently IAR uses a __data20 qualifier, it should be
possible to manage
As noted in earlier email to this list, svn for mspgcc4 is left in its
legacy state in support of the WASP project. Download either the release
tarball of mspgcc4, or clone the git repository. (Sorry if there is still
how-to documentation somewhere that implies otherwise. Somebody needs to
take
10 matches
Mail list logo
