I now have shortfin_dcmwd4c_ed_test_200_overclock running on my SN 26 board. U is 11,53 after one hour.

I will start testing the 200 MH/s bitstream on my SN 26 board tomorrow.

@hm please keep us updated.

@Hpman I guess you have a board with S/N >50?

@spiccioli have you only tried the 140 mhz bitstream yet? Did you try the non-dcmwd bitstreams before?
I'm running the non-dcmwd 150 mhz without problems on my #26 but I'm wondering if the dcmwd-bitstreams allow clocks higher than 150 mhz on pre-50 boards.

Any experiences with pre-S/N-50 boards yet? I cannot test any other bitstream atm because I cannot flip over the dip switch remotely

Thanks. I'm running with icarus-timing=long now. Now MHS av and U are pretty close, even after just 15 minutes.

Which of the values "Hs", "W" and "fullnonce" do I have to pass to icarus-timing to get an accurate reading from the beginning? Found it.

For me it's not... Reported hashrate is 700 MH/s whereas U clearly indicated that the "real" performance is only 600 MH/s. Which is what one would expect from the 150 Mhz bitstream.

I'm currently unable to test any other bitstreams because the board is running in a remote location and I don't want to install VirtualBox risking to kill my network connection.

Which --icarus-timing option do I have to use with cgminer and the shortfin_icarus_cm1_test_150 bitstream to get a correct MH/s readout?

Multiply U with 71.5827883 to get the MH/s.

CGMiner 2.6.1 crashed for the second time now after changing the pool (via API)... This has never happened before. I forgot to enable debug output, so I cannot supply more information atm.

I'm wondering if this could be related to the fixes in 2.6 regarding the "flooding the primary pool with requests"-bug.

@Cranky4u Please try to avoid quoting whole posts and/or images... this really clutters the thread.

Are you sure this board isn't broken? I can run 150 Mhz just fine on my S/N 26 board.
Where are the other pre-S/N-50 board users? I would love to hear some more experiences so maybe we can get a better image on how "bad" pre-50 "really" are...

Thanks - although I had to use escaped backslashes, probably because I'm on Windows.

Is there a way to put this command line into a config file?

-S \\.\COM20 -S \\.\COM22

Because every combination that I tried either failed or only detected one of the two ports (like "scan-serial":"\\\\.\\COM20,\\\\.\\COM22", "scan-serial" on two lines with each port etc...)

I don't know, because I didn't have time to set it up until now. (yes, the board just collected dust for some weeks...)

Currently I have "shortfin_icarus_cm1_test_150.bit" flashed + running and it looks good so far (U is 8.15). But I guess I'll have to wait a few more days to see if it's really stable. Also I didn't try the 160+ Mhz versions.

So at least makomk's bitstreams are working "somehow" on pre-s/n-50 boards, at least on mine.

I have the 150 Mhz version  running on my S/N 26 board. Or are you talking about the 160+ Mhz bitstreams? Didn't try them, yet...

"Serious" as in "cannot be fixed in software"? I'm rather concerned because I have "pre-50" board.

Yohan, can you comment on this?

150 Mhz bitstream working on my sn 26 board for 5+ hours. I won't bother trying the 160 mhz version, but I will now flash the SPI and let it run for some days.

He says "the bitstreams in the following archive are overclocked bitstreams. This means that they run the FPGAs on your board outside of their specified limits. This may void your warranty, damage your hardware, and/or cause cats and dogs to sleep together. Use at your own risk.".

I don't know if this is something I want to run on my board.