problems making binairy to burn in flash

[Faas, Hylke]

Hi All,
 
I'm trying to make a new bootloader to burn in flash. before I always
used the tftp to get my applications to run, so I haven't tried burning
new applications.
I have the problem that I can't flash any application that I have
compiled myself.
 
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.
 
I could not find any information about it on the internet I've already
updated the openocd version because I thought openocd was buggy (read
something about it on the internet). Strangely enough I think it has
something to do with the compile proccess. Have I overseen something?
Does any one had something similar and how did he/she fixed it?
 
Detailed operation and error:
[OpenOCD]:
For bug reports, read
http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
10 kHz
jtag_nsrst_delay: 200
jtag_ntrst_delay: 200
Info : JTAG tap: at9r40008.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787,
part: 0xf0f0, ver: 0x1)
Info : JTAG Tap/device matched
Info : JTAG tap: at9r40008.cpu tap/device found: 0x1f0f0f0f (mfg: 0x787,
part: 0xf0f0, ver: 0x1)
Info : JTAG Tap/device matched
Warn : srst pulls trst - can not reset into halted mode. Issuing halt
after reset.
target state: halted
target halted in ARM state due to debug-request, current mode:
Supervisor
cpsr: 0x200000d3 pc: 0x100021dc
6000 kHz
Info : accepting 'telnet' connection from 0
Info : Flash Manufacturer/Device: 0x001f 0x0090
flash 'cfi' found at 0x10000000
erased sectors 0 through 10 on flash bank 0 in 4.718750s
Error: timed out while waiting for target halted
Error: error writing to flash at address 0x10000000 at offset 0x00000000
(-902)
 
 
[Telnet calls]:
Open On-Chip Debugger
> halt
> flash probe 0
Flash Manufacturer/Device: 0x001f 0x0090
flash 'cfi' found at 0x10000000
> flash erase_sector 0 0 10
erased sectors 0 through 10 on flash bank 0 in 4.718750s
> flash write_bank 0 D:/hylke/temp/bootmon/bootmon.bin 0
timed out while waiting for target halted
error writing to flash at address 0x10000000 at offset 0x00000000 (-902)
 
called at file "command.c", line 469
called at file "embedded:startup.tcl", line 89
called at file "embedded:startup.tcl", line 91
called at file "embedded:startup.tcl", line 93

 
Regards,
Hylke Faas

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Ethernut]

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

[Faas, Hylke]

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@...
[mailto:en-nut-discussion-bounces@...] 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

[uprinz]

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@...
> [mailto:en-nut-discussion-bounces@...] 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

[Faas, Hylke]

Hi,

At this moment I some how managed to lose any control of (one) my arm7
proccessors. I can't access it in supervision mode (at least I guess
that is the problem). The consequenses are that I can't probe nor flash
the Arm, it gives the following error:
<ERROR>
Flash Manufacturer/Device: 0x0090 0x0090
Could not probe bank: no QRY
probing failed for flash bank '#0' at 0x10000000
<\ERROR>

I probebly set some fuses orso, does any one here have some experiance
with oocd and Arm7 and knowes how to reset the hole chip or some how
make it accessable again?

Further I ansewerd some of you questions below.

> -----Original Message-----
> From: en-nut-discussion-bounces@...
> [mailto:en-nut-discussion-bounces@...] 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?

Using the telnet code? if you mean using a local host telnet connection
(explained on http://www.ethernut.de/en/hardware/enut3/openocd.html),
then yes. If you mean configuring and initalizing the oocd from telnet,
no (I have no idea how).

> 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.

Well I guess thats not a problem then sinds I use version 0.2.0.

> 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.

unfortunetly that won't work either.
 

> 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.

I haven't found the .scripts files so thats something I couldn't test
correctly.

At this point I seriously doubt if this problem is caused by me handling
the tools incorrect or faulty installation (or reinstalation) of any of
the applications or drivers. So what I want to try is to test an
ehternut and Turtelizer on a clean system at home. If that is working
correct I'll have to have a chat with the system administrators here and
let them make a clean reinstall.


Thanks for the help,
Hylke

> 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@...
> > [mailto:en-nut-discussion-bounces@...] 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
>

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Ethernut]

Faas, Hylke wrote:

> At this moment I some how managed to lose any control of (one) my arm7
> proccessors. I can't access it in supervision mode (at least I guess
> that is the problem). The consequenses are that I can't probe nor flash
> the Arm, it gives the following error:
> <ERROR>
> Flash Manufacturer/Device: 0x0090 0x0090
> Could not probe bank: no QRY
> probing failed for flash bank '#0' at 0x10000000
> <\ERROR>
>
> I probebly set some fuses orso, does any one here have some experiance
> with oocd and Arm7 and knowes how to reset the hole chip or some how
> make it accessable again?

You're using Ethernut 3.0E, right? AFAIK,tThe AT91R40008 on this board
doesn't have any fuses which may disable JTAG access.

Note, that the JTAG interface is unprotected. Removing or attaching the
JTAG cable requires to switch off the power supply.

Harald

PS: If you come to the conclusion, that your board is broken, you may
contact the manufacturer, in this case
http://www.egnite.de/en/ueber-uns/adresse-und-anreise.html


_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[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@...
> [mailto:en-nut-discussion-bounces@...] 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@...
> > [mailto:en-nut-discussion-bounces@...] 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
>

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Faas, Hylke]

Hi,

Correction, still unsolved (I was unknowingly working with the
downloaded binary at home). :(

Harald, did you once make the bootmon binary wich is included in bootmon
(version 1.0.2) zip file. What OS, toolchain, make version, gcc
compiler, etc. did you use? also did you use Openocd or J-Link GDB
Server?
can someone make me a clean bootmon binary (e.g. version 1.0.6, which is
included in the latest NutOs release) and mail it to me, with some
information about OS, make version, etc. etc.?.

I'm out of ideas so any sugestion or support would be helpfull.

Thanks.

Hylke

> -----Original Message-----
> From: en-nut-discussion-bounces@...
> [mailto:en-nut-discussion-bounces@...] On Behalf Of Faas, Hylke
> Sent: Monday, September 14, 2009 09:24
> To: Ethernut User Chat (English)
> Subject: Re: [En-Nut-Discussion] problems making binairy to
> burn in flash(Solved)
>
> 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@...
> > [mailto:en-nut-discussion-bounces@...] 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@...
> > > [mailto:en-nut-discussion-bounces@...] 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
> >
> _______________________________________________
> http://lists.egnite.de/mailman/listinfo/en-nut-discussion
>
>

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion