Title: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on September 19, 2018, 09:25:13 PM
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 https://image.noelshack.com/minis/2020/09/6/1583005276-20180919-221729.png (https://www.noelshack.com/2020-09-6-1583005276-20180919-221729.jpg) 2 - Connect on MPLAB https://image.noelshack.com/minis/2020/09/6/1583005264-connect.png (https://www.noelshack.com/2020-09-6-1583005264-connect.jpg) 3 - Enter in advanced mode and take "power target circuit from tool" https://image.noelshack.com/minis/2020/09/6/1583005264-voltage-pic.png (https://www.noelshack.com/2020-09-6-1583005264-voltage-pic.jpg) 4 - ERASE the pic (use if you sure that the hash board is hs) 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 ) 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 ! 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) 241 #define ENABLE_RESTORE_PIC_APP // if enabled, will restore PIC APP when the version is not correct!!!
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: x3aklili on September 20, 2018, 08:24:02 PM
exelent Work!!! my miner is back to life again
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on September 20, 2018, 09:48:51 PM
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 :)?
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: zacocity on September 21, 2018, 04:21:13 AM
We have tested this with some users before, but it does not seem to work for everyone. I'm glad it worked for you :)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on September 21, 2018, 05:48:39 PM
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: chain [1] PIC jump to app Check chain [1] PIC fw version = 0x03 (or other)
but if you have: 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 ;)
Title: ayyyyyyyy
Post by: taserz on September 24, 2018, 10:03:06 AM
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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: HagssFIN on September 24, 2018, 10:44:40 AM
Great post and for sure a great help for many people. :) I gave you some merit.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on September 25, 2018, 05:39:17 PM
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;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: digital$ on September 26, 2018, 08:28:13 AM
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?
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on September 28, 2018, 01:51:05 PM
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;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: danielyap on October 02, 2018, 11:57:13 AM
I'm getting this error T9+ August Batch 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! :(
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on October 02, 2018, 01:47:34 PM
Of course ! Plug this on the all on your hash board ! And see my tuto.
Your picture is ok to connect this ! ;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: danielyap on October 07, 2018, 03:32:29 PM
Hmm. I've been successful for some boards but sometimes when I try to connect the board, this is what I get... *****************************************************
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, 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!
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on October 07, 2018, 04:18:53 PM
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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: danielyap on October 08, 2018, 02:13:27 AM
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)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: tim-bc on October 09, 2018, 03:21:35 AM
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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: danielyap on October 09, 2018, 04:22:12 AM
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 [ 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!
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: marlonmem on October 23, 2018, 05:56:41 PM
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
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: BitMaxz on October 23, 2018, 06:35:56 PM
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 (https://reviahh.wordpress.com/2016/01/31/making-a-pickit-3-clone/).
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on October 25, 2018, 02:59:03 PM
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 ;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on October 31, 2018, 11:11:24 PM
Litle UP !
If any people is interessed by HEX file for S9 ??? if yes, i ready to extract this on needed ;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: tim-bc on November 02, 2018, 12:16:14 AM
Does pickit 3 work with pic16 also? Or only pic32?
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on November 02, 2018, 11:37:36 AM
Of corse ! PicKit 3 ready to work for all hashboard for all antminer !!! ;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: Dodgymon on November 21, 2018, 11:12:43 AM
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
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on November 21, 2018, 05:00:53 PM
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;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on November 24, 2018, 03:52:00 PM
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;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: Bill48105 on December 12, 2018, 10:30:27 PM
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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: BitMaxz on December 14, 2018, 12:01:00 AM
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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: Bill48105 on December 14, 2018, 02:51:25 AM
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: 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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on December 14, 2018, 08:48:57 PM
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 !!!
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: Bill48105 on December 16, 2018, 06:00:51 AM
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!! :D 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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on December 16, 2018, 08:53:20 PM
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?
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: Bill48105 on December 16, 2018, 10:24:53 PM
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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: mediann on December 28, 2018, 07:35:56 PM
I'm having this problem. 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. 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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: BitMaxz on December 28, 2018, 10:17:04 PM
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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: mediann on December 29, 2018, 12:51:38 AM
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 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
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: kano on December 29, 2018, 10:44:03 AM
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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: sahinkod on January 17, 2019, 12:22:52 PM
please s9 hex file
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: Bill48105 on January 17, 2019, 04:42:23 PM
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.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on January 17, 2019, 08:51:02 PM
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 : // 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 +
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: HagssFIN on January 21, 2019, 06:09:26 AM
HOW CAN I DISMOUNT FIRMWARE DOLLEMIZER. LOCK MY CONTROL BOARD S9. DO NOT DELIVER IP AND DO NOT ACCEPT RE-INTALING OFFICIAL FIRMWARE BITMAIN. THANK YOU
^You can try the IP Report button reset. Instructions: https://support.bitmain.com/hc/en-us/articles/115003595387-How-to-reset-miner-to-factory-settings- See chapter 3, "Restore via "IP Report" button". Also, please don't overuse CAPS LOCK. IT LOOKS VERY STUPID.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: mikeywith on January 21, 2019, 09:38:02 PM
HOW CAN I DISMOUNT FIRMWARE DOLLEMIZER. LOCK MY CONTROL BOARD S9. DO NOT DELIVER IP AND DO NOT ACCEPT RE-INTALING OFFICIAL FIRMWARE BITMAIN. THANK YOU
would you please stop using caps lock ? why can't you load the original firmware back? what error do you get? edit : lol just found out that i am not the only one disturbed by the caps lock.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: GreenDrago6972 on March 03, 2019, 12:59:25 PM
Is there another way to do this other then this method ?
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: philipma1957 on March 03, 2019, 01:43:30 PM
Is there another way to do this other then this method ?
buy a t9 board with proper flashing
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: MrCrank on March 03, 2019, 04:19:59 PM
Thanks for good job. I have few T9+ and this is very useful information for me. Do you have experience of overclocking upto 14TH?
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: BitMaxz on March 03, 2019, 07:48:00 PM
Do you have experience of overclocking upto 14TH?
There is a method that you can overclock antminer T9 miner to 14TH by editing the set_miner_conf.cgi through ssh. Check it from here How To Overclock Your S9/T9+,T9,R4 To 18TH/s Free. (https://bitcointalk.org/index.php?topic=4425212.0)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: MrCrank on March 04, 2019, 04:52:50 PM
Where can download firmware source code? I checked bitmain and can't found. I want modify it. Thx.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on March 04, 2019, 08:58:59 PM
Hi T9+ can not be overclocked without modification of Bmminer: s this one is blocked at 810mv audela of 675mhz of memory ... I compiled Bmminer for T9 + blocked at 840mv, and that allows me to go up to 750mhz for 13.65Ths with 1600w at Wall ... The max overclock without bmminer modified is 12Th - 12.3Th at 1400w ... https://image.noelshack.com/minis/2019/10/1/1551734305-t9-oc.png (https://www.noelshack.com/2019-10-1-1551734305-t9-oc.png)
There is a method that you can overclock antminer T9 miner to 14TH by editing the set_miner_conf.cgi through ssh.
Check it from here How To Overclock Your S9/T9+,T9,R4 To 18TH/s Free. (https://bitcointalk.org/index.php?topic=4425212.0)
this method works well but is based on a software bug, I strongly don't recommend VERY strongly !!! the miner run VERY VERY VERY HOT !!! warning !!!!
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: aramconde on April 25, 2019, 11:07:45 PM
please can you make for me a video tutorial if your not busy and have time,i buy a old T9+ and 1 hashboard is not working and my hashrate is 7Th only,thank you in advance.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: rotem8866 on June 06, 2019, 11:50:13 AM
Hi. I followed all procedure and flashing is done successfuly. after reconnecting all again i still have 000000 ghz. see kernel log. (i also flashed the official firmware to the controller.) what can cause it ? [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.14.0-xilinx-gb190cb0-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #57 SMP PREEMPT Fri Dec 9 14:49:22 CST 2016 [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: Xilinx Zynq [ 0.000000] cma: CMA: reserved 128 MiB at 16800000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] On node 0 totalpages: 126976 [ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map debd8000 [ 0.000000] Normal zone: 992 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 126976 pages, LIFO batch:31 [ 0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9088 r8192 d15488 u32768 [ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 125984 [ 0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 364356K/507904K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 143548K reserved, 0K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xdf800000 - 0xff000000 ( 504 MB) [ 0.000000] lowmem : 0xc0000000 - 0xdf000000 ( 496 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB) [ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB) [ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB) [ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] ps7-slcr mapped to df802000 [ 0.000000] zynq_clock_init: clkc starts at df802100 [ 0.000000] Zynq clock init [ 0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns [ 0.000311] ps7-ttc #0 at df804000, irq=43 [ 0.000618] Console: colour dummy device 80x30 [ 0.000649] Calibrating delay loop... 1332.01 BogoMIPS (lpj=6660096) [ 0.100251] pid_max: default: 32768 minimum: 301 [ 0.100472] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.100492] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.102644] CPU: Testing write buffer coherency: ok [ 0.102978] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.103038] Setting up static identity map for 0x4c4af8 - 0x4c4b50 [ 0.103260] L310 cache controller enabled [ 0.103280] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB [ 0.181033] CPU1: Booted secondary processor [ 0.270229] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.270360] Brought up 2 CPUs [ 0.270379] SMP: Total of 2 processors activated. [ 0.270387] CPU: All CPU(s) started in SVC mode. [ 0.271047] devtmpfs: initialized [ 0.273472] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.274681] regulator-dummy: no parameters [ 0.282358] NET: Registered protocol family 16 [ 0.284639] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.286921] cpuidle: using governor ladder [ 0.286934] cpuidle: using governor menu [ 0.294307] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered [ 0.295821] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.295834] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.295948] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000 [ 0.317424] bio: create slab <bio-0> at 0 [ 0.318835] vgaarb: loaded [ 0.319535] SCSI subsystem initialized [ 0.320480] usbcore: registered new interface driver usbfs [ 0.320669] usbcore: registered new interface driver hub [ 0.320889] usbcore: registered new device driver usb [ 0.322168] media: Linux media interface: v0.10 [ 0.322331] Linux video capture interface: v2.00 [ 0.322572] pps_core: LinuxPPS API ver. 1 registered [ 0.322583] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.322707] PTP clock support registered [ 0.323067] EDAC MC: Ver: 3.0.0 [ 0.324108] Advanced Linux Sound Architecture Driver Initialized. [ 0.326945] DMA-API: preallocated 4096 debug entries [ 0.326960] DMA-API: debugging enabled by kernel config [ 0.327035] Switched to clocksource arm_global_timer [ 0.347152] NET: Registered protocol family 2 [ 0.347822] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [ 0.347878] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) [ 0.347963] TCP: Hash tables configured (established 4096 bind 4096) [ 0.348009] TCP: reno registered [ 0.348027] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 0.348059] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 0.348295] NET: Registered protocol family 1 [ 0.348640] RPC: Registered named UNIX socket transport module. [ 0.348653] RPC: Registered udp transport module. [ 0.348662] RPC: Registered tcp transport module. [ 0.348670] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.348683] PCI: CLS 0 bytes, default 64 [ 0.349119] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available [ 0.351135] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.353230] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.353414] msgmni has been set to 967 [ 0.354197] io scheduler noop registered [ 0.354210] io scheduler deadline registered [ 0.354263] io scheduler cfq registered (default) [ 0.362865] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208 [ 0.362885] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16 [ 0.485434] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps [ 1.054037] console [ttyPS0] enabled [ 1.058335] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000 [ 1.065935] [drm] Initialized drm 1.1.0 20060810 [ 1.082864] brd: module loaded [ 1.092293] loop: module loaded [ 1.101735] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 1.107590] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 1.115343] libphy: XEMACPS mii bus: probed [ 1.119988] ------------- phy_id = 0x3625e62 [ 1.124723] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54 [ 1.133354] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.140011] ehci-pci: EHCI PCI platform driver [ 1.147250] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing? [ 1.154046] usbcore: registered new interface driver usb-storage [ 1.160921] mousedev: PS/2 mouse device common for all mice [ 1.167081] i2c /dev entries driver [ 1.173959] zynq-edac f8006000.ps7-ddrc: ecc not enabled [ 1.179510] cpufreq_cpu0: failed to get cpu0 regulator: -19 [ 1.185392] Xilinx Zynq CpuIdle Driver started [ 1.190256] sdhci: Secure Digital Host Controller Interface driver [ 1.196353] sdhci: Copyright(c) Pierre Ossman [ 1.200742] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.207517] mmc0: no vqmmc regulator found [ 1.211530] mmc0: no vmmc regulator found [ 1.247056] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA [ 1.255735] usbcore: registered new interface driver usbhid [ 1.261242] usbhid: USB HID core driver [ 1.265957] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda [ 1.272258] nand: Micron MT29F2G08ABAEAWP [ 1.276222] nand: 256MiB, SLC, page size: 2048, OOB size: 64 [ 1.282163] Bad block table found at page 131008, version 0x01 [ 1.288390] Bad block table found at page 130944, version 0x01 [ 1.294444] 3 ofpart partitions found on MTD device pl353-nand [ 1.300231] Creating 3 MTD partitions on "pl353-nand": [ 1.305325] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel" [ 1.313373] 0x000002000000-0x00000b000000 : "angstram-rootfs" [ 1.320687] 0x00000b000000-0x000010000000 : "upgrade-rootfs" [ 1.329639] TCP: cubic registered [ 1.332877] NET: Registered protocol family 17 [ 1.337593] Registering SWP/SWPB emulation handler [ 1.343475] regulator-dummy: disabling [ 1.347819] UBI: attaching mtd1 to ubi0 [ 1.873546] UBI: scanning is finished [ 1.885222] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0 [ 1.892302] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [ 1.899064] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [ 1.905729] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096 [ 1.912607] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0 [ 1.918587] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 [ 1.925695] UBI: max/mean erase counter: 2/0, WL threshold: 4096, image sequence number: 862493722 [ 1.934650] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40 [ 1.943867] UBI: background thread "ubi_bgt0d" started, PID 1080 [ 1.943872] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 1.947834] ALSA device list: [ 1.947837] No soundcards found. [ 1.964211] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082 [ 1.993337] UBIFS: recovery needed [ 2.219536] UBIFS: recovery completed [ 2.223210] UBIFS: mounted UBI device 0, volume 0, name "rootfs" [ 2.229155] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [ 2.238260] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs) [ 2.248149] UBIFS: reserved for root: 0 bytes (0 KiB) [ 2.253179] UBIFS: media format: w4/r0 (latest is w4/r0), UUID 2A24A8E1-2021-4A54-8A4E-D8E294AE00E5, small LPT model [ 2.264484] VFS: Mounted root (ubifs filesystem) on device 0:11. [ 2.271212] devtmpfs: mounted [ 2.274323] Freeing unused kernel memory: 204K (c06d2000 - c0705000) [ 3.113849] random: dd urandom read with 0 bits of entropy available [ 3.507063] [ 3.507063] bcm54xx_config_init [ 4.117083] [ 4.117083] bcm54xx_config_init [ 7.117908] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz [ 7.123999] xemacps e000b000.ps7-ethernet: link up (100/FULL) [ 22.100699] In axi fpga driver! [ 22.103768] request_mem_region OK! [ 22.107190] AXI fpga dev virtual address is 0xdf9fc000 [ 22.112265] *base_vir_addr = 0xc510 [ 22.127201] In fpga mem driver! [ 22.130427] request_mem_region OK! [ 22.133987] fpga mem virtual address is 0xe2000000 [ 22.927048] [ 22.927048] bcm54xx_config_init [ 23.557049] [ 23.557049] bcm54xx_config_init [ 26.557913] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz [ 26.563933] xemacps e000b000.ps7-ethernet: link up (100/FULL) This is XILINX board. Totalram: 507527168 Detect 512MB control board of XILINX DETECT HW version=8000c510 miner ID : 80148c806f904814 Miner Type = T9+ AsicType = 1387 real AsicNum = 18 use critical mode to search freq... get PLUG ON=0x07003f0e Find hashboard on Chain[1] Find hashboard on Chain[2] Find hashboard on Chain[3] Find hashboard on Chain[8] Find hashboard on Chain[9] Find hashboard on Chain[10] Find hashboard on Chain[11] Find hashboard on Chain[12] Find hashboard on Chain[13] set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_reset_pic failed on Chain[1]! try again... dsPIC33EP16GS202_reset_pic failed on Chain[1]! try again... dsPIC33EP16GS202_reset_pic failed on Chain[1]! try again... chain[1] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[1]! try again... dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[1]! try again... dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[1]! try again... dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! Check chain[1] PIC fw version=0xff 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[1] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x01 0x11 0x11 0x11 0x11 0x11 0x12 0x21 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x20 0x11 0x12 0x11 0x10 0x11 0x11 0x11 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x11 0x11 0x11 0x11 0x11 0x11 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] has freq in PIC, will disable freq setting. chain[1] has freq in PIC and will jump over... Chain[1] has core num in PIC Chain[1] ASIC[1] has core num=1 Chain[1] ASIC[2] has core num=1 Chain[1] ASIC[3] has core num=1 Chain[1] ASIC[4] has core num=1 Chain[1] ASIC[5] has core num=1 Chain[1] ASIC[6] has core num=1 Chain[1] ASIC[7] has core num=1 Chain[1] ASIC[8] has core num=1 Chain[1] ASIC[9] has core num=1 Chain[1] ASIC[10] has core num=1 Chain[1] ASIC[11] has core num=1 Chain[1] ASIC[12] has core num=1 Chain[1] ASIC[13] has core num=2 Chain[1] ASIC[14] has core num=2 Chain[1] ASIC[15] has core num=1 Chain[1] ASIC[16] has core num=1 Chain[1] ASIC[17] has core num=1 Chain[2] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x10 0x11 0x11 0x11 0x11 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x10 0x01 0x11 0x11 0x20 0x21 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x10 0x10 0x31 0x11 0x11 0x11 0x11 0x01 0x11 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] has freq in PIC, will disable freq setting. chain[2] has freq in PIC and will jump over... Chain[2] has core num in PIC Chain[2] ASIC[0] has core num=1 Chain[2] ASIC[1] has core num=1 Chain[2] ASIC[2] has core num=1 Chain[2] ASIC[3] has core num=1 Chain[2] ASIC[4] has core num=1 Chain[2] ASIC[5] has core num=1 Chain[2] ASIC[6] has core num=1 Chain[2] ASIC[8] has core num=1 Chain[2] ASIC[9] has core num=1 Chain[2] ASIC[10] has core num=1 Chain[2] ASIC[11] has core num=1 Chain[2] ASIC[12] has core num=1 Chain[2] ASIC[13] has core num=1 Chain[2] ASIC[14] has core num=1 Chain[2] ASIC[15] has core num=1 Chain[2] ASIC[16] has core num=1 Chain[2] ASIC[17] has core num=1 Chain[3] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x01 0x11 0x11 0x31 0x11 0x11 0x11 0x11 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x11 0x10 0x01 0x11 0x11 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x10 0x11 0x11 0x11 0x21 0x11 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] has freq in PIC, will disable freq setting. chain[3] has freq in PIC and will jump over... Chain[3] has core num in PIC Chain[3] ASIC[1] has core num=1 Chain[3] ASIC[2] has core num=1 Chain[3] ASIC[3] has core num=1 Chain[3] ASIC[4] has core num=1 Chain[3] ASIC[5] has core num=1 Chain[3] ASIC[6] has core num=3 Chain[3] ASIC[7] has core num=1 Chain[3] ASIC[8] has core num=1 Chain[3] ASIC[9] has core num=1 Chain[3] ASIC[10] has core num=1 Chain[3] ASIC[11] has core num=1 Chain[3] ASIC[12] has core num=1 Chain[3] ASIC[13] has core num=1 Chain[3] ASIC[14] has core num=1 Chain[3] ASIC[15] has core num=1 Chain[3] ASIC[16] has core num=1 Chain[3] ASIC[17] has core num=1 has freq in PIC, will disable freq setting. chain[8] has freq in PIC and will jump over... Chain[8] has core num in PIC Chain[8] ASIC[0] has core num=2 Chain[8] ASIC[2] has core num=1 Chain[8] ASIC[3] has core num=1 Chain[8] ASIC[4] has core num=1 Chain[8] ASIC[5] has core num=2 Chain[8] ASIC[6] has core num=1 Chain[8] ASIC[7] has core num=1 Chain[8] ASIC[8] has core num=1 Chain[8] ASIC[10] has core num=1 Chain[8] ASIC[11] has core num=1 Chain[8] ASIC[12] has core num=1 Chain[8] ASIC[13] has core num=1 Chain[8] ASIC[14] has core num=1 Chain[8] ASIC[15] has core num=1 Chain[8] ASIC[16] has core num=1 Chain[8] ASIC[17] has core num=1 has freq in PIC, will disable freq setting. chain[9] has freq in PIC and will jump over... Chain[9] has core num in PIC Chain[9] ASIC[0] has core num=1 Chain[9] ASIC[1] has core num=1 Chain[9] ASIC[2] has core num=1 Chain[9] ASIC[3] has core num=1 Chain[9] ASIC[4] has core num=1 Chain[9] ASIC[5] has core num=1 Chain[9] ASIC[6] has core num=1 Chain[9] ASIC[7] has core num=1 Chain[9] ASIC[8] has core num=1 Chain[9] ASIC[9] has core num=1 Chain[9] ASIC[10] has core num=1 Chain[9] ASIC[11] has core num=1 Chain[9] ASIC[12] has core num=1 Chain[9] ASIC[13] has core num=1 Chain[9] ASIC[14] has core num=1 Chain[9] ASIC[15] has core num=1 Chain[9] ASIC[16] has core num=1 Chain[9] ASIC[17] has core num=1 has freq in PIC, will disable freq setting. chain[10] has freq in PIC and will jump over... Chain[10] has core num in PIC Chain[10] ASIC[0] has core num=1 Chain[10] ASIC[1] has core num=1 Chain[10] ASIC[2] has core num=1 Chain[10] ASIC[3] has core num=1 Chain[10] ASIC[4] has core num=1 Chain[10] ASIC[5] has core num=1 Chain[10] ASIC[6] has core num=1 Chain[10] ASIC[9] has core num=1 Chain[10] ASIC[10] has core num=1 Chain[10] ASIC[11] has core num=1 Chain[10] ASIC[12] has core num=1 Chain[10] ASIC[13] has core num=1 Chain[10] ASIC[14] has core num=2 Chain[10] ASIC[16] has core num=2 Chain[10] ASIC[17] has core num=1 has freq in PIC, will disable freq setting. chain[11] has freq in PIC and will jump over... Chain[11] has core num in PIC Chain[11] ASIC[0] has core num=1 Chain[11] ASIC[2] has core num=1 Chain[11] ASIC[4] has core num=3 Chain[11] ASIC[5] has core num=1 Chain[11] ASIC[6] has core num=1 Chain[11] ASIC[7] has core num=1 Chain[11] ASIC[8] has core num=1 Chain[11] ASIC[9] has core num=1 Chain[11] ASIC[10] has core num=1 Chain[11] ASIC[11] has core num=1 Chain[11] ASIC[12] has core num=1 Chain[11] ASIC[13] has core num=1 Chain[11] ASIC[15] has core num=1 Chain[11] ASIC[16] has core num=1 Chain[11] ASIC[17] has core num=1 has freq in PIC, will disable freq setting. chain[12] has freq in PIC and will jump over... Chain[12] has core num in PIC Chain[12] ASIC[0] has core num=1 Chain[12] ASIC[1] has core num=1 Chain[12] ASIC[2] has core num=1 Chain[12] ASIC[3] has core num=1 Chain[12] ASIC[4] has core num=1 Chain[12] ASIC[5] has core num=1 Chain[12] ASIC[6] has core num=1 Chain[12] ASIC[7] has core num=1 Chain[12] ASIC[8] has core num=1 Chain[12] ASIC[11] has core num=1 Chain[12] ASIC[12] has core num=1 Chain[12] ASIC[13] has core num=1 Chain[12] ASIC[14] has core num=1 Chain[12] ASIC[15] has core num=1 Chain[12] ASIC[16] has core num=1 Chain[12] ASIC[17] has core num=1 has freq in PIC, will disable freq setting. chain[13] has freq in PIC and will jump over... Chain[13] has core num in PIC Chain[13] ASIC[0] has core num=1 Chain[13] ASIC[1] has core num=1 Chain[13] ASIC[2] has core num=1 Chain[13] ASIC[3] has core num=1 Chain[13] ASIC[4] has core num=1 Chain[13] ASIC[5] has core num=1 Chain[13] ASIC[6] has core num=1 Chain[13] ASIC[8] has core num=1 Chain[13] ASIC[9] has core num=1 Chain[13] ASIC[10] has core num=1 Chain[13] ASIC[11] has core num=1 Chain[13] ASIC[12] has core num=1 Chain[13] ASIC[13] has core num=1 Chain[13] ASIC[14] has core num=2 Chain[13] ASIC[15] has core num=1 Chain[13] ASIC[16] has core num=1 Chain[13] ASIC[17] has core num=1 get PIC voltage=11 on chain[1], value=870 get PIC voltage=1 on chain[2], value=930 get PIC voltage=1 on chain[3], value=930 get PIC voltage=11 on chain[8], value=870 get PIC voltage=11 on chain[9], value=870 get PIC voltage=1 on chain[10], value=930 get PIC voltage=1 on chain[11], value=930 get PIC voltage=1 on chain[12], value=930 get PIC voltage=1 on chain[13], value=930 dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]! set_reset_allhashboard = 0x00000000 chain[8] temp offset record: -1,-1,-1,-1,-1,-1,-1,-1 chain[8] temp chip I2C addr=0x98 chain[10] temp offset record: -1,-1,-1,-1,-1,-1,-1,-1 chain[10] temp chip I2C addr=0x98 chain[12] temp offset record: -1,-1,-1,-1,-1,-1,-1,-1 chain[12] temp chip I2C addr=0x98 dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[1]! set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 CRC error counter=0 set command mode to VIL
--- check asic number After Get ASIC NUM CRC error counter=0 set_baud=0 The min freq=700 set real timeout 52, need sleep=379392 After TEST CRC error counter=0 search freq for 1 times, completed chain = 9, total chain num = 9 set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 restart Miner chance num=2 waiting for receive_func to exit! waiting for pic heart to exit! bmminer not found= 1451 root 0:00 grep bmminer
bmminer not found, restart bmminer ... This is user mode for mining Detect 512MB control board of XILINX Miner Type = T9+ Miner compile time: Fri Nov 24 23:19:16 EST 2017 type: Antminer T9+set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 set_reset_allhashboard = 0x0000ffff miner ID : 80148c806f904814 set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_reset_pic failed on Chain[1]! dsPIC33EP16GS202_reset_pic failed on Chain[1]! dsPIC33EP16GS202_reset_pic failed on Chain[1]! Checking fans!get fan[5] speed=5760 get fan[2] speed=6120 get fan[5] speed=5760 get fan[2] speed=6120 get fan[5] speed=5760 dsPIC33EP16GS202_reset_pic failed on Chain[1]! dsPIC33EP16GS202_reset_pic failed on Chain[1]! dsPIC33EP16GS202_reset_pic failed on Chain[1]! chain[1] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[1]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[1]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[1]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! Check chain[1] PIC fw version=0xff Chain[1] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x01 0x11 0x11 0x11 0x11 0x11 0x12 0x21 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x20 0x11 0x12 0x11 0x10 0x11 0x11 0x11 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x11 0x11 0x11 0x11 0x11 0x11 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] Chain[J2] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J2] test patten OK temp=-1 chain[2] PIC jump to app Check chain[2] PIC fw version=0x03 Chain[2] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x10 0x11 0x11 0x11 0x11 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x10 0x01 0x11 0x11 0x20 0x21 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x10 0x10 0x31 0x11 0x11 0x11 0x11 0x01 0x11 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] Chain[J3] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J3] test patten OK temp=-1 chain[3] PIC jump to app Check chain[3] PIC fw version=0x03 Chain[3] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x01 0x11 0x11 0x31 0x11 0x11 0x11 0x11 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x11 0x10 0x01 0x11 0x11 0x11 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x11 0x11 0x11 0x10 0x11 0x11 0x11 0x21 0x11 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] Chain[J4] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J4] test patten OK temp=-1 Chain[J9] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J9] test patten OK temp=-1 Chain[J10] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J10] test patten OK temp=-1 Chain[J11] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J11] test patten OK temp=-1 Chain[J12] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J12] test patten OK temp=-1 Chain[J13] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J13] test patten OK temp=-1 Chain[J14] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J14] test patten OK temp=-1 Chain[J2] will use voltage=930 [1] to open core set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[1]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[1]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[1]!
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 Chain[J2] orignal chain_voltage_pic=11 value=870 Chain[J3] orignal chain_voltage_pic=1 value=930 Chain[J3] will use backup chain_voltage_pic=870 [11] Chain[J3] get working chain_voltage_pic=11 Chain[J4] orignal chain_voltage_pic=1 value=930 Chain[J4] will use backup chain_voltage_pic=870 [11] Chain[J4] get working chain_voltage_pic=11 Chain[J9] orignal chain_voltage_pic=11 value=870 Chain[J10] orignal chain_voltage_pic=11 value=870 Chain[J11] orignal chain_voltage_pic=1 value=930 Chain[J11] will use backup chain_voltage_pic=870 [11] Chain[J11] get working chain_voltage_pic=11 Chain[J12] orignal chain_voltage_pic=1 value=930 Chain[J12] will use backup chain_voltage_pic=870 [11] Chain[J12] get working chain_voltage_pic=11 Chain[J13] orignal chain_voltage_pic=1 value=930 Chain[J13] will use backup chain_voltage_pic=870 [11] Chain[J13] get working chain_voltage_pic=11 Chain[J14] orignal chain_voltage_pic=1 value=930 Chain[J14] will use backup chain_voltage_pic=870 [11] Chain[J14] get working chain_voltage_pic=11 dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 1 time Chain[J2] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 2 time Chain[J2] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 3 time Chain[J2] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 4 time Chain[J2] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 5 time Chain[J2] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 6 time Chain[J2] has 0 asic miner total rate=0GH/s fixed rate=0GH/s
Miner fix freq ... max freq = 100 set baud=1 setStartTimePoint total_tv_start_sys=283 total_tv_end_sys=284 restartNum = 2 , auto-reinit enabled... do read_temp_func once... do check_asic_reg 0x08 Done check_asic_reg 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=0
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on June 06, 2019, 08:11:41 PM
Hi , at the first time you are resoled the problem "pic 0xff" , and is good !
After, what firmware you have flashed ? try to flash this (2017) https://file11.bitmain.com/shop-product/firmware/Antminer-T9-PLUS-all-201711242319-autofreq-user-Update2UBI-NF.tar.gz , and reset to default the miner ...
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: rotem8866 on June 07, 2019, 12:02:28 PM
Just did it and nothing. i also flashed with micro sd (https://support.bitmain.com/hc/en-us/articles/360007577214-T9-Control-Board-Program-Recovery) and then put the firmware you attached. still nothing.
i took other control board from second same machine and its work fine. so i guess i need to send the hash boards to repair.
Thanks!
p.s you have hex for s9 ? i have few boards that not working and i dont have any other working boards here.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on June 07, 2019, 02:23:54 PM
I think you had to miss something in the manipulation ...
I look your kernel log, and i see problem only by "chain 1" ... please unplug all hash board... and plug only one hashboard (other than chain 1) , and try it, and past here your new kernel log ...
If is running good, try to plug 1 hashboard to .... if running good to, reflash with pickit3 the last hashboard .
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on June 27, 2019, 03:33:07 PM
hi , i have updated first post with new link.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: Ortadan on July 06, 2019, 08:45:34 PM
Hello, I recently bought a damaged T9+ to replace (Fan, controller card) my other antminer and the 3 hasboard present this error: [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.14.0-xilinx-ge8a2f71-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #82 SMP PREEMPT Tue May 16 19:49:53 CST 2017 [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: Xilinx Zynq [ 0.000000] cma: CMA: reserved 128 MiB at 16800000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] On node 0 totalpages: 126976 [ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map debd8000 [ 0.000000] Normal zone: 992 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 126976 pages, LIFO batch:31 [ 0.000000] PERCPU: Embedded 8 pages/cpu @debc1000 s9088 r8192 d15488 u32768 [ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 125984 [ 0.000000] Kernel command line: noinitrd mem=496M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes) [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Memory: 364356K/507904K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 143548K reserved, 0K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xdf800000 - 0xff000000 ( 504 MB) [ 0.000000] lowmem : 0xc0000000 - 0xdf000000 ( 496 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB) [ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB) [ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB) [ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] ps7-slcr mapped to df802000 [ 0.000000] zynq_clock_init: clkc starts at df802100 [ 0.000000] Zynq clock init [ 0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns [ 0.000315] ps7-ttc #0 at df804000, irq=43 [ 0.000625] Console: colour dummy device 80x30 [ 0.000657] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328) [ 0.040211] pid_max: default: 32768 minimum: 301 [ 0.040434] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.040455] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.042631] CPU: Testing write buffer coherency: ok [ 0.042978] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.043040] Setting up static identity map for 0x4c4b00 - 0x4c4b58 [ 0.043264] L310 cache controller enabled [ 0.043284] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB [ 0.121039] CPU1: Booted secondary processor [ 0.210231] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.210361] Brought up 2 CPUs [ 0.210381] SMP: Total of 2 processors activated. [ 0.210389] CPU: All CPU(s) started in SVC mode. [ 0.211087] devtmpfs: initialized [ 0.213505] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.214759] regulator-dummy: no parameters [ 0.223745] NET: Registered protocol family 16 [ 0.226061] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.228373] cpuidle: using governor ladder [ 0.228386] cpuidle: using governor menu [ 0.235924] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered [ 0.237463] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.237477] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.237598] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xdf880000 [ 0.259526] bio: create slab <bio-0> at 0 [ 0.262232] vgaarb: loaded [ 0.262971] SCSI subsystem initialized [ 0.263864] usbcore: registered new interface driver usbfs [ 0.264037] usbcore: registered new interface driver hub [ 0.264265] usbcore: registered new device driver usb [ 0.264788] media: Linux media interface: v0.10 [ 0.264956] Linux video capture interface: v2.00 [ 0.265197] pps_core: LinuxPPS API ver. 1 registered [ 0.265209] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.265336] PTP clock support registered [ 0.265691] EDAC MC: Ver: 3.0.0 [ 0.266747] Advanced Linux Sound Architecture Driver Initialized. [ 0.269708] DMA-API: preallocated 4096 debug entries [ 0.269724] DMA-API: debugging enabled by kernel config [ 0.269819] Switched to clocksource arm_global_timer [ 0.289887] NET: Registered protocol family 2 [ 0.290585] TCP established hash table entries: 4096 (order: 2, 16384 bytes) [ 0.290644] TCP bind hash table entries: 4096 (order: 3, 32768 bytes) [ 0.290729] TCP: Hash tables configured (established 4096 bind 4096) [ 0.290781] TCP: reno registered [ 0.290799] UDP hash table entries: 256 (order: 1, 8192 bytes) [ 0.290832] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes) [ 0.291082] NET: Registered protocol family 1 [ 0.291466] RPC: Registered named UNIX socket transport module. [ 0.291480] RPC: Registered udp transport module. [ 0.291488] RPC: Registered tcp transport module. [ 0.291497] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.291510] PCI: CLS 0 bytes, default 64 [ 0.291988] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available [ 0.294075] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.296233] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.296420] msgmni has been set to 967 [ 0.297226] io scheduler noop registered [ 0.297239] io scheduler deadline registered [ 0.297282] io scheduler cfq registered (default) [ 0.308907] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208 [ 0.308927] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16 [ 0.437366] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps [ 1.005772] console [ttyPS0] enabled [ 1.010119] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to df866000 [ 1.017740] [drm] Initialized drm 1.1.0 20060810 [ 1.034801] brd: module loaded [ 1.044282] loop: module loaded [ 1.053993] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 1.059743] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 1.067728] libphy: XEMACPS mii bus: probed [ 1.072295] ------------- phy_id = 0x3625e62 [ 1.077045] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54 [ 1.085976] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.092801] ehci-pci: EHCI PCI platform driver [ 1.100057] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing? [ 1.106863] usbcore: registered new interface driver usb-storage [ 1.113778] mousedev: PS/2 mouse device common for all mice [ 1.119908] i2c /dev entries driver [ 1.126866] zynq-edac f8006000.ps7-ddrc: ecc not enabled [ 1.132397] cpufreq_cpu0: failed to get cpu0 regulator: -19 [ 1.138299] Xilinx Zynq CpuIdle Driver started [ 1.143215] sdhci: Secure Digital Host Controller Interface driver [ 1.149311] sdhci: Copyright(c) Pierre Ossman [ 1.153678] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.160542] mmc0: no vqmmc regulator found [ 1.164558] mmc0: no vmmc regulator found [ 1.209863] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA [ 1.218554] usbcore: registered new interface driver usbhid [ 1.224057] usbhid: USB HID core driver [ 1.228793] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda [ 1.235090] nand: Micron MT29F2G08ABAEAWP [ 1.239058] nand: 256MiB, SLC, page size: 2048, OOB size: 64 [ 1.245002] Bad block table found at page 131008, version 0x01 [ 1.251226] Bad block table found at page 130944, version 0x01 [ 1.257278] 3 ofpart partitions found on MTD device pl353-nand [ 1.263057] Creating 3 MTD partitions on "pl353-nand": [ 1.268148] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel" [ 1.276248] 0x000002000000-0x00000b000000 : "angstram-rootfs" [ 1.283570] 0x00000b000000-0x000010000000 : "upgrade-rootfs" [ 1.292565] TCP: cubic registered [ 1.295800] NET: Registered protocol family 17 [ 1.300531] Registering SWP/SWPB emulation handler [ 1.306452] regulator-dummy: disabling [ 1.310853] UBI: attaching mtd1 to ubi0 [ 1.838616] UBI: scanning is finished [ 1.850401] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0 [ 1.857456] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [ 1.864259] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [ 1.870921] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096 [ 1.877765] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0 [ 1.883772] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 [ 1.890894] UBI: max/mean erase counter: 126/62, WL threshold: 4096, image sequence number: 248547359 [ 1.900086] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40 [ 1.909289] UBI: background thread "ubi_bgt0d" started, PID 1080 [ 1.909295] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 1.913327] ALSA device list: [ 1.913331] No soundcards found. [ 1.929720] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082 [ 1.996221] UBIFS: mounted UBI device 0, volume 0, name "rootfs" [ 2.002174] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [ 2.011279] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs) [ 2.021169] UBIFS: reserved for root: 0 bytes (0 KiB) [ 2.026197] UBIFS: media format: w4/r0 (latest is w4/r0), UUID D5E65D66-FDFF-460C-B3DB-A1F2DEB908D8, small LPT model [ 2.037739] VFS: Mounted root (ubifs filesystem) on device 0:11. [ 2.045178] devtmpfs: mounted [ 2.048289] Freeing unused kernel memory: 204K (c06d2000 - c0705000) [ 2.892395] random: dd urandom read with 0 bits of entropy available [ 3.289840] [ 3.289840] bcm54xx_config_init [ 3.899866] [ 3.899866] bcm54xx_config_init [ 7.900703] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz [ 7.906793] xemacps e000b000.ps7-ethernet: link up (100/FULL) [ 24.777082] In axi fpga driver! [ 24.780183] request_mem_region OK! [ 24.783547] AXI fpga dev virtual address is 0xdf9fc000 [ 24.788652] *base_vir_addr = 0xc510 [ 24.804571] In fpga mem driver! [ 24.807646] request_mem_region OK! [ 24.811259] fpga mem virtual address is 0xe2000000 [ 25.619250] [ 25.619250] bcm54xx_config_init [ 26.249199] [ 26.249199] bcm54xx_config_init [ 30.249679] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz [ 30.255702] xemacps e000b000.ps7-ethernet: link up (100/FULL) 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 dsPIC33EP16GS202_reset_pic failed on Chain[1]! dsPIC33EP16GS202_reset_pic failed on Chain[1]! dsPIC33EP16GS202_reset_pic failed on Chain[1]! chain[1] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[1]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[1]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[1]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! Check chain[1] PIC fw version=0xff dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! chain[2] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! Check chain[2] PIC fw version=0xff chain[3] PIC jump to app Check chain[3] PIC fw version=0x90 Chain[J2] will use voltage=930 [1] to open core set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[1]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[1]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[1]!
Chain[J3] will use voltage=930 [1] to open core set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
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=675 custom_voltage_value=890 custom_voltage_enabled=1 disable_fan_check=0 fixed_frequency=1 Fix freq=675 Chain[1] voltage_pic=7 value=890 voltage_config=7792714 Fix freq=675 Chain[2] voltage_pic=7 value=890 voltage_config=7792714 Fix freq=675 Chain[3] voltage_pic=7 value=890 voltage_config=7792714 Fix freq=675 Chain[8] voltage_pic=7 value=890 voltage_config=7792714 Fix freq=675 Chain[9] voltage_pic=7 value=890 voltage_config=7792714 Fix freq=675 Chain[10] voltage_pic=7 value=890 voltage_config=7792714 Fix freq=675 Chain[11] voltage_pic=7 value=890 voltage_config=7792714 Fix freq=675 Chain[12] voltage_pic=7 value=890 voltage_config=7792714 Fix freq=675 Chain[13] voltage_pic=7 value=890 voltage_config=7792714 dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[1]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! 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 0 asic Chain[J10] has 0 asic Chain[J11] has 0 asic Chain[J12] has 0 asic Chain[J13] has 0 asic Chain[J14] has 0 asic miner total rate=0GH/s fixed rate=0GH/s
Miner fix freq ... max freq = 100 set baud=16 restartNum = 2 , auto-reinit enabled... setStartTimePoint total_tv_start_sys=343 total_tv_end_sys=344 do read_temp_func once... do check_asic_reg 0x08 Done check_asic_reg 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=0
would it be possible to repair the hashboards following the steps of this post by means of a pickit3? if possible I would buy this one: https://www.amazon.com/gp/product/B011BBQQEK. Would that do? Thank you!
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: philipma1957 on July 06, 2019, 09:11:44 PM
Well you tried all three when you did the log above.
Try first board all alone. Ie no psu to boards 2 and 3.
Then save log to show us.
Next try board 2 all alone Save log to show us.
Last try board 3 all alone Save long to show us.
Then post the logs for all three boards.
Some times problems are with 1 board And it run the 2 other boards.
You may have 2 good boards.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: mikeywith on July 06, 2019, 10:17:54 PM
This part Chain[J2] has 0 asic Chain[J3] has 0 asic Chain[J4] has 0 asic Chain[J9] has 0 asic Chain[J10] has 0 asic Chain[J11] has 0 asic Chain[J12] has 0 asic Chain[J13] has 0 asic Chain[J14] has 0 asic
non of the hash boards is working, which is very strange to be honest, usually they don't all go bad at the same time, you should first try a couple of resets and firmware upgrades, try Braiins OS it works on T9 as well. your chances with replacing the hex using pickit3 are pretty slim to nothing, I wouldn't waste the money on a T9 given the tiny chance you have with these. however, if you do own other miners and might re-use the pickit3, go for it. I have personally bought one, tried it on a couple of bad S9 boards and was only lucky in a ratio of say 1 to 10.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: WhyFhy on July 06, 2019, 10:55:27 PM
Ive had the same problem I went with the newest firmware by bitmain and started at -2 THS and got all oooo's and my chains all show up with hash I have not gotten braiins to work on T9+ , I think mikey might be reffering to "T1" or possibly T9 (not "+")
try the new firmware, start at the lowest common denominator witch is -2TH if that works walk it up slowly babysitting hash for at least 4-6 hours every step up .
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: Ortadan on July 07, 2019, 12:32:53 AM
Thank you for responding, connect each hashboard individually and no hash lifts. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.14.0-xilinx-ge8a2f71-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #82 SMP PREEMPT Tue May 16 19:49:53 CST 2017 [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: Xilinx Zynq [ 0.000000] cma: CMA: reserved 128 MiB at 27800000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] On node 0 totalpages: 258048 [ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map e6fd8000 [ 0.000000] Normal zone: 1520 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 194560 pages, LIFO batch:31 [ 0.000000] HighMem zone: 496 pages used for memmap [ 0.000000] HighMem zone: 63488 pages, LIFO batch:15 [ 0.000000] PERCPU: Embedded 8 pages/cpu @e6fc0000 s9088 r8192 d15488 u32768 [ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 256528 [ 0.000000] Kernel command line: noinitrd mem=1008M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 884148K/1032192K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 148044K reserved, 253952K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB) [ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB) [ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB) [ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] ps7-slcr mapped to f0004000 [ 0.000000] zynq_clock_init: clkc starts at f0004100 [ 0.000000] Zynq clock init [ 0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns [ 0.000309] ps7-ttc #0 at f0006000, irq=43 [ 0.000616] Console: colour dummy device 80x30 [ 0.000653] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328) [ 0.040209] pid_max: default: 32768 minimum: 301 [ 0.040430] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.040452] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.042579] CPU: Testing write buffer coherency: ok [ 0.042925] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.042986] Setting up static identity map for 0x4c4b00 - 0x4c4b58 [ 0.043213] L310 cache controller enabled [ 0.043232] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB [ 0.121036] CPU1: Booted secondary processor [ 0.210229] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.210359] Brought up 2 CPUs [ 0.210378] SMP: Total of 2 processors activated. [ 0.210387] CPU: All CPU(s) started in SVC mode. [ 0.211040] devtmpfs: initialized [ 0.213443] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.214645] regulator-dummy: no parameters [ 0.222336] NET: Registered protocol family 16 [ 0.224633] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.226908] cpuidle: using governor ladder [ 0.226922] cpuidle: using governor menu [ 0.234345] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered [ 0.235865] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.235878] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.235993] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000 [ 0.257536] bio: create slab <bio-0> at 0 [ 0.258945] vgaarb: loaded [ 0.259632] SCSI subsystem initialized [ 0.260668] usbcore: registered new interface driver usbfs [ 0.260847] usbcore: registered new interface driver hub [ 0.261102] usbcore: registered new device driver usb [ 0.261632] media: Linux media interface: v0.10 [ 0.261789] Linux video capture interface: v2.00 [ 0.262027] pps_core: LinuxPPS API ver. 1 registered [ 0.262039] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.262168] PTP clock support registered [ 0.262524] EDAC MC: Ver: 3.0.0 [ 0.263571] Advanced Linux Sound Architecture Driver Initialized. [ 0.266420] DMA-API: preallocated 4096 debug entries [ 0.266434] DMA-API: debugging enabled by kernel config [ 0.266507] Switched to clocksource arm_global_timer [ 0.287048] NET: Registered protocol family 2 [ 0.287716] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.287811] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.287971] TCP: Hash tables configured (established 8192 bind 8192) [ 0.288032] TCP: reno registered [ 0.288051] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.288104] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.288368] NET: Registered protocol family 1 [ 0.288728] RPC: Registered named UNIX socket transport module. [ 0.288742] RPC: Registered udp transport module. [ 0.288750] RPC: Registered tcp transport module. [ 0.288759] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.288772] PCI: CLS 0 bytes, default 64 [ 0.289219] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available [ 0.291238] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.292650] bounce pool size: 64 pages [ 0.293545] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.293746] msgmni has been set to 1486 [ 0.294532] io scheduler noop registered [ 0.294545] io scheduler deadline registered [ 0.294586] io scheduler cfq registered (default) [ 0.307197] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208 [ 0.307218] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16 [ 0.431138] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps [ 1.003846] console [ttyPS0] enabled [ 1.008118] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000 [ 1.015733] [drm] Initialized drm 1.1.0 20060810 [ 1.032773] brd: module loaded [ 1.042163] loop: module loaded [ 1.051773] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 1.057595] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 1.065330] libphy: XEMACPS mii bus: probed [ 1.069878] ------------- phy_id = 0x3625e62 [ 1.074610] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54 [ 1.083338] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.089995] ehci-pci: EHCI PCI platform driver [ 1.097228] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing? [ 1.104020] usbcore: registered new interface driver usb-storage [ 1.110888] mousedev: PS/2 mouse device common for all mice [ 1.116993] i2c /dev entries driver [ 1.123926] zynq-edac f8006000.ps7-ddrc: ecc not enabled [ 1.129485] cpufreq_cpu0: failed to get cpu0 regulator: -19 [ 1.135368] Xilinx Zynq CpuIdle Driver started [ 1.140236] sdhci: Secure Digital Host Controller Interface driver [ 1.146328] sdhci: Copyright(c) Pierre Ossman [ 1.150709] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.157485] mmc0: no vqmmc regulator found [ 1.161496] mmc0: no vmmc regulator found [ 1.206545] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA [ 1.215229] usbcore: registered new interface driver usbhid [ 1.220747] usbhid: USB HID core driver [ 1.225457] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda [ 1.231757] nand: Micron MT29F2G08ABAEAWP [ 1.235727] nand: 256MiB, SLC, page size: 2048, OOB size: 64 [ 1.241684] Bad block table found at page 131008, version 0x01 [ 1.247940] Bad block table found at page 130944, version 0x01 [ 1.253988] 3 ofpart partitions found on MTD device pl353-nand [ 1.259759] Creating 3 MTD partitions on "pl353-nand": [ 1.264861] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel" [ 1.272924] 0x000002000000-0x00000b000000 : "angstram-rootfs" [ 1.280259] 0x00000b000000-0x000010000000 : "upgrade-rootfs" [ 1.289197] TCP: cubic registered [ 1.292434] NET: Registered protocol family 17 [ 1.297157] Registering SWP/SWPB emulation handler [ 1.303085] regulator-dummy: disabling [ 1.307485] UBI: attaching mtd1 to ubi0 [ 1.833879] UBI: scanning is finished [ 1.845495] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0 [ 1.852571] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [ 1.859334] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [ 1.865998] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096 [ 1.872875] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0 [ 1.878856] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 [ 1.885963] UBI: max/mean erase counter: 17/9, WL threshold: 4096, image sequence number: 248547359 [ 1.895007] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40 [ 1.904222] UBI: background thread "ubi_bgt0d" started, PID 1080 [ 1.904227] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 1.908166] ALSA device list: [ 1.908170] No soundcards found. [ 1.924553] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082 [ 1.953559] UBIFS: recovery needed [ 2.187888] UBIFS: recovery completed [ 2.191570] UBIFS: mounted UBI device 0, volume 0, name "rootfs" [ 2.197519] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [ 2.206626] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs) [ 2.216515] UBIFS: reserved for root: 0 bytes (0 KiB) [ 2.221544] UBIFS: media format: w4/r0 (latest is w4/r0), UUID D5E65D66-FDFF-460C-B3DB-A1F2DEB908D8, small LPT model [ 2.232853] VFS: Mounted root (ubifs filesystem) on device 0:11. [ 2.240045] devtmpfs: mounted [ 2.243146] Freeing unused kernel memory: 204K (c06d2000 - c0705000) [ 3.091434] random: dd urandom read with 0 bits of entropy available [ 3.486534] [ 3.486534] bcm54xx_config_init [ 4.096520] [ 4.096520] bcm54xx_config_init [ 8.097396] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz [ 8.103487] xemacps e000b000.ps7-ethernet: link up (100/FULL) [ 24.221126] In axi fpga driver! [ 24.224217] request_mem_region OK! [ 24.227647] AXI fpga dev virtual address is 0xf01fe000 [ 24.232697] *base_vir_addr = 0xc510 [ 24.248356] In fpga mem driver! [ 24.251429] request_mem_region OK! [ 24.254995] fpga mem virtual address is 0xf3000000 [ 25.055937] [ 25.055937] bcm54xx_config_init [ 25.685885] [ 25.685885] bcm54xx_config_init [ 29.686329] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz [ 29.692346] xemacps e000b000.ps7-ethernet: link up (100/FULL) This is XILINX board. Totalram: 1039794176 Detect 1GB control board of XILINX DETECT HW version=8000c510 miner ID : 81444d227075885c Miner Type = T9+ AsicType = 1387 real AsicNum = 18 use critical mode to search freq... get PLUG ON=0x06003c0c Find hashboard on Chain[2] Find hashboard on Chain[3] Find hashboard on Chain[10] Find hashboard on Chain[11] Find hashboard on Chain[12] Find hashboard on Chain[13] set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_reset_pic failed on Chain[2]! try again... dsPIC33EP16GS202_reset_pic failed on Chain[2]! try again... dsPIC33EP16GS202_reset_pic failed on Chain[2]! try again... chain[2] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! try again... dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! try again... dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! try again... dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! Check chain[2] PIC fw version=0xff chain[3] PIC jump to app Check chain[3] PIC fw version=0x90 Chain[2] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] has freq in PIC, will disable freq setting. chain[2] has freq in PIC and will jump over... Chain[2] has core num in PIC Chain[3] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] has freq in PIC, will disable freq setting. chain[3] has freq in PIC and will jump over... Chain[3] has core num in PIC has freq in PIC, will disable freq setting. chain[10] has freq in PIC and will jump over... Chain[10] has core num in PIC has freq in PIC, will disable freq setting. chain[11] has freq in PIC and will jump over... Chain[11] has core num in PIC has freq in PIC, will disable freq setting. chain[12] has freq in PIC and will jump over... Chain[12] has core num in PIC has freq in PIC, will disable freq setting. chain[13] has freq in PIC and will jump over... Chain[13] has core num in PIC get PIC voltage=1 on chain[2], value=930 get PIC voltage=1 on chain[3], value=930 get PIC voltage=1 on chain[10], value=930 get PIC voltage=1 on chain[11], value=930 get PIC voltage=1 on chain[12], value=930 get PIC voltage=1 on chain[13], value=930 dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! set_reset_allhashboard = 0x00000000 chain[10] temp offset record: 1,5,0,0,0,0,33,28 chain[10] temp chip I2C addr=0x98 chain[12] temp offset record: 1,3,0,0,0,0,33,28 chain[12] temp chip I2C addr=0x98 dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 CRC error counter=0 set command mode to VIL
--- check asic number After Get ASIC NUM CRC error counter=0 set_baud=0 The min freq=700 set real timeout 52, need sleep=379392 After TEST CRC error counter=0 search freq for 1 times, completed chain = 6, total chain num = 6 set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 restart Miner chance num=2 waiting for receive_func to exit! waiting for pic heart to exit! bmminer not found= 1389 root 0:00 grep bmminer
bmminer not found, restart bmminer ... This is user mode for mining Detect 1GB control board of XILINX Miner Type = T9+ Miner compile time: Fri Nov 17 18:17:49 CST 2017 type: Antminer T9+set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 set_reset_allhashboard = 0x0000ffff miner ID : 81444d227075885c set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! Checking fans!get fan[5] speed=4560 get fan[2] speed=4440 get fan[5] speed=4560 get fan[2] speed=4440 get fan[5] speed=4560 dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! chain[2] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! Check chain[2] PIC fw version=0xff Chain[2] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] Chain[J3] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J3] test patten OK temp=-1 chain[3] PIC jump to app Check chain[3] PIC fw version=0x90 Chain[3] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] Chain[J4] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J4] test patten OK temp=-1 Chain[J11] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J11] test patten OK temp=-1 Chain[J12] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J12] test patten OK temp=-1 Chain[J13] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J13] test patten OK temp=-1 Chain[J14] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J14] test patten OK temp=-1 Chain[J3] will use voltage=930 [1] to open core set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
Chain[J4] 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 Chain[J3] orignal chain_voltage_pic=1 value=930 Chain[J3] will use backup chain_voltage_pic=870 [11] Chain[J3] get working chain_voltage_pic=11 Chain[J4] orignal chain_voltage_pic=1 value=930 Chain[J4] will use backup chain_voltage_pic=870 [11] Chain[J4] get working chain_voltage_pic=11 Chain[J11] orignal chain_voltage_pic=1 value=930 Chain[J11] will use backup chain_voltage_pic=870 [11] Chain[J11] get working chain_voltage_pic=11 Chain[J12] orignal chain_voltage_pic=1 value=930 Chain[J12] will use backup chain_voltage_pic=870 [11] Chain[J12] get working chain_voltage_pic=11 Chain[J13] orignal chain_voltage_pic=1 value=930 Chain[J13] will use backup chain_voltage_pic=870 [11] Chain[J13] get working chain_voltage_pic=11 Chain[J14] orignal chain_voltage_pic=1 value=930 Chain[J14] will use backup chain_voltage_pic=870 [11] Chain[J14] get working chain_voltage_pic=11 dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 1 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 2 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 3 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 4 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 5 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 6 time Chain[J3] has 0 asic miner total rate=0GH/s fixed rate=0GH/s
Miner fix freq ... max freq = 100 set baud=1 do heat board 8xPatten for 1 times setStartTimePoint total_tv_start_sys=252 total_tv_end_sys=253 restartNum = 2 , auto-reinit enabled... do read_temp_func once... do check_asic_reg 0x08 Done check_asic_reg 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=1
[ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.14.0-xilinx-ge8a2f71-dirty (lzq@armdev2) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-23) ) #82 SMP PREEMPT Tue May 16 19:49:53 CST 2017 [ 0.000000] CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=18c5387d [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] Machine model: Xilinx Zynq [ 0.000000] cma: CMA: reserved 128 MiB at 27800000 [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] On node 0 totalpages: 258048 [ 0.000000] free_area_init_node: node 0, pgdat c0740a40, node_mem_map e6fd8000 [ 0.000000] Normal zone: 1520 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 194560 pages, LIFO batch:31 [ 0.000000] HighMem zone: 496 pages used for memmap [ 0.000000] HighMem zone: 63488 pages, LIFO batch:15 [ 0.000000] PERCPU: Embedded 8 pages/cpu @e6fc0000 s9088 r8192 d15488 u32768 [ 0.000000] pcpu-alloc: s9088 r8192 d15488 u32768 alloc=8*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 256528 [ 0.000000] Kernel command line: noinitrd mem=1008M console=ttyPS0,115200 root=ubi0:rootfs ubi.mtd=1 rootfstype=ubifs rw rootwait [ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) [ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) [ 0.000000] Memory: 884148K/1032192K available (5032K kernel code, 283K rwdata, 1916K rodata, 204K init, 258K bss, 148044K reserved, 253952K highmem) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB) [ 0.000000] vmalloc : 0xf0000000 - 0xff000000 ( 240 MB) [ 0.000000] lowmem : 0xc0000000 - 0xef800000 ( 760 MB) [ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB) [ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB) [ 0.000000] .text : 0xc0008000 - 0xc06d1374 (6949 kB) [ 0.000000] .init : 0xc06d2000 - 0xc0705380 ( 205 kB) [ 0.000000] .data : 0xc0706000 - 0xc074cf78 ( 284 kB) [ 0.000000] .bss : 0xc074cf84 - 0xc078d9fc ( 259 kB) [ 0.000000] Preemptible hierarchical RCU implementation. [ 0.000000] Dump stacks of tasks blocking RCU-preempt GP. [ 0.000000] RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] ps7-slcr mapped to f0004000 [ 0.000000] zynq_clock_init: clkc starts at f0004100 [ 0.000000] Zynq clock init [ 0.000015] sched_clock: 64 bits at 333MHz, resolution 3ns, wraps every 3298534883328ns [ 0.000302] ps7-ttc #0 at f0006000, irq=43 [ 0.000611] Console: colour dummy device 80x30 [ 0.000649] Calibrating delay loop... 1325.46 BogoMIPS (lpj=6627328) [ 0.040208] pid_max: default: 32768 minimum: 301 [ 0.040429] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.040451] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes) [ 0.042571] CPU: Testing write buffer coherency: ok [ 0.042922] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 [ 0.042981] Setting up static identity map for 0x4c4b00 - 0x4c4b58 [ 0.043206] L310 cache controller enabled [ 0.043225] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x72760000, Cache size: 512 kB [ 0.121031] CPU1: Booted secondary processor [ 0.210226] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 [ 0.210357] Brought up 2 CPUs [ 0.210376] SMP: Total of 2 processors activated. [ 0.210384] CPU: All CPU(s) started in SVC mode. [ 0.211038] devtmpfs: initialized [ 0.213441] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 [ 0.214648] regulator-dummy: no parameters [ 0.222343] NET: Registered protocol family 16 [ 0.224633] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.226907] cpuidle: using governor ladder [ 0.226921] cpuidle: using governor menu [ 0.234353] syscon f8000000.ps7-slcr: regmap [mem 0xf8000000-0xf8000fff] registered [ 0.235869] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. [ 0.235883] hw-breakpoint: maximum watchpoint size is 4 bytes. [ 0.235997] zynq-ocm f800c000.ps7-ocmc: ZYNQ OCM pool: 256 KiB @ 0xf0080000 [ 0.257531] bio: create slab <bio-0> at 0 [ 0.258945] vgaarb: loaded [ 0.259641] SCSI subsystem initialized [ 0.260699] usbcore: registered new interface driver usbfs [ 0.260872] usbcore: registered new interface driver hub [ 0.261124] usbcore: registered new device driver usb [ 0.261655] media: Linux media interface: v0.10 [ 0.261812] Linux video capture interface: v2.00 [ 0.262060] pps_core: LinuxPPS API ver. 1 registered [ 0.262072] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.262195] PTP clock support registered [ 0.262556] EDAC MC: Ver: 3.0.0 [ 0.263601] Advanced Linux Sound Architecture Driver Initialized. [ 0.266443] DMA-API: preallocated 4096 debug entries [ 0.266456] DMA-API: debugging enabled by kernel config [ 0.266536] Switched to clocksource arm_global_timer [ 0.287117] NET: Registered protocol family 2 [ 0.287761] TCP established hash table entries: 8192 (order: 3, 32768 bytes) [ 0.287856] TCP bind hash table entries: 8192 (order: 4, 65536 bytes) [ 0.288015] TCP: Hash tables configured (established 8192 bind 8192) [ 0.288076] TCP: reno registered [ 0.288095] UDP hash table entries: 512 (order: 2, 16384 bytes) [ 0.288147] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes) [ 0.288413] NET: Registered protocol family 1 [ 0.288723] RPC: Registered named UNIX socket transport module. [ 0.288735] RPC: Registered udp transport module. [ 0.288744] RPC: Registered tcp transport module. [ 0.288752] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 0.288764] PCI: CLS 0 bytes, default 64 [ 0.289203] hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available [ 0.291229] futex hash table entries: 512 (order: 3, 32768 bytes) [ 0.292617] bounce pool size: 64 pages [ 0.293537] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc. [ 0.293731] msgmni has been set to 1486 [ 0.294502] io scheduler noop registered [ 0.294516] io scheduler deadline registered [ 0.294554] io scheduler cfq registered (default) [ 0.308477] dma-pl330 f8003000.ps7-dma: Loaded driver for PL330 DMAC-2364208 [ 0.308498] dma-pl330 f8003000.ps7-dma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-4 Num_Events-16 [ 0.433037] e0001000.serial: ttyPS0 at MMIO 0xe0001000 (irq = 82, base_baud = 3124999) is a xuartps [ 1.006101] console [ttyPS0] enabled [ 1.010397] xdevcfg f8007000.ps7-dev-cfg: ioremap 0xf8007000 to f0068000 [ 1.018072] [drm] Initialized drm 1.1.0 20060810 [ 1.034963] brd: module loaded [ 1.044358] loop: module loaded [ 1.053786] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 1.059750] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 1.067493] libphy: XEMACPS mii bus: probed [ 1.071862] ------------- phy_id = 0x3625e62 [ 1.076775] xemacps e000b000.ps7-ethernet: pdev->id -1, baseaddr 0xe000b000, irq 54 [ 1.085410] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.092201] ehci-pci: EHCI PCI platform driver [ 1.099457] zynq-dr e0002000.ps7-usb: Unable to init USB phy, missing? [ 1.106254] usbcore: registered new interface driver usb-storage [ 1.113201] mousedev: PS/2 mouse device common for all mice [ 1.119358] i2c /dev entries driver [ 1.126265] zynq-edac f8006000.ps7-ddrc: ecc not enabled [ 1.131785] cpufreq_cpu0: failed to get cpu0 regulator: -19 [ 1.137719] Xilinx Zynq CpuIdle Driver started [ 1.142556] sdhci: Secure Digital Host Controller Interface driver [ 1.148678] sdhci: Copyright(c) Pierre Ossman [ 1.152993] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.159885] mmc0: no vqmmc regulator found [ 1.163898] mmc0: no vmmc regulator found [ 1.206557] mmc0: SDHCI controller on e0100000.ps7-sdio [e0100000.ps7-sdio] using ADMA [ 1.215256] usbcore: registered new interface driver usbhid [ 1.220760] usbhid: USB HID core driver [ 1.225479] nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda [ 1.231773] nand: Micron MT29F2G08ABAEAWP [ 1.235742] nand: 256MiB, SLC, page size: 2048, OOB size: 64 [ 1.241677] Bad block table found at page 131008, version 0x01 [ 1.247898] Bad block table found at page 130944, version 0x01 [ 1.253952] 3 ofpart partitions found on MTD device pl353-nand [ 1.259737] Creating 3 MTD partitions on "pl353-nand": [ 1.264824] 0x000000000000-0x000002000000 : "BOOT.bin-env-dts-kernel" [ 1.272879] 0x000002000000-0x00000b000000 : "angstram-rootfs" [ 1.280195] 0x00000b000000-0x000010000000 : "upgrade-rootfs" [ 1.289142] TCP: cubic registered [ 1.292380] NET: Registered protocol family 17 [ 1.297095] Registering SWP/SWPB emulation handler [ 1.302989] regulator-dummy: disabling [ 1.307328] UBI: attaching mtd1 to ubi0 [ 1.833699] UBI: scanning is finished [ 1.845340] UBI: attached mtd1 (name "angstram-rootfs", size 144 MiB) to ubi0 [ 1.852423] UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [ 1.859185] UBI: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [ 1.865848] UBI: VID header offset: 2048 (aligned 2048), data offset: 4096 [ 1.872726] UBI: good PEBs: 1152, bad PEBs: 0, corrupted PEBs: 0 [ 1.878707] UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 [ 1.885814] UBI: max/mean erase counter: 17/9, WL threshold: 4096, image sequence number: 248547359 [ 1.894857] UBI: available PEBs: 0, total reserved PEBs: 1152, PEBs reserved for bad PEB handling: 40 [ 1.904074] UBI: background thread "ubi_bgt0d" started, PID 1080 [ 1.904079] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [ 1.908036] ALSA device list: [ 1.908040] No soundcards found. [ 1.924446] UBIFS: background thread "ubifs_bgt0_0" started, PID 1082 [ 1.953592] UBIFS: recovery needed [ 2.088314] UBIFS: recovery completed [ 2.091994] UBIFS: mounted UBI device 0, volume 0, name "rootfs" [ 2.097946] UBIFS: LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [ 2.107047] UBIFS: FS size: 128626688 bytes (122 MiB, 1013 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs) [ 2.116935] UBIFS: reserved for root: 0 bytes (0 KiB) [ 2.121965] UBIFS: media format: w4/r0 (latest is w4/r0), UUID D5E65D66-FDFF-460C-B3DB-A1F2DEB908D8, small LPT model [ 2.133261] VFS: Mounted root (ubifs filesystem) on device 0:11. [ 2.140449] devtmpfs: mounted [ 2.143552] Freeing unused kernel memory: 204K (c06d2000 - c0705000) [ 2.986842] random: dd urandom read with 0 bits of entropy available [ 3.376569] [ 3.376569] bcm54xx_config_init [ 3.986579] [ 3.986579] bcm54xx_config_init [ 7.987410] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz [ 7.993500] xemacps e000b000.ps7-ethernet: link up (100/FULL) [ 22.201415] In axi fpga driver! [ 22.204480] request_mem_region OK! [ 22.207901] AXI fpga dev virtual address is 0xf01fe000 [ 22.212978] *base_vir_addr = 0xc510 [ 22.228456] In fpga mem driver! [ 22.231528] request_mem_region OK! [ 22.235094] fpga mem virtual address is 0xf3000000 [ 23.025951] [ 23.025951] bcm54xx_config_init [ 23.655907] [ 23.655907] bcm54xx_config_init [ 27.656357] xemacps e000b000.ps7-ethernet: Set clk to 24999999 Hz [ 27.662379] xemacps e000b000.ps7-ethernet: link up (100/FULL) This is XILINX board. Totalram: 1039794176 Detect 1GB control board of XILINX DETECT HW version=8000c510 miner ID : 81444d227075885c Miner Type = T9+ AsicType = 1387 real AsicNum = 18 use critical mode to search freq... get PLUG ON=0x06003c0c Find hashboard on Chain[2] Find hashboard on Chain[3] Find hashboard on Chain[10] Find hashboard on Chain[11] Find hashboard on Chain[12] Find hashboard on Chain[13] set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_reset_pic failed on Chain[2]! try again... dsPIC33EP16GS202_reset_pic failed on Chain[2]! try again... dsPIC33EP16GS202_reset_pic failed on Chain[2]! try again... chain[2] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! try again... dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! try again... dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! try again... dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! Check chain[2] PIC fw version=0xff dsPIC33EP16GS202_reset_pic failed on Chain[3]! try again... dsPIC33EP16GS202_reset_pic failed on Chain[3]! try again... dsPIC33EP16GS202_reset_pic failed on Chain[3]! try again... chain[3] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[3]! try again... dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[3]! try again... dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[3]! try again... dsPIC33EP16GS202_get_pic_sw_version failed on Chain[3]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[3]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[3]! Check chain[3] PIC fw version=0xff Chain[2] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] has freq in PIC, will disable freq setting. chain[2] has freq in PIC and will jump over... Chain[2] has core num in PIC Chain[3] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] has freq in PIC, will disable freq setting. chain[3] has freq in PIC and will jump over... Chain[3] has core num in PIC has freq in PIC, will disable freq setting. chain[10] has freq in PIC and will jump over... Chain[10] has core num in PIC has freq in PIC, will disable freq setting. chain[11] has freq in PIC and will jump over... Chain[11] has core num in PIC has freq in PIC, will disable freq setting. chain[12] has freq in PIC and will jump over... Chain[12] has core num in PIC has freq in PIC, will disable freq setting. chain[13] has freq in PIC and will jump over... Chain[13] has core num in PIC get PIC voltage=1 on chain[2], value=930 get PIC voltage=1 on chain[3], value=930 get PIC voltage=1 on chain[10], value=930 get PIC voltage=1 on chain[11], value=930 get PIC voltage=1 on chain[12], value=930 get PIC voltage=1 on chain[13], value=930 dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[3]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[3]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[3]! set_reset_allhashboard = 0x00000000 chain[10] temp offset record: 1,5,0,0,0,0,33,28 chain[10] temp chip I2C addr=0x98 chain[12] temp offset record: 1,3,0,0,0,0,33,28 chain[12] temp chip I2C addr=0x98 dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[2]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[3]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[3]! dsPIC33EP16GS202_pic_heart_beat failed on Chain[3]! set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 CRC error counter=0 set command mode to VIL
--- check asic number After Get ASIC NUM CRC error counter=0 set_baud=0 The min freq=700 set real timeout 52, need sleep=379392 After TEST CRC error counter=0 search freq for 1 times, completed chain = 6, total chain num = 6 set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 restart Miner chance num=2 waiting for receive_func to exit! waiting for pic heart to exit! bmminer not found= 2329 root 0:00 grep bmminer
bmminer not found, restart bmminer ... This is user mode for mining Detect 1GB control board of XILINX Miner Type = T9+ Miner compile time: Fri Nov 17 18:17:49 CST 2017 type: Antminer T9+set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 set_reset_allhashboard = 0x0000ffff miner ID : 81444d227075885c set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[3]! dsPIC33EP16GS202_reset_pic failed on Chain[3]! dsPIC33EP16GS202_reset_pic failed on Chain[3]! Checking fans!get fan[5] speed=4440 get fan[2] speed=4320 get fan[5] speed=4440 get fan[2] speed=4320 get fan[5] speed=4440 dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! dsPIC33EP16GS202_reset_pic failed on Chain[2]! chain[2] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! Check chain[2] PIC fw version=0xff Chain[2] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[2]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] Chain[J3] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J3] test patten OK temp=-1 dsPIC33EP16GS202_reset_pic failed on Chain[3]! dsPIC33EP16GS202_reset_pic failed on Chain[3]! dsPIC33EP16GS202_reset_pic failed on Chain[3]! chain[3] PIC jump to app dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[3]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[3]! dsPIC33EP16GS202_jump_to_app_from_loader failed on Chain[3]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[3]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[3]! dsPIC33EP16GS202_get_pic_sw_version failed on Chain[3]! Check chain[3] PIC fw version=0xff Chain[3] read_freq_badcores : 0x7d 0x33 0x33 0x33 0x11 0x33 0x33 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x3e 0x57 0x00 0xff 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x3e 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff chain[3]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] Chain[J4] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J4] test patten OK temp=-1 Chain[J11] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J11] test patten OK temp=-1 Chain[J12] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J12] test patten OK temp=-1 Chain[J13] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J13] test patten OK temp=-1 Chain[J14] has backup chain_voltage=870 Detect: use voltage limit rules on single board! Detect: T9+ use voltage level=1 Chain[J14] test patten OK temp=-1 Chain[J3] will use voltage=930 [1] to open core set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[2]!
Chain[J4] will use voltage=930 [1] to open core set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[3]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[3]!
set_Voltage_S9_plus_plus_BM1387_54 failed on Chain[3]!
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 Chain[J3] orignal chain_voltage_pic=1 value=930 Chain[J3] will use backup chain_voltage_pic=870 [11] Chain[J3] get working chain_voltage_pic=11 Chain[J4] orignal chain_voltage_pic=1 value=930 Chain[J4] will use backup chain_voltage_pic=870 [11] Chain[J4] get working chain_voltage_pic=11 Chain[J11] orignal chain_voltage_pic=1 value=930 Chain[J11] will use backup chain_voltage_pic=870 [11] Chain[J11] get working chain_voltage_pic=11 Chain[J12] orignal chain_voltage_pic=1 value=930 Chain[J12] will use backup chain_voltage_pic=870 [11] Chain[J12] get working chain_voltage_pic=11 Chain[J13] orignal chain_voltage_pic=1 value=930 Chain[J13] will use backup chain_voltage_pic=870 [11] Chain[J13] get working chain_voltage_pic=11 Chain[J14] orignal chain_voltage_pic=1 value=930 Chain[J14] will use backup chain_voltage_pic=870 [11] Chain[J14] get working chain_voltage_pic=11 dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! set_reset_allhashboard = 0x0000ffff set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 1 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 2 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 3 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 4 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 5 time Chain[J3] has 0 asic set_reset_allhashboard = 0x0000ffff dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[2]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! dsPIC33EP16GS202_enable_pic_dc_dc failed on Chain[3]! set_reset_allhashboard = 0x00000000 T9+ try get asic num for the 6 time Chain[J3] has 0 asic miner total rate=0GH/s fixed rate=0GH/s
Miner fix freq ... max freq = 100 set baud=1 do heat board 8xPatten for 1 times setStartTimePoint total_tv_start_sys=315 total_tv_end_sys=316 restartNum = 2 , auto-reinit enabled... do read_temp_func once... do check_asic_reg 0x08 Done check_asic_reg 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=0
the 3 have the same fault, I do not raise the 3rd log by the limit of 64000 characters, I bought this equipment at about $ 30 to have spare fan and controller card but I noticed that the 3 hashboard presented the same error and I assumed that they updated the firmware and something went wrong. I'm from Venezuela, I know it's an old equipment but as you know the energy is free I have other miners of this model and I try changing the controller card and still have the same fault. can still be an update error? or are already physical failures in the hashboard.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: mikeywith on July 07, 2019, 07:08:58 PM
can still be an update error? or are already physical failures in the hashboard
It could be anything, but if I had to bet one BTC on it, i would say the 3 hash boards are physically damaged. Did the seller say the hash boards were running fine? Anyhow you still havn't informed us whether you did try the latest firmware or not?
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: romeorex on August 11, 2019, 04:17:59 PM
Hello, can this be done with pickit 2? Thank you.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: alvinke on October 25, 2019, 04:49:18 AM
I repeat it there is an error in the source code of bitmain for the T9 +...
what is error in detail you say? are you have solution? I compiled self-firmware use link: https://github.com/bitmaintech/S9_makepackage for antminer T9+ and S9, then flashing self-firmware to T9+/S9, both T9+ and S9 lost chain. even though I flash to offical firmware through sd card recovery, miners lost chain yet. Logs: main.c:14097: Miner Type = T9+ main.c:14101: AsicType = 1387 main.c:14104: real AsicNum = 18 main.c:14197: use critical mode to search freq... driver-bitmain.c:1876: get PLUG ON=0x03000f06 driver-bitmain.c:1907: Find hashboard on Chain[1] driver-bitmain.c:1907: Find hashboard on Chain[2] driver-bitmain.c:1907: Find hashboard on Chain[8] driver-bitmain.c:1907: Find hashboard on Chain[9] driver-bitmain.c:1907: Find hashboard on Chain[10] driver-bitmain.c:1907: Find hashboard on Chain[11] main.c:2126: chain[1] PIC jump to app dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[1]! main.c:2134: Check chain[1] PIC fw version=0xff main.c:2126: chain[2] PIC jump to app dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! dsPIC33EP16GS202.c:61: dsPIC33EP16GS202_get_pic_sw_version failed on Chain[2]! main.c:2134: Check chain[2] PIC fw version=0xff main.c:8651: Chain[1] read_freq_badcores : 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff 0xff main.c:8665: chain[1]: [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] [255:255] main.c:9148: chain[1] has no freq in PIC! Will use default freq=550 and jump over...
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: milani1387 on April 08, 2020, 01:48:39 PM
hi i have s9 v4.21 hashboards ... pic ic need programmed where can i find pic hex file ????????? thanks
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on April 08, 2020, 08:06:49 PM
hi, you find this on good working hashboard ...
Sorry i don't have it on my and at this time
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: milani1387 on April 09, 2020, 09:23:14 PM
thanks i i have tnm 5000 prgrammer i can read hex file from hashboards succesfully.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on April 10, 2020, 11:30:11 PM
if you can read the HEX file, you can WRITE this on bad hashboard !!! 8)
Ps : i have edited my first post with corrected the bitmain source code for never problem with this pic program ;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: milani1387 on April 11, 2020, 08:13:20 PM
hi. thanks for t9 hex file uploading.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: Animas on April 14, 2021, 06:39:53 PM
hi guys. is there any option other than flashing the pic with the pickit3?
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: mikeywith on April 16, 2021, 05:41:14 AM
hi guys. is there any option other than flashing the pic with the pickit3?
If you are looking for another way to write on that digital signal controller or wherever the hex file resides then the short answer is NO, if it's not pickit3 then it has to be another similar tool, but your problem might be solved using another method, post your issue in a sperate thread and you might get some answers.
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: KTzMg on June 09, 2021, 03:30:23 PM
hi guys i have 6 T9+ hashboard and all of them have PIC problem
when i try to write hex file i get this error Too much current has been drawn on VDD. Please disconnect your circuit, check the CLK and DATA lines for shorts and then reconnect.
what should i do with this problem ? i try disconnect and then reconnect
when i try to do read verify or anything like that get this or just failed
when i try to do this work with ok hashboard there is no problem and anything work correctly
my power settings 3.25 circuit from tool
i very need help
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on June 09, 2021, 03:39:59 PM
Hi, try 3,50V :)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: KTzMg on June 09, 2021, 03:50:36 PM
i try it but there is no diffrent
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: charcousse on June 17, 2021, 08:15:11 PM
hola amigo saludos desde acá desde Venezuela... estoy tratando de reparar una t9+ con problemas en placa DSPIC32 y hago exactamente lo que tu explicas paso a paso pero me sale el siguiente error.......
The target circuit may require more power than the debug tool can provide. An external power supply might be necessary. Connection Failed.
:o :o :o como puedo solucionarlo gracias de antemano
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: thierry4wd on June 19, 2021, 07:36:20 AM
this is part of the strange errors, which I also had, check all the parameters! chip model in particular ... and try again several times,
I had the same problem, after 2 or 3 or 4 tries, it worked without changing anything ... strange but that's how it's happening;)
Title: Re: repair a T9 + after a bad firmware (lost chain)
Post by: KTzMg on July 05, 2021, 02:40:36 PM
Guys clean hashboard Completely and try to write hex file sometimes its Sometimes it answers
|