Hi,
Having a bit of a tidy up and found the src to the various ram loaders i
have written over the years - no objections i will commit.
Cheers
Spen
From 5c25c2cbec8d4a7966ccb18b8dadbde5da59b4b9 Mon Sep 17 00:00:00 2001
From: Spencer Oliver ntfr...@users.sourceforge.net
Date: Wed, 27 Oct 2010
On Wed, Oct 27, 2010 at 6:21 PM, Peter Stuge pe...@stuge.se wrote:
Spencer Oliver wrote:
Having a bit of a tidy up and found the src to the various ram loaders
i have written over the years - no objections i will commit.
Acked-by: Peter Stuge pe...@stuge.se
Could they also be magically
Øyvind Harboe wrote:
Having a bit of a tidy up and found the src to the various ram loaders
i have written over the years - no objections i will commit.
Could they also be magically hooked up to OpenOCD?
I think a good start would be to add comments in the
code where these stubs are
On Wed, Oct 27, 2010 at 10:10 PM, Peter Stuge pe...@stuge.se wrote:
Øyvind Harboe wrote:
Having a bit of a tidy up and found the src to the various ram loaders
i have written over the years - no objections i will commit.
Could they also be magically hooked up to OpenOCD?
I think a good
Hi!
Someone has asked me for help with using OpenOCD + STM32F100 (8kB of
RAM). After some time I've come to conclusion that the problem was
caused by incorrect workareasize value, which in stm32.cfg is defined to
be 16kB. With std cfg files flashing the device resulted in:
Error: JTAG-DP
On 10/27/2010 10:29 PM, Øyvind Harboe wrote:
I actually don't think it is an unreasonable expectation. I know I
have not had OpenOCD without the cross toolchain.
However, compiling them could be done in make dist, rather than make.
(Ie. when preparing a tarball, rather than when compiling
