hello,
linux-2.6$ arm-linux-objdump -D .vmlinux | egrep -2 c0023a70:
c0023a68: e595601cldr r6, [r5, #28]
c0023a6c: e356cmp r6, #0 ; 0x0
c0023a70: 116f5f16clzne r5, r6
c0023a74: 1045subne r0, r0, r5
c0023a78: 11a0100
Committed.
Thanks!
--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_en.html
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.b
Committed.
Thanks!
On Tue, Mar 24, 2009 at 1:01 AM, Uwe Hermann wrote:
> It's astounding how many ways you can find to misspell ixp42x.
Goes to show how little engineers care about product naming :-)
It's great to have someone who actually fixes these things. It
adds a lot of shine to OpenOCD!
On Mar 23, 2009, at 7:57 PM, Duane Ellis wrote:
So - I guess the next step with OMAP - aka: CortexA8 is to figure out
how the DAP interface works.
The existing dap code - well - It's a bit confusing to me, and has
such
wonderful documentation.
The dap code provides a layer to handle reque
Add new board configs: Olimex LPC-H2148, Keil MCB2140.
Both boards use an LPC2148, no external flash or RAM.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.org | http://www.unmaintained-free-software.org
Index: src/target/board/olimex_lpc_h2148.cfg
So - I guess the next step with OMAP - aka: CortexA8 is to figure out
how the DAP interface works.
The existing dap code - well - It's a bit confusing to me, and has such
wonderful documentation.
===
I'm thinking that adding a "dap" command will be helpful - for both
Cortex M3 - and A8. A
It's astounding how many ways you can find to misspell ixp42x.
Fix various ixp42x typos in config files. Also, rename an incorrectly
named 'pxi42x.cfg' file.
Untested, but should work. I doubt the current svn files work.
Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http:/
Spencer Oliver wrote:
>> But I still think it's slow. When I write the same image to a
>> STM Primer using RFlasher 7, it only takes ~3 seconds.
>>
>> I also tried to use OpenOCD's RLink interface: 7.241484 kb/s.
>> Much slower than the native RFlasher application.
> You could try the following
Is that a perfectly good idea to force the flash vectors? What is the
exact purpose of that step? Personally I see no purpose of that step and
it makes the config file more complex.
___
Openocd-development mailing list
Openocd-development@lists.berlios.
On Mar 23, 2009, at 2:15 PM, Johann F. wrote:
Hi List,
i need openocd + sxvf support for my project, but the openocd's sxvf
didn't worked, i have done some changes. It works now for me, tested
with parport and own jtag gpio bitbang adapter, here is the patch
openocd's source code have really
Hi List,
i need openocd + sxvf support for my project, but the openocd's sxvf
didn't worked, i have done some changes. It works now for me, tested
with parport and own jtag gpio bitbang adapter, here is the patch
openocd's source code have really long lines :)
mfg
Johann
xsvf_patch
Descriptio
Committed.
Thanks!
--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_en.html
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists
Here's a patch for a real _CPUTAPID entry for the LPC2148. I don't know
if they're the same for all LPC214x, this number is from an Olimex
LPC-H2148. The chip on that board is LPC2148FBD64.
Also fix a few cosmetic issues and comments in the file and add
more docs and pointers to the datasheet.
U
> Quick update: the attached patch fixes all STR9-comstick
> issues so far for me. On my STR9-comstick the _BSTAPID is
> 0x2457f041 (contrary to
> 0x1457f041 which is indeed correct as per manual). Maybe
> there are multiple versions of the STR9-comstick? My device
> says STR912CS-A2 on the ba
>
> I'll hold off committing the patch until I get the word that
> the patch is ready.
>
>
The patch should be ok because win32 does not use the ft2232_vid_pid field -
only linux requires it.
Cheers
Spen
___
Openocd-development mailing list
Openocd
> Ok, now I get:
>
>wrote 85144 byte from file main.elf in 9.609000s (8.653183 kb/s)
>
> But I still think it's slow. When I write the same image to a
> STM Primer using RFlasher 7, it only takes ~3 seconds.
>
> I also tried to use OpenOCD's RLink interface: 7.241484 kb/s.
> Much slower t
I'll hold off committing the patch until I get the word that the
patch is ready.
--
Øyvind Harboe
PayBack incident management system
Reduce costs and increase quality, free Starter Edition
http://www.payback.no/index_en.html
___
Openocd-development ma
17 matches
Mail list logo
