On a different note, i was wondering if anybody on the list have the same
problem as me, using the TI pre-compiled binaries for the MSP430 (the RH
port, downloaded from TI web site), the msp430-elf-gdb.exe , works Ok with
430 and 430X but using only small memory model for a 430X. If you
On 06/03/14 17:34, DJ Delorie wrote:
Even if you have the smallest mps430 with 512 bytes flash, it does
not matter if your program is 24 bytes or 511 bytes - all that
matters is that it fits in the chip you have.
If the startup is more than 512 bytes, it matters a lot. If you only
have
OK, if it is /that/ much space then it's a completely different
matter. I thought we were just talking about clearing the bss and
setting the initialised data, which should just be a couple of
short simple loops.
Worst case startup is around 400 bytes, but once you start optimizing,
you
Hi DJ,
Thank you for your prompt reply, I understand, it is just always
frustrating for Windows users to deal with this, i will try your
configuration and do some research.
On a different note, i was wondering if anybody on the list have the same
problem as me, using the TI pre-compiled
On 05/03/14 23:25, DJ Delorie wrote:
I'm writing this document to collect some of the current/new knowledge
on how to minimize the flash/rom size needed for MSP430 applications,
using the new msp430-elf (FSF/Red Hat) tools. I'll keep a copy at
On Thu, Mar 6, 2014 at 6:05 AM, David Brown da...@westcontrol.com wrote:
Will the __intN stuff ever make it into mainline? The msp430 port may
be the only chip that needs __int20, but there are other chips that
could benefit from different integer sizes - perhaps __int24 on the
8-bit AVR, or
Even if you have the smallest mps430 with 512 bytes flash, it does
not matter if your program is 24 bytes or 511 bytes - all that
matters is that it fits in the chip you have.
If the startup is more than 512 bytes, it matters a lot. If you only
have 512 bytees of code space and you discover
Er, that reminds me, I missed some stuff in the doc about removing
Java support... sigh.
I added this:
Lastly, there's a GCC option -minrt that tells gcc to use a minimum
runtime for programs that do not need static initializers or
constructors (popular in C++ and Java). Note that this is
Is it the intent to fully support C++ in this port, inclusive of
static initializers and exceptions? (Exclusive of features that
require host support like threads, though it'd be good if chrono
could be used with various MSP430 clocks providing the underlying
timers.)
Proper support for C++11
Is it the intent to fully support C++ in this port, inclusive of
static initializers and exceptions?
If you have enough flash/ram, yes. We fully test C++ in our
simulators, so if gcc/newlib support it in general, it should work for
msp430 also.
(Exclusive of features that require host
On Thu, Mar 6, 2014 at 12:47 PM, DJ Delorie d...@redhat.com wrote:
If you have enough flash/ram, yes. We fully test C++ in our
simulators, so if gcc/newlib support it in general, it should work for
msp430 also.
Great. I'll try that out once it looks like all the TI patches are
applied to the
Hi DJ,
Great news and thank you for the update, is it possible to throw
somewhere the Windows binaries? I think it is time for fresh windows
binaries, the last one was back in December. Is it possible to have Windows
binaries every 3-4 months?Someplace on TI web site or some other site, or
Great news and thank you for the update, is it possible to throw
somewhere the Windows binaries? I think it is time for fresh windows
binaries, the last one was back in December.
Sorry, I don't work for TI, so I can't make them do a release or say
anything about their schedule or
I'm writing this document to collect some of the current/new knowledge
on how to minimize the flash/rom size needed for MSP430 applications,
using the new msp430-elf (FSF/Red Hat) tools. I'll keep a copy at
http://people.redhat.com/~dj/msp430/size-optimizations.html
This document has two
14 matches
Mail list logo
