How to use ASICMiner Block Erupters with CGMiner on Windows 7

[maud138]

I hope somebody can help me.
I use Windows XP and have 3 block erupters. One is working fine with cgminer 3.1.1
I followed the instructions, used the toUARTBridgeVCPDrivers and Zadig.

When I try to install a second (or a third) one, Windows gives an error and says: " I can't load the driver because there is already an exactly the same piece of hardware."

So There isn't a new COM popping up in the hardwaremanager and Zadig doesn't see the second one.

What can I do?

[kano]

With 3.1.1 you don't use Zadig for AMUs

[maud138]

Thanks Kano,

I still don't have more than one Block Erupter working on my Windows XP. Everytime I plug in another one, Windows gives me code 42 "duplicate device".

Is there a solution for this (other than buying a hub, I just have 2 erupters and lots of USB-ports)

Thanks

[Xian01]

With 3.1.1 you don't use Zadig for AMUs

 Sorry for the slight derail, but have you gentlemen made any progress with the USB 3 issues in your latest-and-greatest ? I'm still using 3.1.1 for simplicity as I have USB 3 hubs galore under Windows 

[kano]

With 3.1.1 you don't use Zadig for AMUs

 Sorry for the slight derail, but have you gentlemen made any progress with the USB 3 issues in your latest-and-greatest ? I'm still using 3.1.1 for simplicity as I have USB 3 hubs galore under Windows 

Next release will have the fixed libusb in it (it seems a lot of OS have a bad libusb)
https://bitcointalk.org/index.php?topic=220905.msg2870499#msg2870499
Shouldn't be too far away ...

[Xian01]

Next release will have the fixed libusb in it (it seems a lot of OS have a bad libusb)
https://bitcointalk.org/index.php?topic=220905.msg2870499#msg2870499
Shouldn't be too far away ...

 Kick-ass ! Looking forward to it.

 Cheers.

[dingens]

Im gettin following error:

 [2013-08-05 23:38:50] Started cgminer 3.3.0
 [2013-08-05 23:38:50] Started cgminer 3.3.0
 [2013-08-05 23:38:50] USB init, open device failed, err -12, you need to instal
l a WinUSB driver for - AMU device 1:2
 [2013-08-05 23:38:50] Icarus detect (1:2) failed to initialise (incorrect devic
e?)
 [2013-08-05 23:38:51] No devices detected!
 [2013-08-05 23:38:51] Waiting for USB hotplug devices or press q to quit
 [2013-08-05 23:38:51] Need to specify at least one pool server.
Input server details.
URL:
Im on win 7 64, the usb driver is visable at the control panel.

[kano]

Im gettin following error:

 [2013-08-05 23:38:50] Started cgminer 3.3.0
 [2013-08-05 23:38:50] Started cgminer 3.3.0
 [2013-08-05 23:38:50] USB init, open device failed, err -12, you need to instal
l a WinUSB driver for - AMU device 1:2
 [2013-08-05 23:38:50] Icarus detect (1:2) failed to initialise (incorrect devic
e?)
 [2013-08-05 23:38:51] No devices detected!
 [2013-08-05 23:38:51] Waiting for USB hotplug devices or press q to quit
 [2013-08-05 23:38:51] Need to specify at least one pool server.
Input server details.
URL:
Im on win 7 64, the usb driver is visable at the control panel.

"USB init, open device failed, err -12, you need to install a WinUSB driver for - AMU device 1:2"

... as per ASIC-README, FPGA-README and README ... on windows you need to switch to the WinUSB driver using Zadig

[dingens]

Oh I got it! Thx so far but my cgminer/cmd closes after the input of pool info...
What Im doing wrong? Im at 50btc.com

[kano]

Oh I got it! Thx so far but my cgminer/cmd closes after the input of pool info...
What Im doing wrong? Im at 50btc.com

No idea ... more info required ...
Run cgminer in a cmd window and you'll see what your next problem is.
My guess would be incorrect pool info - but no idea.

[Sharky444]

I'm mining Litecoins with my Radeon 7970, so I have some cgminer experience.

Today I've purchased 2 Block Erupters to also mine Bitcoins.

Unfortunately I've a problem to get both of them running.

I've created a new cgminer folder and installed cgminer 3.2.2 there.

Plugged in the two Block Erupters and installed the drivers from here:

http://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx

cgminer 3.2.2 did not detect the Erupters, so I've found this thread.

Used zadig.exe to replace the drivers with the WinUSB versions.

So far so good, cgminer-nogpu detection problem is solved. But there's still a problem left!.

Problem: only ONE Erupter is detected!

This is no hardware fault, because if ANY of the TWO erupters I have is plugged to any USB port cgminer detects it, but always only one, so I see this:

 AMU 0:                | 321.5M/317.1Mh/s | A:0 R:0 HW:0 WU: 6.7/m
 
there is no AMU 1:, no matter what I do!?

The device manager (Windows 7 x64) shows two CP21202 USB devices.

Please help!

[kano]

... use 3.3.2 ...

[Yinero]

I have no idea what is going on but it is really aggravating....

