The Habanero - 650GH/s - OOS

[MrTeal]

After running fine with zero issues forever, I'm now getting a ZOMBIE status in cgminer with the following error displayed in the console:

ERR: Asked to memcpy 0 bytes from usbutils.c _usb_read(): 3075
HFA: OP_USB_INIT failed! Operation status 20 (Regulator programming error)

I've tried cycling power, restarting, doesnt seem to help.

Any ideas? 

Any time I've seen that error it was a loose or disco'd power connector or the PSU wasn't turned on.  Have you tried a different supply?

I did, tried another supply that is guaranteed working, and got the same error.

Did you unplug the USB cable when you changed power supplies?

[1715272273]

1715272273

[1715272273]

1715272273

[1715272273]

1715272273

[1715272273]

1715272273

[1715272273]

1715272273

[1715272273]

1715272273

[Batshark]

After running fine with zero issues forever, I'm now getting a ZOMBIE status in cgminer with the following error displayed in the console:

ERR: Asked to memcpy 0 bytes from usbutils.c _usb_read(): 3075
HFA: OP_USB_INIT failed! Operation status 20 (Regulator programming error)

I've tried cycling power, restarting, doesnt seem to help.

Any ideas? 

Any time I've seen that error it was a loose or disco'd power connector or the PSU wasn't turned on.  Have you tried a different supply?

I did, tried another supply that is guaranteed working, and got the same error.

Did you unplug the USB cable when you changed power supplies?

I don't think so, I powered down PSU 1, swapped PCI connectors to PSU 2, and powered up PSU 2. At what point should I unplug USB and plug it back in?

[MrTeal]

After running fine with zero issues forever, I'm now getting a ZOMBIE status in cgminer with the following error displayed in the console:

ERR: Asked to memcpy 0 bytes from usbutils.c _usb_read(): 3075
HFA: OP_USB_INIT failed! Operation status 20 (Regulator programming error)

I've tried cycling power, restarting, doesnt seem to help.

Any ideas? 

Any time I've seen that error it was a loose or disco'd power connector or the PSU wasn't turned on.  Have you tried a different supply?

I did, tried another supply that is guaranteed working, and got the same error.

Did you unplug the USB cable when you changed power supplies?

I don't think so, I powered down PSU 1, swapped PCI connectors to PSU 2, and powered up PSU 2. At what point should I unplug USB and plug it back in?

While the 12V power is off. Because the board can be powered over USB (at least the microcontroller), it never really fully power cycles if you just remove the 12V.

[h@shKraker]

Anyone have instructions on how to reflash these boards?

Just posted.
https://peppermining.com/flashing-the-firmware-on-a-habanero/

Mr. Teal,

Is there any chance this updated firmware and firmware update process would work with a HF BabyJet board?

H@shKraker

[MrTeal]

Anyone have instructions on how to reflash these boards?

Just posted.
https://peppermining.com/flashing-the-firmware-on-a-habanero/

Mr. Teal,

Is there any chance this updated firmware and firmware update process would work with a HF BabyJet board?

H@shKraker

The firmware update process should be the same, but the firmware itself is different. I'm not sure it would explicitly break a Babyjet board, but I wouldn't try it.

[Batshark]

After running fine with zero issues forever, I'm now getting a ZOMBIE status in cgminer with the following error displayed in the console:

ERR: Asked to memcpy 0 bytes from usbutils.c _usb_read(): 3075
HFA: OP_USB_INIT failed! Operation status 20 (Regulator programming error)

I've tried cycling power, restarting, doesnt seem to help.

Any ideas? 

Any time I've seen that error it was a loose or disco'd power connector or the PSU wasn't turned on.  Have you tried a different supply?

I did, tried another supply that is guaranteed working, and got the same error.

Did you unplug the USB cable when you changed power supplies?

I don't think so, I powered down PSU 1, swapped PCI connectors to PSU 2, and powered up PSU 2. At what point should I unplug USB and plug it back in?

While the 12V power is off. Because the board can be powered over USB (at least the microcontroller), it never really fully power cycles if you just remove the 12V.

I've completely powered down the board (both 12V and USB unplugged). Then I plugged in USB first, then 12V. I still the the same repeating reset cycle with that error.

[daddyfatsax]

So I got the new firmware installed, but I don't see any other temps in the app. How do I see what the VRM temps are?

[MrTeal]

So I got the new firmware installed, but I don't see any other temps in the app. How do I see what the VRM temps are?

