Patch appended.
>From e1fa97a81eba9901b3fa3af9169705d745406661 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Wed, 21 Sep 2011 19:18:26 +0200
Subject: add target events, run algorithm and default r/w buffer api
Target events are added to get better gdb support. The run
algorithm functionality ar
Hello,
i have checked the sources to find a way that works for this issue but this
would make a big api
change. Currently there is no way to tell the target write memory function the
kind of memory that
needs to be written. In my case the dsp563xx p,x,y memory.
Would it make sense to change th
Does anyone know if users of OpenOCD can access the ETM Regisiters?
Peter Tympanick
Product Manager
Ultimate Solutions, Inc.
==
Your Single Source for Professional Development Tools & Embedded Solutions
Ph: 978-455-3383 x202
Fx: 978-926-
It is looking much better. Some more comments:
1. I'd remove comments such as the below though.
+ // Create the bank structure
+ stm32lx_info = malloc(sizeof(struct stm32lx_flash_bank));
+
+ // Check allocation
+ if (stm32lx_info == NULL)
2. Missing error check:
target
New patch attached.
Cheers,
Clément
On 09/19/2011 06:00 PM, Øyvind Harboe wrote:
Some more nit-picking:
1. Switch more LOG_INFO() to LOG_DEBUG(). LOG_INFO() is intended for
'users'
+ LOG_INFO("allocating working area for algo (%u bytes)", reg32);
2. Purge unused prototypes and reorder
