Re: Quad XC6SLX150 Board - Initial Price £400/$640/520€

Quote from: daemonic on July 16, 2012, 06:29:51 AM

shipping_test.bit (DIP's setup as per shipping_test.pdf)
Permanent Flash;

Code:

CM1: Running at 24.803891 MH/s
  CM1: Job interval: 47.000000 seconds
  CM2: Running at 24.803891 MH/s
  CM2: Job interval: 47.000000 seconds

These number are incorrect with my worker. My worker is only correct for the 190Mh bitstreams (SW6#1 off!). The interval that is detected is wrong here also. For shipping bitstream please use the icarus worker, it should show correct numbers.

Quote from: daemonic on July 16, 2012, 06:29:51 AM

twin_test.bit (DIP's setup as per twin_test.pdf)
Temporary Flash

Code:

CM1: Running at 182.715256 MH/s
  CM1: Job interval: 17.805074 seconds
  CM2: Running at 181.279004 MH/s
  CM2: Job interval: 17.954064 seconds

Notes
CM2 (FPGA3) gets 50-70% less shares than CM1 (FPGA0) (Average Utility of 1.4-1.5 & 0.8-0.9)
Also quite a few of the following errors on both FPGA's

Code:

Watchdog triggered: 27276.511018 MHashes without share

Permanent Flash;

Code:

CM1: Running at 185.160183 MH/s
  CM1: Job interval: 17.556764 seconds
  CM2: Running at 185.160183 MH/s
  CM2: Job interval: 17.556764 seconds

Notes
   CM2 (FPGA3) gets 50-70% less shares than CM1 (FPGA0) (Average Utility of 1.4-1.5 & 0.8-0.9)
   Also quite a few of the following errors on both FPGA's
   Watchdog triggered: 27276.511018 MHashes without share

The detected Mh/s is completly different each start of the worker, but after some seconds it will show you the correct Mh/s in the website of mpbm.
The Watchdog message come from my changes in the timings, the original timings wait ~3 times longer until it restarts the worker. It could be realy normal to get that message from time to time. But if you can watch the LED's and if you get the message when the orange LED is turned on, you will notice that then it turn off. this is the behavor I had on my board#0015. And my shorten timings make sure the board don't have the orange LED (no work/job) to long.

Quote from: daemonic on July 16, 2012, 06:29:51 AM

190M_V3.bit (DIP's setup as per twin_test.pdf)
Temporary Flash

Code:

CM2: Running at 180.333944 MH/s
  CM2: Job interval: 18.053395 seconds
  CM1: Running at 180.333944 MH/s
  CM1: Job interval: 18.053395 seconds

Notes
First few shares ok, then;

Code:

CM1: Got K-not-zero share eed4cb24
   CM1: Got K-not-zero share c1842661
   CM2: Got K-not-zero share 8c318943
   CM2: Got K-not-zero share 2fc4854e

Permanent Flash
  Not even detected

200M_BETA.bit (DIP's setup as per twin_test.pdf)
Temporary Flash
  Not even detected
Permanent Flash
  Not even detected

I know we're not at full potential, and no sign of any full potential yet, but id at least like to get this one board working ok before i dump a load more cash into more boards Sad

Please take a look at the mpbm webconfiguration, the interessting part are the invalid shares, they must be realy high on your board or the Watchdog messages come really often (orange LED turn on very often).

eb