The Chili – 30+GH/s BFL based Bitcoin Miner Assembly

[nexus99]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

[Bargraphics]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

Try downloading 3.4.0

Haven't tried 3.5.0

[jelin1984]

which is final better for chilli

cgminer
or bfgminer?

[nexus99]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

Try downloading 3.4.0

Haven't tried 3.5.0

Tried both 32 and 64 bit (on a 64 bit OS) but no dice.

[Bargraphics]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

Try downloading 3.4.0

Haven't tried 3.5.0

Tried both 32 and 64 bit (on a 64 bit OS) but no dice.

Try the part in bold then run the latest BFGMiner

This is a workaround version of BFGMiner until a new firmware update for the chilis

Here's a modified version of BFGMiner, I also included the driver inside of it as well that should fix your problem. (I don't know much about CGMiner though)

http://www.speedyshare.com/uKncp/BFGMiner-Chili.zip

Open up bfgminer.conf and change the Pool and Username to whatever you want (It currently uses mine so make sure you change it)
Run CDM v2.08.30 WHQL Certified.exe to install the correct driver for windows

Once you do both of those, just open up bfgminer.exe and it should read from the config automatically and start hashing for you.
If it doesn't see the Chili, all you have to do is keep BFGMiner open, unplug the USB, Plug it back in, press M then + then type all or auto and enter. It should find it.

Please note if it still isn't working then you need to exit BFGMiner, unplug you chili power, plug it back in and wait for all the lights to stop blinking. If you try to find the miner while it's "Booting up" it will have issues.
"Booting Up" is the two most right LEDs (Closer to the Power) blinking back and forth. Again once all the LEDs are not blinking anymore it should be ready to start hashing, start your BFGMiner and follow the above steps.

Let me know if this helps

[nexus99]

I took the back plate off of a chili, replaced the pad with cream and pointed a fan at the back. Added 4 GH/S. Not sure which thing did which... but something there helped out.

[Keefe]

Probably the added airflow over the back of the regulator area.

[i3luefire]

update on second batch pcb issue?

 

[Luke-Jr]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

No, WinUSB is always the wrong driver for ASICs.
Chilis are FTDI: http://ftdichip.com/Drivers/VCP.htm

[Luke-Jr]

These is new firmware?
How I install it?

No, it's the same firmware that shipped on the second half of the first batch.

Open ChiliFlash, and select the Chili that needs to be flashed from the drop down menu. Browse the the ChiliFW14c.hex hex file, and then hit program. The LEDs on the board should binary count quickly, and when it's done it will prompt to power cycle the unit and the LEDs should flash outer 4 then inner 4 until you do.

Is there a way to determine a board's current firmware version with a serial console? I don't know if I already have 14c, and they're connected to a linux pc. I tried the ZCX command but the output doesn't appear to include the firmware version.

No, not right now. Unfortunately cgminer uses the FW version to determine if it should be using per chip or per board work queuing, so we need to keep 1.0.0. I've edited my personal copy to report back 1.0.14c and it works although cgminer throws a warning. I haven't tested it on Bitminter or bfg though so I don't want to do it until I have a chance to test it in case that breaks compatibility. It's definitely on the to do list though.

BFGMiner doesn't do anything based on the version (because that'd be stupid and cause problems like you've found..).

[nexus99]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

No, WinUSB is always the wrong driver for ASICs.
Chilis are FTDI: http://ftdichip.com/Drivers/VCP.htm

Interesting. I am using WinUSB CGMINER. That would explain why BFG miner isn't working though.

[Luke-Jr]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

No, WinUSB is always the wrong driver for ASICs.
Chilis are FTDI: http://ftdichip.com/Drivers/VCP.htm

Interesting. I am using WinUSB CGMINER. That would explain why BFG miner isn't working though.

Yes, cgminer requires the wrong driver.
But we were talking about BFGMiner...

[daemonfox]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

No, WinUSB is always the wrong driver for ASICs.
Chilis are FTDI: http://ftdichip.com/Drivers/VCP.htm

Interesting. I am using WinUSB CGMINER. That would explain why BFG miner isn't working though.

Yes, cgminer requires the wrong driver.
But we were talking about BFGMiner...

