Bitcoin Forum
June 24, 2024, 06:21:55 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: January 25, 2019, 08:50:25 AM
Anything news about OC function?

greetings

I've found something in a discord channel:

To overclock your Baikal BK-X, try this command in Ubuntu sudo dfu-util -a 0 -d 0483:df11 -s 0x08000000:leave -U /home/baikal/tmp.bin

someone dares?
2  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: January 02, 2019, 03:20:36 PM
Bus 007 Device 002: ID 0483:5740 STMicroelectronics STM32F407 is the current result, blue LEDs are up, sgminer is running (with your firmware).

root@Baikal:~# md5sum /media/boot/G*.bin
d806968a965a7499b026ee558073af54  /media/boot/GX10.bin

root@Baikal:~# python /usr/bin/update_fw.py

Downloading...
Done

That all looks good except for the checksum of the bin file you're using. I'm getting b7ee4ca88a190fb086655761e1f55c6c for the stock v1.2 file. I'd try pulling the file from the v1.2 OrangePi image and try again. Remember to revert back to the stock v1.2 sgminer too.

Seems like i really had a broken GX10.bin file... i extracted the bin file again from trhe v1.2 img and ran md5sum again. result: b7ee4ca88a190fb086655761e1f55c6c
python /usr/bin/update_fw.py worked, miner is up normal state.

Thanks a lot, tboy32c - good job! :-)
Now i can confirm rollback is working!
3  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: January 02, 2019, 11:51:46 AM

Is 0483:5740 STMicroelectronics STM32F407 the result you have currently? If so, are you also saying you do not see the blue LED at all? IF the STM has my firmware, AND it is in RUN mode (as your last result would indicate), AND sgminer is not running (as indicated by your previous post where you ran the miner-stop script), then the blue LED should be flashing (especially if you also ran the reset_stm script as previously indicated).

Try this next if you would:
  • Put the desired .bin firmware file in /media/boot
  • Make sure the filename starts with a capital G
  • Run md5sum /media/boot/G*.bin    -what is the result?
  • Run python /usr/bin/update_fw.py   & please post the entire output of that command

Bus 007 Device 002: ID 0483:5740 STMicroelectronics STM32F407 is the current result, blue LEDs are up, sgminer is running (with your firmware).

root@Baikal:~# md5sum /media/boot/G*.bin
d806968a965a7499b026ee558073af54  /media/boot/GX10.bin

root@Baikal:~# python /usr/bin/update_fw.py

Downloading... /media/boot/GX10.bin
dfu-util 0.8

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2014 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash  "
Downloading to address = 0x08000000, size = 16616
Download        [=========================] 100%        16616 bytes
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state
Done


4  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 31, 2018, 09:56:18 AM
I can not confirm rolling back to 1.2. If i try to, controler board stays in DFU mode (red LEDs).

I did those steps:
Code:
./opt/scripta/startup/miner-stop.sh
python /usr/bin/update_fw.py
python reset_stm.py
lsusb | grep 0483

What does this command show when you run it?
Code:
lsusb | grep 0483
Either there's nothing, or something with "STMicroelectronics" in it.

Same question as to chup: What was the last firmware you successfully flashed (the one I posted? flexmeister's? One of the stock images?)

lsusb | grep 0483 (with v1.2)
Code:
Bus 007 Device 013: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
lsusb | grep 0483 (with your firmware)
Code:
Bus 007 Device 014: ID 0483:5740 STMicroelectronics STM32F407
5  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 30, 2018, 09:28:47 PM

From these quotes I'm not sure if there are actual "bricking" problems or if people are just having trouble with the steps to change firmware. I will confirm that I am able to rollback firmware from the firmware image I posted. If ONLY the red LEDs are showing, then that should mean the control board is in firmware update mode. If the red LEDs are on and you see a blue flashing LED, then the control board is in RUN mode but sgminer has not given it work to do (either sgminer died or the pools are all down, etc). If you see blue solid LEDs then it's hashing. If you don't see any LEDs then your device is not powered Tongue.

If you run update_fw.py and get:
Code:
dfu-util: No DFU capable USB device available
you can try editing the update_fw.py script by commenting out (adding a "#" at the start of the line) the last couple lines:
Code:
#update_firmware()
#exit_dfumode()
Run the modified script and it should have reset the STM and left it in firmware update mode. Then run:
Code:
lsusb | grep 0483
And the result sholuld be this:
Code:
Bus 007 Device 002: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
(the "device" number will vary)
If instead you get:
Code:
ID 0483:5740 STMicroelectronics STM32F407
we'll have to go from there.


I can not confirm rolling back to 1.2. If i try to, controler board stays in DFU mode (red LEDs). With your custom firmware the device is running fine, but with lower hashrate. (3,5Gh @skein).

I did those steps:
Code:
./opt/scripta/startup/miner-stop.sh
python /usr/bin/update_fw.py
python reset_stm.py
lsusb | grep 0483
6  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 30, 2018, 02:28:30 PM
Store the backup file into media/boot and reboot your device. Ensure the filename begins with "G"...bin
Cheers

unfortunately didn't work. so i decided to reflash sd card with org. image v1.1 and/or v1.2 - still not working. hashboards are showing only red leds :-(
i've already trieded to change sd cards and orange pi - doesn't matter, hashboards don't work- leds red.





Wellcome to the club of bricked X10s.

If You put GX10.bin in /media/boot folder and execute

sudo update_fw.py

are You getting

dfu-util: No DFU capable USB device available

message?

witch GX10.bin? original one? and witch update_fw.py ? meanwhile i've changed psu, sd card, hashboard.... looks like control board is defective
7  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 30, 2018, 12:01:47 AM
Store the backup file into media/boot and reboot your device. Ensure the filename begins with "G"...bin
Cheers

unfortunately didn't work. so i decided to reflash sd card with org. image v1.1 and/or v1.2 - still not working. hashboards are showing only red leds :-(
i've already trieded to change sd cards and orange pi - doesn't matter, hashboards don't work- leds red.



8  Alternate cryptocurrencies / Mining (Altcoins) / Re: sgminer: Baikal Giant X10 / N / B - Open Source - Confirmed OC Giant B! on: December 29, 2018, 09:13:25 PM
Rollback is working.

Same here, "No devices running" can you please explain how to rollback proper? ty
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!