[FIX] Issue antminer l3+ (boards not recognized, bad fw flash , etc)

[cryptonitro]

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

[versuss]

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]

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]

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]

worked for me thanks

[versuss]

worked for me thanks

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

[microtechies]

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]

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

[aardvark20188]

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]

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 ?

[aardvark20188]

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]

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

[cryptonitro]

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 ...

[m0nngis]

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]

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]

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

[MarcusD]

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

Ok, any idea how to fix ? 

Thanks

[stevebills]

Here's the issue you may have , hashboards are not recognized, anymore

https://img15.hostingpics.net/pics/396492403293Screenshot201711101152151.jpg

/!\ please read carefuly /!\

**************************************************************
Firmware Flash
**************************************************************

Here's a fix solution to rewite PIC's of L3+ after some of us flash bad firmware to their L3+.

Many has recovered 3 boards , some all of it

Thanks to Blissz for this fix (please do not pm him for this )

1. Download File
(re-up)

WARNING: Don't flash this to anything else as a bricked L3(+) caused by flashing a wrong firmware version, as this might harm a working L3(+).
MEGA
or
1fichier

2. Plug only 1 board from chain 0 (white cable on the left) as you can see under , you can plug upper hashboard 1st

https://img15.hostingpics.net/pics/67636520171209112922.jpg

3. Go to system -> Upgrade -> "Flash new firmware image" choose the file downloaded to flash new firmware and click flash image
wait for reboot.

If kernel logs get this ... 0xcc , wait after you see it (5 minutes, to see again 0xcc or most of time 0x3 and then it will fix your board) other way try to connect an other boards and restart from "3"

Dec 17 14:09:30 (none) local0.warn cgminer: Started cgminer 4.9.0
Dec 17 14:09:30 (none) local0.notice cgminer[377]:  detected at /sys/class/gpio/gpio51/value  chain 0
Dec 17 14:09:30 (none) local0.notice cgminer[377]: detect total chain num 1
Dec 17 14:09:30 (none) local0.notice cgminer[377]: i2c init ok
Dec 17 14:09:32 (none) local0.notice cgminer[377]: Chain 0 PIC Version 0xcc
Dec 17 14:13:45 (none) local0.err cgminer[377]: Blisssz: Chain not found 1
Dec 17 14:13:45 (none) local0.err cgminer[377]: Blisssz: Chain not found 2
Dec 17 14:13:45 (none) local0.err cgminer[377]: Blisssz: Chain not found 3
Dec 17 14:13:51 (none) local0.notice cgminer[377]: Chain 0 PIC Version 0x3
[...]

you will see some logs like this , PIC's is currently writing.

Code:

Dump IIC Data:[41][98][0][0]@ChainID:[0], Chip[C9]

wait logs "miner start and switching pool" the board has been flashed with success.


After fixing all or some of boards , you can finaly flash back bitmain l3+  original Firmware.

**************************************************************
Manually Flash
**************************************************************

/!\ I will not assist with "how to" here cause i didnt experience it yet
but if you have stuff (pickit3) and knowledge to manually flash chip of your miner here's the files

 ! warning ! have a look to the pic version you have (writed on the chip).

there is PIC16F1704 or PIC16F1705

Here's the hexa files for each version

MEGA
PIC16F1704.hex
PIC16F1705.hex

1FICHIER
PIC16F1704.hex
PIC16F1705.hex

Thanks to martin_fryc for sharing files, after succefully fix his L3+ by manually flashing PICs

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

hello Sir
I am looking on the board for the pic chip number and i cant se it please help me?
thx
steve

[xefe]

Is there a version similar but for D3?

[cryptonitro]

Here's the issue you may have , hashboards are not recognized, anymore



/!\ please read carefuly /!\

**************************************************************
Firmware Flash
**************************************************************

Here's a fix solution to rewite PIC's of L3+ after some of us flash bad firmware to their L3+.

Many has recovered 3 boards , some all of it

Thanks to Blissz for this fix (please do not pm him for this )

1. Download File
(re-up)

WARNING: Don't flash this to anything else as a bricked L3(+) caused by flashing a wrong firmware version, as this might harm a working L3(+).
MEGA
or
1fichier

2. Plug only 1 board from chain 0 (white cable on the left) as you can see under , you can plug upper hashboard 1st



3. Go to system -> Upgrade -> "Flash new firmware image" choose the file downloaded to flash new firmware and click flash image
wait for reboot.

If kernel logs get this ... 0xcc , wait after you see it (5 minutes, to see again 0xcc or most of time 0x3 and then it will fix your board) other way try to connect an other boards and restart from "3"

Dec 17 14:09:30 (none) local0.warn cgminer: Started cgminer 4.9.0
Dec 17 14:09:30 (none) local0.notice cgminer[377]:  detected at /sys/class/gpio/gpio51/value  chain 0
Dec 17 14:09:30 (none) local0.notice cgminer[377]: detect total chain num 1
Dec 17 14:09:30 (none) local0.notice cgminer[377]: i2c init ok
Dec 17 14:09:32 (none) local0.notice cgminer[377]: Chain 0 PIC Version 0xcc
Dec 17 14:13:45 (none) local0.err cgminer[377]: Blisssz: Chain not found 1
Dec 17 14:13:45 (none) local0.err cgminer[377]: Blisssz: Chain not found 2
Dec 17 14:13:45 (none) local0.err cgminer[377]: Blisssz: Chain not found 3
Dec 17 14:13:51 (none) local0.notice cgminer[377]: Chain 0 PIC Version 0x3
[...]

you will see some logs like this , PIC's is currently writing.

Code:

Dump IIC Data:[41][98][0][0]@ChainID:[0], Chip[C9]

wait logs "miner start and switching pool" the board has been flashed with success.


After fixing all or some of boards , you can finaly flash back bitmain l3+  original Firmware.

**************************************************************
Manually Flash
**************************************************************

/!\ I will not assist with "how to" here cause i didnt experience it yet
but if you have stuff (pickit3) and knowledge to manually flash chip of your miner here's the files

 ! warning ! have a look to the pic version you have (writed on the chip).

there is PIC16F1704 or PIC16F1705

Here's the hexa files for each version

MEGA
PIC16F1704.hex
PIC16F1705.hex

1FICHIER
PIC16F1704.hex
PIC16F1705.hex

Thanks to martin_fryc for sharing files, after succefully fix his L3+ by manually flashing PICs

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

hello Sir
I am looking on the board for the pic chip number and i cant se it please help me?
thx
steve

its directly write on the pic (find 5 linear  wholes) the pic is just close to
some people say the manual flash  is working and not depending the pic you have , in fact flash any of 1704 or 1705 file.
i didnt experience manual flash. and people did it , dont send back tutorial.
hopefully someone send the files , thanks again to him