Bitcoin Forum
June 17, 2024, 07:43:40 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 [4] 5 »  All
  Print  
Author Topic: [FIX] Issue antminer l3+ (boards not recognized, bad fw flash , etc)  (Read 25238 times)
cryptonitro (OP)
Full Member
***
Offline Offline

Activity: 348
Merit: 119



View Profile
December 17, 2017, 02:14:17 PM
Last edit: December 17, 2017, 02:35:24 PM by cryptonitro
 #61

This is very strange. After flashing with PICkit all 6 badly flashed boards were working perfectly, it has nothing to do with the controller AFAIK.
One thing to notice, there are 2 different types of PIC chips, one has more memory, might the issue be in this direction? They are mixed in even one L+3 device, so random,

seems some boards get logs like, and generaly flashing after a bit less than 5 minutes
Code:
Chain 0 PIC Version 0xcc


and other

Code:
Chain 0 PIC Version 0x0
this one seem cant be flashed with the FIX2

The only project make me believe ... Holochain
cryptonitro (OP)
Full Member
***
Offline Offline

Activity: 348
Merit: 119



View Profile
December 18, 2017, 06:25:25 AM
Last edit: December 18, 2017, 02:57:14 PM by cryptonitro
 #62

Had hexa files on 1st post for people want to manually flash

thanks to martin_fryc for sharing it

The only project make me believe ... Holochain
MoNTE48
Newbie
*
Offline Offline

Activity: 29
Merit: 0


View Profile
December 22, 2017, 01:46:55 AM
 #63

I FIXED my board! Big thank!
versuss
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
December 29, 2017, 11:12:23 AM
 #64

Hello Friends,
I have the same problem - hashboard cannot be recognized from the Control IO Board. I read all posts here but can not understand where is this PIC and where is this EEPROM? On the hashboard I have 6 hole and I think that is for programming. Where can I get the pinout?
The hashboard is L3+ and the controller with firmware for L3+.
Please guys witch have experience with fixing of this problem on L3+ to write the procedure to resolve this problem.

Best Regards
cryptonitro (OP)
Full Member
***
Offline Offline

Activity: 348
Merit: 119



View Profile
December 29, 2017, 11:38:15 AM
 #65

Hello Friends,
I have the same problem - hashboard cannot be recognized from the Control IO Board. I read all posts here but can not understand where is this PIC and where is this EEPROM? On the hashboard I have 6 hole and I think that is for programming. Where can I get the pinout?
The hashboard is L3+ and the controller with firmware for L3+.
Please guys witch have experience with fixing of this problem on L3+ to write the procedure to resolve this problem.

Best Regards

hi, did you try the firmware method ? manually write pic is delicate

The only project make me believe ... Holochain
versuss
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
December 29, 2017, 11:57:47 AM
 #66

Yes I trying with FW method but without result. manual method is not problem for me I have pickit 3 and electronic knowledges but I need help and support...
versuss
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
December 29, 2017, 01:47:24 PM
 #67

Dear Friends,
I was connect my pickit3 to the hashboard as follow but I can not find programming software for pickit3 witch support PIC16F1704
Any ideas?
versuss
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
December 29, 2017, 03:38:12 PM
 #68

Dear Friends,
i desolder programming and again solder the pic but without result. I am trying to load your fix firmware and with your firmware flashing the led green and nothing. When  I load the original bitmain firmware the green led flashing than stop and start flashing the red led and after that the red led light on. Any ideas?
microtechies
Newbie
*
Offline Offline

Activity: 34
Merit: 0


View Profile
December 29, 2017, 04:33:44 PM
 #69

worked for me thanks
versuss
Newbie
*
Offline Offline

Activity: 18
Merit: 0


View Profile
December 29, 2017, 04:41:49 PM
 #70

worked for me thanks

Witch one work for you... FixFW or with programming the pic manually?
microtechies
Newbie
*
Offline Offline

Activity: 34
Merit: 0


View Profile
December 29, 2017, 06:02:47 PM
 #71

worked for me thanks

Witch one work for you... FixFW or with programming the pic manually?

The modded firmware and ruining one board at a time, then flashing official firmware and all 4 boards working.

BTW I had this problem by accidentally installing the Blissz D3 Mod on my L3+
cryptonitro (OP)
Full Member
***
Offline Offline

Activity: 348
Merit: 119



View Profile
January 05, 2018, 03:40:53 PM
 #72

worked for me thanks

Witch one work for you... FixFW or with programming the pic manually?

The modded firmware and ruining one board at a time, then flashing official firmware and all 4 boards working.

