[En-Nut-Discussion] problems making binairy to burn in flash (Solved)

[Faas, Hylke]

Hi,

A little update about the flashing problem I had.

After only 10 minutes (installing the necessary software) I was able to
compile and burn the bootmon binary at home. Here at work it is, with no
doubt, a problem caused by the toolchain and/or drivers installation. It
will be reinstalled later this day.

Thanks for all your support

Hylke

> -----Original Message-----
> From: en-nut-discussion-bounces at egnite.de 
> [mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of Ulrich Prinz
> Sent: Tuesday, September 08, 2009 20:44
> To: Ethernut User Chat (English)
> Subject: Re: [En-Nut-Discussion] problems making binairy to 
> burn in flash
> 
> Hi!
> 
> Did you try to flash by starting oocd and using the telnet code?
> Another thing is, that I found some older versions of oocd 
> that use some not so correct register setups for the SAM7X-EK 
> platform. They setup PLL for 16 or 12MHz chrystals but on the 
> EK a 14.xxMHz is mounted.
> 
> I recommend to use oocd version 0.1.0 or 0.2.0. Both work 
> fine with my integration of the make burn in the trunk of 
> nutos. Select arm-oocd instead of arm-jom.
> 
> The scripts have a small problem I could'nt solve. I didn't 
> manage to find out the CPU the binary is compiled for. So the 
> scripts under tools/scripts/flash-entry.script and 
> flash-exit.script are fixed to
> SAM7X256 so you might have to exchange that.
> 
> I tested the scripts with SAM7X-EK and the SAM7S based EIR 
> and they are working quite good with oocd 0.1.0 and nearly 
> perfect with oocd 0.2.0 and the upenocd-usb dongle.
> If you have another dongle, you need to adjust Makeburn.oocd
> 
> For testing it might be easier to put the commands by hand 
> via telnet instead of modify script, run make burn, fail, and 
> again. So call openocd -f interface/yourif.cfg -f 
> target/sam7x256.cfg -c init and telnet to localhost:4444 Then 
> try giving the commands from flash-entry, that flashing part 
> from Makeburn.oocd and flash-exit.script by hand.
> 
> Hope it helps.
> 
> Faas, Hylke schrieb:
> > Hi Harald,
> > 
> > I have indeed seen the Openocd page on ethernut.de and have allmost 
> > all the information based on the instructions given there.
> > I have also tried to use jtagomat, only jtagomat gives an 
> error that 
> > it can't find the turtelizer so I steped back to openocd.
> > 
> > I have seen that bootmon is using its own makefile en 
> linker script, 
> > that is excactly why I don't understand what is going wrong.
> > 
> > The size of my own binary is only 6 bytes bigger than the original 
> > provided with the source. Thats not disturbing but strangely not 
> > working.
> > 
> > If you have any idea please tell me.
> > 
> > Regards,
> > Hylke
> > 
> > 
> > System information:
> > Windows XP Pro SP2
> > openOCD 0.2.0 (with libUsb driver 0.1.8.0 both downloaded
> > at:http://www.freddiechopin.info/)
> > jatagomat 1.2.7 (although not used)
> > Nut/OS 4.8.3
> > 
> > Build of yagarto use the following versions:
> > binutils: 2.19.1
> > gcc:      4.3.3
> > newlib:   1.17.0
> > gdb:      6.8.50-20080308-cvs
> > 
> > 
> > 
> > 
> > -----Original Message-----
> > From: en-nut-discussion-bounces at egnite.de
> > [mailto:en-nut-discussion-bounces at egnite.de] On Behalf Of 
> Harald Kipp
> > Sent: Monday, September 07, 2009 17:31
> > To: Ethernut User Chat (English)
> > Subject: Re: [En-Nut-Discussion] problems making binairy to burn in 
> > flash
> > 
> > Faas, Hylke wrote:
> > 
> >> For example; If I try to compile and burn the bootmon 
> 1.0.6 version 
> >> (downloaded from ethernut.de) I get a time out error form openocd, 
> >> but
> > 
> >> when I burn the bootmon (version 1.0.2) binairy that is already 
> >> compiled It just work.
> > 
> > You may already know
> > http://www.ethernut.de/en/hardware/enut3/openocd.html
> > 
> > I can see from your output, that you are using the correct sequence.
> > 
> > If the original bootmon binary works, then the problem may 
> be related 
> > to your linker script. Note, that bootmon is compiled and linked in 
> > its own subdirectory, using its own Makefiles and linker script.
> > 
> > Does the size of your binary look acceptable?
> > 
> > Harald
> > 
> > _______________________________________________
> > http://lists.egnite.de/mailman/listinfo/en-nut-discussion
> > _______________________________________________
> > http://lists.egnite.de/mailman/listinfo/en-nut-discussion
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>