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

[thierry4wd]

Litle UP !

If any people is interessed by HEX file for S9 if yes, i ready to extract this on needed

[tim-bc]

Does pickit 3 work with pic16 also? Or only pic32?

[thierry4wd]

Of corse ! PicKit 3 ready to work for all hashboard for all antminer !!!

[Dodgymon]

Wow it worked for me!
I am so happy I could kiss you.

I'll throw some LTC your way for being such a champ

[thierry4wd]

With pleasure !!!!

A big thank you for this donation !!!! really generous, it's very enjoyable !!!!

please s9 for hex file.

I'm sorry but I finished my development of S9 (AsicBoost + fan + voltage) and so I do not have it at hand ... my work is "for the moment" finished with him ...

On the other hand, if you have at least one card that works, you can extract the HEX yourself! if need I can help you;)

[thierry4wd]

hi, the error come on this :

chain[2] PIC jump to app
dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]

.... you are already try to flash my HEX files ?

Or not, put your own HEX (on MPLAB take "extract") from the good hashboard.

Connect one of the 2 hashboards that works from the minor to the PICKIT3. And in MPLAB does extract (same as my tutorial but EXTRACT).

once the file is recovered, flash it on the failed hashboard, the J2, normally the middle one on the minor;)

I'm confident about the procedure, it should work!

Thanks for giving a feedback;)

[Bill48105]

Thanks for this info it gives me hope I can fix my T9+.  I never even tried the dozer build I just built from the official source!  It really sucks their own software breaks our miners!  The other thing that I'm confused about is if the mminer program can flash & wreck the boards how come it can't flash & repair the board using a good hex file?  Maybe I'm missing something.

[BitMaxz]

Thanks for this info it gives me hope I can fix my T9+.  I never even tried the dozer build I just built from the official source!  It really sucks their own software breaks our miners!  The other thing that I'm confused about is if the mminer program can flash & wreck the boards how come it can't flash & repair the board using a good hex file?  Maybe I'm missing something.

If the flashing doesn't work in your hashboard it's not a software related issue.
Broken or damaged hashboard must be replaced or if you have some hardware repair experience you can experiment the hashboard by heating some ICs and chips using hot air and flux and flash them again with a good hex file. However, if you don't have any hardware experience better to replace it with new one.

[Bill48105]

If the flashing doesn't work in your hashboard it's not a software related issue.
Broken or damaged hashboard must be replaced or if you have some hardware repair experience you can experiment the hashboard by heating some ICs and chips using hot air and flux and flash them again with a good hex file. However, if you don't have any hardware experience better to replace it with new one.

Hi BitMaxz. It's hard to believe all these bricked T9+'s after running older/built bmminer or older/built firmwares are a sudden in-common hardware issue?! Check out the logs..  The code incorrectly detects wrong fw ver then attempts to flash but then after that the version is 0xFF & the cards no longer work..  On top of that why would dumping PIC from working card then restoring onto the newly dead card fix it if it was hardware?  Perhaps you didn't see my post in another thread with the log & details but here's a link:
https://bitcointalk.org/index.php?topic=4513567.msg48611011#msg48611011
That thread is very very long so I don't expect you to follow the entire thing but many people with T9+'s have run into this issue after running old/custom builds of firmware and/or custom built bmminer from the official bitmain github..

So no flashing doesn't work but it appears either the firmware in dsPIC33EP16GS202_app.txt is wrong/corrupt, something changed (perhaps with the new LOW POWER firmware) that when running older versions incorrectly flashes the PIC, there's a bug in the old miner code (least likely as it would have surely cropped up before now if that was the case..).  What would be handy is to have a copy of old firmware dated same time as github source with copy of the then dsPIC33EP16GS202_app.txt file or better yet updated LOW POWER Nov 2018 source on github along with the updated/correct dsPIC33EP16GS202_app.txt file.  Either one should provide a way to test this further.

In the meantime I added a bug to the source warning T9+ users to beware of this issue & not run the code on github and I have a pickit 3 on the way to attempt recover per 1st post in this thread which would indeed confirm it's not a hardware issue.

Thanks again for the response & appreciate in advance any help in tracking down & resolving this issue.
Bill

EDIT: Here's a snippet of the log to make it easier:

Code:

Miner Type = T9+
Check chain[1] PIC fw version=0x90
chain[1] PIC need restore ...
Later:
Check chain[1] PIC fw version=0xff
chain[1] PIC need restore ...

Note the pic fw version was 0x90 before, the built bmminer tried to restore the firmware then from that point on it read & logged 0xff every time.

[thierry4wd]

Strongly that your PicKit arrives, that you see for yourself, I experimented all this, I repeat it there is an error in the source code of bitmain for the T9 + (by the way I share a bmminer eco mode, and it works, I've cracked the code for that, just try it after repairing your card), there's just 99.9% chance I'm right, just wait for your PicKit and follow my tutorial, and .. .. ENJOY !!!

[Bill48105]

Strongly that your PicKit arrives, that you see for yourself, I experimented all this, I repeat it there is an error in the source code of bitmain for the T9 + (by the way I share a bmminer eco mode, and it works, I've cracked the code for that, just try it after repairing your card), there's just 99.9% chance I'm right, just wait for your PicKit and follow my tutorial, and .. .. ENJOY !!!

OMG I COULD KISS YOU!   IT WORKED!!  My picKit 3 arrived, I followed your directions on the 2 dead cards 1 by 1 & BOOM all 3 cards are working great again!!  THANKS A MILLION!! I gave you a merit I had available & EDIT: I SENT YOU a bit of LTC to say thanks  Sorry it's not much but know I *REALLY* appreciate your work on this solution & taking the time to point me here from the other thread.

Ps. Safe to say this confirms it's not a hardware issue & bitmain's source is F'd up.

[thierry4wd]

SUPERS! it is always a real pleasure to see that my hard work is helping! and a gift is the cherry on the cake !!! then a real thank you;)

Ps: Have you tested my eco mode?

[Bill48105]

SUPERS! it is always a real pleasure to see that my hard work is helping! and a gift is the cherry on the cake !!! then a real thank you;)

Ps: Have you tested my eco mode?

indeed i appreciate it. i was getting nowhere with bitmain support.

No i haven't seen your eco mode stuff. Is that in another post? I messed around with voltage on the github source but only dropped my power usage a couple watts per card which is better than nothing but not as much as I had hoped.

[mediann]

I'm having this problem.

Code:

Connecting to MPLAB PICkit 3...

Currently loaded firmware on PICkit 3
Firmware Suite Version.....01.54.00
Firmware type..............dsPIC33E/24E
PICkit 3 is trying to supply 3.250000 volts from the USB port, but the target VDD is measured to be 3.000000 volts. This could be due to the USB port power capabilities or the target circuitry affecting the measured VDD.

The target circuit may require more power than the debug tool can provide. An external power supply might be necessary.
Connection Failed.

I dont know whats the problem, but i cant connect the pickit cant find vdd target voltage.

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.

[BitMaxz]

I don't enough experience to any error from PICKit 3 but I will try to help you.
Let me ask why you want to flash the hashboard with PICKit 3? You must check first what is the logs from your miner before you going to flash the hashboard.

Have you check this http://image.noelshack.com/fichiers/2018/38/3/1537391587-power-target.jpg

If not check the Power target circuit from the tool then try to connect again if the pickit 3 couldn't detect the hashboard you can try to reattach the connector and USB cable then test it again. If still doesn't work you can check the connector 6 pin with multi-tester check the terminal if there still has a connection of both ends if not your problem is the 6 pin connector.

[mediann]

i just had success pickit the hashboards, some of them are working now great but some of them are showing to me like this

http://www.noelshack.com/2018-52-6-1546044666-t9-problem.png

Code:

set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J2] has 0 asic
Chain[J3] has 0 asic
Chain[J4] has 0 asic
Chain[J9] has 18 asic
Chain[J10] has 18 asic
Chain[J11] has 18 asic
Chain[J12] has 18 asic
Chain[J13] has 18 asic
Chain[J14] has 18 asic

