Hi,
I've been trying the compiler on a msp430f2617. So far I haven't been
able to use printf using the -mdata-64k option. The same program with
the linux version of the compiler works just fine. Any thoughts on
what may cause this?
2010/1/12 Gerald Lutter ger...@itzgrund.net:
Hi Mark,
Am
Hi,
I've been trying the compiler on a msp430f2617. So far I haven't
been able to use printf using the -mdata-64k option. The same
program with the linux version of the compiler works just fine.
Any thoughts on what may cause this?
we use this compiler and it works for us using exactly the
Hi,
I've installed it in both c:/mspgcc (just in case) and
c:/cygwin/opt/msp430 and if I run which msp430-gcc I get the
/opt/msp430/bin folder. I'm using other flags along with -mdata-64k,
could them cause this behaviour? I'm using the compiler to build a
TinyOS application and the build system is
In support of OSHAN http://sourceforge.net/projects/oshan/, an open source
home area network targeted to embedded devices, I've implemented CC430
support in MSPGCC. It is currently available for download from the OSHAN
project page on SourceForge, in a Bazaar repository based on the MSPGCC one
at
Hi Jordi,
besides the problems with parameters, there is another problem with the MSP430X
command set:
Calling functions in the FARMEM requires different function calls (CALLA
instead of CALL) as well as different return codes (RETA instead of RET).
This is somewhat backward compatible, as it
Hi Roman,
Nice to hear that some progress has been made.
But I think the whole thing has been addressed from the wrong side.
Rather than trying to make the copiler smart enough to decide what to do, or to
add switches and whatever, it would have been smarter to return to something
that has
