Bitcoin Forum
December 12, 2024, 08:36:45 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 3 4 5 6 7 8 9 10 11 »  All
  Print  
Author Topic: How to use ASICMiner Block Erupters with CGMiner on Windows 7  (Read 87370 times)
mdude77 (OP)
Legendary
*
Offline Offline

Activity: 1540
Merit: 1001



View Profile
May 30, 2013, 06:42:32 PM
Last edit: September 08, 2013, 11:18:23 AM by mdude77
 #1

If there's another thread that describes this, I apologize.  I had to hunt a bit to find everything needed to get it working, so I thought I'd paste it all here so future miners can save some time:

If using version 3.1.1, it needs a driver to make the USB devices visible as COM devices (a UART driver).  Follow these instructions:

1 - As listed in the FPGA-README doc with cgminer, install this driver for your little USB miners: http://sourceforge.net/projects/libwdi/files/zadig/

Note the "latest" link on the top of the page isn't what you want!  You want the one that starts with Zadig.  As of this writing, the version is: zadig_v2.0.1.160.7z
Also note you will need 7zip to unzip it.

2 - After it installs, reboot as windows tells you do.  Wait until Zadig tells you its done installing, windows may ask you before Zadig says it is done.  

Note that you only have to do it once for all your miners, not once for each one.
Also note that the renaming doesn't seem to work right, or is not intuitive.  I tried renaming one and it didn't work.

3 - Install the UART to COM drivers from here: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

4 - Check device manager, you should see items under your ports section now, with the COM port assigned for each one.

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that if you have more than 7, you will probably need to use this format for the COM ports to recognize COM10 and beyond:

-S \\.\COM3 -S \\.\COM4 -S \\.\COM5 -S \\.\COM6 -S \\.\COM7 -S \\.\COM8 -S \\.\COM9 -S \\.\COM11 -S \\.\COM12 -S \\.\COM13


If using version 3.4.2 (or higher), you do NOT want the UART driver, so follow these instructions:

1 - As listed in the FPGA-README doc with cgminer, install this driver for your little USB miners: http://sourceforge.net/projects/libwdi/files/zadig/

Note the "latest" link on the top of the page isn't what you want!  You want the one that starts with Zadig.  As of this writing, the version is: zadig_v2.0.1.160.7z
Also note you will need 7zip to unzip it.

2 - After it installs, reboot as windows tells you do.  Wait until Zadig tells you its done installing, windows may ask you before Zadig says it is done.  

Note that you only have to do it once for all your miners, not once for each one.
Also note that the renaming doesn't seem to work right, or is not intuitive.  I tried renaming one and it didn't work.

3 - Run cgminer-nogpu with whatever options you need to point to your pools.  No other parms are necessary.  

For my 25 miners, I'm using:

cgminer-nogpu.exe -c "cgminer.conf"


Version 3.1.1 gives me about 333mh/s on Win7x64.  Version 3.4.2 gives me about 335mh/s.  I seem to get less hardware errors on 3.4.2 as well.


If you need a configuration file for pools, here is what I use:

Code:
{
"pools" : [
{
"url" : "http://stratum.btcguild.com:3333",
"user" : "user",
"pass" : "password"
},
{
"url" : "http://stratum.ozco.in:3333",
"user" : "user",
"pass" : "password"
},
{
"url" : "http://192.168.0.194:8332",
"user" : "user",
"pass" : "password"
}
]
}

Note that the first two pools are true pools, the third one is a local instance of bitcoind. 

M


***UPDATED 9/8/2013 to include info on 3.4.2 and an example of cgminer.conf with pools.

I mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!
Xian01
Legendary
*
Offline Offline

Activity: 1652
Merit: 1067


Christian Antkow


View Profile
May 30, 2013, 07:50:43 PM
 #2

Great post ! FWIW, if you don't want to run the separate nogpu executable, you can specify the regular cgminer.exe with the -G flag.

According to Kano in the CGMiner thread, v3.2.0 will have some spectacular work done to make mining with these easier, complete with hot-swap capabilities. Great stuff !
Adrian-x
Legendary
*
Offline Offline

Activity: 1372
Merit: 1000



View Profile
May 30, 2013, 08:00:11 PM
 #3

Thanks to both of you, just posting so I can find this later, when my USB thingies ship.

Thank me in Bits 12MwnzxtprG2mHm3rKdgi7NmJKCypsMMQw
kano
Legendary
*
Offline Offline

Activity: 4634
Merit: 1851


Linux since 1997 RedHat 4


