Quote from: CrazyGuy on November 01, 2013, 02:23:54 AM

Quote from: nwfella on October 31, 2013, 07:15:59 AM

Quote from: ChipGeek on October 25, 2013, 01:15:52 PM

Quote from: shade88 on October 25, 2013, 03:19:47 AM

Quote from: ysyang21 on October 25, 2013, 02:52:08 AM

Two out of them is harder to get them start mining, at the very first beginning. and it become harder and harder with each reboot. These two eventually cease to operate yesterday, until now (but still viewable in cgminer console)

I got 2 boards that won't boot up (2nd led keep blinking) but once I turn on the AC to cool the room they boot up in about 1 minute. After that they will hash just fine even with AC off.

When a board first starts up, the firmware makes sure the board and chips are cooled down before it starts the self test. This helps ensure the maximum number of engines (cores) will pass self test.

LED decoder ring

The LEDs are numbered 1 to 8 with #1 closest to the USB connector and #8 closest to the power and fan connectors. During first power up, LEDs 5, 6, 7, and 8 will light up and LEDs 1, 2, 3, and 4 will indicate a failure code if anything is wrong with the hardware. This happens VERY quickly - in less than a second.

If the initial hardware checks are good, #7 will blink indicating it is waiting for the board to cool down. This will always blink for a few seconds even if the board is cold.

Then #7 and #8 will blink indicating ASIC self test.

After that, 1, 2, 3, 4 will indicate how many jobs from cgminer are waiting to run in the input queue. LED 5 is just a debug output for me but it roughly indicates a job has completed - but sometimes blinks too fast for the human eye to see. Just ignore LED 5.

I am working on some firmware updates that will fix most (or all?) of the problems the boards are having. For example, one failure I think I have figured out is occasionally a board will jump to more than 100 GH/s but have 100% hardware errors. I have one board that does this once per day or so and needs to be rebooted. After chasing this for a while, I believe I have finally figured out what is going on and will have a fix in the next release.

I am having some serious difficulty getting either of my two chilis to run properly. After replacing my BFL drivers with Zadig v6.1.7600.16385 driver(s) and loading cgminer v3.6.6 I am getting the device to detect but getting the following output:
"AVA looking for AVA 0403:6001 but found 05e3:0608 instead" <---which varies at times
Any idea what may be causing this.

*Also, LED's 7 and 8 are flashing at different speeds (seven faster than eight), while LED's 2,3,4, and 5 are all solid green.

Any suggestions you might be able to offer would be greatly appreciated.

Vendor and product ID should be 0403:6014, not sure what that one is. Second id might be a hub(maybe try plugging directly into your controller). WinUSB driver installation can be a real pain when you already have a default set, like FTDI. Were you using bfgminer beforehand? I would suggest completely removing the existing drivers and then reinstalling with winusb. Once Winusb is the default driver for that device type, you won't have to go through the process again with each new device. Don't forget to unplug the device and re-plug it in after installing WinUSB drivers.

I was indeed using bfgminer beforehand. I'll go ahead and give your suggestion a try.

*Although I thought the LED's 7 and 8 where supposed to stop flashing at some point.