I want to share my experiences of the last two days with my new CM1 boards.
First of all they are working great @ 3900Mh/s. Not as my early board (SN# 15), witch was a pain!
TML Bitstream: Is not working at the moment. I get the same results as I already posted in Ellentyrell's thread.
I'm working unter Win7 32bit.
I started with cgminer, but after 5 hours one board disappeared and some where realy slow U 1.9 and 2.1 and so on. I tried ep cgminer and cgminer 2.4.3.
I see a problem using cgminer with the CM1 board at this stage. It's more incompatible or have an bug or somthing. Also you don't see Invalid Shares witch is bad, you don't know why your FPGA is slow etc.
So I started again with MPBM. Here I can see Invalid Shares, I can Flash the CM1 boards in VM and after I reconnect them to windows, MPBM start hashing on it rigth away without a restart or something.
Then I was trying to get the most out of my Boards. MPBM was running with under 1% Invalid Shares in one hour with the Twin_test.bit Bitstream. I started the VM and flashed ALL Boards to the 200M_beta.bit Icarus Bitstream. Realy nice, after each board was flashed, MPBM started hashing with them without anything to do.
I was waiting again 1 hour to check the Invalid Shares and flashed the FPGAs that had more then 1% back to twin_test.bit.
Here my results:
as you can see only 2 FPGAs with 200M_beta.bit (200Mh/s) have <1% Invalid Shares, the others have the twin_test.bit (190Mh/s).
From 20 FPGAs have 15 200M_beta.bit and only 5 twin_test.bitI have made also some modifications the my cairnsmore worker for MPBM. I change some settings to meet the CM1 board at this stage. It restarts the worker earlyer when the FPGA have no share summitted in an spezified timeframe. Some wait times have been shorten to make sure an disconnected CM1 board get faster reconnected and so on.
You can download the modified cairnsmore worker
here.
One more problem I had was, when I was "searching" the right Com ports for the FPGAs the boards become unresponsive. I think when I started the miner on a Com port related to the Jtag or SPI port, the FTDI chip scrwed up until complette power down. In windows this is a pain with 40 USB devices automaticly creates a Com port XX, so you don't know what it is and you need to test it if it's a FPGA or not. We need here something changed in the driver or what ever.
I hope this helps someone to get the most out of the CM1 board.
Happy mining!
eb
EDIT:
Set the Jobinterval as follows:
twin_test.bit (190Mh/s) = 11.33
200M_beta.bit (200Mh/s) = 10.6
The orange LED's should only "flash" <1 second betwen the jobs!