I have a problem the the msp430-gcc when compiling assembly. Im using
gcc-3.2.2 with msp430 Ext from the mspgcc/files on Source Forge
gdb-5.1.1 with msp430 Ext from the mspgcc/files on Source Forge
binutils-2.14
Note:
I tried binutils-2.15 but it failed to compile/assembled gcc so I
downgraded to 2.14 that seemed to work.
msp430-libc
im my code I add .section .vectors and describe what all of the interrupt
vectors are by using .org and .word
then I compile/assemble them. I then use pyjtag or msp430-gdbproxy to upload
the code to the MCU. when using eaither if I use msp430-gdb to try and debug
the program, if I do a Reset or a PUC. when I use c to continue. it returns
with an error message od E00, So I went over to another computer running the
quadravox tools and downloaded the code from the MCU into a TI Hex File.
then I built the same program (used the quadravox syntax) and uploaded it to
the chip. then I downloaded the TI Hex file from the chip and compared the two
files. Well they looked pretty much Identical around Address 0x1100 which is
where your main program is supposed to be. but down at the bottom around 0xFFE0
(Interrupt table) it was all 0xFF. the Quadravox program had the correct
interrupt vectors there. this made me think about where am I messing up so I
checked the linker script for the mps430x149 and it had definitions for the
.section .vectors and appeared to be OK. I don't know much about linker
scripts. so can anyone help me out with this? I was hoping to streamline alot
of my compile and builds for msp430 as well as continue to work on a Linux only
system.
Oh yeah I'm running slackware-9.1 with kernel 2.6.7
-thanks
--Del
--
--Delbert B Martin IV
Calient Optical Components
22 Thornwood Dr.
Ithaca, NY 14850
Phone: (607)-257-1525
Fax: (607)-257-1612
dmar...@calient.net
(607)-257-1525x188
