OpenOCD / Flashing AT91

OP #1171661
Rate this post
• ▲ useful
▼ not useful
Martin Thomas's tutorial on flashing with openOCD uses the
"working_area" directive in the OpenOCD configuration file.
(http://www.siwawi.arubi.uni-kl.de/avr_projects/arm_projects/openocd_intro/index.html)

The address value shown in the sample for the AT91SAM7 is incorrect if
the "working_area" refers to target's RAM.  The address of RAM is at
0x200000 for the SAM7 series, correct?

In any event, I do not see any improvement in the time it takes to flash
the AT91SAM7X with the working_area configured.

(I get about .44K/s flashing an empty flash via a wiggler, or 5.5K/s if
the processor has code to get the clocks up to speed before flashing)

- Joe
#1171662
Rate this post
• ▲ useful
▼ not useful
There's no support for speeding up programming of AT91SAM7 devices with
an on-chip algorithm like there is for external flashes using the 'cfi'
driver. Writing flash at 5.5kb/s using a wiggler aint that bad, so
there's little reason to look into using an on-chip algorithm for these
devices.

You should be able to initialize the PLL using the memory write commands
provided by the OpenOCD (mw[bhw]).

Regards,

Dominic

Reply

Note: the original post is older than 6 months. Please don't ask any new questions in this thread, but start a new one.

Formatting
  • [c]C-Code[/c]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]
  • [[Title]] – link to an article
  • Link to another post: right-click its post ID (#8078628), copy the address, paste it into the text

More about formatting

Post long source code as an attachment, not in the text.

Already registered? Log in

Not shown to anyone. We send you a link; your post appears once you confirm it there.

By submitting you create a free account and accept the terms of use.