I'm using the 20040723 win32 version because the 20041112 version don't work
with my current code.
The code compiled with the newest version seems to crash during execution,
each time at different time.
It's like memory corruption. I obtain different code size with each version:
20040723
.text 40154
.data 130
.bss 1324
.vector 32
.stab 122124
.stabstr 53183
20041112
.text 39996
.data 130
.bss 1324
.vector 32
.stab 120984
.stabstr 53039
Is there someone who can give me some hint to fix this strange behaviour?
Thanks!
Fred
N.B. I have put a part of my makefile.
-------------------------------------------------------------------
MAKEFILE
-------------------------------------------------------------------
MCPU = msp430x1612
MCC = msp430-gcc
MCCOPTIONS = -c -mmcu=${MCPU} -Wall -fshort-enums
MOPTIMIZER = -Os
MDEBUGGER = -g
MNODEBUGGER =
MLDFLAGS =
MDEFINED = -DBOARD_V1_2
MINCLDIR = include
MCC_INC_DIR = C:/mspgcc/msp430/include
MSRCDIR = cc
MOBJ_DIR = obj
SRC = ApplicationLayer.c \
ExpertSystem.c \
messages.c \
ApplicationMsg.c \
ModemApplication.c \
StateMachine.c \
Master.c \
Slave.c \
SlaveApplication.c \
isr.c \
rs232.c \
rssi.c \
util.c \
xe1203.c \
flashaccess.c \
Sensors.c \
RS232Interface.c \
rfseals.c
DOBJECTS := $(SRC:%.c=$(MOBJ_DIR)/%.mo)
OBJECTS := $(SRC:%.c=%.mo)
OBJDIR:
-mkdir obj
$(MOBJ_DIR)/%.mo : $(MSRCDIR)/%.c
$(MCC) $(MCCOPTIONS) $(MOPTIMIZER) $(MDEBUGGER)
$(MDEFINED) -I$(MINCLDIR) -I$(MCC_INC_DIR) $< -o $@
rfseals: OBJDIR rfseals.elf rfseals.a43 rfseals.lst
-------------------------------------------------------------------
-----Original Message-----
From: [email protected]
[mailto:[email protected]]on Behalf Of Steve
Underwood
Sent: 28 février, 2005 19:21
To: [email protected]
Subject: Re: [Mspgcc-users] F1612 linker file???
Garst R. Reese wrote:
> Frederic Beaulieu wrote:
>
>> Hi all,
>> Is there someone who can explain some curiosities in the linker file
>> for the
>> new msp430f1612?
>>
>> 1- Why the origin of the text section begin at 0x2800 instead of
>> 0x2500 like
>> in the datasheet.
>> 2- Why the data length is 0x13ff instead of 0x1400 (begin @ 0x1100
>> and end @
>> 0x24ff)?
>> 3- What is the impact of RAM mirrored? Is it include in the linker
>> file? How
>> its works? etc
>>
>> Thanks a lot in advance and hope this help others!
>> Fred
>>
>>
> Your binutils is out of date:
> if [ "${MSP430_NAME}" = "msp430x1612" ] ; then
> ARCH=msp:16
> MACHINE=
> SCRIPT_NAME=elf32msp430
> OUTPUT_FORMAT="elf32-msp430"
> MAXPAGESIZE=1
> EMBEDDED=yes
> TEMPLATE_NAME=generic
>
> ROM_START=0x2500
> ROM_SIZE=0xdae0
> RAM_START=0x1100
> RAM_SIZE=0x1400
>
> STACK=0x2500
More than a little out of date, too. This was only wrong before the 1612
was launched, when I had to use preliminary data to create initial
support for the device. The above settings were introduced about the
time the preliminary 1612 silicon became available, and a solid data
sheet was made available.
Regards,
Steve
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
