I've moved from the Keil uVision3 to a linux hosted GNU build using the exact same linker script. Here are the two pertinent targets from the Makefile, one for linking and one for creating the hex file (which I then download from my windows system with Philip's LPC210x_ISP utility). FW.elf : $(SOBJS) $(COBJS) $(LD) -o FW.elf $(SOBJS) $(COBJS) $(LIBPATH) -lc -lgcc -T Target.ld FW.hex : FW.elf arm-elf-objcopy -O ihex FW.elf FW.hex hth, --rich ________________________________ From: Charles Manning [mailto:manningc2@...] Sent: Sat 10/23/2004 9:18 PM To: lpc2000@yahoogroups.com; peterburdine Subject: Re: [lpc2000] Programming GNU hex files On Saturday 23 October 2004 03:42, peterburdine wrote: > I seem to be having problems trying to program my Phycore LPC2994 > module when I use the GNU toolset. I have tried using both JTAG and > the Philips utility, and neither of them will successfully program the > chip. It will instead have the the previous program. If I used the > Keil toolset I do not have this problem. Does anyone have any > suggestions? I am using uVision 3. > > Thanks, > Peter This is most likely something to do with either your start up file or your ldscript. Have a look at the two map files and see how they differ, that should give some clues. -- CHarles Yahoo! Groups Sponsor ADVERTISEMENT click here <http://us.ard.yahoo.com/SIG=129ko57bh/M=295196.4901138.6071305.3001176/D=groups/S=1706554205:HM/EXP=1098677698/A=2128215/R=0/SIG=10se96mf6/*http://companion.yahoo.com> ________________________________ Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/lpc2000/ * To unsubscribe from this group, send an email to: lpc2000-unsubscribe@yahoogroups.com <mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe> * Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service <http://docs.yahoo.com/info/terms/> . [Non-text portions of this message have been removed]
Message
RE: [lpc2000] Programming GNU hex files
2004-10-24 by Richard Rauscher
Attachments
- No local attachments were found for this message.