Pages:
Author

Topic: Baikal Giant X10 - page 54. (Read 132901 times)

sr. member
Activity: 420
Merit: 255
February 10, 2018, 03:57:44 AM
which one is the best coin to mine on X10 nowadays?
newbie
Activity: 28
Merit: 0
February 09, 2018, 09:24:17 PM
Your also assuming their imaged and ready to go.

Either way, lets see. I know we all want to know.
sr. member
Activity: 544
Merit: 250
February 09, 2018, 09:14:25 PM
There are 3 parts inside the Bikal miner

1) OrangePi
2) Control Board
3) Hashing boards

Can you try swapping the OrangePi and Control Board and leaving the hashing boards the same between the x10 and Giant B?

@ismurdegus, have you tried this yet? See if it's just the control board determining the algo's, if it works, then maybe all you need to do is clone the control board to switch between the X10 and Giant B.


I will send you the link to the Giant B and X10 firmwares shortly.

If you want to try and see if you can run the GB setup feel free.
Obviously you do this and could risk damaging something.

If you decide to do this, limit your risk. By using your spare board and spare Orange Pi to be safe

  • Download the GB Image from Baikal
  • Flash a spare SDcard with the Giant b image
  • Place the GB firmware bin file in the folder “/media/boot/“
  • Inster SD Card in OrangePi
  • Rebuild miner and boot up

If everything we understand about the miner is true, that they are the same hardware, just with different firmwares, you would have effectively been the first known individual that has successfully transitioned the miner if all goes well.



You are over thinking it, all he needs to do is switch over the orangepi and control board and test. That will truely determine if the hashing boards are identical or not between the x10 and Giant B.
newbie
Activity: 28
Merit: 0
February 09, 2018, 08:51:56 PM
Here is the GB firmware.

https://uploadfiles.io/4y950

The file name must start with the letter G.

Example GB.bin
newbie
Activity: 28
Merit: 0
February 09, 2018, 08:44:23 PM
There are 3 parts inside the Bikal miner

1) OrangePi
2) Control Board
3) Hashing boards

Can you try swapping the OrangePi and Control Board and leaving the hashing boards the same between the x10 and Giant B?

@ismurdegus, have you tried this yet? See if it's just the control board determining the algo's, if it works, then maybe all you need to do is clone the control board to switch between the X10 and Giant B.


I will send you the link to the Giant B and X10 firmwares shortly.

If you want to try and see if you can run the GB setup feel free.
Obviously you do this and could risk damaging something.

If you decide to do this, limit your risk. By using your spare board and spare Orange Pi to be safe

  • Download the GB Image from Baikal
  • Flash a spare SDcard with the Giant b image
  • Place the GB firmware bin file in the folder “/media/boot/“
  • Inster SD Card in OrangePi
  • Rebuild miner and boot up

If everything we understand about the miner is true, that they are the same hardware, just with different firmwares, you would have effectively been the first known individual that has successfully transitioned the miner if all goes well.

sr. member
Activity: 544
Merit: 250
February 09, 2018, 08:37:26 PM
There are 3 parts inside the Bikal miner

1) OrangePi
2) Control Board
3) Hashing boards

Can you try swapping the OrangePi and Control Board and leaving the hashing boards the same between the x10 and Giant B?

@ismurdegus, have you tried this yet? See if it's just the control board determining the algo's, if it works, then maybe all you need to do is clone the control board to switch between the X10 and Giant B.
newbie
Activity: 25
Merit: 0
February 09, 2018, 08:28:01 PM
You are missing the crucial part when replacing the images of the OrangePI. The firmware bin file for the STM chip.

The STM chip has a specific set of algorithms pre-coded into the firmware code. You cannot get around it.

You will have to get the running bin file from a Giant B or X10's STM chip and place it in the "/media/boot/" folder and call it, "G*.bin"

When the miner reboots on the new image of the miner it will compare versions and replace the existing flashed image by entering DFU Mode.

Once updated, it will reenable the hash boards and being mining.

It's doable.



The reason behind that is that the file location and name is here, update_fw.py. Located in the \usr\bin folder.

Code:
#!/usr/bin/env python
import subprocess
import os
import sys
from subprocess import Popen, PIPE
import fcntl
import time
import glob
tmpfile = '/home/baikal/tmp.bin'
path = '/media/boot/G*.bin'
fwfile = glob.glob(path)
if not fwfile:
print 'No firmware'
sys.exit()

USBDEVFS_RESET= 21780

