Hi Folks!
Absolutely the same stuff I'm having now with my L3+ too.
I had a well working L3+, then by mistake flashed it with D3 firmware (instead of different ASIC device... to fix the "x" issue solved in the 20th of November 2017 formware for D3). After that I immediately re-flashed back to the L3+ firmware but got what i got, Zero chips on each of the four hash-blades...
I tried all the stuff including Micri SD image as did here and the same it didn't help.
I also need this suggestion on which hex file to take and from where (the path) on the correctly working hash blade from another L3+. So I "ssh" the L3+ and should "scp" the file ?? to the same location on the malfunctioning L3+ (do that for all 4 blades) and then reboot. Cirrect? Which path to the file then guys?
Please help.
Thanks,
Egor
Absolutely the same stuff I'm having now with my L3+ too.
I had a well working L3+, then by mistake flashed it with D3 firmware (instead of different ASIC device... to fix the "x" issue solved in the 20th of November 2017 formware for D3). After that I immediately re-flashed back to the L3+ firmware but got what i got, Zero chips on each of the four hash-blades...
I tried all the stuff including Micri SD image as did here and the same it didn't help.
I also need this suggestion on which hex file to take and from where (the path) on the correctly working hash blade from another L3+. So I "ssh" the L3+ and should "scp" the file ?? to the same location on the malfunctioning L3+ (do that for all 4 blades) and then reboot. Cirrect? Which path to the file then guys?
Please help.
Thanks,
Egor
need to plug programmation stuff in 6 holes on the right of eeprom texas , and extract hexa file from a working l3+ hashboard, then flash it manually on the fail board $
and share the hexa file for some of us have only one fail l3+ but no other to fix
