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
Topic: [FIX] Issue antminer l3+ (boards not recognized, bad fw flash , etc) - page 2. (Read 25235 times)
January 30, 2018, 08:12:00 AM
January 29, 2018, 01:32:10 PM
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.
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.
January 13, 2018, 06:50:51 AM
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 ... 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 ...
January 10, 2018, 05:28:37 PM
Actually it does not matter which hex file you use, you can write the same to both types of chip
January 10, 2018, 05:15:41 PM
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 ...
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 ...
January 09, 2018, 09:36:09 AM
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 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 ..
..
whats are le kernel logs with this fix ?
January 07, 2018, 05:41:30 PM
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 ..
..
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 ..
..
January 05, 2018, 11:40:53 AM
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
December 29, 2017, 02:02:47 PM
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+
December 29, 2017, 12:41:49 PM
worked for me thanks
Witch one work for you... FixFW or with programming the pic manually?
December 29, 2017, 12:33:44 PM
worked for me thanks
December 29, 2017, 11:38:12 AM
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?
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?
December 29, 2017, 09:47:24 AM
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?
I was connect my pickit3 to the hashboard as follow but I can not find programming software for pickit3 witch support PIC16F1704
Any ideas?
December 29, 2017, 07:57:47 AM
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...
December 29, 2017, 07:38:15 AM
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
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
December 29, 2017, 07:12:23 AM
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
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
December 21, 2017, 09:46:55 PM
I FIXED my board! Big thank!
December 18, 2017, 02:25:25 AM
Had hexa files on 1st post for people want to manually flash
thanks to martin_fryc for sharing it
thanks to martin_fryc for sharing it
December 17, 2017, 10:14:17 AM
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,
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 December 16, 2017, 06:40:53 AM
i think you didnt have the same error than people flash bad firmware ... this cant force flashing pics , or blissz fix have flash all your boards may be , i will try this firmware , but i m sure that wont change , but thanks for your try*
Jump to: