On 08/25/2011 02:17 PM, Øyvind Harboe wrote:
On Thu, Aug 25, 2011 at 2:16 PM, j. m. norris wrote:
Would it make sense for someone to collect a 'wish list' of
'architectures
and registers'
and then prioritize it?
Ultimately we need patches :-) It doesn't matter if we want something but
nobody
After updating to GDB 7.3 from 7.2, I can no longer connect to openocd
(git version from couple of days ago). The target is a Cortex-M3
STM32F207, and I start openocd using:
openocd -f interface/jlink.cfg -f target/stm32f2x.cfg
The output from GDB looks like this:
arm-none-eabi-gdb
On 12/23/2010 10:09 AM, Spencer Oliver wrote:
I am going to have a change around for the stm32 flash as i am also
working on a flash driver for the stm32lx and stm32f2x.
An eval board with an stm32f207 just landed on my desk, and I was not
aware that it wasn't supported by OpenOCD until a few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/11/2010 09:53 PM, Spencer Oliver wrote:
> On 11/05/2010 18:22, Øyvind Harboe wrote:
>> So should we just apply this patch you think?
Possibly limiting the revision to <= B1. I don't have access to a later
revision chip, and I will most likely n
On 2010-04-30 14:20, freddie_cho...@op.pl wrote:
Użytkownik Tobias Ringström napisał:
The current timeout for STM32 flash block erase and flash mass erase is
10 (ms), which is too tight, and fails around 50% of the time for me.
The data sheet for STM32F107VC specifies a maximum erase time
On 2010-05-02 18:52, Øyvind Harboe wrote:
2010/4/30 Tobias Ringström:
The current timeout for STM32 flash block erase and flash mass erase is
10 (ms), which is too tight, and fails around 50% of the time for me.
The data sheet for STM32F107VC specifies a maximum erase time of 40 ms
(for
The current timeout for STM32 flash block erase and flash mass erase is
10 (ms), which is too tight, and fails around 50% of the time for me.
The data sheet for STM32F107VC specifies a maximum erase time of 40 ms
(for both operations).
I'd also consider it a bug that the code does not detect a tim
On 04/27/2010 03:38 PM, Øyvind Harboe wrote:
Could you attach a patch?
Of course, but as I said, I don't know for certain that this is a
correct fix or not. I also don't know if it is needed only for certain
revisions of the device (<= B1). It would be nice if someone with a C1
or C3 rev
[I accidentally sent this from the wrong email address. I'm resending
from the correct (subscribed) address. My apologies if both arrive.]
I'm having problems with "reset halt" and "reset init" with the
EK-LM3S9B92, both with 0.4.0 and the latest git. I'm starting openocd using
openocd
