Avalon2 based miner from Technobit - HEX16A2

[stiffla]

no
u should use fetch from git. the patch filename is the commit id ur supposed to use
Lets say you wanna use 2e9afa38e39678a5dc5bf8be6d20baf1849b548c.patch

Code:

git clone https://github.com/ckolivas/cgminer.git
cd cgminer
wget https://www.dropbox.com/s/5suzudn2t06087u/2e9afa38e39678a5dc5bf8be6d20baf1849b548c.patch
git checkout 2e9afa38e39678a5dc5bf8be6d20baf1849b548c
patch -p1 < 2e9afa38e39678a5dc5bf8be6d20baf1849b548c.patch
./autogen.sh --enable-avalon --enable-bitfury --enable-hexminera --enable-hexminerb --enable-hexminerc 
make

doing the git checkout thingy makes sure u r at the exact version the patch was made for.

Alright, thank you, the make process worked fine now.
Unfortunately, I am not able to test it right now since I'm not home, but i will give feedback.
Thanks man!!!

[stiffla]

Well,

I am not able to get the board running again:

After make process, i tried to start cgminer with the following instructions:

1:

Code:

--hexminerc-voltage 1060 --hexminerc-options 16:1400 

error message:

Code:

-bash: --hexminerc-voltage: command not found

2:

Code:

sudo ./cgminer --hexminerc-voltage 1060 --hexminerc-options 16:1400 --set_default_to_c

error message:

Code:

[2013-12-26 15:19:19] ./cgminer: --set_default_to_c: unrecognized option  

3: Cgminer only starts this way:

Code:

sudo ./cgminer --hexminerc-voltage 1060 --hexminerc-options 16:1400

but only recognizing HEXa:


Edit:
with the parameter

Code:

sudo ./cgminer --hexminera-voltage 1120 --hexminera-options 16:1500

it starts mining for 5 seconds and the pi freezes

[turtle83]

Well,

I am not able to get the board running again:

After make process, i tried to start cgminer with the following instructions:

1:

Code:

--hexminerc-voltage 1060 --hexminerc-options 16:1400 

error message:

Code:

-bash: --hexminerc-voltage: command not found

2:

Code:

sudo ./cgminer --hexminerc-voltage 1060 --hexminerc-options 16:1400 --set_default_to_c

error message:

Code:

[2013-12-26 15:19:19] ./cgminer: --set_default_to_c: unrecognized option  

3: Cgminer only starts this way:

Code:

sudo ./cgminer --hexminerc-voltage 1060 --hexminerc-options 16:1400

but only recognizing HEXa:
http://www.bilder-upload.eu/upload/70126b-1388071301.jpg

Edit:
with the parameter

Code:

sudo ./cgminer --hexminera-voltage 1120 --hexminera-options 16:1500

it starts mining for 5 seconds and the pi freezes

i dont have a hex16A2... but u could try

Code:

sudo ./cgminer --hexminera-voltage 1120 --hexminera-options 16:1500 --text-only --debug

that should spit out loads of things... paste the full output here maybe something stands out...

pi freezing also sounds like power issues.... how are you powering the pi? and are you providing enough power to the miners?

[stiffla]

[quote)

i dont have a hex16A2... but u could try

Code:

sudo ./cgminer --hexminera-voltage 1120 --hexminera-options 16:1500 --text-only --debug

that should spit out loads of things... paste the full output here maybe something stands out...

pi freezing also sounds like power issues.... how are you powering the pi? and are you providing enough power to the miners?
[/quote]

Code:

