Пoдeлитecь фaйлoм пpoшивки нa G-Blade пoдaлyйcтa
Share the firmware on G-Blade Plz
Topic: Gridseed G-blade firmware for ARM (STM32F103RCT6) (Read 3079 times)
Here is my post with a quick "how to".
https://bitcointalksearch.org/topic/m.9138488
I'll add pics later.
https://bitcointalksearch.org/topic/m.9138488
I'll add pics later.
I was able to solder a new chip and found that the 8pin single row pin header is the programming connector
1. 3v3
2. Reset
3. RX
4. TX
5. Boot0
6. Boot1
7. GND
8. GND
i'l share the boot pin settings this evening
1. 3v3
2. Reset
3. RX
4. TX
5. Boot0
6. Boot1
7. GND
8. GND
i'l share the boot pin settings this evening
It took me some time to do it, but here is the file someone would need to flash the Gridseed G-Blade if the STM32F103RCT6 failed or was erased for some reason.
http://dl.free.fr/vLuvCPiD9
I'll post a quick "how to" in my G-Blade 7MH overlocking thread
http://dl.free.fr/vLuvCPiD9
I'll post a quick "how to" in my G-Blade 7MH overlocking thread
Hello Gades, i have the same problem with 3 g-blades i need to have the STM chips replaced. A buddy of mine can replace them but needs the firmware i was wondering if you could share the firmware with me? Would be so great. Thanks in advance mate
EDIT: WILLUMPIE is my buddy lol see the post above me
EDIT: WILLUMPIE is my buddy lol see the post above me
bin file I have, but after soldering "expert" does not help because he first chip soldered on the contrary, and then the board came off the track.
http://i.piccy.info/i9/b6b794e37b8d2df80f42296d2ab3be4d/1403946870/9315/652200/Foto_28_06_14_10_59_20_240.jpghttp://i.piccy.info/a3/2014-06-28-09-14/i9-6621159/180x240-r/i.gif
http://i.piccy.info/i9/219e3018f7d78ade9e1320677f3d043f/1403946906/10211/652200/Foto_28_06_14_11_38_51_240.jpghttp://i.piccy.info/a3/2014-06-28-09-15/i9-6621162/240x180-r/i.gif
You can try to recover it and solder another chip (just bought two of them). Maybe it makes sense to look to the side connector CON4. Is it possible to connect it to the raspberry pi?
http://i.piccy.info/i9/b6b794e37b8d2df80f42296d2ab3be4d/1403946870/9315/652200/Foto_28_06_14_10_59_20_240.jpghttp://i.piccy.info/a3/2014-06-28-09-14/i9-6621159/180x240-r/i.gif
http://i.piccy.info/i9/219e3018f7d78ade9e1320677f3d043f/1403946906/10211/652200/Foto_28_06_14_11_38_51_240.jpghttp://i.piccy.info/a3/2014-06-28-09-15/i9-6621162/240x180-r/i.gif
You can try to recover it and solder another chip (just bought two of them). Maybe it makes sense to look to the side connector CON4. Is it possible to connect it to the raspberry pi?
Did you manage to get your blade up and running again? can you share the compiled firmware file?
bin file I have, but after soldering "expert" does not help because he first chip soldered on the contrary, and then the board came off the track.
You can try to recover it and solder another chip (just bought two of them). Maybe it makes sense to look to the side connector CON4. Is it possible to connect it to the raspberry pi?
You can try to recover it and solder another chip (just bought two of them). Maybe it makes sense to look to the side connector CON4. Is it possible to connect it to the raspberry pi?
The connection is explained in the datasheets and schematics in github, but you can't connect directly to raspberry. It's used to access to the stm32F103 chip via JTAG or similar protocol.
Easier thing would be to solder the stm32F103 chip on an external PCB and jump wire it to the Blade. there are very few connections needed to communicate with the chips and the PW OK to the UP1509 pin 3
Use the 5 chips for release schematics to see the wiring.
Beware, the 5 chips gridseed used QFP48 package for the stm32F103 and blades uses QFP64.
You will have to check the pinout.
bin file I have, but after soldering "expert" does not help because he first chip soldered on the contrary, and then the board came off the track.
You can try to recover it and solder another chip (just bought two of them). Maybe it makes sense to look to the side connector CON4. Is it possible to connect it to the raspberry pi?
You can try to recover it and solder another chip (just bought two of them). Maybe it makes sense to look to the side connector CON4. Is it possible to connect it to the raspberry pi?
sources found here https://github.com/gridseed/usb-miner
Compiled firmware something suspiciously small size turned hex - ie 31363 ~ 13-15Kb microcode
MD5 (STM3210B-EVAL.hex) = c35920ee382295df05f996c6ab840d7a
Compiled firmware something suspiciously small size turned hex - ie 31363 ~ 13-15Kb microcode
MD5 (STM3210B-EVAL.hex) = c35920ee382295df05f996c6ab840d7a
I'll check if there is an easy way to grab it from one of my blades.
If so, I'll upload it.
Edit:
looks like we can't access it easily with USB and STM flashloader demo. Maybe read protected
JTAG access is probably required
sources found here https://github.com/gridseed/usb-miner
Compiled firmware something suspiciously small size turned hex - ie 31363 ~ 13-15Kb microcode
MD5 (STM3210B-EVAL.hex) = c35920ee382295df05f996c6ab840d7a
Compiled firmware something suspiciously small size turned hex - ie 31363 ~ 13-15Kb microcode
MD5 (STM3210B-EVAL.hex) = c35920ee382295df05f996c6ab840d7a
Where can I download the firmware for this chip? (seller deceived and sold to the off-chip device STM32F103RCT6)
Can I run this device without ARM - for example through the raspberry pi? The board has two connectors - JTAG and some other (whether it can be used)?
Maybe there is a circuit diagram of the board g-blade?
1. Place stabilizer;
2. Search faults using thermal paper;
Can I run this device without ARM - for example through the raspberry pi? The board has two connectors - JTAG and some other (whether it can be used)?
Maybe there is a circuit diagram of the board g-blade?
1. Place stabilizer;
2. Search faults using thermal paper;
Jump to: