I respectfully disagree. MSPGCC is one of the better documented efforts in 
embedded/gnu/open source world. Have you read and followed 
http://mspgcc.sourceforge.net/manual/  ??? It may be a bit outdated but should 
get you started right away. BTW, you do not have to use msp-jtag. GDB/insight 
can program the part directly.
 
Sergei
 
P.S. Insight WILL give you problems. Single stepping, stepping out does not 
always (usually? ;-) work. Use a breakpoint if in doubt. Eclipse suppose to be 
a better front end but it did not work for me. That is I can compile the 
project but the debugger is failing saying something about not been able to get 
info threads. I've seen posts from other people with the same problem. Anybody?

-----Original Message-----
From: mspgcc-users-ad...@lists.sourceforge.net 
[mailto:mspgcc-users-ad...@lists.sourceforge.net] On Behalf Of Garret Crisler
Sent: Thursday, November 18, 2004 8:39 AM
To: mspgcc-users@lists.sourceforge.net
Subject: Re: [Mspgcc-users] msp430-gcc + Eclipse support under Linux?


Can you tell me what this file is??
 
 f:
    cd f:\programme\mspgcc\bin
    msp430-jtag -e f:\programme\eclipse\workspace\...\....elf
    msp430-gdbproxy --port=2000 msp430

 
Anymore information that you could give us would be greatly appreciated as I 
also have now spend about 2 days trying to get this system up and running.
 
I seem to be having trouble with the makefile, where does it come from?
 
I believe this complier works and has great potential, however the supporting 
literature is worse than terrible.
 
Garret Crisler
 

----- Original Message ----- 
From: Dieter Teuchert <mailto:die...@cadt.de>  
To: mspgcc-users@lists.sourceforge.net 
Sent: Thursday, November 18, 2004 3:57 AM
Subject: [Mspgcc-users] msp430-gcc + Eclipse support under Linux?

Hi,
i have been successfully debugging with Eclipse 3.0 and mspgcc unter W2K. There 
was one major problem getting it to work:

I found a web site with a description on how to do it. Besides a lack of 
explanation of the intended workings, that description was old and invalid. It 
seems like, there has been an important change in Eclipse in that recent 
versions can make msp430-gdb connect to msp430-gdbproxy automatically. With old 
versions you had to include statements in the gdb.ini file to setup the 
connection. Now when you use the new Eclipse with the old ini file, you are 
really trying to connect to msp430-gdbproxy TWICE and an error results. It 
cannot work. So my ini file looks like this:

    set remoteaddresssize 16
    set remotetimeout 999999
    set download-write-size 512
    set remote memory-write-packet-size 512
    set remote memory-write-packet-size fixed
    set remote memory-read-packet-size 512
    set remote memory-read-packet-size fixed
    mon reset

The ini file sits in the Eclipse workspace in the same directory as the elf 
file. There is no "target remote localhost:2000" command and no "load ....elf" 
command.

Loading the elf file to the debugger and to the debugging gui is automatic in 
Eclipse, if you select the right binary parser. The download (jtag programming) 
is included in a batch file that also starts up gdbproxy. The default port 
number is as good as 2000, except you have to setup eclipse to tell msp430-gdb 
to use the correct port.

    f:
    cd f:\programme\mspgcc\bin
    msp430-jtag -e f:\programme\eclipse\workspace\...\....elf
    msp430-gdbproxy --port=2000 msp430

f:\programme\eclipse is the path where i installed Eclipse. f:\programme\mspgcc 
is the path where i installed mspgcc.

Solving the problems took some time and is impossible without studying a little 
bit the gdb manual. Eclipse includes a console window where you can watch some 
of the data exchanged with the msp430-gdb. You can also enter commands by hand, 
e.g. to reset everything.

So the intended connection scheme looks like this:

Eclipse <-> msp430-gdb <-> Socket <-> msp430-gdbproxy <-> Parallel port <-> 
JTAG cable <-> MSP430 (DUT)
    
msp430-jtag AND msp430-gdb AND Eclipse need to read the elf file

Eclipse is something rather impressive. Debugging failed, though, when i had 
multiline embedded assembler sequences in my MSP430 source.

Regards
Dieter Teuchert



-- 

Dipl.-Phys. Dieter Teuchert
Software und Systeme
        
Postanschrift:



Telefon:
Telefax:
EMail Firma:
EMail persönlich:
Internet:
        Rommelstr. 6
D-76571 Gaggenau
Germany

+49 7225 989253
+49 7225 989254
i...@cadt.de
die...@cadt.de
 <http://www.cadt.de> http://www.cadt.de
        

Reply via email to