I'm using the PCB from TI with the msp4302211 packaged in a 14 pin DIP.
My msp430-gcc --version from Mint13 is
msp430-gcc (GNU GCC patched mspgcc-20110716) 4.5.3
I have made a small c program to get into the swing of it and that
loaded into 0xf800 with mspdebug ran the way I expected.
Trying the
Hi,
I'm trying to get the I2C working on an msp439f5438 and I have the
following code in my source file.
UCB0CTL0 = 0;
UCB0CTL1 = 0;
This gives the following compile errors.
make
msp430-gcc -Os -Wall -g -mmcu=msp430f5438 -c main.c
main.c:117:2: warning: data definition has no type or storage
I'm awake and I've fixed it sorry to bother. Ian.
On 12-12-02 10:05 AM, Ian Chapman wrote:
Hi,
I'm trying to get the I2C working on an msp439f5438 and I have the
following code in my source file.
UCB0CTL0 = 0;
UCB0CTL1 = 0;
This gives the following compile errors.
make
msp430-gcc -Os
Hi, I do not seem to have all the files to deal with msp430f5338, I get
the below error. Usin msp430f5438 all compiles well and runs under
mspdebug rf2500 program all works great. I guess I'm missing a few
headers. I have the following version. Any suggestions welcome. Ian.
msp430-gcc
Hi,
I pulled over the libbluetooth-dev package and I can compile a
simple exercise and run it on my Mint 13 PC using gcc.
Moving onto msp430-gcc I get
msp430-gcc -Os -Wall -g -mmcu=msp430f5438a -c main.c
main.c:4:20: fatal error: unistd.h: No such file or directory
compilation
Hi all,
I'm a bit lost with this. The Mint13 version of msp430-gcc runs
fine. I think I compiled mspdebug from sources it's version 0.20. When
I try to run msp430-gdb it tells me to get gdb-msp430. The package
manager fails to install gdb-msp430 as there is a conflict.
E:
and and and
Remote debugging using localhost:2000
Segmentation fault
Both of the above are known bugs and are documented. Any ideas? Ian.
On 13-04-09 08:45 PM, Ian Chapman wrote:
Hi all,
I'm a bit lost with this. The Mint13 version of msp430-gcc runs
fine. I think I compiled mspdebug from sources
Hi all,
My Makefile produces all the dot.o files from the dot.c files with
a few warnings. However the link stage fails to find the functions
called by main.c that are specified in the dot.h and defined in the
dot.c files and by then should be in dot.o files.
Makefile
CC=msp430-gcc
Hi,
I have a silly problem. Mspdebug runs and reports :--
#mspdebug rf2500
MSPDebug version 0.19 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2012 Daniel Beer dlb...@gmail.com
This is free software; see the source for copying conditions. There is NO
warranty; not even for
On 09/26/2013 04:18 PM, Daniel Beer wrote:
On Thu, Sep 26, 2013 at 09:12:50AM -0400, Ian Chapman wrote:
I have a silly problem. Mspdebug runs and reports :--
#mspdebug rf2500
MSPDebug version 0.19 - debugging tool for MSP430 MCUs
Copyright (C) 2009-2012 Daniel Beer dlb...@gmail.com
Hi,
I'm running this in a terminal mspdebug rf2500 gdb and this cgdb
-d msp430-gdb main.elf or msp430-gdb main.elf in a second terminal.
cgdb looks really good. I've not been able to determine how to control
msp430-gdb, the info file for gdb is not supported in target and help
target is
Hi,
cgdb -d msp430-gdb main.elf // I do not get the source file
displayed in the source window. cgdb is able to set breakpoints using
line numbers and labels also step to the break point but I'm not able to
see the source file in the cgdb source window. Any suggestions? Ian.
Hi, I'm moving from to msp430g2553 from msp430f5438a and after some work
I have a clean compile. However I'm getting this linker error. Linking
and running are still okay with the previous chip.
msp430-gcc -o main.elf main.o uart.o ADC.o Timer.o Xref.o -Os -Wall -g
-mmcu=MSP430g2553
Hi all,
I'm having difficulty understanding this situation.
flag = 1;
while ( 0 != flag )
{
code;
}
generates strange assembly code till I commented out
// flag = 1;
it looked to me like the optimizer realized that from then on the code
would be planted in a " $ jmp $; " situation. I
05:01:34PM -0500, Ian Chapman wrote:
>> Hi all,
>>I'm having difficulty understanding this situation.
>> flag = 1;
>> while ( 0 != flag )
>> {
>> code;
>> }
>>generates strange assembly code till I commented out
>> // flag = 1;
Hi,
I have mspdebug --version
MSPDebug version 0.22 - debugging tool for MSP430 MCUs
1. After running a few program loads into the chip (prog main.elf) I
eventually get locked out. In fact lsusb hangs til I remove the
spy-wire. I fixed the problem by replacing the chip on the TI
16 matches
Mail list logo