Your message dated Wed, 25 Nov 2009 13:22:13 +0000
with message-id <[email protected]>
and subject line Bug#537740: fixed in openocd 0.3.1-1
has caused the Debian Bug report #537740,
regarding openocd: Regression from r1606 - playsxvf programming not working
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
537740: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537740
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: openocd
Version: 0.0+r2403-1
Severity: normal

We have been using the version of openocd in testing (r1606) for a
while to program pxa270 and xilinx coolrunner CPLDs. It all worked
fine once we got the config correct.

However we have just updated to current testing version (0.0+r2403-1 0)
and whilst with a small commandchange the pxa programming (need to
add -s /usr/lib/openocd so that the xscale/debug_handler.bin file is
found) still works, the CPLD programming is now broken. We get the
following complaint and so far as we can tell the device has not been
programmed at all:

==============output======
p...@triumph:~/balloon3/distro/binaries$ openocd -s utils/openocd/ -s
 /usr/lib/openocd -f balloon3-cpld-olimex.cfg -f loadcpld.cfg
Open On-Chip Debugger 0.2.0-in-development (2009-06-25-18:22) svn:r2403

BUGS? Read /usr/share/doc/openocd/BUGS

$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c
5000 kHz
Info : JTAG tap: xcr.tap tap/device found: 0x0494c093 (mfg: 0x049, part: 
0x494c, ver: 0x0)
Warn : no gdb ports allocated as no target has been specified
     TapName            | Enabled |   IdCode      Expected    IrLen IrCap  
IrMask Instr
---|--------------------|---------|------------|------------|------|------|------|---------
 0 | xcr.tap            |    Y    | 0x0494c093 | 0x00000000 | 0x06 | 0x01 | 
0x03 | 0x3f
xsvf processing file: "vhdl/cpld/l3cpld.xsvf"
Error: BUG: TAP path doesn't finish in a stable state
Error: XSTATE IRUPDATE is not reachable from current state IRPAUSE in one clock 
cycle
Error: XSTATE DRSELECT is not reachable from current state IRPAUSE in one clock 
cycle
Error: XSTATE DRCAPTURE is not reachable from current state IRPAUSE in one 
clock cycle
Error: XSTATE DREXIT1 is not reachable from current state IRPAUSE in one clock 
cycle
Error: BUG: TAP path doesn't finish in a stable state
Error: XSTATE DRUPDATE is not reachable from current state DRPAUSE in one clock 
cycle
Error: BUG: TAP path doesn't finish in a stable state
Error: XSTATE DRCAPTURE is not reachable from current state RUN/IDLE in one 
clock cycle
Error: XSTATE DREXIT1 is not reachable from current state RUN/IDLE in one clock 
cycle
Runtime error, file "utils/openocd//cpld.cfg", line 5:


The xsvf file was generated with Xilinx webpack 9.2 on a windows
machine. The original jed and the svf and xsvf files generated from it are here:
http://balloonboard.org/files/balloon3/openocd/bugrep/

We get exactly the same results using an Olimex-usb-tiny and an
Amontec JTAGkey

Interestingly, we did find that with r1606 the target board was left
in a 'bad state' after programming and a power cycle of both the board
and the JTAG dongle was required before it would program again,
suggesting that the xsvf file does indeed contain something which
openocd doesn't like. The above error may just be the effect of more
rigorours checking in openocd. However from our point of view this is
entirely fatal - it did at least work before.


So, the question is - has the openocd playsxvf stuff changed in any
way that we should account for in our config (whch is below): I saw
nothing in the changelog to suggest so. And what can we do to help
track down the problem? We were about to go into production with this
so the regression in testing is quite serious. I'm assuming that we
can rebuild r1606 from svn and get going again, but have not yet tested.


=======cpld.cfg========
# CPLD programming
# use xlinx-generated xsvf file and program it in
# may need to specify device if it in chain with cpu

xsvf plain vhdl/cpld/l3cpld.xsvf
shutdown





===============================balloon3-cpld-olimex.cfg=======
# config for Intel PXA270 Balloon 3, with olimex dongle
# connected to CPLD JTAG port

#set up ports and standard config
source [find base.cfg]

jtag_khz 5000

source [find olimex-jtag-tiny.cfg]

