On 04/11/2010 21:35, Andreas Fritiofson wrote:
On Wed, Nov 3, 2010 at 10:01 AM, Chris Jonesch...@martin-jones.com
wrote:
I tried the IAR software but don't have a JTAG dongle directly
compatible with it. I tried to get it to talk to OpenOCD via GDB
but attempting to download the code to the
On 23/11/2010 18:21, Chris Jones wrote:
I've now spent some more time looking at this problem and have been
digging around in arm_adi_v5.c to see what's going on.
In the fault condition, even the first few operations in
ahbap_debugport_init() don't seem to work. For example, reading the
2010/10/31 Michel Catudal michelcatu...@gmail.com:
Le 2010-10-29 19:15, Andreas Fritiofson a écrit :
One can also ponder why you need debug access to something molded in
plastic... Wouldn't it be better to debug your application on a more
lab-friendly setup?
A production unit that is to
On Wed, Nov 3, 2010 at 10:01 AM, Chris Jones ch...@martin-jones.com wrote:
I tried the IAR software but don't have a JTAG dongle directly compatible
with it. I tried to get it to talk to OpenOCD via GDB but attempting to
download the code to the STM32 that way just resulted in streams of
Le 2010-11-04 17:10, Andreas Fritiofson a écrit :
2010/10/31 Michel Catudalmichelcatu...@gmail.com:
Le 2010-10-29 19:15, Andreas Fritiofson a écrit :
One can also ponder why you need debug access to something molded in
plastic... Wouldn't it be better to debug your application on a
On 31/10/2010 13:40, Michel Catudal wrote:
Le 2010-10-30 04:20, Chris Jones a écrit :
I'd like to work out whether the debug unit really does break, or
whether there's just a misunderstanding about state between it and
OpenOCD.
Wouldn't pulling the boot pin and send the reset core work?
I
On 30/10/2010 09:20, Chris Jones wrote:
On 30/10/2010 00:15, Andreas Fritiofson wrote:
On Fri, Oct 29, 2010 at 8:58 PM, Chris Jonesch...@martin-jones.com wrote:
But there's a way of breaking it semi-permanently. The application on the
STM32 is one which spends most of its time with the CPU in
Le 2010-10-29 19:15, Andreas Fritiofson a écrit :
On Fri, Oct 29, 2010 at 8:58 PM, Chris Jonesch...@martin-jones.com wrote:
Am I stuck? Or is there a way of finding out how the Cortex-M3 debug unit is
wedged, if that's the case, and tickling it back to life?
Would it reset
Le 2010-10-30 04:20, Chris Jones a écrit :
I'd like to work out whether the debug unit really does break, or
whether there's just a misunderstanding about state between it and OpenOCD.
Wouldn't pulling the boot pin and send the reset core work?
I would suggest to use the IAR limited
On 30/10/2010 00:15, Andreas Fritiofson wrote:
On Fri, Oct 29, 2010 at 8:58 PM, Chris Jones ch...@martin-jones.com wrote:
But there's a way of breaking it semi-permanently. The application on the
STM32 is one which spends most of its time with the CPU in Stop mode, waking
up periodically
Hi all,
I'm using OpenOCD (version 0.4.0, downloaded from SourceForge and built
about half an hour ago) on Debian Lenny (5.0, stable) running under
VMWare Fusion on an x86 Mac Pro. The microcontroller I'm using is an
STM32F103C6T6, and the JTAG dongle is an Amontec JTAGKey. By and large
it
Hi Chris,
I'm not an expert, nor a typical poster on this list, but have you properly
configured the DBGMCU_CR register to allow debugging support while the STM32
is in STOP mode?
Best,
Kyle
On Fri, Oct 29, 2010 at 2:58 PM, Chris Jones ch...@martin-jones.com wrote:
Hi all,
I'm using
On Fri, Oct 29, 2010 at 8:58 PM, Chris Jones ch...@martin-jones.com wrote:
Hi all,
I'm using OpenOCD (version 0.4.0, downloaded from SourceForge and built
about half an hour ago) on Debian Lenny (5.0, stable) running under VMWare
Fusion on an x86 Mac Pro. The microcontroller I'm using is an
13 matches
Mail list logo
