Yes, very much so!
I've managed to get p0 & p1 permaflashed with nodynclock_175, but p2 & p3 fail to verify, but a temp flash seems to succeed. I'm having com port problems so cgminer only sees on usable device, but starts to mine.
I think I'd be better off doing this with Linux...
Steve, if you having problems flashing just some of them, erasing them in full before you flash does work for me.
I wrote a full up guide on this a few pages back.
https://bitcointalksearch.org/topic/m.1110647Lethos - I was following your guide of erase 0,l, 2, 3 but programming 3 & 2 always gave a verify error, hence me only permflashing 0&1. I can and have tempflashed 2&3 and can hash badly (e.g. 15min gives):
[2012-08-26 22:54:20] ICA0 | (5s):380.0 (avg):378.9 Mh/s | A:3 R:0 HW:0 U:0.2/m
[2012-08-26 22:54:20] ICA1 | (5s):169.4 (avg):184.8 Mh/s | A:36 R:0 HW:0 U:2.4/m
[2012-08-26 22:54:20] ICA2 | (5s):0.0 (avg):272.9 Mh/s | A:5 R:1 HW:0 U:0.3/m
[2012-08-26 22:54:20] ICA3 | (5s):10.0 (avg):253.8 Mh/s | A:7 R:0 HW:0 U:0.5/m
trying the erase command on 0&1 reports success:
Cable cm1 type ftdi VID 0x0403 PID 0x8350 dbus data 00 enable 0b cbus data 00 data 00
Using Libftdi, Using JTAG frequency 1500000 from undivided clock
JTAG chainpos: 0 Device IDCODE = 0x3401d093 Desc: XC6SLX150
USB transactions: Write 9 read 6 retries 0
but doesn't seem to do anything - the amber & red LED remain lit as if the FPGA is still waiting for work
permflashing 2&3 report errors such as:
DNA is 0x192fe44a926474f0
JEDEC: 20 20 0x18 0x00
Found Numonyx Device, Device ID 0x2018
256 bytes/page, 65536 pages = 16777216 bytes total
Page Program failed for flashpage 3073
But the failed flashpage has also been 1, 11265 (p2) & 1, 2049, 3073, 7169, 16385 (p3)
Is this an indicator of a hardware problem?
Should I try reverting to the enterpoint rev 1.5 controller and flash each fpga with a makomk bitstream?
Any help here is much appreciated, thanks!
(edit: for reference, my board SN is 62-0444)