The app hasn't been updated yet. It's in the API and debug data though.

[r00t$]

I have Ubuntu running fine in a VM and the HF-tool works as desired, but I am having problems updating firmware.

When I run the update command, it finds the device, retrieves the serial OK, but eventually give me an error.

Any thoughts?

Code:

xxx@MINER:~/hf-tool/firmware-20140713-0$ lsusb
Bus 001 Device 028: ID 297c:8001  
Bus 001 Device 012: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
rkotsybar@MINER:~/hf-tool/firmware-20140713-0$ ./field_firmware_update.py
('confirm is ', False)
('FIRMWARE_DIR is ', '.')
UC_HFU_FILE at './uc3.cropped.hfu'.
READSERIAL found at 'i686/readserial'.
HFUPDATE found at 'i686/hfupdate'.
ENTERLOADER found at 'i686/enterloader'.

HashFast Firmware Updater

Please connect HashFast device to update.
Enumerating modules...
Found 1 modules.
Loading Firmware...
Updating module 0...
hfupdate v0.1
module chain config 1 master 1 slaves 0
module 0 version 0x80000003 crc 0x23ed99de
module 0 serial number: 25 1f de 78 74 34 9c 34 15 35 09 43 17 87 6c b7 
done
hfupdate v0.1
module chain config 1 master 1 slaves 0
module 0 version 0x80000003 crc 0x23ed99de
module 0 serial number: 25 1f de 78 74 34 9c 34 15 35 09 43 17 87 6c b7 
done
Traceback (most recent call last):
  File "./field_firmware_update.py", line 184, in <module>
    firmware_updater()
  File "./field_firmware_update.py", line 160, in firmware_updater
    wait_for_device([(USBID_HF_VID, USBID_HF_PID)], 10)
  File "./field_firmware_update.py", line 114, in wait_for_device
    raise Exception("Error: timeout.  Failed to find device.")
Exception: Error: timeout.  Failed to find device.
Error: timeout.  Failed to find device.
Firmware Update had an error.  Please retry or report to HashFast Support.
xxx@MINER:~/hf-tool/firmware-20140713-0$ 

[xjack]

So I got the new firmware installed, but I don't see any other temps in the app. How do I see what the VRM temps are?

If you don't want to wait for the pepper app, the vrm temps show in cgminer's miner.php.

[MrTeal]

I have Ubuntu running fine in a VM and the HF-tool works as desired, but I am having problems updating firmware.

When I run the update command, it finds the device, retrieves the serial OK, but eventually give me an error.

Any thoughts?

Code:

xxx@MINER:~/hf-tool/firmware-20140713-0$ lsusb
Bus 001 Device 028: ID 297c:8001  
Bus 001 Device 012: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
rkotsybar@MINER:~/hf-tool/firmware-20140713-0$ ./field_firmware_update.py
('confirm is ', False)
('FIRMWARE_DIR is ', '.')
UC_HFU_FILE at './uc3.cropped.hfu'.
READSERIAL found at 'i686/readserial'.
HFUPDATE found at 'i686/hfupdate'.
ENTERLOADER found at 'i686/enterloader'.

HashFast Firmware Updater

Please connect HashFast device to update.
Enumerating modules...
Found 1 modules.
Loading Firmware...
Updating module 0...
hfupdate v0.1
module chain config 1 master 1 slaves 0
module 0 version 0x80000003 crc 0x23ed99de
module 0 serial number: 25 1f de 78 74 34 9c 34 15 35 09 43 17 87 6c b7 
done
hfupdate v0.1
module chain config 1 master 1 slaves 0
module 0 version 0x80000003 crc 0x23ed99de
module 0 serial number: 25 1f de 78 74 34 9c 34 15 35 09 43 17 87 6c b7 
done
Traceback (most recent call last):
  File "./field_firmware_update.py", line 184, in <module>
    firmware_updater()
  File "./field_firmware_update.py", line 160, in firmware_updater
    wait_for_device([(USBID_HF_VID, USBID_HF_PID)], 10)
  File "./field_firmware_update.py", line 114, in wait_for_device
    raise Exception("Error: timeout.  Failed to find device.")
Exception: Error: timeout.  Failed to find device.
Error: timeout.  Failed to find device.
Firmware Update had an error.  Please retry or report to HashFast Support.
xxx@MINER:~/hf-tool/firmware-20140713-0$ 