pi@raspberrypi ~/cgminer $ sudo ./cgminer --hexminera-voltage 1120 --hexminera-options 16:1500 --text-only --debug
 [2013-12-26 17:03:55] Started cgminer 3.8.1
 [2013-12-26 17:03:55] USB scan devices: checking for HEXa devices              
 [2013-12-26 17:03:55] RES: thread starting
 [2013-12-26 17:03:55] HEXa looking for and found HEXa 04d8:000a                
 [2013-12-26 17:03:55] USB lock hexminera 1-5
 [2013-12-26 17:03:55] RES: hexminera (1:5) lock=1
 [2013-12-26 17:03:55] USB res lock hexminera 1-5
 [2013-12-26 17:03:55] RES: hexminera (1:5) lock ok=1
 [2013-12-26 17:03:55] USB init, kernel attached ... - HEXa device 1:5          
 [2013-12-26 17:03:55] USB init, kernel detached ifinfo 0 interface 1 successfully - HEXa device 1:5
 [2013-12-26 17:03:55] USB init - HEXa device 1:5 usbver=0200 prod='' manuf='' serial=''
 [2013-12-26 17:03:55] HEXa looking for HEXa 04d8:000a but found 0424:ec00 instead
 [2013-12-26 17:03:55] HEXa looking for HEXa 04d8:000a but found 0424:9512 instead
 [2013-12-26 17:03:55] HEXa looking for HEXa 04d8:000a but found 1d6b:0002 instead
 [2013-12-26 17:03:55] USB scan devices: checking for HEXb devices              
 [2013-12-26 17:03:55] HEXb looking for HEXb 04d8:000b but found 04d8:000a instead
 [2013-12-26 17:03:55] HEXb looking for and found HEXb 04d8:000a                
 [2013-12-26 17:03:55] HEXb looking for HEXb 04d8:000b but found 0424:ec00 instead
 [2013-12-26 17:03:55] HEXb looking for HEXb 04d8:000a but found 0424:ec00 instead
 [2013-12-26 17:03:55] HEXb looking for HEXb 04d8:000b but found 0424:9512 instead
 [2013-12-26 17:03:55] HEXb looking for HEXb 04d8:000a but found 0424:9512 instead
 [2013-12-26 17:03:55] HEXb looking for HEXb 04d8:000b but found 1d6b:0002 instead
 [2013-12-26 17:03:55] HEXb looking for HEXb 04d8:000a but found 1d6b:0002 instead
 [2013-12-26 17:03:55] USB scan devices: checking for HEXc devices              
 [2013-12-26 17:03:56] HEXc looking for and found HEXc 04d8:000a                
 [2013-12-26 17:03:56] HEXc looking for HEXc 04d8:000a but found 0424:ec00 instead
 [2013-12-26 17:03:56] HEXc looking for HEXc 04d8:000a but found 0424:9512 instead
 [2013-12-26 17:03:56] HEXc looking for HEXc 04d8:000a but found 1d6b:0002 instead
 [2013-12-26 17:03:56] USB scan devices: checking for BF1 devices               
 [2013-12-26 17:03:56] BF1 looking for BF1 03eb:204b but found 04d8:000a instead
 [2013-12-26 17:03:56] BF1 looking for BF1 03eb:204b but found 0424:ec00 instead
 [2013-12-26 17:03:56] BF1 looking for BF1 03eb:204b but found 0424:9512 instead
 [2013-12-26 17:03:56] BF1 looking for BF1 03eb:204b but found 1d6b:0002 instead
 [2013-12-26 17:03:56] USB scan devices: checking for AVA devices               
 [2013-12-26 17:03:56] AVA looking for BTB 0403:6001 but found 04d8:000a instead
 [2013-12-26 17:03:56] AVA looking for BBF 0403:6001 but found 04d8:000a instead
 [2013-12-26 17:03:56] AVA looking for AVA 0403:6001 but found 04d8:000a instead
 [2013-12-26 17:03:56] AVA looking for BTB 0403:6001 but found 0424:ec00 instead
 [2013-12-26 17:03:56] AVA looking for BBF 0403:6001 but found 0424:ec00 instead
 [2013-12-26 17:03:56] AVA looking for AVA 0403:6001 but found 0424:ec00 instead
 [2013-12-26 17:03:56] AVA looking for BTB 0403:6001 but found 0424:9512 instead
 [2013-12-26 17:03:56] AVA looking for BBF 0403:6001 but found 0424:9512 instead
 [2013-12-26 17:03:56] AVA looking for AVA 0403:6001 but found 0424:9512 instead
 [2013-12-26 17:03:56] AVA looking for BTB 0403:6001 but found 1d6b:0002 instead
 [2013-12-26 17:03:56] AVA looking for BBF 0403:6001 but found 1d6b:0002 instead
 [2013-12-26 17:03:56] AVA looking for AVA 0403:6001 but found 1d6b:0002 instead
 [2013-12-26 17:03:56] Need to specify at least one pool server.                
 [2013-12-26 17:03:56] Pool setup failed

pi is powerd with a 700mA mobile phone charger for a LG nexus.
there should be enough power for the miners, it has been running under linux since sunday without any problems

[2GOOD]

I was not able to run stable A and A2 on the same Ubuntu host, either one is working fine alone.
Also AFAIK it is best to power the Pi/usb hub from the same power source as HEX16A.

[stiffla]

I was not able to run stable A and A2 on the same Ubuntu host, either one is working fine alone.
Also AFAIK it is best to power the Pi/usb hub from the same power source as HEX16A.

