News:

To visit MidNite Solar click this link www.midnitesolar.com

Main Menu

Bootloader error

Started by Jones, November 20, 2016, 07:21:17 AM

Previous topic - Next topic

Jones

Guy's,

Tried to update firmware today.  Kid got stuck in a loop and wouldn't appear as a drive on the connected win8 laptop for more than a second or two. 

No opportunity to drag firmware file over.

Is it recoverable?   

Unit now reads:
Bootloader 2.3 - Bad firmware

Jones

All sorted now.    After reading another members report on this.  -    Managed to copy firmware during a connection cycle after about 20 attempts

ClassicCrazy

Glad to hear you got it - bet you were pretty happy when it took !

Larry
system 1
Classic 150 , 5s3p  Kyocera 135watt , 12s Soneil 2v 540amp lead crystal 24v pack , Outback 3524 inverter
 5s 135w Kyocero , 3s3p 270w Kyocera   Classic 150 ,8s2p  Kyocera 225w to Hawkes Bay Jakiper 48v 20kwh  ,Gobel 16 kwh  lifepo4 Outback VFX 3648  8s2p 380w Rec pv EG4 6000XP

Jones

Yep, out on an extended road trip so delighted.    Like the new features on 1820fw vs 1733   Nice Job Mario!

PKsolar

Help!

Now the whole Kid is down and no buttons work. I need power! I have the same "Bootlegger 2.3 Bad Firmware"

That just happened to me... What do you mean by "Managed to copy firmware during a connection cycle after about 20 attempts" I left it on the laptop for twenty minutes and nothing popped up. On the laptop screen it kept asking me about a (G:) drive ???? but that came and went every two seconds so very hard to read.

PK
10 Evergreen 215, 150 Classic, 48V (8x US Battery 400AH), MNPV Disco; Plus original system - 10 Evergreen, Fronius 2000 grid tie. 2014 added KID, Exeltech 1KW inverter, 12V (2 6V US Battery 400AH) to run garage. Classic 200 w 8 x 285 Solar World in Follow me mode.

ClassicCrazy

Quote from: PKsolar on November 30, 2016, 10:57:32 PM
Help!

Now the whole Kid is down and no buttons work. I need power! I have the same "Bootlegger 2.3 Bad Firmware"

That just happened to me... What do you mean by "Managed to copy firmware during a connection cycle after about 20 attempts" I left it on the laptop for twenty minutes and nothing popped up. On the laptop screen it kept asking me about a (G:) drive ???? but that came and went every two seconds so very hard to read.

PK

I am guessing he meant that you have to keep trying to drag in the update fast as you see that drive popup  - maybe even try to anticipate it and be ready. So that is what he probably meant it took 20 tries before it grabbed it to do the update.

Larry
system 1
Classic 150 , 5s3p  Kyocera 135watt , 12s Soneil 2v 540amp lead crystal 24v pack , Outback 3524 inverter
 5s 135w Kyocero , 3s3p 270w Kyocera   Classic 150 ,8s2p  Kyocera 225w to Hawkes Bay Jakiper 48v 20kwh  ,Gobel 16 kwh  lifepo4 Outback VFX 3648  8s2p 380w Rec pv EG4 6000XP

bjornb

#6
Same problem here when about to update from 1811 to 1856.

I was able to copy both by dragging and using command line, but it took many attempts before firmware was accepted and started loading.
I found it easier to use the command line (as you can see it said 'file copied' several times, but it didnt work until the last attempt shown):

ClassicCrazy

Quote from: bjornb on May 28, 2017, 06:14:55 PM
Same problem here when about to update from 1811 to 1856.

I was able to copy both by dragging and using command line, but it took many attempts before firmware was accepted and started loading.
I found it easier to use the command line (as you can see it said 'file copied' several times, but it didnt work until the last attempt shown):

There is a reg edit program you need to run first if you are using windows - then restart the computer . Then that problem won't happen. Directions on Kid download page.

Larry
system 1
Classic 150 , 5s3p  Kyocera 135watt , 12s Soneil 2v 540amp lead crystal 24v pack , Outback 3524 inverter
 5s 135w Kyocero , 3s3p 270w Kyocera   Classic 150 ,8s2p  Kyocera 225w to Hawkes Bay Jakiper 48v 20kwh  ,Gobel 16 kwh  lifepo4 Outback VFX 3648  8s2p 380w Rec pv EG4 6000XP

bjornb

The registry file was already loaded from previous upgrade (1811).

I also verified that it was set in registry.