I am using Windows 2000 and downloaded the Win build. I had installed the package in "c:\program files\mspgcc" so just as a try, I uninstalled and re-installed in "c:\mspgcc" which is the default. Now everything is working! I added a command in the target dialog for "monitor erase all" so now all you have to do is: 1. File->open 2. Click run button 3. Click continue
If you uncheck "breakpoint at main" you don't even need step 3. Insight does not remember that it is a remote tcp target so I need to reselect this each time. The real annoyance is that it opens the .elf file and apparently does not close it so I am unable to re-compile because the .elf is in use. Thus, I must choose File->Close and then recompile and then open it again. I hope this is fixed in a later release. Regards, Tom ----- Original Message ----- From: "Steve Underwood" <[email protected]> To: <[email protected]> Sent: Sunday, June 15, 2003 10:12 AM Subject: Re: [Mspgcc-users] load in gdb and insight > Tom Russell wrote: > > >I am having trouble with the load function in insight (gdb): > > > >I start msp430-gdbproxy and then insight. > >I use File->Open and open test1.elf > >I use Run->Connect to connect to the JTAG. > >I open the Console and issue > >commands: > > monitor erase all > > load test1.elf > > > That looks OK. If the "monitor erase all" command works, you should be > communicating OK with msp430-gdbproxy and the MCU. > > >If I just type "load", I get the error > >Error: Invalid download offset: Files/mspgcc/demo/test1.elf > > > Strange. That doesn't normally happen. I have no idea what "load > test1.elf" will do, as "load" is usually used without parameters. > However, you indicate you have tried without parameters and had trouble, > > >The same thing happens if I use the download function in the Run menu. > > > The download function is just the same as using "load" from a console > window, and you would expect it to do the same thing. > > > My makefile (adopted from CVS archives) is: > >NAME = test1 > > > >CPU = msp430x147 > >ASMOPT = -mmcu=${CPU} > >COPT = -mmcu=${CPU} -O1 -Wall -g > > > >${NAME}.elf: test1.o > > msp430-gcc -mmcu=${CPU} -o $@ $^ > > msp430-objcopy -O ihex $@ ${NAME}.a43 > > msp430-objdump -DS ${NAME}.elf >${NAME}.lst > > > >test1.o: test1.c > > msp430-gcc ${COPT} -c $< > > > Those options look OK, wlthough msp430-objcopy and msp430-objdump are > needed if you are usign gdb. It only requires the elf file. "-O2" is the > more useful optimisation level, but "-O1" shouldn't give any trouble. > > >Did I do something wrong in the compilation? > > > > > You didn't say what platform you are using. Did you build the tools > yourself, or use an installer? > > Regards, > Steve > > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: eBay > Great deals on office technology -- on eBay now! Click here: > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users >
