Dne Pá 16. dubna 2010 09:45:09 Kaius Häggblom napsal(a):
> The JTAGkey-tiny dongle and board work OK, I have now successfully used
> the ColibriLoader software to download images to the board.
>
> ~kaius
Hey,
firstly, please stop top-posting (aka post below the email you are replying to
or into
The JTAGkey-tiny dongle and board work OK, I have now successfully used
the ColibriLoader software to download images to the board.
~kaius
Kaius Häggblom wrote:
The attached trace was produced by starting program:
./src/openocd -s tcl -f board/colibri_pxa320.cfg -f nterface/jtagkey.cfg
-d 3
The attached trace was produced by starting program:
./src/openocd -s tcl -f board/colibri_pxa320.cfg -f nterface/jtagkey.cfg
-d 3 -l openocd.lo
... and issuing following commands through telnet client:
> reg
> reset halt
> reg cpsr 0xd3
> reset halt
Exactly as in original post with this is
>
>Was this issue ever solved?
>
I'm not seeing this on the pxa270. I've been using OpenOCD on the 270 for
several months now, staying current with code from git, and don't recall ever
seeing it. I'm using a parallel port wiggler, if that could be relevant.
Mike
_
I would strongly encourage someone who's familiar with these patches
to repost them to this list so we can work on getting the changes merged.
Should be in that projects and OpenOCD's interest...
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy
On Wed, Apr 14, 2010 at 4:01 PM, Kaius Häggblom wrote:
> Hello.
>
> I'm having this same problem with Colibri PXA320, Amontec jtagkey-tiny and
> latest openocd pulled down from git (patched with openpxa PXA320 patches).
>
Hmm... why aren't these patches posted and discussed here?
Seems like some
Hello.
I'm having this same problem with Colibri PXA320, Amontec jtagkey-tiny
and latest openocd pulled down from git (patched with openpxa PXA320
patches).
Was this issue ever solved?
~kaius
___
Openocd-development mailing list
Openocd-development
On Friday 11 September 2009, Wookey wrote:
> +++ Sergey Lapin [2009-09-08 22:50 +0400]:
> > Hi, all!
> >
> > When working with PXA270 I see the following messages on reset.
> >
> > JTAG tap: pxa270.cpu tap/device found: 0x49265013 (mfg: 0x009, part:
> > 0x9265, ver: 0x4)
> > value captured during
On Sunday 11 October 2009, Øyvind Harboe wrote:
> >> I've got some more complicated patches to come so pointers to how to
> >> make patches that make your life easy are welcome.
> >
> > Start with "git diff"...
> >
> > It'd be nice if we could get to the point where patches sent
> > to the mailing
On Sat, Oct 10, 2009 at 10:15 PM, David Brownell wrote:
> On Saturday 10 October 2009, Wookey wrote:
>> +++ Øyvind Harboe [2009-10-10 09:10 +0200]:
>> > I've committed your changes + tried to clean up
>> > the CPUTAPID stuff a little bit. Not pretty, but I'll post
>> > something separate about tha
On Saturday 10 October 2009, Wookey wrote:
> +++ Øyvind Harboe [2009-10-10 09:10 +0200]:
> > I've committed your changes + tried to clean up
> > the CPUTAPID stuff a little bit. Not pretty, but I'll post
> > something separate about that.
> >
> > Did you look into how to create patches for git yet
+++ Øyvind Harboe [2009-10-10 09:10 +0200]:
> I've committed your changes + tried to clean up
> the CPUTAPID stuff a little bit. Not pretty, but I'll post
> something separate about that.
>
> Did you look into how to create patches for git yet?
No. I managed a checkout, but I know almost nothing
I've committed your changes + tried to clean up
the CPUTAPID stuff a little bit. Not pretty, but I'll post
something separate about that.
Did you look into how to create patches for git yet?
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash
here's a patch:
The important bit is the reset timing change. Without this things work
but not at all relaibaly. Took us some time to realise that 0 was
wrong. I don't know what the optimum value is but 250 works a hell of
a lot better - a lot of warnings went away
The other half is more controve
+++ Sergey Lapin [2009-09-08 22:50 +0400]:
> Hi, all!
>
> When working with PXA270 I see the following messages on reset.
>
> JTAG tap: pxa270.cpu tap/device found: 0x49265013 (mfg: 0x009, part:
> 0x9265, ver: 0x4)
> value captured during scan didn't pass the requested check:
> captured: 0x00 che
> I just don't understand what really do you want to fix as proper fix.
> We have ${prefix}/lib/openocd/, which is PKGLIBDIR. Do you want to
> install all that to PKGDATADIR (${prefix}/share/openocd)?
You'll have to start a new thread on this. I attempted a fix, but I was
told it wouldn't work on
Sorry, forgot to Cc list
-- Forwarded message --
From: Sergey Lapin
Date: Wed, Sep 9, 2009 at 12:00 PM
Subject: Re: [Openocd-development] PXA270 problems
To: Øyvind Harboe
On Wed, Sep 9, 2009 at 11:45 AM, Øyvind Harboe wrote:
> On Wed, Sep 9, 2009 at 9:39 AM, Mich
On Wed, Sep 9, 2009 at 9:39 AM, Michael
Schwingen wrote:
> Øyvind Harboe wrote:
>>> I've failed to find link now, but reproduced patch and attached it to this
>>> mail,
>>> so I think you will remember this one.
>>>
>>
>> That one... It's in TODO file. Someone needs to step up to the plate and
>>
Øyvind Harboe wrote:
>> I've failed to find link now, but reproduced patch and attached it to this
>> mail,
>> so I think you will remember this one.
>>
>
> That one... It's in TODO file. Someone needs to step up to the plate and
> fix the automake files I don't know the install rules, et
> I've failed to find link now, but reproduced patch and attached it to this
> mail,
> so I think you will remember this one.
That one... It's in TODO file. Someone needs to step up to the plate and
fix the automake files I don't know the install rules, etc. that need to be
followed.
--
Øy
>> Anyone got a PXA270 to donate so I can test?
>
> We can almost certainly get you a balloon board if it would help keep
> Openocd-on-pxa270 in good fettle.
Thanks!
Please mail it to:
Zylin AS
att. Øyvind Harboe
Auglendsdalen 78
4017 Stavanger
Norway
tel. +47 51 63 25 00
--
Øyvind Harboe
Embe
On Wed, Sep 9, 2009 at 12:25 AM, Øyvind Harboe wrote:
> On Tue, Sep 8, 2009 at 8:50 PM, Sergey Lapin wrote:
>> Hi, all!
>>
>> When working with PXA270 I see the following messages on reset.
>>
>> JTAG tap: pxa270.cpu tap/device found: 0x49265013 (mfg: 0x009, part:
>> 0x9265, ver: 0x4)
>> value capt
+++ Øyvind Harboe [2009-09-08 22:25 +0200]:
> On Tue, Sep 8, 2009 at 8:50 PM, Sergey Lapin wrote:
> > Hi, all!
> >
> > When working with PXA270 I see the following messages on reset.
> >
> > JTAG tap: pxa270.cpu tap/device found: 0x49265013 (mfg: 0x009, part:
> > 0x9265, ver: 0x4)
That is the corr
On Tue, Sep 8, 2009 at 8:50 PM, Sergey Lapin wrote:
> Hi, all!
>
> When working with PXA270 I see the following messages on reset.
>
> JTAG tap: pxa270.cpu tap/device found: 0x49265013 (mfg: 0x009, part:
> 0x9265, ver: 0x4)
> value captured during scan didn't pass the requested check:
> captured: 0
Hi, all!
When working with PXA270 I see the following messages on reset.
JTAG tap: pxa270.cpu tap/device found: 0x49265013 (mfg: 0x009, part:
0x9265, ver: 0x4)
value captured during scan didn't pass the requested check:
captured: 0x00 check_value: 0x02 check_mask: 0x07
JTAG error while writing DC
+++ Øyvind Harboe [2009-05-19 13:54 +0200]:
> Committed.
>
> Thanks!
>
> Note that you can list several -expected-id on the same command line.
OK. that's good, but I'm not sure it addresses teh more general
question about why isn't the cpu.cfg file supplying those default IDs
instead of 0xff
> This patch also lists the two CPU IDs I've found in testing.
> This leads on to two related points about how the CPUTAPID
> thing is used.
>
> 1) How do I specify that a bit is don't care for
> -expected-id? As you can see pxas can be (at least) rev 7 and
> rev4: 0x79265013 and 0x49265013.
Committed.
Thanks!
Note that you can list several -expected-id on the same command line.
W.r.t. reset capabilities then really for XScale it is probably better to
stick with a dongle that can assert srst & trst separately.
--
Øyvind Harboe
Embedded software and hardware consulting services
htt
Hi, I've been doing quite a lot of beating my head against open OCD
over the last few weeks in order to get it working with balloonboard.
Results detailed at
http://www.balloonboard.org/balloonwiki/Balloon3OpenOCD and
http://www.balloonboard.org/balloonwiki/BalloonJTAGing
I have various comments,
Hi,
On Mon, Mar 02, 2009 at 04:40:12PM +0300, Sergey Lapin wrote:
> But, I have PXA270 board (Colibri PXA270 + Orchid board) on my desk
Can you please make a patch to add this as a board cfg file?
Thanks, Uwe.
--
http://www.hermann-uwe.de | http://www.holsham-traders.de
http://www.crazy-hacks.
Hi everyone,
I'm an experienced developer, but I'd have to say that I'm quite new
to JTAG. The concepts are fairly clear, but I don't have enough
experience debugging with JTAG to be able to make any predictions.
I've read the app note regarding isolation of the xscale nTRST nSRST
pins, and I und
> Hi, all!
Do you speak Russian ?
--
Regards,
Alexei Babich, circuit engineer, OOO NPP "Rezonans", Chelyabinsk, Russia
http://www.rez.ru
Jabber ID: imp...@jabber.ru
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.b
Hi, all!
Since I'm really interested in support for pxa270 in OpenOCD for my
OpenSurce - related projects,
I'd like to know what could I do for a project. I'm pretty good with C
and hopefully have enough
of knowledge about various ARM/PXA devices, I have very little
knowledge about JTAG/EICE.
But
Hi, all!
Reading through mail list archives and by trial-and-error, I found that:
1. Latest SVN revision which works with PXA270 is 825.
2. jlink won't work with this version, but olimex arm-usb-ocd will
(probably any with ft2232)
with closed source driver. libftdi tries to work, but fails with
ch
I have the same kind of problem on Colibri PXA270 module, with different b/l
so I'll add a bit.
On Thu, Dec 4, 2008 at 2:53 AM, Duane Ellis wrote:
> dswei wrote> [pxa270 - I can change cpu regs, not memory, target is in
> USER mode]
>
>
> Question #2 - Maybe UBOOT is turning the CPU cache on and
On Feb 17, 2009, at 3:29 AM, Sergey Lapin wrote:
Hi, all!
Do anybody have proper pxa270 config to play with?
I try to use colibri board.
btw, target/pxa270.cfg soesn't work.
All the best,
S.
___
Openocd-development mailing list
Openocd-development@l
Hi Sergey,
On Tue, Feb 17, 2009 at 8:29 AM, Sergey Lapin wrote:
> Hi, all!
>
> Do anybody have proper pxa270 config to play with?
> I try to use colibri board.
> btw, target/pxa270.cfg soesn't work.
>
I'm not sure, but I think some people from OpenEZX project used
openocd to un-brick Motorola A1
Hi, all!
Do anybody have proper pxa270 config to play with?
I try to use colibri board.
btw, target/pxa270.cfg soesn't work.
All the best,
S.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/list
dswei wrote> [pxa270 - I can change cpu regs, not memory, target is in
USER mode]
Question #1 - Did this work with an older version of OpenOCD or is this
the first time you used this?
Question #2 - Maybe UBOOT is turning the CPU cache on and configuring
the MMU in some special way?
Maybe below d
Hi, all.
I have checkout the latest openocd today, and use it on PXA270.
1. There is u-boot on the board , when I connect it with openocd and reset it,
it is halted with pc equal to 0, and in User mode.
2. I can use the command 'reg cpsr 0xd3' to force it enter Supervisor
3. Both in user mode
40 matches
Mail list logo
