SparkFun Forums

[Will_i_am]

I am using the MSPGCC toolchain on Windows 2000. I have succesfully built and downloaded the easyweb example to the EasyWEB3 board. My problem is when I recompile for MSP430F1611 prototype board or header board I can't download (see transcript below) I suspect the boards since my tools work with the EasyWEB3 board. Also the MSP430F1611 boards send a disturbing message to the console port "Short with GND" on power-up.

Has anyone sucessfully used the MSP430F1611 proto or header board?
Any ideas?


D:\mspgcc\examples\tcpip>make clean
rm -f easyweb easyweb.o tcpip.o cs8900.o

D:\mspgcc\examples\tcpip>make
msp430-gcc -c -g -O2 -mmcu=msp430x149 -c -o easyweb.o easyweb.c
msp430-gcc -c -g -O2 -mmcu=msp430x149 -c -o tcpip.o tcpip.c
msp430-gcc -c -g -O2 -mmcu=msp430x149 -c -o cs8900.o cs8900.c
msp430-gcc -mmcu=msp430x149 -oeasyweb easyweb.o tcpip.o cs8900.o

D:\mspgcc\examples\tcpip>msp430-jtag -e easyweb.elf
MSP430 parallel JTAG programmer Version: 2.1
Mass Erase...
Program...
9714 bytes programmed.
Reset and release device...

D:\mspgcc\examples\tcpip>


If I attempt to download to the MSP430F1611 prototype board I get the following result;

D:\mspgcc\examples\tcpip_msp4301611>make clean
rm -f easyweb easyweb.o tcpip.o cs8900.o

D:\mspgcc\examples\tcpip_msp4301611>make
msp430-gcc -c -g -O2 -mmcu=msp430x1611 -c -o easyweb.o easyweb.c
msp430-gcc -c -g -O2 -mmcu=msp430x1611 -c -o tcpip.o tcpip.c
msp430-gcc -c -g -O2 -mmcu=msp430x1611 -c -o cs8900.o cs8900.c
msp430-gcc -mmcu=msp430x1611 -oeasyweb easyweb.o tcpip.o cs8900.o

D:\mspgcc\examples\tcpip_msp4301611>msp430-jtag -e easyweb.elf
MSP430 parallel JTAG programmer Version: 2.1
Cleaning up after error...
Reset and release device...

An error occoured:
Can't open interface

D:\mspgcc\examples\tcpip_msp4301611>

Clearly I dont' expect this image to run properly since the board doesn't have a CS8900 chip but it should download properly. I suspect some problem with the MSP430F1611 prototype board. I have tried this on two differend boards. Curiously when I power the MSP430F1611 prototype board the serial port emits the following;

WWW.OLIMEX.COM/DEV

Short with GND

I don't know what image comes preloaded on the MSP430F1611 prototype board but if it is diagnostic, it seems to be reporting a problem.

[OLIMEX]

if you suspect the board why don't you make simple blink led program but build TCP/IP code?

of course test will fail if the board is not connected to our test jig

Tsvetan

[Will_i_am]

So I took your advise and built a blinking led program but got the following result on two different MSP430F1611 prototype boards and a MSP430F1611 header board.

MSP430 parallel JTAG programmer Version: 2.1
Mass Erase...
Cleaning up after error...
Reset and release device...

An error occoured:
Could not erase the Flash

I have been happy with my EasyWEB3 board but dissapointed with the MSP4301611 boards. What recource do I have?

[OLIMEX]

we don't use MSP430GCC and I can't give you any advice on this, but what you can easy check is to download the MSP430 Kickstart from IAR and compile small LED blink code
you will find at least that our board is working and if the problem is in MSP430GCC this way
MSP430F1611 are newer devices and MSP430GCC may not handle them correctly

Tsvetan

[Will_i_am]

I downloaded IAR Kickstart and was able to connect and download to both MSP4301611 proto and header board with the JTAG-TINY. I reprogrammed the flash with the blinking led program and it worked fine. I then switched to my parallel JTAG with MSPGCC and was able to connect and reprogram. My conclusion is the diagnostic program OLIMEX uses as a functional test of the boards and which is still programmed in the flash when they ship them, is incompatible with the parallel JTAG and MSPGCC. I don't know exactly what the nature of the incompatibility is but my previous posts show this clearly. Does it make sense for OLIMEX to do a mass erase of the proto and header boards before they ship them?

Thanks for your replies.

[OLIMEX]

Hi,
you definitely do something wrong, or MSP430GCC have bug, but according to all MSP430 specifications the code in MSP430 memory can't influence JTAG debugger in any way

Tsvetan

[englere]

>msp430-jtag -e easyweb.elf

Is there a different msp430-jtag command that you need to use to erase flash before downloading your program?

[OLIMEX]

we never used MSP430GCC and I can't tell you what is the right command