curious why this is "wrong" with cgminer? Is there a performance gain using FTDI with BFG?

[Luke-Jr]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

No, WinUSB is always the wrong driver for ASICs.
Chilis are FTDI: http://ftdichip.com/Drivers/VCP.htm

Interesting. I am using WinUSB CGMINER. That would explain why BFG miner isn't working though.

Yes, cgminer requires the wrong driver.
But we were talking about BFGMiner...

curious why this is "wrong" with cgminer? Is there a performance gain using FTDI with BFG?

It's wrong because FTDI made the chip and only supports their own driver on Windows.
Also because cgminer's replacement driver (only built on top of WinUSB) doesn't provide the standard VCOM interfaces the chip is supposed to have.

[btchedge]

Hey MrTeal & ChipGeek,

I have a couple questions that others may have as well.

1. What is the recommended fix for a board that shows up in CG or BFG but just never hashes? LEDs 1-4 are solid and then 7 & 8 may blink or remain solid. Device shows up as enabled and send temp reading but never hashes.

2. What is the recommended fix for a board that consistently starts showing a hash rate of 200GH+ and its all hardware errors?

3. Is there any known method to override the throttling at current temp settings other than a firmware change?

Thanks again for the great boards!

[ChipGeek]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

No, WinUSB is always the wrong driver for ASICs.
Chilis are FTDI: http://ftdichip.com/Drivers/VCP.htm

Keep this political shit out of our thread.

cgminer requires the WinUSB driver.
bfgminer requires the FTDI serial driver.

[Luke-Jr]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

No, WinUSB is always the wrong driver for ASICs.
Chilis are FTDI: http://ftdichip.com/Drivers/VCP.htm

Keep this political shit out of our thread.

cgminer requires the WinUSB driver.
bfgminer requires the FTDI serial driver.

Nothing political about it, just answering his question.

[ChipGeek]

Hey MrTeal & ChipGeek,

I have a couple questions that others may have as well.

1. What is the recommended fix for a board that shows up in CG or BFG but just never hashes? LEDs 1-4 are solid and then 7 & 8 may blink or remain solid. Device shows up as enabled and send temp reading but never hashes.

2. What is the recommended fix for a board that consistently starts showing a hash rate of 200GH+ and its all hardware errors?

3. Is there any known method to override the throttling at current temp settings other than a firmware change?

Thanks again for the great boards!

1. Update to the newest firmware.  This is a known issue with the new Rev B ASIC chips that we did not see in the older Rev A samples.

2. Rebooting the board will fix the problem if it is what I think it is.  If rebooting never helps, then send MrTeal a PM for directions on what to do next.  I will have a firmware fix for this but have been busy with real life stuff and getting batch 2 built.

3. No other than keep the board cooler with a better heatsink or TIM.  We plan to have a firmware update to assist you in having more control over this.  (See excuses in #2)

Please remember, we're a very small team - not a swarm of locusts. 

[ChipGeek]

I am searching for BFGMiner love. I have the newest version 3.5 running but it doesn't identify my miners. Is WinUSB the correct USB driver to use?

No, WinUSB is always the wrong driver for ASICs.
Chilis are FTDI: http://ftdichip.com/Drivers/VCP.htm

Keep this political shit out of our thread.

cgminer requires the WinUSB driver.
bfgminer requires the FTDI serial driver.

Nothing political about it, just answering his question.

Except that WinUSB *IS* the correct driver for ASICs if using cgminer.

End of topic.

[MrTeal]

update on second batch pcb issue?

 

The PCB fab has the PCBs back, and spent time today recalibrating their air knife. They're confident going forward, and they should be fixing the boards up on 3rd shift tonight and they should be done tomorrow morning. We'll get them back Friday and they'll be inspected to make doubly sure they're ready to go.

In retrospect, it was a mistake to go with HASL instead of ENIG (Electroless Nickel Immersion Gold). ENIG is the better process for pad levelness, but we had good results with HASL before. I was going to make the switch anyway, but it would have added a couple days to the timeline and we wouldn't have gotten started until today or so and I didn't want to do that. It turns out it would have saved time in the end with the poor work since we now won't have boards coming off the line this week anyway.