source [find xilinx-xcr3256.cfg]

reset_config trst_and_srst separate

init
scan_chain

==========base.cfg======
telnet_port 4444
gdb_port 3333
tcl_port 6666


=========xilinx-xcr3256.cfg==========
#xilinx coolrunner xcr3256
#simple device - just configure a tap
jtag newtap xcr tap -irlen 6 -ircapture 0x01 -irmask 0x03 -expected-id  
0x0494c093


-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (990, 'testing'), (700, 'stable'), (500, 'oldstable'), (300, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages openocd depends on:
ii  libc6                        2.9-4       GNU C Library: Shared libraries
ii  libftdi1                     0.15-2      Library to control and program the
ii  libusb-0.1-4                 2:0.1.12-13 userspace USB programming library

openocd recommends no packages.

openocd suggests no packages.

-- no debconf information

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________



--- End Message ---
--- Begin Message ---
Source: openocd
Source-Version: 0.3.1-1

We believe that the bug you reported is fixed in the latest version of
openocd, which is due to be installed in the Debian FTP archive:

openocd_0.3.1-1.diff.gz
  to main/o/openocd/openocd_0.3.1-1.diff.gz
openocd_0.3.1-1.dsc
  to main/o/openocd/openocd_0.3.1-1.dsc
openocd_0.3.1-1_i386.deb
  to main/o/openocd/openocd_0.3.1-1_i386.deb
openocd_0.3.1.orig.tar.gz
  to main/o/openocd/openocd_0.3.1.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Uwe Hermann <[email protected]> (supplier of updated openocd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 25 Nov 2009 12:20:04 +0100
Source: openocd
Binary: openocd
Architecture: source i386
Version: 0.3.1-1
Distribution: unstable
Urgency: low
Maintainer: Uwe Hermann <[email protected]>
Changed-By: Uwe Hermann <[email protected]>
Description: 
 openocd    - Open on-chip JTAG debug solution for ARM and MIPS systems
Closes: 537740 554598 555553
Changes: 
 openocd (0.3.1-1) unstable; urgency=low
 .
   * New upstream release (Closes: #554598, #537740).
   * Add sh4 (instead of sh) to the list of architectures (Closes: #555553).
   * Standards-Version: 3.8.3 (no changes required).
   * debian/watch: Add file.
   * debian/docs: Updates, some files were removed, some added.
Checksums-Sha1: 
 eaadca997a944d343fb741ab3b34d8000d301fe2 1198 openocd_0.3.1-1.dsc
 953889b3261a45344d43ec5cc1f0fd3a092d7d19 1585636 openocd_0.3.1.orig.tar.gz
 0115dfda3d87a866b05bb9cb0a1eed88b94d71b7 268316 openocd_0.3.1-1.diff.gz
 836985d204974332f2836c69002d117ce4f83343 2210396 openocd_0.3.1-1_i386.deb
Checksums-Sha256: 
 3e210d0e000717365c8dbff418101b77aa0854e440d0b222ea14782966d8bfbc 1198 
openocd_0.3.1-1.dsc
 e1511809b8464912ecd945c288e37401cb23ff5c57fff44b27c5a7aecc292e70 1585636 
openocd_0.3.1.orig.tar.gz
 e7239787edc5abbacb4ce2c2801098153f0d41b9823cb2295b295820003cd55b 268316 
openocd_0.3.1-1.diff.gz
 19fbc56cbffaf7ddf47f29d60a7dd0817b25d79bfb1d73294e77d978ba00600d 2210396 
openocd_0.3.1-1_i386.deb
Files: 
 a8991e861298b8b90e688bdef63771b7 1198 embedded extra openocd_0.3.1-1.dsc
 6c0dafa892e236bab5a9db2a8c651b84 1585636 embedded extra 
openocd_0.3.1.orig.tar.gz
 c7330025fea8072b4d203ea07bf823de 268316 embedded extra openocd_0.3.1-1.diff.gz
 d95e0679237e7d5d0b1e9ad05db194a5 2210396 embedded extra 
openocd_0.3.1-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAksNFDAACgkQXdVoV3jWIbTcXwCeLwuFwbqqzcHe8FDainNA39CV
E4MAoIQxXI+KgE6XRBysPM3R5tYjjfuE
=zdfs
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to