Hi Kipp Thanks for the report. I havent used the embedded cable on S3 myself, but I have asked a colleague to share a similar board than yours with me so I can run some tests, and at least replicate the bug.
Will ping to you when I give it a try Regards On Mon, Apr 20, 2020 at 8:15 PM Kipp Cannon <k...@resceu.s.u-tokyo.ac.jp> wrote: > > Package: xc3sprog > Version: 0+svn795+dfsg-1+b1 > Severity: important > > I am new to FPGA development, so I don't have the ability to test a variety > of configurations. I have a Spartan-3E Starter Kit development board, > which has a built-in Xilinx "platform cable" interface. I am using the > Xilinx platform cable firmware that ships with ISE 14.7, specifically I am > using the xusb_emb.hex file with md5sum 545ce982a72441822960fb66a28bde98. > The information available online implies to me that xc3sprog should work > with this development kit, but it does not. The device IDs is reports are > nonsense, and without being able to identify the devices the software > cannot interact with them rendering it effectively non-functional. > > What I get is > > $ xc3sprog -c xpc_internal > XC3SPROG (c) 2004-2011 xc3sprog project $Rev$ OS: Linux > Free software: If you contribute nothing, expect nothing! > Feedback on success/failure/enhancement requests: > http://sourceforge.net/mail/?group_id=170565 > Check Sourceforge for updates: > http://sourceforge.net/projects/xc3sprog/develop > > Cannot find device having IDCODE=1070607 Revision A > JTAG loc.: 0 IDCODE: 0x01070607 not found in 'built-in device list'. > JTAG loc.: 1 IDCODE: 0x03030707 not found in 'built-in device list'. > JTAG loc.: 2 IDCODE: 0x03070707 not found in 'built-in device list'. > > > The board does have 3 devices in the jtag chain, so that much is correct. > > The "jtag" program from the urjtag package works correctly, it is > able to scan the jtag chain and program devices on it. It reports the > following for the board so you can see what the device IDs should be: > > jtag> cable xpc_int > firmware version = 0x0404 (1028) > cable CPLD version = 0x0006 (6) > jtag> detect > IR length: 22 > Chain length: 3 > Device Id: 00000110111001011110000010010011 (0x06E5E093) > Manufacturer: Xilinx (0x093) > Part(0): XC2C64-VQ44 (0x6E5E) > Stepping: 0 > Filename: > /home/kipp/urjtag/share/urjtag/xilinx/xc2c64a-vq44/xc2c64a-vq44 > Device Id: 00000101000001000110000010010011 (0x05046093) > Manufacturer: Xilinx (0x093) > Part(1): xcf04s (0x5046) > Stepping: 0 > Filename: /home/kipp/urjtag/share/urjtag/xilinx/xcf04s/xcf04s > Device Id: 00000001110000100010000010010011 (0x01C22093) > Manufacturer: Xilinx (0x093) > Part(2): xc3s500e_fg320 (0x1C22) > Stepping: 0 > Filename: > /home/kipp/urjtag/share/urjtag/xilinx/xc3s500e_fg320/xc3s500e_fg320 > > -Kipp > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_FIRMWARE_WORKAROUND > Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), > LANGUAGE=en_CA.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages xc3sprog depends on: > ii libc6 2.30-4 > ii libftdi1-2 1.4-2+b2 > ii libgcc-s1 [libgcc1] 10-20200411-1 > ii libgcc1 1:10-20200411-1 > ii libstdc++6 10-20200411-1 > ii libusb-0.1-4 2:0.1.12-32 > ii libusb-1.0-0 2:1.0.23-2 > > xc3sprog recommends no packages. > > xc3sprog suggests no packages. > > -- no debconf information -- Ricardo Ribalda
