Pages:
Author

Topic: How to use ASICMiner Block Erupters with CGMiner on Windows 7 - page 11. (Read 87358 times)

legendary
Activity: 2702
Merit: 1468
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?
legendary
Activity: 1540
Merit: 1001
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
full member
Activity: 215
Merit: 100
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.
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
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.
legendary
Activity: 966
Merit: 1000
- - -Caveat Aleo- - -
Kano, keep us posted on 3.2.0. A bunch of USB miner group purchases are being delivered.  Smiley
legendary
Activity: 1652
Merit: 1067
Christian Antkow
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
sr. member
Activity: 574
Merit: 250
So has anyone gotten it to work with 3.2.0 yet?
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 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://bitcointalksearch.org/topic/m.2129115

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.
legendary
Activity: 2702
Merit: 1468
Kano,

What sort of errors do you see with your emerald that put it into the "zombie" state?

Can you share some details? It does look that sapphires don't get initialized properly?
I don't have the device yet so I cannot debug this.  Maybe the two issues are related.
legendary
Activity: 1540
Merit: 1001
...
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://bitcointalksearch.org/topic/m.2129115

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
donator
Activity: 2352
Merit: 1060
between a rock and a block!
...
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://bitcointalksearch.org/topic/m.2129115

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
donator
Activity: 2352
Merit: 1060
between a rock and a block!
...
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://bitcointalksearch.org/topic/m.2129115

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
legendary
Activity: 2702
Merit: 1468
...
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://bitcointalksearch.org/topic/m.2129115

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 ...

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.

legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
...
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 ...
legendary
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 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://bitcointalksearch.org/topic/m.2129115

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 ...
legendary
Activity: 1372
Merit: 1000
Thanks to both of you, just posting so I can find this later, when my USB thingies ship.
legendary
Activity: 1652
Merit: 1067
Christian Antkow
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 !
legendary
Activity: 1540
Merit: 1001
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.
Pages:
Jump to: