Is anyone else seeing any similar issues to the below with their board?
Mine is 62-0018 updated to rev 1.3; Ive also tried 2 different machines and multiple different usb leads, all of which seem to give similar results;
(All excerpts below are from latest git MPBM with ebereon's Cairnsmore worker.)
For starters my job intervals seem way off compared to the likes of ebereon's previously posted.
shipping_test.bit (DIP's setup as per shipping_test.pdf)
Permanent Flash;
twin_test.bit (DIP's setup as per twin_test.pdf)
Temporary Flash
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
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
190M_V3.bit (DIP's setup as per twin_test.pdf)
Temporary Flash
First few shares ok, then;
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
Mine is 62-0018 updated to rev 1.3; Ive also tried 2 different machines and multiple different usb leads, all of which seem to give similar results;
(All excerpts below are from latest git MPBM with ebereon's Cairnsmore worker.)
For starters my job intervals seem way off compared to the likes of ebereon's previously posted.
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
CM1: Job interval: 47.000000 seconds
CM2: Running at 24.803891 MH/s
CM2: Job interval: 47.000000 seconds
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
NotesCM1: Job interval: 17.805074 seconds
CM2: Running at 181.279004 MH/s
CM2: Job interval: 17.954064 seconds
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
NotesCM1: Job interval: 17.556764 seconds
CM2: Running at 185.160183 MH/s
CM2: Job interval: 17.556764 seconds
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
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
NotesCM2: Job interval: 18.053395 seconds
CM1: Running at 180.333944 MH/s
CM1: Job interval: 18.053395 seconds
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 FlashCM1: Got K-not-zero share c1842661
CM2: Got K-not-zero share 8c318943
CM2: Got K-not-zero share 2fc4854e
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