I cant upload an image into internal SRAM (AT91SAM9).
it can really write only 20 bytes.
load_image into internal flash area works fine.
But why it doesn't fail if it writes the other regions?
It crashes only if it writes into internal SRAM.
Could it be that the load_image command uses
On Fri, Oct 7, 2011 at 7:34 AM, Dmitry E. Oboukhov un...@debian.org wrote:
I cant upload an image into internal SRAM (AT91SAM9).
it can really write only 20 bytes.
load_image into internal flash area works fine.
But why it doesn't fail if it writes the other regions?
It crashes only
Hi,
On Sat, Sep 24, 2011 at 2:00 PM, Dmitry E. Oboukhov un...@debian.orgwrote:
Dmitry E. Oboukhov wrote:
I cant upload an image into internal SRAM (AT91SAM9).
it can really write only 20 bytes.
load_image into internal flash area works fine.
But why it doesn't fail if it writes the
I cant upload an image into internal SRAM (AT91SAM9).
it can really write only 20 bytes.
load_image into internal flash area works fine.
But why it doesn't fail if it writes the other regions?
It crashes only if it writes into internal SRAM.
Could it be that the load_image command uses
Hi, there!
I cant upload an image into internal SRAM (AT91SAM9).
When I try to process a command:
load_image filename.bin 0x30 bin
it crashes with the text:
Error: DCC write failed, expected end address 0x0030060c got
0x300014.
File has length: 1548 bytes (0x60C)
it can really
Hi Dmitry,
Dmitry E. Oboukhov wrote:
I cant upload an image into internal SRAM (AT91SAM9).
it can really write only 20 bytes.
load_image into internal flash area works fine.
Are you using latest openocd git code, if not which version?
Perhaps this is a problem of clocking, OpenOCD may need
Dmitry E. Oboukhov wrote:
I cant upload an image into internal SRAM (AT91SAM9).
it can really write only 20 bytes.
load_image into internal flash area works fine.
Are you using latest openocd git code, if not which version?
I'm using the latest openocd release (0.5.0/Debian)
Perhaps this
