repair a T9 + after a bad firmware (lost chain)

[thierry4wd]

Hi all!

I know some people have had a problem with their T9 + who lost 2 hash board, especially after flashing the firmware Dollemizer! or build own bmminer by source code

What happens, the bad firmware erases the board DSPIC32 to reprogram them, but as it does not have the HEX file, it reprograms nothing, and therefore the chain is definitely lost!

I also had the problem after trying a BMMINER custom that had exactly the same effect! so I got hooked on the question ... and HERE IS THE SOLUTION!

pre-requisite:
- a PICKIT 3 case
- MPLAB X IPE
- Bitmain HEX original file (pic32)

After :

1 - connect to the board, pin1 in front of the PICKIT arrow


2 - Connect on MPLAB


3 - Enter in advanced mode and take "power target circuit from tool"


4 - ERASE the pic (use if you sure that the hash board is hs)

Code:

Erasing...
Erase successful
2018-09-19 22:17:36 +0200 - Programming...

5 - Put in Hex File my Hex file extracted from good board (download here http://www.k-upload.fr/afficher-fichier-2018-09-19-103561fd6dspic33ep16g.hex.html ) or ( http://www.mediafire.com/file/mk8ivrax849ztxp/DSPIC33EP16GS202-ORIGINAL-T9%252B.hex/file )

Code:

Connecting to MPLAB PICkit 3...
Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.54.00
Firmware type..............dsPIC33E/24E
Programmer to target power is enabled - VDD = 3,250000 volts.
Target device dsPIC33EP16GS202 found.
Device ID Revision = 4003
DEVSN0 = 00000000
DEVSN1 = 00000000
2018-09-19 22:16:21 +0200 - Hex file loaded successfully.
Loading code from C:\Users\xxx\Desktop\Firmware antminer D3 et L3+\pump firmware T9+\Prog PIC\DSPIC33EP16GS202.hex...

6 - "Program" and wait !

Code:

Programming...

The following memory area(s) will be programmed:
program memory: start address = 0x0, end address = 0x1dff
Programming/Verify complete
2018-09-19 22:18:13 +0200 - Programming complete

once the cards flash with PicKit, do not forget to reflash the minor with official firmware bitmain before reboot the minor ...

to do this, do it before you flash the card, or just connect the controller card (without the hashboard) and flash the official firmware, power off the miner, reconnect the hashboard and turn on again.

Essenciel is that the first start after flashing the board is done with an official firmware on the minor (with hashboard connected) otherwise the problem will come back immediately..

Now your board is reprogramed ! and working !!!

For any advice or request do not hesitate!

If you like it;)
BTC: 1FWpeHCs7rB7LgWUiU2j2GgwuZpEYtfGm2
LTC: LShLPeXRMgRg3K2DP1ZMmWXbfS3Fh4ATNQ



EDIT : FREE GIFT ! for no error / brick your miner after compile your own code for bmminer

Modifi this "define" to "undefine" on the bitmain code on "driver-btm-c5.H" (the effect : no flash pic)

Code:

241 #define ENABLE_RESTORE_PIC_APP          // if enabled, will restore PIC APP when the version is not correct!!!

[1714907439]

1714907439

[1714907439]

1714907439

[1714907439]

1714907439

[1714907439]

1714907439

[x3aklili]

exelent Work!!!
my miner is back to life again

[thierry4wd]

Great! Glad to see that his help !!!

I think that now that I extracted the program HEX pic32, it should not be difficult to inject it into an update, to reprogram via software;)

ps: you already had a Pickit3 on hand ?

[zacocity]

We have tested this with some users before, but it does not seem to work for everyone. I'm glad it worked for you

[thierry4wd]

be careful, my "tutor" only fixes the problem of the lost pic, in the log of the kernel there must be this after having checked the fan:

Code:

chain [1] PIC jump to app
Check chain [1] PIC fw version = 0x03 (or other)

but if you have:

Code:

chain [1] PIC jump to app
Check chain [1] PIC fw version = 0x00 or 0xff

so my tutorial will be useful!

Also beware, my HEX file is ONLY for the T9+ ! it is equipped with a PIC32 while all other antminer are equipped with PIC16 !!!

We have tested this with some users before, but it does not seem to work for everyone. I'm glad it worked for you

You said that it did not work for many others, which model? what process? have you program the pic?

Thank you

[taserz]

Good job bud! You just saved a lot of headache of trying to figure out how to do this from the software point of view.

[HagssFIN]

Great post and for sure a great help for many people.
I gave you some merit.

[thierry4wd]

Thank you ! your comments are a pleasure to hear!

You see now that I am not a scamer or even a naughty perssonne: p

I noticed that some perssonne have the same problem with their S9, I do not have S9 on hand but if I had one, then it would be just as easy to do the same tutorial! (if you have an S9 down I'm interested)

I remain at disposal to give help;)

[digital$]

thanks for a working fix, greatly appreciated.  would it be possible to inject code into a soft update for those without access to a pickit3 device?

[thierry4wd]

Thank you;) so at worst, a PicKit 3 does not cost anything, I got mine for 20USD new
this solution works very well, and will only cost you 20usd and it's easy to do, I explain everything;) if you really have no choice ...

I pence that may have integrated my HEX file in a firmware, it must necessarily be able to do it in a software way (it already does with bad firmware) ...

I'm going to hang on this question but currently I'm working on other small projects so I do not have much time ...