# enter dfu mode
def enter_dfumode():
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def exit_dfumode():
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def reset_usb(driver):
  try:
    lsusb_out = Popen("lsusb | grep -i %s"%driver, shell=True, bufsize=64, stdin=PIPE, stdout=PIPE, close_fds=True).stdout.read().strip().split()
    bus = lsusb_out[1]
    device = lsusb_out[3][:-1]
    f = open("/dev/bus/usb/%s/%s"%(bus, device), 'w', os.O_WRONLY)
    fcntl.ioctl(f, USBDEVFS_RESET, 0)
  except Exception, msg:
    print ""

def update_firmware():
  enter_dfumode()
  reset_usb("DFU")
  print 'Downloading... ' + fwfile[0]
  cmd = 'sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -D ' + fwfile[0]
  subprocess.call(cmd, shell=True)
  cmd = 'sudo rm -rf ' + path
  subprocess.call(cmd, shell=True)

enter_dfumode()
reset_usb("STM32F407")
reset_usb("DFU")
update_firmware()
exit_dfumode()

print "Done"

I am not an expert like you, but looks we are talking about the same thing.
The control board with the ST chip must be re-programmed.

I have 2 x OrangePI and 1 x Control board for spare.

newbie
Activity: 49
Merit: 0
February 09, 2018, 07:33:58 PM
ok so you also have problems with the Baikal giant X10. The funny thing is that a miner runs normally and the 2 te fails again and again does not restart by itself. will help a new control board
newbie
Activity: 28
Merit: 0
February 09, 2018, 04:08:04 PM
You are missing the crucial part when replacing the images of the OrangePI. The firmware bin file for the STM chip.

The STM chip has a specific set of algorithms pre-coded into the firmware code. You cannot get around it.

You will have to get the running bin file from a Giant B or X10's STM chip and place it in the "/media/boot/" folder and call it, "G*.bin"

When the miner reboots on the new image of the miner it will compare versions and replace the existing flashed image by entering DFU Mode.

Once updated, it will reenable the hash boards and being mining.

It's doable.



The reason behind that is that the file location and name is here, update_fw.py. Located in the \usr\bin folder.

Code:
#!/usr/bin/env python
import subprocess
import os
import sys
from subprocess import Popen, PIPE
import fcntl
import time
import glob
tmpfile = '/home/baikal/tmp.bin'
path = '/media/boot/G*.bin'
fwfile = glob.glob(path)
if not fwfile:
print 'No firmware'
sys.exit()

USBDEVFS_RESET= 21780

# enter dfu mode
def enter_dfumode():
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def exit_dfumode():
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA18/data', shell=True)
  subprocess.call('echo 0 > /sys/class/gpio_sw/PA10/data', shell=True)
  subprocess.call('echo 1 > /sys/class/gpio_sw/PA10/data', shell=True)

def reset_usb(driver):
  try:
    lsusb_out = Popen("lsusb | grep -i %s"%driver, shell=True, bufsize=64, stdin=PIPE, stdout=PIPE, close_fds=True).stdout.read().strip().split()
    bus = lsusb_out[1]
    device = lsusb_out[3][:-1]
    f = open("/dev/bus/usb/%s/%s"%(bus, device), 'w', os.O_WRONLY)
    fcntl.ioctl(f, USBDEVFS_RESET, 0)
  except Exception, msg:
    print ""

def update_firmware():
  enter_dfumode()
  reset_usb("DFU")
  print 'Downloading... ' + fwfile[0]
  cmd = 'sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -D ' + fwfile[0]
  subprocess.call(cmd, shell=True)
  cmd = 'sudo rm -rf ' + path
  subprocess.call(cmd, shell=True)

enter_dfumode()
reset_usb("STM32F407")
reset_usb("DFU")
update_firmware()
exit_dfumode()

print "Done"
full member
Activity: 262
Merit: 100
February 09, 2018, 02:35:35 PM
Hi,

have the problem that my Baikal Gaint X10 will fail about 1 time a day.

I have to restart the miner every time.


If there is a remedy, the blue LEDs on the hashboard light up.

new Firmware update did not bring any improvement
everyone have the same problem, there is no solution yet
newbie
Activity: 49
Merit: 0
February 09, 2018, 02:26:38 PM
Hi,

have the problem that my Baikal Gaint X10 will fail about 1 time a day.

I have to restart the miner every time.


If there is a remedy, the blue LEDs on the hashboard light up.

new Firmware update did not bring any improvement
newbie
Activity: 24
Merit: 0
February 09, 2018, 09:39:30 AM
If the device's asics are fpga's and programmed differently at B it will just never work...

On the control board there is a micro usb connector. I am sure is used to flash the controller onboard.

If we had the possibility to extract the firmware from a Giant B and flash it on an X10 board, I am sure will work


