Hi Magnus,
Magnus Lundin wrote:
That looks very interesting.
Here is a new patch against head that should give very much information.
It is tested on a STM32 CortexM3.
Looking at the code you can se how I think we must read the ROMTABLE
information structure.
The command syntax is now
On Sun, 2009-04-26 at 00:19 +, Martin Panter wrote:
[snip]
From your patch:
+/// @brief calculates number of bytes required to hold @a n TAP scan bits
+#define TAP_SCAN_BYTES(n)(((n) / 8) + !!((n) % 8))
Are you aware that in src/helper/binarybuffer.h there's a similar
macro?
On Sun, 2009-04-26 at 11:43 -0700, Zach Welch wrote:
On Sun, 2009-04-26 at 16:16 +0200, Dirk Behme wrote:
[snip]
3. Running resulting openocd binary for OMAP3 tests immediately stops
with
Runtime error, file src/target/board/ti_beagleboard.cfg, line 10:
Line 10 in this file is
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Hi all,
The attached patch wraps two definitions of _GNU_SOURCE in the code,
which could cause problems with -D_GNU_SOURCE -Wredundant-decls.
Cheers,
Zach
Index: src/helper/jim.c
===
--- src/helper/jim.c (revision 1531)
+++
Hi
There are some problems with dap info, but it seems the results are
useful anyway.
Her comes my interpretation:
dap info 0
ap debugbase 0x
ap identification register 0x14770001
No ROM table present
This is a MEM-AP port AHB bus with no ROM table. This could be the
Hi all,
This patch adds two additional warnings with --enable-extra-warnings:
-Wcast-align (to prevent mis-aligned memory accesses through bad casts)
and -Wbad-function-cast (to prevent casts to 'anything *'). I believe
these will assist developers with portability when writing new code.
Please
On Mon, 2009-04-27 at 02:33 +0200, Magnus Lundin wrote:
We should be a bit more careful. I am all in favour of cleaning up the
bit rot !!! But how to fix the warnings needs to be not carefully
considered.
My example:
cortex_me.c : cortex_m3_register_command. It is declared both at the
What's wrong with this code?
long long then=timeval_ms();
while ((timeval_ms()-then)duration)
This appears many places in the code.
comparision will work unless the difference is
greater than 31/63 bits in signed mode...
The changes to target/* are a mix between
11 matches
Mail list logo