Detect 1GB 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=0x03
chain[2] PIC jump to app
Check chain[2] PIC fw version=0x03
chain[3] PIC jump to app
Check chain[3] PIC fw version=0x03
Chain[J2] will use voltage=930 [1] to open core
Chain[J3] will use voltage=930 [1] to open core
Chain[J4] will use voltage=930 [1] to open core
Chain[J9] will use voltage=930 [1] to open core
Chain[J10] will use voltage=930 [1] to open core
Chain[J11] will use voltage=930 [1] to open core
Chain[J12] will use voltage=930 [1] to open core
Chain[J13] will use voltage=930 [1] to open core
Chain[J14] will use voltage=930 [1] to open core
Fix freq=400 Chain[1] voltage_pic=1 value=930
Fix freq=400 Chain[2] voltage_pic=1 value=930
Fix freq=400 Chain[3] voltage_pic=1 value=930
Fix freq=400 Chain[8] voltage_pic=1 value=930
Fix freq=400 Chain[9] voltage_pic=1 value=930
Fix freq=400 Chain[10] voltage_pic=1 value=930
Fix freq=400 Chain[11] voltage_pic=1 value=930
Fix freq=400 Chain[12] voltage_pic=1 value=930
Fix freq=400 Chain[13] voltage_pic=1 value=930
set_reset_allhashboard = 0x0000ffff
set_reset_allhashboard = 0x00000000
Chain[J2] has 0 asic
Chain[J3] has 0 asic
Chain[J4] has 0 asic
Chain[J9] has 18 asic
Chain[J10] has 18 asic
Chain[J11] has 18 asic
Chain[J12] has 18 asic
Chain[J13] has 18 asic
Chain[J14] has 18 asic
Chain[J9] has no freq in PIC, set default freq=400M
Chain[J9] has no core num in PIC
Chain[J10] has no freq in PIC, set default freq=400M
Chain[J10] has no core num in PIC
Chain[J11] has no freq in PIC, set default freq=400M
Chain[J11] has no core num in PIC
Chain[J12] has no freq in PIC, set default freq=400M
Chain[J12] has no core num in PIC
Chain[J13] has no freq in PIC, set default freq=400M
Chain[J13] has no core num in PIC
Chain[J14] has no freq in PIC, set default freq=400M
Chain[J14] has no core num in PIC

Miner fix freq ...
read PIC voltage=930 on chain[8]
Chain:8 chipnum=18
Asic[ 0]:400 
Asic[ 1]:400 Asic[ 2]:400 Asic[ 3]:400 Asic[ 4]:400 Asic[ 5]:400 Asic[ 6]:400 Asic[ 7]:400 Asic[ 8]:400 
Asic[ 9]:400 Asic[10]:400 Asic[11]:400 Asic[12]:400 Asic[13]:400 Asic[14]:400 Asic[15]:400 Asic[16]:400 
Asic[17]:400 
Chain:8 max freq=400
Chain:8 min freq=400

read PIC voltage=930 on chain[9]
Chain:9 chipnum=18
Asic[ 0]:400 
Asic[ 1]:400 Asic[ 2]:400 Asic[ 3]:400 Asic[ 4]:400 Asic[ 5]:400 Asic[ 6]:400 Asic[ 7]:400 Asic[ 8]:400 
Asic[ 9]:400 Asic[10]:400 Asic[11]:400 Asic[12]:400 Asic[13]:400 Asic[14]:400 Asic[15]:400 Asic[16]:400 
Asic[17]:400 
Chain:9 max freq=400
Chain:9 min freq=400

read PIC voltage=930 on chain[10]
Chain:10 chipnum=18
Asic[ 0]:400 
Asic[ 1]:400 Asic[ 2]:400 Asic[ 3]:400 Asic[ 4]:400 Asic[ 5]:400 Asic[ 6]:400 Asic[ 7]:400 Asic[ 8]:400 
Asic[ 9]:400 Asic[10]:400 Asic[11]:400 Asic[12]:400 Asic[13]:400 Asic[14]:400 Asic[15]:400 Asic[16]:400 
Asic[17]:400 
Chain:10 max freq=400
Chain:10 min freq=400