I follow the guide here to the T. this is what happens.

I instal the zandig drivers then did the UAT to COM driver. Go to start cgminer-nogpu and it says that I need to instal the zandig drivers again.... so I do that and then it says no devices detected. I try to then make a .bat file instead of just starting cgminer-nogpu and all it does is instantly crash and I have everything typed in properly and correct. I'm also using 3.3.2 like everyone is saying too...

[mdude77]

I have no idea what is going on but it is really aggravating....

I follow the guide here to the T. this is what happens.

I instal the zandig drivers then did the UAT to COM driver. Go to start cgminer-nogpu and it says that I need to instal the zandig drivers again.... so I do that and then it says no devices detected. I try to then make a .bat file instead of just starting cgminer-nogpu and all it does is instantly crash and I have everything typed in properly and correct. I'm also using 3.3.2 like everyone is saying too...

You don't want 3.3.2 if you're using the UAT to COM driver.  Use 3.1.1 with the UAT to COM, or don't use the UAT to COM.

M

[Yinero]

I have no idea what is going on but it is really aggravating....

I follow the guide here to the T. this is what happens.

I instal the zandig drivers then did the UAT to COM driver. Go to start cgminer-nogpu and it says that I need to instal the zandig drivers again.... so I do that and then it says no devices detected. I try to then make a .bat file instead of just starting cgminer-nogpu and all it does is instantly crash and I have everything typed in properly and correct. I'm also using 3.3.2 like everyone is saying too...

You don't want 3.3.2 if you're using the UAT to COM driver.  Use 3.1.1 with the UAT to COM, or don't use the UAT to COM.

M

Switched to 3.1.1 didn't change a thing. Still says no USB detected.... and when i run the .bat it just crashes instantly again...

Figured it out:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4

when making the .bat file for 3.1.1. I deleted the strikedout portion of the above quote and cgminer would work with the asics. However instead of them appearing as COM or AMU, it shows up as ICA.

[mdude77]

I have no idea what is going on but it is really aggravating....

I follow the guide here to the T. this is what happens.

I instal the zandig drivers then did the UAT to COM driver. Go to start cgminer-nogpu and it says that I need to instal the zandig drivers again.... so I do that and then it says no devices detected. I try to then make a .bat file instead of just starting cgminer-nogpu and all it does is instantly crash and I have everything typed in properly and correct. I'm also using 3.3.2 like everyone is saying too...

You don't want 3.3.2 if you're using the UAT to COM driver.  Use 3.1.1 with the UAT to COM, or don't use the UAT to COM.

M

Switched to 3.1.1 didn't change a thing. Still says no USB detected.... and when i run the .bat it just crashes instantly again...

Figured it out:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4

when making the .bat file for 3.1.1. I deleted the strikedout portion of the above quote and cgminer would work with the asics. However instead of them appearing as COM or AMU, it shows up as ICA.

All mine show up as ICA.  I have 22 of them on one computer now with 3.1.1, and one long command line.

M

[kano]

...
Figured it out:

--icarus-options 115200:1:1 --icarus-timing 3.0=100 -S COM3 -S COM4

when making the .bat file for 3.1.1. I deleted the strikedout portion of the above quote and cgminer would work with the asics. However instead of them appearing as COM or AMU, it shows up as ICA.

If you don't use --icarus-options 115200:1:1 --icarus-timing 3.0=100 it will not report on the screen correctly and will probably not hash correctly

You should be using the latest 3.3.3

3.1.1 will show all Icarus driver devices as ICA no matter what they are (and requires -S)

3.3.3 uses the USB naming ICA/LLT/BLT/AMU/CMR and automatically sets the options and automatically finds them ... if you follow the simple documented instructions I wrote in cgminer ...

[ommfpt]

So I've tried this for the past few hours, but nothing is working. The program always tell me something like "error 0 on select in avalon_gets" and something about it not being an avalon. Anyone got anything?

Using 3.3.3. Tried with 3.1.1 and 3.2.1, but no dice on either.

[mdude77]

So I've tried this for the past few hours, but nothing is working. The program always tell me something like "error 0 on select in avalon_gets" and something about it not being an avalon. Anyone got anything?

Using 3.3.3. Tried with 3.1.1 and 3.2.1, but no dice on either.

The latest version is 3.4.0.

Using it for USB erupters is very different between 3.1.1 and newer version.  3.1.1 must have the USB to UART driver installed.  Newer versions must not.  What exactly are you trying?

M

[ommfpt]

So I've tried this for the past few hours, but nothing is working. The program always tell me something like "error 0 on select in avalon_gets" and something about it not being an avalon. Anyone got anything?

Using 3.3.3. Tried with 3.1.1 and 3.2.1, but no dice on either.

The latest version is 3.4.0.

Using it for USB erupters is very different between 3.1.1 and newer version.  3.1.1 must have the USB to UART driver installed.  Newer versions must not.  What exactly are you trying?

M

I have tried both 3.3.3 and 3.4.0 with no luck, but this may be because of the drivers that I had installed from trying with 3.1.1

edit: uninstalled drivers, now get "No devices detected!"