View Profile
May 31, 2013, 01:42:28 AM
 #4

...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day Tongue
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
kano
Legendary
*
Offline Offline

Activity: 4634
Merit: 1851


Linux since 1997 RedHat 4


View Profile
May 31, 2013, 10:42:40 AM
 #5

...
Awesome, I cannot wait to try 3.2.0.  Still waiting for my erupters.

Kano,

Have you had a chance to test 3.2.0 on Windows?  It should work by just compiling git sources or do I have to do anything special?
Same build instructions as 3.1.1?  For running, we need to set WinUSB in zadig, right?  So 3.2.0 will be the first version to use direct USB for Icarus driver.

Feels like I've been working more on the damn windows side than the linux code recently.
Linux on 3.2.0 (out now) is pretty rock solid.

Windows seems to have finally settled down after some strange problems with my VM and power issues with USB on a real windows box.
I'll not be surprised if there are Windows problems, but do help by reporting them if you find any.

Yes all USB devices in cgminer now use WinUSB, the two driver changes for 3.2.0 are Avalon and Icarus = Icarus, Lancelot, Black Arrow Lancelot, Asicminer USB and Cairnsmore1 - but I've no idea even if the Cairnsmore1 code works ...

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
CanaryInTheMine
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
May 31, 2013, 08:27:33 PM
 #6

...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day Tongue
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...
not sure how the new version is supposed to work, but 10 sticks on a hub and not a single one detected with new version... same result as arklan is reporting
CanaryInTheMine
Donator
Legendary
*
Offline Offline

Activity: 2352
Merit: 1060


between a rock and a block!


View Profile
June 01, 2013, 08:17:48 AM
 #7

...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day Tongue
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...

i've yet to see 3.2.0 work for me... it does not detect anything... i'm still running bfgminer instead.
would like to get cgminer 3.2.0 working though
mdude77 (OP)
Legendary
*
Offline Offline

Activity: 1540
Merit: 1001



View Profile
June 01, 2013, 11:35:02 AM
 #8

...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day Tongue
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...

i've yet to see 3.2.0 work for me... it does not detect anything... i'm still running bfgminer instead.
would like to get cgminer 3.2.0 working though

3.1.1 works fine with the info I posted above.  I can't get 3.2.0 to work either.  Some people seem to think it's USB 3.0 hub related.

M

I mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!
kano
Legendary
*
Offline Offline

Activity: 4634
Merit: 1851


Linux since 1997 RedHat 4


View Profile
June 02, 2013, 01:01:09 AM
 #9

...
Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed.  
...
Yes I posted 115200:2:1 on the first day I got it almost 3 weeks ago and then corrected it that day Tongue
https://bitcointalk.org/index.php?topic=28402.msg2129115#msg2129115

As you used, you would only use 115200:1:1

3.1.1 still requires the windows serial driver for Icarus devices (but only for Icarus and Avalon devices)

3.2.0 will not use any serial drivers and you must use zadig to set the WinUSB driver for them (3.2.0 will be released shortly)

3.2.0 auto detects all supported USB mining devices and auto hotplugs them all also.
It sets the --icarus-options and --icarus-timing performance numbers automatically for each device also - but you can override them of course.

The Asicminer USB (Block Erupter USB) shows up as "AMU" i.e. AMU 0, AMU 1, AMU 2 ...

i've yet to see 3.2.0 work for me... it does not detect anything... i'm still running bfgminer instead.
would like to get cgminer 3.2.0 working though

3.1.1 works fine with the info I posted above.  I can't get 3.2.0 to work either.  Some people seem to think it's USB 3.0 hub related.

M
Yes USB 3.0 is certainly on the top of the list for problems (that I'll need to sort out shortly)

Also the initialisation error (4) I've yet to be able to reproduce the cause for me (and work out a fix)
So certainly for windows, for now I'll say 3.1.1 while I try sort out solutions to problems being seen.
On linux, if 3.2.0 just works, then go with that, if it gets initialisation failures, use 3.1.1 for now until I can sort out that error.

On linux the switch from 3.2.0 back to 3.1.1 just requires you to stop cgminer 3.2.0 and then unplug+replug the USB devices.
If you run USB on both 3.2.0 and 3.1.1 at the same time, it will cause problems.

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
twobits
Sr. Member
****
Offline Offline

Activity: 574
Merit: 250



View Profile
June 02, 2013, 03:12:48 AM
 #10

So has anyone gotten it to work with 3.2.0 yet?

█████                █████      ███████             
█████                ███    █████████████       
█████                ██  █████████████████   
█████                █  ██████              ██████ 
█████                    ████                      ████ 
█████████████  █████                        ████
█████████████  █████                        ████
█████████████  █████                        ████
█████                    █████                             
█████                █  ██████              ███████
█████                ██  ███████████    █████ 
█████                ███    █████████    ████   
█████                █████      ███████    ██
███
███
███
███
███
███
███
███
███
HyperQuant.net
Platform for Professional Asset Management
███
███
███
███
███
███
███
███
███
WhitePaper
One-Pager
███
███
███
███
███
███
███
███
███
Telegram 
Facebook
Twitter
Medium
███
███
███
███
███
███
███
███
███
███
███
███
███
███
███
███
███
███
█████                █████      ███████             
█████                ███    █████████████       
█████                ██  █████████████████   
█████                █  ██████              ██████ 
█████                    ████                      ████ 
█████████████  █████                        ████
█████████████  █████                        ████
█████████████  █████                        ████
█████                    █████                             
█████                █  ██████              ███████
█████                ██  ███████████    █████ 
█████                ███    █████████    ████   
█████                █████      ███████    ██
Xian01
Legendary
*
Offline Offline

Activity: 1652
Merit: 1067


Christian Antkow


View Profile
June 02, 2013, 03:28:03 AM
 #11

So has anyone gotten it to work with 3.2.0 yet?

 Not here. Can't get any of the Erupters to show up in Device Manager as COM devices with the WinUSB driver installed Sad Have only been able to get 3.1.1 working with the SiLabs driver Sad
dwdoc
Legendary
*
Offline Offline

Activity: 966
Merit: 1000


- - -Caveat Aleo- - -


View Profile
June 02, 2013, 03:32:43 AM
 #12

Kano, keep us posted on 3.2.0. A bunch of USB miner group purchases are being delivered.  Smiley
kano
Legendary
*
Offline Offline

Activity: 4634
Merit: 1851


Linux since 1997 RedHat 4


View Profile
June 02, 2013, 04:45:47 AM
 #13

So has anyone gotten it to work with 3.2.0 yet?

 Not here. Can't get any of the Erupters to show up in Device Manager as COM devices with the WinUSB driver installed

I thought 3.2.0 is using direct USB so you don't need USB/COM divers.  It suppose to detect Erupters as a device attached to USB port not a COM port.
so you should not see any COM ports in the Device Manager.

Or am I missing something?
Yes that's the idea (and it was working for me on windows with just one emerald)
However, the "(4)" error (debug shows that) is something I've not yet resolved - which is I think the cause of failure to initialise on windows for anyone getting that problem.
(and on linux I think some may have see it)

Yes I'll update here once it's sorted out.

Pool: https://kano.is - low 0.5% fee PPLNS 3 Days - Most reliable Solo with ONLY 0.5% fee   Bitcointalk thread: Forum
Discord support invite at https://kano.is/ Majority developer of the ckpool code - k for kano
The ONLY active original developer of cgminer. Original master git: https://github.com/kanoi/cgminer
flowdab
Full Member
***
Offline Offline

Activity: 215
Merit: 100


View Profile
June 02, 2013, 06:25:25 AM
 #14

If there's another thread that describes this, I apologize.  I had to hunt a bit to find everything needed to get it working, so I thought I'd paste it all here so future miners can save some time:

1 - As listed in the FPGA-README doc with cgminer, install this driver for your little USB miners: http://sourceforge.net/projects/libwdi/files/zadig/

Note the "latest" link on the top of the page isn't what you want!  You want the one that starts with Zadig.  As of this writing, the version is: zadig_v2.0.1.160.7z
Also note you will need 7zip to unzip it.

2 - After it installs, reboot as windows tells you do.  Wait until Zadig tells you its done installing, windows may ask you before Zadig says it is done. 

Note that you only have to do it once for all your miners, not once for each one.
Also note that the renaming doesn't seem to work right, or is not intuitive.  I tried renaming one and it didn't work.

3 - Install the UART to COM drivers from here: http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

4 - Check device manager, you should see items under your ports section now, with the COM port assigned for each one.

5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed. 

I'm getting about 333mh/s with the above on Win7x64.

M


You sir are a man among men. Thanks for posting.
mdude77 (OP)
Legendary
*
Offline Offline

Activity: 1540
Merit: 1001



View Profile
June 02, 2013, 10:13:10 AM
 #15

So has anyone gotten it to work with 3.2.0 yet?

 Not here. Can't get any of the Erupters to show up in Device Manager as COM devices with the WinUSB driver installed

I thought 3.2.0 is using direct USB so you don't need USB/COM divers.  It suppose to detect Erupters as a device attached to USB port not a COM port.
so you should not see any COM ports in the Device Manager.

Or am I missing something?

The way I understand it, there are 2 drivers needed for 3.1.1 to work:

1 - the WinUSB driver to get the item recognized by windows as a USB device
2 - the USB to UART driver to make them accessible via COM port

3.2.0 still requires #1, but not #2.

M

I mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!
Rant2112
Newbie
*
Offline Offline

Activity: 70
Merit: 0



View Profile
June 02, 2013, 06:54:20 PM
 #16

I can't get 3.2 to work.

I'm running xUbuntu 13.04.

When I start up cgminer 3.2, syslog shows:

cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
cp210x 2-2.2:1:0: device disconnected

cgminer 3.1.1 works fine with the -S option.
True___Blue
Sr. Member
****
Offline Offline

Activity: 354
Merit: 250



View Profile WWW
June 03, 2013, 09:45:06 PM
 #17


5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed. 

I'm getting about 333mh/s with the above on Win7x64.

M


I really appreciate your post. For all of us noobs out there can you be a bit more specific on how you do step 5? Very basic stuff I know, but I am trying to learn. When I run my cgminer no gpu it first wants me to enter a url. After I put in the mining pool info and my worker info it goes away. How do I set it up to run using the options you have specified?  I know its connected and working b/c I am able to mine using the USB BE using bitminter's software. Thanks.

mdude77 (OP)
Legendary
*
Offline Offline

Activity: 1540
Merit: 1001



View Profile
June 03, 2013, 10:11:12 PM
 #18


5 - Run cgminer-nogpu with these options:
--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COMx -S COMy -S COMz -S COMetc

For my 7 miners, I'm using:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4 -S COM5 -S COM6 -S COM7 -S COM8 -S COM9

Note that I saw a post from one of the cgminer authors suggesting to use 115200:2:1 and 3.0=80.  When I did that, I got errors and cgminer immediately crashed. 

I'm getting about 333mh/s with the above on Win7x64.

M


I really appreciate your post. For all of us noobs out there can you be a bit more specific on how you do step 5? Very basic stuff I know, but I am trying to learn. When I run my cgminer no gpu it first wants me to enter a url. After I put in the mining pool info and my worker info it goes away. How do I set it up to run using the options you have specified?  I know its connected and working b/c I am able to mine using the USB BE using bitminter's software. Thanks.

Sounds like you are trying to run it from windows explorer?  What you want to do is create a command script to run it that pauses at the end, so you can see what it's saying before windows closes the command window.  If Bitminter's software is working for you, you might want to stick with that.  Bitminter is one of the best pools around if you don't want to go pay per share (PPS).  It's what I use. Smiley

To make a command script, open notepad and enter something like this:

Code:
cd \mining\cgminer
cgminer.exe [with your parameters]
pause

Then save it where you can easily get to it as cgminer.cmd. Hopefully you've already turned off the "feature" in windows to hide known file extensions (tools -> folder options in windows explorer), otherwise you'll end up with a file called cgminer.cmd.txt.

The cgminer readme has info on what parms to use to specify a pool, password, and so forth.

M

I mine at Kano's Pool because it pays the best and is completely transparent!  Come join me!
logicbomb666
Sr. Member
****
Offline Offline

Activity: 260
Merit: 250



View Profile WWW
June 04, 2013, 12:53:43 AM
 #19

just wanted to say thanks for making this thread, go my USB miner in the mail today and had it hashing away within minutes due to your info.

I think snare rolls should be used as a currency.
thoughtcourier
Member
**
Offline Offline

Activity: 96
Merit: 10


View Profile
June 04, 2013, 04:51:25 AM
 #20

I downloaded CGMiner 3.2 which got rid of the -S flag, leading to much swearing on my end before I put a pause on the batch file and the diffed the repo to figure out what this mysterious flag did. There is no -S flag in 3.2, and personally, my auto-detect doesn't work. Only in Bitcoinland does removing features count for user-friendliness (I believe they removed it because 3.2 is supposed to autodetect, but it didn't. Complaints aside, serious thanks to kano and cgminer people)

These instructions work fine for 3.1.
Also, I'm on XP but your instructions worked fine.


Edit: If anyone is wondering, that flag does the following:

--scan-serial|-S <arg> Serial port to probe for Icarus mining device
Pages: [1] 2 3 4 5 6 7 8 9 10 11 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!