BTW I had this problem by accidentally installing the Blissz D3 Mod on my L3+

Very happy for you friend

The only project make me believe ... Holochain
aardvark20188
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
January 07, 2018, 09:41:30 PM
 #73

Hi All ,

I had the same problem , i erroneously flashed one of my antminer L+ miners with the wrong firmware ,  i dont know it was late , im sure i clicked on a link which was meant for a L3+ and not a D....however , i did flash it , and it was truly buggered
... tried reflashing original firmware, no good ,
tried  the other firmware flash from this post, no good
tried a support ticket with bitmain .....lol

what did work was buying a pic programmer pulling the boards out and re-programming the the pic chips on the hash boards , one at time.. with the code from one of my working non flashed L+ miners ,  works perfectly now.

Lessons learned , dont flash your L+ antminers with 3rd party incorrect miner firmware meant for dash miners...


If anyone else is in the same predicament,anywhere north london, pm me , i do a program whilst you wait  , for 10 a board ..

..

 

cryptonitro (OP)
Full Member
***
Offline Offline

Activity: 348
Merit: 119



View Profile
January 09, 2018, 01:36:09 PM
 #74

Hi All ,

I had the same problem , i erroneously flashed one of my antminer L+ miners with the wrong firmware ,  i dont know it was late , im sure i clicked on a link which was meant for a L3+ and not a D....however , i did flash it , and it was truly buggered
... tried reflashing original firmware, no good ,
tried  the other firmware flash from this post, no good
tried a support ticket with bitmain .....lol

what did work was buying a pic programmer pulling the boards out and re-programming the the pic chips on the hash boards , one at time.. with the code from one of my working non flashed L+ miners ,  works perfectly now.

Lessons learned , dont flash your L+ antminers with 3rd party incorrect miner firmware meant for dash miners...


If anyone else is in the same predicament,anywhere north london, pm me , i do a program whilst you wait  , for 10 a board ..

..

 


what is your batch
whats are le kernel logs with this fix ?

The only project make me believe ... Holochain
aardvark20188
Newbie
*
Offline Offline

Activity: 2
Merit: 0


View Profile
January 10, 2018, 09:15:41 PM
 #75

Hi there

I  have the Dec 2017 batch L+ ,l the ones i've checked so far have the PIC16F1704 chip, but i believe there is also a batch with PIC16F1705 chips , however i have the hex for both

I know don't why you would need kernel logs i just pulled the bricked hashing board out , connected it to the pickit3 tag and re-programmed it, popped it back in , and it worked , ive had no issues since ...


omshree
Full Member
***
Offline Offline

Activity: 270
Merit: 100


View Profile
January 10, 2018, 09:28:37 PM
 #76

Actually it does not matter which hex file you use, you can write the same to both types of chip

Donate if you like 1ANALSEXXGMd6HaN6CzQXtURLC5H9TjKoo
cryptonitro (OP)
Full Member
***
Offline Offline

Activity: 348
Merit: 119



View Profile
January 13, 2018, 10:50:51 AM
 #77

Hi there

I  have the Dec 2017 batch L+ ,l the ones i've checked so far have the PIC16F1704 chip, but i believe there is also a batch with PIC16F1705 chips , however i have the hex for both

I know don't why you would need kernel logs i just pulled the bricked hashing board out , connected it to the pickit3 tag and re-programmed it, popped it back in , and it worked , ive had no issues since ...



had a tutorial how to flash manually could be very nice from you for next people ...

The only project make me believe ... Holochain
m0nngis
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
January 29, 2018, 05:32:10 PM
 #78

I have a D3 with the same problem - one of the boards show "0 ASICs" in the kernel log.

Any chance that someone (blissz?) could create a firmware fix for the D3 as well?  I have neither the skills nor the tools to grab the PIC from one of the working boards and flashing it to the bricked one.

MarcusD
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
January 30, 2018, 12:12:00 PM
 #79

Hi all,

Board 1,2,4 works perfect, Board 3 comes up and after few sec. the MH/s(RT) are 0.

Can using this FIX ?

Thanks
Marcus
cryptonitro (OP)
Full Member
***
Offline Offline

Activity: 348
Merit: 119



View Profile
January 30, 2018, 10:16:51 PM
 #80

Hi all,

Board 1,2,4 works perfect, Board 3 comes up and after few sec. the MH/s(RT) are 0.

Can using this FIX ?

Thanks
Marcus

this do not seem an pic problem. if the board dont show 0 asic in logsd at start , this fix wont fix it

The only project make me believe ... Holochain
Pages: « 1 2 3 [4] 5 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!