On Fri, Mar 26, 2010 at 4:46 AM, michal smulski wrote:
> Have anyone tried using cp15 command on arm9 recently?
What version are you using of OpenOCD?
Have you tried the mrc/mcr commands?
"help mrc"
--
Meet us in Paris at rts EMBEDDED SYSTEMS 2010 - March 30. and April 1.
http://www.zylin.co
Have anyone tried using cp15 command on arm9 recently? Here is my
attempt:
mww 0x0030 0xee100f10
armv4_5 disassemble 0x0030
>0x0030 0xee100f10 MRC p15, 0x00, r0, c0, c0, 0x00
reg pc 0x0030
step
reg r0
>r0 (/32): 0x41059680
# implementor: 0x41
# architecture: 0x05 (ARM
I'm a bit worried about applying this patch, it does look sensible
to me, but I don't know that cfi.c code very well...
Perhaps if you improved the comments or even made a fn,
you would attract comments/reviews from others who know
the code better?
--
Meet us in Paris at rts EMBEDDED SYSTEMS 2
Hi,
I would like to have some i.MX51 testing hardware (Cortex A8).
Could someone on the list contact me by if you are able to help out?
I've got an i.MX31 that we have put to good use, but that's ARM11
and Cortex A8 is heating up these days and i.MX51 would be nice
in that regard.
There has bee
support
> >> it in OpenOCD.
> >> I have 2 ST-Link sent by vendor of ST, but now, they are Versaloon.
> >>
> >>
> > ST sent me the api, it is based on mass storage device.
> > They are happy for openocd to support it.
> >
> > The current issue is that i
Antonio Borneo wrote:
On Thu, Mar 25, 2010 at 9:31 PM, Laurent Gauch
wrote:
T H E S O L U T I O N ---
The solution is to add the absolute max frequency for a given device when we
create a "jtag newtap" as
jtag newtap $_CHIPNAME cpu .-freqmax_khz 1 -irle
On Thu, Mar 25, 2010 at 9:31 PM, Laurent Gauch
wrote:
> T H E S O L U T I O N ---
>
> The solution is to add the absolute max frequency for a given device when we
> create a "jtag newtap" as
> jtag newtap $_CHIPNAME cpu .-freqmax_khz 1 -irlen 7 -ircapture 0x1
David Brownell wrote:
On Thursday 25 March 2010, Laurent Gauch wrote:
... OK, but we do not resolve the problem by DON'T DO THAT!!
Actually there are a lot of target scripts working with JTAGkey but not
with JTAGkey-2,
Specifically which ones?
Amontec customers feedback this t
I don't know when "poll off" broke, but "poll off" didn't
stop background polling of target. The polling status flag
simply wasn't checked in the handle_target timer callback.
All target polling(including power/reset state) is now stopped
upon "poll off".
Signed-off-by: Øyvind Harboe
---
src/ta
Pushed.
Thanks!
--
Meet us in Paris at rts EMBEDDED SYSTEMS 2010 - March 30. and April 1.
http://www.zylin.com/events_rts.html
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash progra
When using uint32_t in LOG_xxx functions the PRIx32 or PRId32 macros are needed
in the format string instead of x and d to compile with cygwin.
The attached patch corrects this.
>From 6ce7282be99d073f4ef9d71feda770b67eb12080 Mon Sep 17 00:00:00 2001
From: Daniel Bäder
Date: Thu, 25 Mar 2010 11:2
On Thursday 25 March 2010, Laurent Gauch wrote:
>
> ... OK, but we do not resolve the problem by DON'T DO THAT!!
>
> Actually there are a lot of target scripts working with JTAGkey but not
> with JTAGkey-2,
Specifically which ones?
> just because the JTAGkey-2 run by default at his highest
David Brownell wrote:
On Thursday 25 March 2010, Laurent Gauch wrote:
JTAG and SWD share key signals though ... on both adapter and target
sides. Lots of boards have a single JTAG/SWD connector.
Yes, lot of boards, but not all boards. Amontec has customers having
JTAG daisy chai
Hi David,
Brownell wrote:
On Thursday 25 March 2010, Laurent Gauch wrote:
Again, having adapter_khz in the target scripts is really confusing.
SO DON'T DO THAT!!
... OK, but we do not resolve the problem by DON'T DO THAT!!
Actually there are a lot of target scripts working
On Thursday 25 March 2010, Laurent Gauch wrote:
> > JTAG and SWD share key signals though ... on both adapter and target
> > sides. Lots of boards have a single JTAG/SWD connector.
> >
> >
> >
> Yes, lot of boards, but not all boards. Amontec has customers having
> JTAG daisy chains of more th
On Thursday 25 March 2010, Laurent Gauch wrote:
> Again, having adapter_khz in the target scripts is really confusing.
SO DON'T DO THAT!!
As repeated elsewhere ... i's board-specific, so it normally doesn't
belong there. When it's in the board config files, no confusion.
If you persist in
David Brownell wrote:
On Wednesday 24 March 2010, Øyvind Harboe wrote:
I think it makes sense that target scripts now
have to work on SWD *and* JTAG and that they shouldn't really
contain anything jtag or swd specific unless there is a reason to.
Exactly where I'm coming from...
plus,
David Brownell wrote:
On Wednesday 24 March 2010, Laurent Gauch wrote:
Electrically, the JTAG serial port as a SPI serial port will ever have a
faster frequency capability than SWD,
Yet ... the same wire is used for JTAG/TCK -or- SWD/SWCLK. And the
same pin on the target/chip uses tha
On Thu, Mar 25, 2010 at 2:49 PM, Øyvind Harboe wrote:
> Did you test it?
The patch changes 3 parts but, I have executed and tested only 2 of them.
I cannot test the function cfi_spansion_write_words() since don't have
boards with such device.
Anyway, in the original code the same algorithm is re
David Brownell wrote:
On Wednesday 24 March 2010, Laurent Gauch wrote:
We really don't want to need JTAG and SWD versions of every config
script and event handler based on what transport is in use...
We do not need to write specific scipt versions for JTAG or SWD serial
port, but w
>> targetspeed jtag rclk 6000
>> targetspeed swd 1000
>>
>
> Good solution for me ! We should go in this way.
I'm happy with waiting a while before we decide on anything.
0.5 is a looong way off. There seems to be a consensus that
fast and stable SWD is really the next real feature that would mer
David Brownell wrote:
On Wednesday 24 March 2010, Laurent Gauch wrote:
We really don't want to need JTAG and SWD versions of every config
script and event handler based on what transport is in use...
We do not need to write specific scipt versions for JTAG or SWD serial
port, but w
Øyvind Harboe wrote:
I just want to have in the target file the possibility to have something
like :
target_jtag_max_frequency_khz 4
target_swd_max_frequency_khz 12000
target_spi_max_frequency_khz 5
target_i2c_max_frequency_khz 480
I think I see what you mean.
A hypothetical targ
23 matches
Mail list logo