possibly but it is surely locked by baikal Sad , only if their support could give us information but i think they will not Sad
newbie
Activity: 39
Merit: 0
February 09, 2018, 08:51:43 AM
Hi guys

Not sure where to post this maybe useful information.....

I did some test with my X10 and I find that the Giant-B and X10 are the same machine.

The only difference is of course the OS inside the SD card and the firmware inside the controller board (blue card with ST microcontroller)

So, what I did is install the Giant-B image on my X10 .... :-0

The miner start like normal. The interface show all correct and also the hash cards show the right frequency and right hash power.

At this point I try to connect my unit at a lby pool..... The pool accept the connection but the miner reject the data to decrypt.

Ask me some question if you want...


Ciao


Read this please, not only overclocking.
https://bitcointalksearch.org/topic/baikal-x10-overclock-claim-reward-02-btc-for-tutorial-how-to-2790982
sr. member
Activity: 544
Merit: 250
February 09, 2018, 08:40:12 AM
There are 3 parts inside the Bikal miner

1) OrangePi
2) Control Board
3) Hashing boards

Can you try swapping the OrangePi and Control Board and leaving the hashing boards the same between the x10 and Giant B?
newbie
Activity: 78
Merit: 0
February 09, 2018, 07:35:34 AM
Hi guys

Not sure where to post this maybe useful information.....

I did some test with my X10 and I find that the Giant-B and X10 are the same machine.

The only difference is of course the OS inside the SD card and the firmware inside the controller board (blue card with ST microcontroller)

So, what I did is install the Giant-B image on my X10 .... :-0

The miner start like normal. The interface show all correct and also the hash cards show the right frequency and right hash power.

At this point I try to connect my unit at a lby pool..... The pool accept the connection but the miner reject the data to decrypt.

Ask me some question if you want...


Ciao

I don't think you've uncovered anything that anyone doesn't know.  While the controller board is the same (Orange Pi I believe?), from your report it also appears that the hash-boards themselves are different because the hash boards in your x10 do not have the capability to do lby... hence your rejections.


There are 3 parts inside the Bikal miner

1) OrangePi
2) Control Board
3) Hashing boards

When I try to mine lbry, the miner was up and running. Temperature of chips went UP and was generating 40GH/s
The rejection was from the pool not from the miner.

I think I did a screenshot, let me find it
I have no doubt that it's "mining". I have doubt that what is coming out is lbry hashes (my doubts are confirmed by your rejections).  The issue is likely that the software is saying 'give me algorithm 1' to the hash boards (thinking algorithm 1 is lbry), but your hashboards aren't b+ boards, so 'algorithm 1' on them is something different.  I'm not saying this is "proof", but I could certainly see how this situation would lead to what you are experiencing.
member
Activity: 168
Merit: 10
February 09, 2018, 07:02:27 AM
Is there a video available where I can see how to unbox the Pi for flashing firmware?
newbie
Activity: 25
Merit: 0
February 09, 2018, 06:22:20 AM
If the device's asics are fpga's and programmed differently at B it will just never work...

On the control board there is a micro usb connector. I am sure is used to flash the controller onboard.

If we had the possibility to extract the firmware from a Giant B and flash it on an X10 board, I am sure will work
newbie
Activity: 24
Merit: 0
February 09, 2018, 06:19:41 AM
If the device's asics are fpga's and programmed differently at B it will just never work...
newbie
Activity: 25
Merit: 0
February 09, 2018, 05:59:29 AM
newbie
Activity: 25
Merit: 0
February 09, 2018, 05:51:10 AM
Hi guys

Not sure where to post this maybe useful information.....

I did some test with my X10 and I find that the Giant-B and X10 are the same machine.

The only difference is of course the OS inside the SD card and the firmware inside the controller board (blue card with ST microcontroller)

So, what I did is install the Giant-B image on my X10 .... :-0

The miner start like normal. The interface show all correct and also the hash cards show the right frequency and right hash power.

At this point I try to connect my unit at a lby pool..... The pool accept the connection but the miner reject the data to decrypt.

Ask me some question if you want...


Ciao

I don't think you've uncovered anything that anyone doesn't know.  While the controller board is the same (Orange Pi I believe?), from your report it also appears that the hash-boards themselves are different because the hash boards in your x10 do not have the capability to do lby... hence your rejections.


There are 3 parts inside the Bikal miner

1) OrangePi
2) Control Board
3) Hashing boards

When I try to mine lbry, the miner was up and running. Temperature of chips went UP and was generating 40GH/s
The rejection was from the pool not from the miner.

I think I did a screenshot, let me find it
Pages:
Jump to: