> -----Original Message----- > From: [email protected] [mailto:mspgcc-users- > [email protected]] On Behalf Of Roland Laurès > Sent: 16. august 2007 16:27 > To: GCC for MSP430 - http://mspgcc.sf.net > Subject: Re: [Mspgcc-users] Problem with MSP-FET430PIF > > Anders Hørtvedt a écrit : > > Did you try chmod 777 /dev/parport0? > > > > I had similar problems, and I seem to remember setting 777 solved it. > Of > > course being part of the correc t group is a better way, but you > could try > > it just to test? > > > > Anders > > > > > > > > > Ok, i did it and it seems to work a little better... I mean that now i > have this : > " > $ msp430-gdbproxy --debug msp430 > > Remote proxy for GDB, v0.7.1, Copyright (C) 1999 Quality Quorum Inc. > MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood > > GDBproxy comes with ABSOLUTELY NO WARRANTY; for details > use `--warranty' option. This is Open Source software. You are > welcome to redistribute it under certain conditions. Use the > '--copying' option for details. > > debug: msp430: msp430_open() > error: msp430: Could not find device (or device not supported) (4) > "
Yes, now it accesses the /dev/parport0, I think. > Sounds like I have a device that doesn't work with the gdbproxy i > have... All the references i have are : > " > MSP430 Flash Emulation Tool > Interface board MSP-FETP430IF 1.4 > " > This is from Texas Instruments. Should I get an other one ? If yes > which > one will work both with gdbproxy and the MSP430F22x2 (and if possible > also with the MSP430FG4618 from the developpement kit). Well, I am no expert. I cannot really say. But the one I use, is the parallel port version from Olimex. http://www.olimex.com/dev/msp-jtag.html On the other hand, I had similar experiences with gdbproxy on my Olimex tool, but I got it to work after some iterations. Actually, I ended up building it all from source, because I didn't find the correct libraries in binary form. Not too hard, the description is fairly good. I'm sorry, but I cannot describe my actions accurately, it was late in the night, and I tried a lot of things :-) What you will experience when you get it working, is that gdb download thru msp430-gdbproxy slow compared to the msp430-jtag python program. Of course you need gdb to be able to debug, but for everyday use, a quick download thru the Python program is much faster. I am lucky having a display on my msp board, so I use the display for debugging purposes, actually I developed my complete application without using gdb. I started out using the IAR compiler / debugger, and ported it to gcc when I had the core functions running, and display system working. Now I can't switch back, it has become too big for IAR's free version. So my tip of the day is: try to download a small test program (flash a LED or similar) using the Python program. If that works, you know your hardware is OK. Anders
