Quote from: twib2 on December 21, 2013, 09:25:45 AM

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

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.

My new Chili has been hashing well for a few days now, and I fairly often stop bfgminer and restart it with a different coin. However, just recently, it's gotten stuck in the startup process - #7 is blinking and it never gets farther than that. I've reseated the cooling solution 212EVO and even tried my H60 to no avail. I've reflashed the firmware 14e again to no avail. If I go ahead and try to use it after waiting "forever" of course bfgminer finds it just fine, but it's doing no hashing: 0 GH/s.

The weird thing is that nothing changed. Without me even being near it (ssh'd from upstairs to the miner computer), one time when I was switching coins it starting giving 0 GH/s. So I went downstairs to check on it. Rebooted the computer, and it, and all sorts of combinations, but nothing.

EDIT: Of course after I posted this, it decided to start working again. Not sure why, unless one of my many automatic resets of the USB bus slapped it around enough to realize that it was indeed cool enough. It's running below 70C now and hashing at 35GH/s with the cheap refurbished Corsair H60 on it - sweet!

Sorry for the "false" alarm, but I'm leaving it here in case a) someone might also benefit from knowing that they can wake up again on their own, or b) someone can help us avoid this altogether.

Cheers,
- Tye

This happens to me sometimes and unplugging power for a few seconds helps.