I don't understand why the A2 board was recognized on monday as HEXcand has been running ever since und your Ubunto version, and now i wanted to try it again, because on my pi it won't work,
it is also only been recognized as HEXa which is wrong in my opinion.

Edit:
I claim, that the patch is not working, because if I use ./autogen.sh --enable-hexminerc, there is still the undefined reference to SHA256 in the make process.

[loshia]

I was not able to run stable A and A2 on the same Ubuntu host, either one is working fine alone.
Also AFAIK it is best to power the Pi/usb hub from the same power source as HEX16A.

Strange?
On my tplink both fly....
Which version are you using?

[2GOOD]

I was not able to run stable A and A2 on the same Ubuntu host, either one is working fine alone.
Also AFAIK it is best to power the Pi/usb hub from the same power source as HEX16A.

Strange?
On my tplink both fly....
Which version are you using?

I believe the problem is with my HEX16A, mine is one of the first devices with older firmware and it is recognized by cgminer as:

Code:

 .USB dev 0: Bus 2 Device 11 ID: 04d8:000a
  Manufacturer: 'Microchip Technology Inc.'
  Product: 'CDC RS-232 Emulation Demo'

while HEX16A2 is:

Code:

 .USB dev 0: Bus 5 Device 4 ID: 04d8:000a
  Manufacturer: 'TECHNOBIT HEX ASIC Miner.'
  Product: 'HEX16C-Avalon2 ASIC Miner'

When both are connected on same host either one is detected wrong, I was able to run them manually with --usb select but it was not a good solution and I've moved the one to other host - problem solved for me.

This was with the old patch - 7ddb94d6964f2451d2e76f70b069dfdf2b3d4d6f.patch
It might be possible to edit the patch and force it to detect 'CDC RS-232 Emulation Demo' as HEX16A, but never tried it.

[loshia]

I was not able to run stable A and A2 on the same Ubuntu host, either one is working fine alone.
Also AFAIK it is best to power the Pi/usb hub from the same power source as HEX16A.

Strange?
On my tplink both fly....
Which version are you using?

I believe the problem is with my HEX16A, mine is one of the first devices with older firmware and it is recognized by cgminer as:

Code:

 .USB dev 0: Bus 2 Device 11 ID: 04d8:000a
  Manufacturer: 'Microchip Technology Inc.'
  Product: 'CDC RS-232 Emulation Demo'

while HEX16A2 is:

Code:

 .USB dev 0: Bus 5 Device 4 ID: 04d8:000a
  Manufacturer: 'TECHNOBIT HEX ASIC Miner.'
  Product: 'HEX16C-Avalon2 ASIC Miner'

When both are connected on same host either one is detected wrong, I was able to run them manually with --usb select but it was not a good solution and I've moved the one to other host - problem solved for me.

This was with the old patch - 7ddb94d6964f2451d2e76f70b069dfdf2b3d4d6f.patch
It might be possible to edit the patch and force it to detect 'CDC RS-232 Emulation Demo' as HEX16A, but never tried it.

That is why set-default-to-a is there. In case of USB detect errors HexB and C are ok though and are detected fine. The issue is that devid/vendid is equal on all hex boards and HexA is missing proper description string - not present. You can try 1.3 cgminer 3.8.5 all works even nanos

[VForrest]

Hi all,

I hope someone can give me an answer / solution to my problem. I just received my HEX16A2 today and connected it to my Windows laptop to test it, but got issues with Hexminer. Following error message is being spammed in the entire miner_proxy. Tested both older and the newest version, but still the same error message. It seem to be able to connect to the pool but when start mining it doesn't seem to be able to get any further.

2013-12-28 00:44:58,982 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:58,984 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,012 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,013 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,032 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,033 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,042 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,043 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,069 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,071 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,078 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,082 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,101 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,105 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,141 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,144 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,151 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,154 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,167 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,170 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,187 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,190 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,197 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,200 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,217 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,220 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:44:59,234 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:44:59,237 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:00,792 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:00,796 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:02,351 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:02,354 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:03,907 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:03,911 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:05,467 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:05,470 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:07,026 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:07,029 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:08,588 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:08,592 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:10,154 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:10,157 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:11,711 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:11,714 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:13,267 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:13,270 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:13,759 INFO proxy client_service.handle_event # New job 54881 f
or prevhash fb52f083, clean_jobs=False
2013-12-28 00:45:14,832 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:31,726 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:33,335 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:33,338 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:34,891 WARNING proxy getwork_listener.render_POST # Authorizati
on required
2013-12-28 00:45:34,894 INFO proxy getwork_listener._on_authorized # Worker 'vfo
rrest_1' asks for new work
2013-12-28 00:45:44,058 INFO proxy client_service.handle_event # New job 54882 f
or prevhash fb52f083, clean_jobs=False

