Re: [Openocd-development] PXA270 problems
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 scan didn't pass the requested check: > > captured: 0x00 check_value: 0x02 check_mask: 0x07 > > JTAG error while writing DCSR > > value captured during scan didn't pass the requested check: > > captured: 0x00 check_value: 0x01 check_mask: 0x7F > > value captured during scan didn't pass the requested check: > > captured: 0x00 check_value: 0x01 check_mask: 0x7F Interesting: captured == 0, as if TDO were stuck *low* ... which I usually see when JTAG is stuck in reset. > > Unimplemented instruction, could not simulate it. > > > > Working with CPU is very unstable. PXA255 too, but that's slowly getting better ... though I'd be surprised if too many people still try to use those! > > I use Olimex ARM-USB-OCD, under Linux with libftdi. > > This is fixed by changing > jtag_ntrst_delay 0 > to > jtag_ntrst_delay 250 > We just recently worked this out. For the record, and with PXA255 not PXA270, a TRST delay is not sufficient to eliminate such problems. Of course, at this point I usually see those scan errors reporting TDO being stuck *HIGH* and it happens for all IR and DR scans after a certain point. - Dave ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] PXA270 problems
+++ 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 check_value: 0x02 check_mask: 0x07 > JTAG error while writing DCSR > value captured during scan didn't pass the requested check: > captured: 0x00 check_value: 0x01 check_mask: 0x7F > value captured during scan didn't pass the requested check: > captured: 0x00 check_value: 0x01 check_mask: 0x7F > Unimplemented instruction, could not simulate it. > > Working with CPU is very unstable. > I use Olimex ARM-USB-OCD, under Linux with libftdi. This is fixed by changing jtag_ntrst_delay 0 to jtag_ntrst_delay 250 We just recently worked this out. I have a pile of pending changes for balloon3, xcr3256 and pxa270 which I just tidied up last night after fixing various annoyances like this (it works OK for us with this set wrong, but you get a lot of whinging). Will send them in shortly. Wookey -- Principal hats: iEndian - Balloonboard - Toby Churchill - Emdebian http://wookware.org/ ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] PXA270 problems
> 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 all distributions, so I decided not to get involved.
Perhaps you can post the patch and suggest that it should be applied
and then perhaps we can hear the protests again?
See TODO for more details.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] PXA270 problems
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, 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
>>> fix the automake files I don't know the install rules, etc. that need
>>> to be
>>> followed.
>>>
>> Maybe we should commit that fix as a temporary solution until "someone"
>> fixes the automake files?
>
> Ah!
>
> Should we commit kludges or wait for a proper fix?
>
> There is a good workaround for this, use the "-s" option. No patch
> is necessary.
>
>> What's annoying is that we had a working state, which was later broken -
>> and the breakage was never taken back or fixed.
>
> Something else was fixed that broke this... yes. Don't ask me
> about install issues under various *nix distributions...
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)?
Or what goal do you want to achieve? as I understand, everything which
is installed to lib is not found. Does -s option adds search paths,
or redefines default one?
All the best,
S.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] PXA270 problems
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 >> fix the automake files I don't know the install rules, etc. that need to >> be >> followed. >> > Maybe we should commit that fix as a temporary solution until "someone" > fixes the automake files? Ah! Should we commit kludges or wait for a proper fix? There is a good workaround for this, use the "-s" option. No patch is necessary. > What's annoying is that we had a working state, which was later broken - > and the breakage was never taken back or fixed. Something else was fixed that broke this... yes. Don't ask me about install issues under various *nix distributions... -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] PXA270 problems
Ø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, etc. that need to > be > followed. > Maybe we should commit that fix as a temporary solution until "someone" fixes the automake files? The current state is not very useful, even if the goal is a cleaner solution - a clean solution that does not work for users is useless. What's annoying is that we had a working state, which was later broken - and the breakage was never taken back or fixed. cu Michael ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] PXA270 problems
> 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. -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] PXA270 problems
>> 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 Embedded software and hardware consulting services http://www.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] PXA270 problems
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 captured during scan didn't pass the requested check:
>> captured: 0x00 check_value: 0x02 check_mask: 0x07
>> JTAG error while writing DCSR
>> value captured during scan didn't pass the requested check:
>> captured: 0x00 check_value: 0x01 check_mask: 0x7F
>> value captured during scan didn't pass the requested check:
>> captured: 0x00 check_value: 0x01 check_mask: 0x7F
>> Unimplemented instruction, could not simulate it.
>
> Anyone got a PXA270 to donate so I can test?
>
>> Working with CPU is very unstable.
>> I use Olimex ARM-USB-OCD, under Linux with libftdi.
>> I also use patch which fixes monitor loading, from Øyvind,
>
> Which patch is this?
>
I've failed to find link now, but reproduced patch and attached it to this mail,
so I think you will remember this one.
Index: src/helper/Makefile.am
===
--- src/helper/Makefile.am (revision 2678)
+++ src/helper/Makefile.am (working copy)
@@ -1,6 +1,7 @@
AM_CPPFLAGS = \
-I$(top_srcdir)/src/server \
-I$(top_srcdir)/src/target \
+ -DPKGLIBDIR=\"$(pkglibdir)\" \
-DPKGDATADIR=\"$(pkgdatadir)\"
METASOURCES = AUTO
Index: src/helper/options.c
===
--- src/helper/options.c (revision 2678)
+++ src/helper/options.c (working copy)
@@ -105,6 +105,7 @@
/// @todo Implement @c add_script_search_dir("${HOME}/.openocd").
add_script_search_dir(PKGDATADIR "/site");
add_script_search_dir(PKGDATADIR "/scripts");
+ add_script_search_dir(PKGLIBDIR);
#endif
}
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] PXA270 problems
+++ Ø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 correct value. Values we have observed so far are:
0x79265013 and 0x49265013 which I believe are now in openocd.
> > value captured during scan didn't pass the requested check:
> > captured: 0x00 check_value: 0x02 check_mask: 0x07
I see errors like this too and have never understood why the boundary
scan seems to work OK ('scan_chain'), but then other commands cause the
above errors.
> 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.
> > Working with CPU is very unstable.
> > I use Olimex ARM-USB-OCD, under Linux with libftdi.
Same here. We have found cpu and NOR flash uploading reliable - all
our problems are with CPLD loading and USB getting 'stuck'.
> > I also use patch which fixes monitor loading, from Øyvind,
>
> Which patch is this?
I wondered that too.
Wookey
--
Principal hats: iEndian - Balloonboard - Toby Churchill - Emdebian
http://wookware.org/
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] PXA270 problems
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: 0x00 check_value: 0x02 check_mask: 0x07 > JTAG error while writing DCSR > value captured during scan didn't pass the requested check: > captured: 0x00 check_value: 0x01 check_mask: 0x7F > value captured during scan didn't pass the requested check: > captured: 0x00 check_value: 0x01 check_mask: 0x7F > Unimplemented instruction, could not simulate it. Anyone got a PXA270 to donate so I can test? > Working with CPU is very unstable. > I use Olimex ARM-USB-OCD, under Linux with libftdi. > I also use patch which fixes monitor loading, from Øyvind, Which patch is this? -- Øyvind Harboe Embedded software and hardware consulting services http://www.zylin.com ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] PXA270 problems
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 DCSR value captured during scan didn't pass the requested check: captured: 0x00 check_value: 0x01 check_mask: 0x7F value captured during scan didn't pass the requested check: captured: 0x00 check_value: 0x01 check_mask: 0x7F Unimplemented instruction, could not simulate it. Working with CPU is very unstable. I use Olimex ARM-USB-OCD, under Linux with libftdi. I also use patch which fixes monitor loading, from Øyvind, I can do basic commands like mww or mdw on SRAM, but loading images generally fail due to timeouts, which makes me reset hardware. Single SRAM writes, like mww 0x5C00 0xdeadbeef work perfectly. Config: set CPUTAPID 0x49265013 source [find interface/olimex-arm-usb-ocd.cfg] source [find target/pxa270.cfg] reset_config trst_and_srst separate jtag_nsrst_delay 2000 jtag_ntrst_delay 2000 flash bank cfi 0x 0x100 2 4 0 jtag_khz 8 All the best, S. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