read PIC voltage=930 on chain[11]
Chain:11 chipnum=18
Asic[ 0]:400 
Asic[ 1]:400 Asic[ 2]:400 Asic[ 3]:400 Asic[ 4]:400 Asic[ 5]:400 Asic[ 6]:400 Asic[ 7]:400 Asic[ 8]:400 
Asic[ 9]:400 Asic[10]:400 Asic[11]:400 Asic[12]:400 Asic[13]:400 Asic[14]:400 Asic[15]:400 Asic[16]:400 
Asic[17]:400 
Chain:11 max freq=400
Chain:11 min freq=400

read PIC voltage=930 on chain[12]
Chain:12 chipnum=18
Asic[ 0]:400 
Asic[ 1]:400 Asic[ 2]:400 Asic[ 3]:400 Asic[ 4]:400 Asic[ 5]:400 Asic[ 6]:400 Asic[ 7]:400 Asic[ 8]:400 
Asic[ 9]:400 Asic[10]:400 Asic[11]:400 Asic[12]:400 Asic[13]:400 Asic[14]:400 Asic[15]:400 Asic[16]:400 
Asic[17]:400 
Chain:12 max freq=400
Chain:12 min freq=400

read PIC voltage=930 on chain[13]
Chain:13 chipnum=18
Asic[ 0]:400 
Asic[ 1]:400 Asic[ 2]:400 Asic[ 3]:400 Asic[ 4]:400 Asic[ 5]:400 Asic[ 6]:400 Asic[ 7]:400 Asic[ 8]:400 
Asic[ 9]:400 Asic[10]:400 Asic[11]:400 Asic[12]:400 Asic[13]:400 Asic[14]:400 Asic[15]:400 Asic[16]:400 
Asic[17]:400 
Chain:13 max freq=400
Chain:13 min freq=400

max freq = 400
set baud=4
Chain[J9] PIC temp offset=1,-7,0,0,0,0,33,28
Chain[J9] chip[0] use PIC middle temp offset=-7 typeID=55
New offset Chain[8] chip[0] local:27 remote:34 offset:23 
Chain[J9] chip[0] get middle temp offset=23 typeID=55
Chain[J9] chip[128] use PIC middle temp offset=28 typeID=00
Warning: Chain[J9] has no temp offset in PIC! will fix it
New offset Chain[8] chip[0] local:27 remote:34 offset:23 
Chain[J9] chip[0] get middle temp offset=23 typeID=55
New offset Chain[8] chip[32] local:-64 remote:0 offset:-42 
Chain[J9] chip[32] get middle temp offset=-42 typeID=00
Chain[J11] PIC temp offset=1,-4,0,0,0,0,33,28
Chain[J11] chip[0] use PIC middle temp offset=-4 typeID=55
New offset Chain[10] chip[0] local:30 remote:34 offset:26 
Chain[J11] chip[0] get middle temp offset=26 typeID=55
Chain[J11] chip[128] use PIC middle temp offset=28 typeID=00
Warning: Chain[J11] has no temp offset in PIC! will fix it
New offset Chain[10] chip[0] local:31 remote:34 offset:27 
Chain[J11] chip[0] get middle temp offset=27 typeID=55
New offset Chain[10] chip[32] local:-64 remote:0 offset:-42 
Chain[J11] chip[32] get middle temp offset=-42 typeID=00
Chain[J13] PIC temp offset=1,-5,0,0,0,0,33,28
Chain[J13] chip[0] use PIC middle temp offset=-5 typeID=55
New offset Chain[12] chip[0] local:25 remote:26 offset:29 
Chain[J13] chip[0] get middle temp offset=29 typeID=55
Chain[J13] chip[128] use PIC middle temp offset=28 typeID=00
Warning: Chain[J13] has no temp offset in PIC! will fix it
New offset Chain[12] chip[0] local:25 remote:27 offset:28 
Chain[J13] chip[0] get middle temp offset=28 typeID=55
New offset Chain[12] chip[32] local:-64 remote:0 offset:-42 
Chain[J13] chip[32] get middle temp offset=-42 typeID=00
setStartTimePoint total_tv_start_sys=178 total_tv_end_sys=179
restartNum = 2 , auto-reinit enabled...
do read_temp_func once...
do check_asic_reg 0x08

