Re: [Xc3sprog-users] Xilinx Spartan-3A-DSP SPI programming issues

[Uwe B. <bo...@el...>]

>>>>> "Tomek" == Tomek CEDRO <tom...@gm...> writes:

    Tomek> Hello Uwe :-) On Mon, Aug 29, 2011 at 4:16 PM, Uwe Bonnes
    Tomek> <bo...@el...> wrote:
    >> after fighting normal bitrot (see recent SVN checins)

    Tomek> ? :-)

Bitrot: You have a working program on your disk, and trying to use it after
some time, nothing works any longer: Libraries have changed, compilers get
strikter, API changed, etc 
http://en.wikipedia.org/wiki/Bit_rot#Problems_with_software

    >> I can program the flash successfully.  I also read back the flash of
    >> the s3adspstarter kit, verified and reprogrammed.

    Tomek> Uhm, the Amontec JTAGKey2P seems to be working far better and
    Tomek> faster than Xilinx "USB Download Cable" (XUP?) because there are
    Tomek> no errors during flash write, there are errors however on flash
    Tomek> read, also the program does not start so the flashing fails. I
    Tomek> have mounted ST 25P64 chip.

Something is fishy here.
Are you sure you don't have some flaky JTAG or SPI connection, a ringing
JTAG cable, some heavy noise source, too low supply voltage, a
microcontroller addressing the SPI lines after some time or something else? 

I have seen all on my designs...

Test the JTAG chain with the -T0 option, and probably -I -T0 should test
both JTAG and SPI. 

    Tomek> Maybe slowing down will help.. but there is no slow-down option
    Tomek> in release 449 and the fresh release 635 does have slow down but
    Tomek> does not have -c ftdi -V -P switches anymore?! why? how should I
    Tomek> select my ftdi cable? -s does not work :-(

As explained before, define your cable in cablelist.txt.

Slow down only helps in rare cases. E.g. a ringing TCK line may show double
clocking even on slowest JTAG frequencies, as ringing happens at the edges,
with edge rates remaining the same. With an on-board connector I didn't see
problems up to the max JTAG frequency of the slowest device, and AVR with 8
MHz in my case. Cable connected adapters are something different.


Try 
<your cable>          ftdi    <your VID>:<your PID>:       1500000
or
<your cable>          ftdi    <your VID>:<your PID>::1:0x00:0x10:0x00:0x0 1500000

The new scheme works better for people with standard cables, and custom
cables are added more easy. 

Sorry that things work so hard with the end for your diplome work nearing...

Bye
-- 
Uwe Bonnes                bo...@el...

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------