Have I configured it wrong or what could be the reason of these errors?  


Thanks in advanced!

[acidfox]

Have I configured it wrong or what could be the reason of these errors?  
Thanks in advanced!

try it with 1500 Mhz / 1150mV

https://bitcointalk.org/index.php?topic=323727.msg3599912#msg3599912

[Zich]

Hi all,

I hope someone can give me an answer / solution to my problem. I just received my HEX16A2 today and connected it to my Windows laptop to test it, but got issues with Hexminer. Following error message is being spammed in the entire miner_proxy. Tested both older and the newest version, but still the same error message. It seem to be able to connect to the pool but when start mining it doesn't seem to be able to get any further.

Have I configured it wrong or what could be the reason of these errors?  


Thanks in advanced!

Did the driver installed correctly?
Did HEX MINER software setting point to correct com port & use right baud rate? Use the same baud rate that shown in device manager(default 9600).

Maybe you could post screen shot of device manager & HEX MINER 1.0.0.3
What i see in your mining_proxy seem normal.

I just received HEX16A2 & run it in WIN 7 64 bit. check my post on https://bitcointalk.org/index.php?topic=323727.msg4168053#msg4168053

[VForrest]

Hi all,

I hope someone can give me an answer / solution to my problem. I just received my HEX16A2 today and connected it to my Windows laptop to test it, but got issues with Hexminer. Following error message is being spammed in the entire miner_proxy. Tested both older and the newest version, but still the same error message. It seem to be able to connect to the pool but when start mining it doesn't seem to be able to get any further.

Have I configured it wrong or what could be the reason of these errors?  


Thanks in advanced!

Did the driver installed correctly?
Did HEX MINER software setting point to correct com port & use right baud rate? Use the same baud rate that shown in device manager(default 9600).

Maybe you could post screen shot of device manager & HEX MINER 1.0.0.3
What i see in your mining_proxy seem normal.

I just received HEX16A2 & run it in WIN 7 64 bit. check my post on https://bitcointalk.org/index.php?topic=323727.msg4168053#msg4168053

This is the settings I'm using, checked that the drivers is installed and working and also that HEXminer is using correct rate.

http://s27.postimg.org/5g805vy83/hex16a2.png

[Zich]

This is the settings I'm using, checked that the drivers is installed and working and also that HEXminer is using correct rate.

You should enable auto reset(10 min is fine). I hope you not forget to switch on the PSU to powering the HEX16A2.

[acidfox]

This is the settings I'm using, checked that the drivers is installed and working and also that HEXminer is using correct rate.

Please correct the Serial Bitrate to 115200 then the miner will work.

[Zich]

This is the settings I'm using, checked that the drivers is installed and working and also that HEXminer is using correct rate.

Please correct the Serial Bitrate to 115200 then the miner will work.

Since my board work with 9600 so i forget this, sorry. Then change the baudrate on windows device manager to 115200 & select that too on HEX Miner.


Edit:

I just found out that baudrate can increase & decrease your hash rate. Try each baud rate to find best performance
115200 make my hash rate decrease.

[VForrest]

This is the settings I'm using, checked that the drivers is installed and working and also that HEXminer is using correct rate.

Please correct the Serial Bitrate to 115200 then the miner will work.

Since my board work with 9600 so i forget this, sorry. Then change the baudrate on windows device manager to 115200 & select that too on HEX Miner.


Edit:

I just found out that baudrate can increase & decrease your hash rate. Try each baud rate to find best performance
115200 make my hash rate decrease.

I have tested both with 9600 and 115200, changed it within the Device Manager and in HEXminer, still the same error. The PSU is turned on and seem to be working, could try with another one as this PSu haven't been in use for a while..

Any other ideas if it isn't a PSU related problem?


Many thanks!

[btmtb]

Pos and neg/gnd leads connected to the board the right way round, and taken from the psu the right way round? Have you got any photo's showing your setup which might answer silly little things like these?

[VForrest]

Pos and neg/gnd leads connected to the board the right way round, and taken from the psu the right way round? Have you got any photo's showing your setup which might answer silly little things like these?

I don't think it is possible to connect it wrong, here is the pic.

http://s10.postimg.org/u0tlfvlx4/bild.jpg

[VForrest]

Something i noticed now when the light was off, is that one LED is RED, should it be so? - The LED that is green is closet to the mini-USB port, the other one is lightning RED...  

http://s22.postimg.org/ahravqn6p/bild_1.jpg