get RT hashrate from Chain[8]: (asic index start from 1-18)

get RT hashrate from Chain[9]: (asic index start from 1-18)

get RT hashrate from Chain[10]: (asic index start from 1-18)

get RT hashrate from Chain[11]: (asic index start from 1-18)

get RT hashrate from Chain[12]: (asic index start from 1-18)

get RT hashrate from Chain[13]: (asic index start from 1-18)
Check Chain[J9] ASIC RT error: (asic index start from 1-18)
Check Chain[J10] ASIC RT error: (asic index start from 1-18)
Check Chain[J11] ASIC RT error: (asic index start from 1-18)
Check Chain[J12] ASIC RT error: (asic index start from 1-18)
Check Chain[J13] ASIC RT error: (asic index start from 1-18)
Check Chain[J14] ASIC RT error: (asic index start from 1-18)
Done check_asic_reg
do read temp on Chain[8]
Chain[8] Chip[1] TempTypeID=55 middle offset=23
read failed, old value: Chain[8] Chip[1] local Temp=0
read failed on Chain[8] Chip[1] middle Temp old value:0
Chain[8] Chip[9] TempTypeID=00 middle offset=-42
read failed, old value: Chain[8] Chip[9] local Temp=0
read failed on Chain[8] Chip[9] middle Temp old value:0
Done read temp on Chain[8]
do read temp on Chain[10]
Chain[10] Chip[1] TempTypeID=55 middle offset=27
read failed, old value: Chain[10] Chip[1] local Temp=0
read failed on Chain[10] Chip[1] middle Temp old value:0
Chain[10] Chip[9] TempTypeID=00 middle offset=-42
read failed, old value: Chain[10] Chip[9] local Temp=0
read failed on Chain[10] Chip[9] middle Temp old value:0
Done read temp on Chain[10]
do read temp on Chain[12]
Chain[12] Chip[1] TempTypeID=55 middle offset=28
read failed, old value: Chain[12] Chip[1] local Temp=0
read failed on Chain[12] Chip[1] middle Temp old value:0
Chain[12] Chip[9] TempTypeID=00 middle offset=-42
read failed, old value: Chain[12] Chip[9] local Temp=0
read failed on Chain[12] Chip[9] middle Temp old value:0
Done read temp on Chain[12]
set FAN speed according to: temp_highest=0 temp_top1[PWM_T]=0 temp_top1[TEMP_POS_LOCAL]=0 temp_change=0 fix_fan_steps=0
set full FAN speed...
FAN PWM: 100
read_temp_func Done!
CRC error counter=44

[kano]

I think the obvious point to make is don't put non-original firmware in your miners.
There are plenty of reasons why not to.

[sahinkod]

please s9 hex file

[Bill48105]

I think the obvious point to make is don't put non-original firmware in your miners.
There are plenty of reasons why not to.

Generally speaking yes it's a bad idea to run non-original or unofficial firmware *except* in my case (and seems with others), downloading the source for the original/official miner from official bitmain github, building it per included instructions, then running it on T9+ essentially bricks the cards. One by one.. The longer you leave it running & auto-rebooting, the more cards it kills. It seems to happen if someone upgraded to the autotune firmware which must flash updates to the boards then the older software thinks the boards are corrupt so it tries to flash them & it appears to flash them wrong or with wrong version etc.  I didn't make note of what version of firmware these shipped with but if it wasn't the autotune one that's available on their site it's possible anyone flashing the pre-autotune firmware might end up in the same boat.

[thierry4wd]

by force of working on the source I noticed an error,

in the source code to bmminer more problem, that I coriated, BUT, in the source code, for the T9 +, he verifies the verssion of the PIC, then ... against all odds, apply the update of the S9 !! ! to know :

Code:

// S9 , T9,  R4    PIC PROGRAM
#define PIC_PROGRAM "/etc/config/hash_s8_app.txt"

so there would be a solution to flash the card without pickit .... corrected this problem, but I have neither the temp nor the envi of brick again and restart my T9 +