It looks like it updated ok. The firmware update python script can be a little flaky in a VM because it's expecting to have the unit there after a reset, not have the VM have to pull it back in from Windows.

[r00t$]

I have Ubuntu running fine in a VM and the HF-tool works as desired, but I am having problems updating firmware.

When I run the update command, it finds the device, retrieves the serial OK, but eventually give me an error.

Any thoughts?

Code:

xxx@MINER:~/hf-tool/firmware-20140713-0$ lsusb
Bus 001 Device 028: ID 297c:8001  
Bus 001 Device 012: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
rkotsybar@MINER:~/hf-tool/firmware-20140713-0$ ./field_firmware_update.py
('confirm is ', False)
('FIRMWARE_DIR is ', '.')
UC_HFU_FILE at './uc3.cropped.hfu'.
READSERIAL found at 'i686/readserial'.
HFUPDATE found at 'i686/hfupdate'.
ENTERLOADER found at 'i686/enterloader'.

HashFast Firmware Updater

Please connect HashFast device to update.
Enumerating modules...
Found 1 modules.
Loading Firmware...
Updating module 0...
hfupdate v0.1
module chain config 1 master 1 slaves 0
module 0 version 0x80000003 crc 0x23ed99de
module 0 serial number: 25 1f de 78 74 34 9c 34 15 35 09 43 17 87 6c b7 
done
hfupdate v0.1
module chain config 1 master 1 slaves 0
module 0 version 0x80000003 crc 0x23ed99de
module 0 serial number: 25 1f de 78 74 34 9c 34 15 35 09 43 17 87 6c b7 
done
Traceback (most recent call last):
  File "./field_firmware_update.py", line 184, in <module>
    firmware_updater()
  File "./field_firmware_update.py", line 160, in firmware_updater
    wait_for_device([(USBID_HF_VID, USBID_HF_PID)], 10)
  File "./field_firmware_update.py", line 114, in wait_for_device
    raise Exception("Error: timeout.  Failed to find device.")
Exception: Error: timeout.  Failed to find device.
Error: timeout.  Failed to find device.
Firmware Update had an error.  Please retry or report to HashFast Support.
xxx@MINER:~/hf-tool/firmware-20140713-0$ 

It looks like it updated ok. The firmware update python script can be a little flaky in a VM because it's expecting to have the unit there after a reset, not have the VM have to pull it back in from Windows.

Thanks for taking a look. I figured it may have updated alright. Windows will sometimes steal the USB device if I use Ubuntu to run cgminer. It can run fine for days, then Windows will suddenly decide it wants the device back. Probably some obscure registry setting to adjust...

Maybe it's time to break the bank and buy one of those new Ras-Pi B+ 

[GenTarkin]

Am i right in assuming flashing the new firmware will set the voltages back to default?

[MrTeal]

Am i right in assuming flashing the new firmware will set the voltages back to default?

No, it shouldn't affect the voltages or the name of the device.

[GenTarkin]

Am i right in assuming flashing the new firmware will set the voltages back to default?

No, it shouldn't affect the voltages or the name of the device.

Ah ok, also , how do you set the name?

[JakeTri]

Am i right in assuming flashing the new firmware will set the voltages back to default?

No, it shouldn't affect the voltages or the name of the device.

Ah ok, also , how do you set the name?

To set device name use:

Code:

cgminer --hfa-name "name"

[GenTarkin]

Am i right in assuming flashing the new firmware will set the voltages back to default?

No, it shouldn't affect the voltages or the name of the device.

Ah ok, also , how do you set the name?

To set device name use:

Code:

cgminer --hfa-name "name"

How about for different devices(habs) on same cgminer instance?

[JakeTri]

Am i right in assuming flashing the new firmware will set the voltages back to default?

No, it shouldn't affect the voltages or the name of the device.

Ah ok, also , how do you set the name?

To set device name use:

Code:

cgminer --hfa-name "name"

How about for different devices(habs) on same cgminer instance?

Device name is saved to the board flash so you need to set the device name only once for each board.
Use "--usb" to specify the board when you have multiple connected to the same system.  For example to set name "hab1" for habanero board connected as device 5 from usb bus 2 use:

Code:

--hfa-name hab1 --usb 2:5

To get the usb bus ID and device ID use "lsusb" as described in cgminer ASIC-README file.

[Batshark]

After running fine with zero issues forever, I'm now getting a ZOMBIE status in cgminer with the following error displayed in the console:

ERR: Asked to memcpy 0 bytes from usbutils.c _usb_read(): 3075
HFA: OP_USB_INIT failed! Operation status 20 (Regulator programming error)

I've tried cycling power, restarting, doesnt seem to help.

Any ideas? 

Any time I've seen that error it was a loose or disco'd power connector or the PSU wasn't turned on.  Have you tried a different supply?

I did, tried another supply that is guaranteed working, and got the same error.

Did you unplug the USB cable when you changed power supplies?

I don't think so, I powered down PSU 1, swapped PCI connectors to PSU 2, and powered up PSU 2. At what point should I unplug USB and plug it back in?

While the 12V power is off. Because the board can be powered over USB (at least the microcontroller), it never really fully power cycles if you just remove the 12V.

I've completely powered down the board (both 12V and USB unplugged). Then I plugged in USB first, then 12V. I still the the same repeating reset cycle with that error.

Is there anymore information I can provide to get someone to help me figure out what is going on? I'm now 3 days down with ZERO direction. I'm completely at a loss here

[MedinaMiner]

I've just purchased a couple of Habanero's, and in the process of bringing them up.

Neither seems to work like I would expect them to.

I have read through all of this thread, researched the Habanero website, pulled hair... lost sleep... to no avail.

I think that the problem has to do with the Habanero making 'contact' with the miner. (Not sure of the technical terms)

It appears that the actual Habanero is working. I can issue a cgminer --benchmark and it starts up and merrily runs hashing away happily... too bad I can't grab some of those and toss them into my wallet.

So - here is my cg.bat - which has been edited many times to try different things, but nothing seems to be the correct combination...

cgminer -o http://stratum.btcguild.com:3333 -u {user} -p {xxxx} --hfa-name OZ --usb 2:3 --hfa-fan 100 --hfa-temp-target 0 --hfa-temp-overheat 103 --hfa-fail-drop 0 --hfa-hash-clock 300 --api-port 4028 --verbose 2>>logfile_hab.txt

I have found that the --verbose is really handy in helping to debug... but the output is cryptic to me. Perhpas someone more knowledgeable will see what I am doing wrong...

 [2014-07-17 20:10:27] Started cgminer 4.4.1
 [2014-07-17 20:10:29] HFA: Found device with name OZ
 [2014-07-17 20:10:30] Probing for an alive pool
 [2014-07-17 20:10:30] HFA : Sending OP_USB_INIT with GWQ protocol specified
 [2014-07-17 20:10:30] Testing pool http://stratum.btcguild.com:3333
 [2014-07-17 20:10:30] HTTP request failed: Empty reply from server
 [2014-07-17 20:10:30] HTTP request failed: Empty reply from server
 [2014-07-17 20:10:31] JSON-RPC decode failed: (unknown reason)
 [2014-07-17 20:10:31] Pool 0 difficulty changed to 2
 [2014-07-17 20:10:31] Closing socket for stratum pool 0
 [2014-07-17 20:10:33] HFB :      firmware_rev:    0.5
 [2014-07-17 20:10:33] HFB :      hardware_rev:    1.1
 [2014-07-17 20:10:33] HFB :      serial number:   9e4c7500
 [2014-07-17 20:10:33] HFB :      hash clockrate:  300 Mhz
 [2014-07-17 20:10:33] HFB :      inflight_target: 768
 [2014-07-17 20:10:34] HFB :      sequence_modulus: 2048
 [2014-07-17 20:10:36] Testing pool http://stratum.btcguild.com:3333
 [2014-07-17 20:10:37] Pool 0 difficulty changed to 2
 [2014-07-17 20:10:37] Closing socket for stratum pool 0
 [2014-07-17 20:10:42] Testing pool http://stratum.btcguild.com:3333
 [2014-07-17 20:10:43] Pool 0 difficulty changed to 2
 [2014-07-17 20:10:43] Closing socket for stratum pool 0
 [2014-07-17 20:10:44] Waiting for work to be available from pools.
 [2014-07-17 20:10:48] Testing pool http://stratum.btcguild.com:3333
 [2014-07-17 20:10:48] Pool 0 difficulty changed to 2
 [2014-07-17 20:10:49] Closing socket for stratum pool 0

I have a few more details, but am not sure which ones may be relevant. Feel free to beat me over the head... I'm a newbie.

Please help... please???

Thanks in advance...

James