friendly;)

[danielyap]

I'm getting this error T9+ August Batch

Code:

dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!

Does this mean my PIC is PIC33 not PIC32?

Also, how do I connect the PicKit 3 to my board? there's no slot for me to put it in...

https://imgur.com/a/DxJdSzH

Please help me! Thank you so much!

[thierry4wd]

Of course ! Plug this on the all on your hash board ! And see my tuto.

Your picture is ok to connect this !

[danielyap]

Hmm. I've been successful for some boards but sometimes when I try to connect the board, this is what I get...

Code:

*****************************************************

Connecting to MPLAB PICkit 3...

Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.54.00
Firmware type..............dsPIC33E/24E
Target device was not found (could not detect target voltage VDD). You must connect to a target device to use PICkit 3.


*****************************************************

Connecting to MPLAB PICkit 3...

Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.54.00
Firmware type..............dsPIC33E/24E
Programmer to target power is enabled - VDD = 3.250000 volts.
Target device dsPIC33EP16GS202 found.
Device ID Revision = 4003
DEVSN0 = 00000000
DEVSN1 = 00000000

Erasing...
Erase successful
2018-10-04 21:51:39 +0800 - Hex file loaded successfully.
Loading code from \\Mac\Home\Downloads\k-upload-file_2018-09-19-103561fd6dspic33ep16g.hex...
2018-10-04 21:51:41 +0800 - Programming...


You are trying to change protected boot memory. In order to do this you must select the "Boot, Secure and General Segments" option on the debug tool Secure Segment properties page.
Failed to program device
Too much current has been drawn on VDD. Please disconnect your circuit, check the CLK and DATA lines for shorts and then reconnect.

Any idea why this happens?

Also, I find that when I try to upload a custom bmminer, I get this same error all the time,

Code:

dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]!

Which I'll then have to flash your working HEX in order for that bmminer to work. Any idea why that happens as well? Thanks!

[thierry4wd]

for the error:

"Boot, Secure and General Segments" "You are trying to change your boot.

simply follow the instructions: D then activate "advanced setting", then go to "setting" then in the "secure segment" tab choose "Boot, Secure and General Segments"

For the problem: Too much current has been drawn on VDD. Please disconnect your circuit and check the CLK and DATA lines for shorts and then reconnect. I also had the problem, maybe a procedural error, try to disconnect and reconnect ... it worked for me.

[danielyap]

for the error:

"Boot, Secure and General Segments" "You are trying to change your boot.

simply follow the instructions: D then activate "advanced setting", then go to "setting" then in the "secure segment" tab choose "Boot, Secure and General Segments"

For the problem: Too much current has been drawn on VDD. Please disconnect your circuit and check the CLK and DATA lines for shorts and then reconnect. I also had the problem, maybe a procedural error, try to disconnect and reconnect ... it worked for me.

Thanks! will try that out.. how about the hex problem? Your HEX works but the stock HEX will cause this error all the time...instead of opening each miner to program the HEX, how do I program via the PIC? (if possible)

[tim-bc]

For the problem: Too much current has been drawn on VDD. Please disconnect your circuit and check the CLK and DATA lines for shorts and then reconnect. I also had the problem, maybe a procedural error, try to disconnect and reconnect ... it worked for me.

Have you considered that there actually might be a short that's causing the overcurrent on VDD? You can also check voltages on VDD, should be 1.8V on VDD1V8, then look at VDD2V5 if it's anything like the S9.

[danielyap]

Hi guys, so I just restarted my computer and sometimes it works, sometimes it don't. I'm not entirely sure why this happens.

In any case, does any one know why do I need to flash my board with the Hex provided by @thierry4wd in order for a custom bmminer to work? Is there any way to do this without flashing the board. Right now, I have to take out each board and flash them 1 by 1 with the pickit 3 in order for the custom bmminer to work...

Here's a snippet of the kernel log when I paste the bmminer in before flashing the boards with the hex

Code:

[   23.956220] bcm54xx_config_init
[   26.956770] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz
[   26.962790] xemacps e000b000.ps7-ethernet: link up (100/FULL)
[  100.487087] random: nonblocking pool is initialized
Detect 512MB control board of XILINX
Miner Type = T9+
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x0000ffff
chain[1] PIC jump to app
Check chain[1] PIC fw version=0x90
chain[1] PIC need restore ...

Thanks for the help so far guys! Really appreciate it!

[marlonmem]

Hello, I do not have pick 3 at hand, and in my country, it is very expensive, is there any other way to program the pic, without the pickit 3 I am willing to give btc if you help me please, or I can do it on-line by terminal or something better. Thank you

[BitMaxz]

Hello, I do not have pick 3 at hand, and in my country, it is very expensive, is there any other way to program the pic, without the pickit 3 I am willing to give btc if you help me please, or I can do it on-line by terminal or something better. Thank you

I couldn't find any alternative for PICKit 3 but I found a guide where you can make a DIY PICKit 3 clone. Honestly, making a clone of PICKit is not easy to do but if you are willing to make you can follow the guide from here Making A Pickit 3 Clone.

[thierry4wd]

Hello, I do not have pick 3 at hand, and in my country, it is very expensive, is there any other way to program the pic, without the pickit 3 I am willing to give btc if you help me please, or I can do it on-line by terminal or something better. Thank you

i buy my PICKIT3 by 20usd shipping included ... is to hi ?

please shearch on website e**y