On Mon, Aug 16, 2010 at 11:30:39AM +1200, Daniel Beer wrote:
On Sun, Aug 15, 2010 at 04:31:47PM +0100, Robert Spanton wrote:
Hi,
At the moment, the uif driver in mspdebug waits 0.5 seconds between
polling the device's state -- i.e. querying whether it has hit an
interrupt etc. There's
G'day,
Using the current SVN source tree, I've built mspgcc4 on NetBSD-5.0.2. The
building and installation process completed without any noticeable problems.
When compiling projects I'm getting the following error messages:
[...]
/usr/pkg/msp430-gcc-4.4.3/bin/msp430-gcc -O2 -s
The -T msp430x149.x option overrides the default linker script. Does
the one you're using provide definitions for those symbols?
Try eliminating that option; it shouldn't be necessary unless you're
doing something special.
Peter
On Tue, Aug 17, 2010 at 8:54 AM, Berndt Josef Wulf
G'day Peter,
many thanks for your reply. I've tried to leave this option out, but it
produces a similar error:
/usr/pkg/msp430-gcc-4.4.3/bin/msp430-gcc -O2 -s -mmcu=msp430x149 -Wall
-D__MSPGCC__ -Wl,-Map monitor.map -T msp430x149.x -o
monitor command.o monitor.o usart.o utilities.o version.o
The new linker script,
/usr/pkg/msp430-gcc-4.4.3/msp430/lib/ldscripts/msp430x149.x is empty and just
contains a header declaring
that it is the default linker script for normal executables.
That is the problem. The script should not be empty. Something went
wrong with the binutils
