Hi David,
On Thu, 20 Jun 2002 11:30:45 +0200 "David Brown" <[email protected]> wrote: > Hi, > > We do embedded systems programming, using the msp430 among other > microcontrollers. At the moment, I have used assembly on the msp430, using > IAR's assembler and C-Spy debugger, with the jtag interface that comes with > the kickstart kit (all under w2k). We want to use C for the msp430, but do > not want to use IAR (it's way too pricy, unpleasant to use, and has rotten > support). I use gcc for m68k/Coldfire development, so it makes sense to see > how gcc for the msp430 is getting on (even if it is still labelled as > "alpha" - experiance suggests that "alpha" status of open source projects > often corresponds to "release" status of commercial projects). > Well, windoze build is a bit outdated, cause recently we have fixed some bugs which might be vital. So, try to build it yourself or ask the community to build a recent snap under win. > I downloaded the windows build, which works nicely (I tried, but failed, to > build it from scratch under cygwin - when I have the chance, I'll try > again). I wrote a short test program, and the generated code looks good. > But the real problem is debugging. > > As far as I can see, there are a number of ways to get good debugging using > the jtag interface: > > 1) A gdb stud using the msp430's serial port could work, but with limited > functionality, and it uses a critical resource on the micro, so it's not a > good general solution. > Will not. GDB is just only _prepared_ for the jtag integration. BUt you can run built-in gdb simulator. > 2) Generate iar-type debugging information, probably as the target of an > msp430-objcopy. I don't know if enough information is available on IAR's > format to make this possible. Then you'll have to debug this in assembler mode I think. > > 3) Generate iar assembler files from gcc instead of gas-compatible assembly > files, with the original C code as comments, and use iar's assembler and > linker. This will at least give far better assembly-level debugging using > C-Spy, with at least basic variable watch capability. gcc does not generate IARs code. It does not include C lines as comments. > > 4) Make a gdb back-end that uses the kickstart jtag adaptor. This is, of > course, the best solution in the long run, since it is cross-platform and > gives a complete indepentant developement tool set. This is the route taken > for m68k debugging - there is a gdb back-end that for the m68k using bdm > (which is roughly like jtag) adaptors. I combine it with gvd to give a nice > gui under windows and *nix. > TIs jtag uses propretary interface which is not published yet. But gdb is prepared for it. > > Has anyone worked towards any of these solutions? All I have found out so > far is that there is a work in progress on jtag debugging (presumably that > means gdb), but I'd love to know how things are going - we are going to have > to see whether we can use msp430 gcc for development, or whether we should > wait for other compilers (like Imagecraft - we have been very happy with > their avr compiler) which are easier for debugging. We do... Thing are going well - We do use gcc for development :) > > I have had some experience with digging through the gdb drivers for the m68k > bdm back-end, so I am happy to help debugging (when I have time, at least), > but I am not going to be able to put it together myself from scratch. The only thing I wait is jtag interface, cause the rest works. cheers, ~d > > regards, > > David Brown > Norway > > > > > ------------------------------------------------------- > Bringing you mounds of caffeinated joy > >>> http://thinkgeek.com/sf <<< > > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > /******************************************************************** ("`-''-/").___..--''"`-._ (\ Dimmy the Wild UA1ACZ `6_ 6 ) `-. ( ).`-.__.`) Enterprise Information Sys (_Y_.)' ._ ) `._ `. ``-..-' Nevsky prospekt, 20 / 44 _..`--'_..-_/ /--'_.' ,' Saint Petersburg, Russia (il),-'' (li),' ((!.-' +7 (812) 3468202, 5585314 ********************************************************************/
