I've worked a bit more on testing lpc2148 and except for that *one*
time I haven't seen the error you saw.
Perhaps this is easier to reproduce on an ft2232 adapter?
Below are some commands I used to run a 1000 iterations of this test...
# tried messing about with options...
arm7_9 fast_memory_ac
Could this be an intermittant problem?
I was able to reproduce this problem *once* using 1770 and
the script below on a parport interface with an LPC2148 target
and the command below:
reset init
for {set i 0} {$i < 100} {set i [expr $i+1]} {puts $i ; dump_image
c:\\temp\\test.bin 0x4000 0x80
Hello list,
here is a new test which I had make with r1606 / r1770,
done with a FT2232 device. The result look like:
Windows-ft2232-1606
Open On-Chip Debugger
> version
Open On-Chip Debugger 0.2.0-in-development (2009-05-13-21:55) svn:1606
> load_image testimg.bin 0x8100
est it again with the 1606 and 1770.
Regards,
Michael
-Ursprüngliche Nachricht-
Von: oyvindhar...@gmail.com [mailto:oyvindhar...@gmail.com]im Auftrag
von Øyvind Harboe
Gesendet: Mittwoch, 13. Mai 2009 21:32
An: Michael Fischer
Cc: Openocd-Dev
Betreff: Re: [Openocd-development] r1770, load_ima
Referring to our offlist discussion: 1606 has the same problem
per your testing.
What I find curious about the lpc2294.cfg and your posting above
is that working memory is at 0x4000.
Does the lpc2294 have two ram regions?
Could it be that the config script is busted and that working memory
Hello list,
please can some one try if the load_image is working?
I want to download data into an external RAM of the LPC2294
CPU. Interface is a FT2232 device, command looks like:
load_image test.bin 0x8100
The telnet prompt come back, but I could not
found any data at 0x8100.
The ext
