Bug 3881 - Recent nightlies fail to complete firmware update
: Recent nightlies fail to complete firmware update
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Misc
: 6.5b1
: PC Windows XP
: P2 critical (vote)
: ---
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-08-07 17:30 UTC by Chris Owens
Modified: 2008-09-15 14:39 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
Log file showing attempted firmware upgrade (22.32 KB, text/plain)
2006-08-07 17:35 UTC, Chris Owens
Details
log file showing successful fw upgrade over wired connxn (27.24 KB, text/plain)
2006-08-08 09:09 UTC, Chris Owens
Details
log file showing successful fw upgrade using ss6.3 (39.29 KB, text/plain)
2006-08-08 09:20 UTC, Chris Owens
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Owens 2006-08-07 17:30:03 UTC
On recent 6.5 nightlies, firmware updates do not complete.  Starting with FW55, I connect to 6.5 and get the "Squeezebox Software Update" message.  I hold down the brightness button as directed.  The bar graph goes most (or all?) of the way over, and then suddenly I'm back at the "Squeezebox Software Update" message again.

After that, holding down brightness results in the message: "update_begin: bad state" (typical message following an interrupted firmware update)

I tried using 6.3.1 to upgrade from FW55 to 59, just by placing the fw59 binary in the Firmware directory and editing the squeezebox2.version file, and encountered no problems.

Also I tried using 6.5 to downgrade to FW55, or reload 59, and each time I experienced this problem.

So, it seems to be related to the Slimserver version, not to the firmware version.
Comment 1 Dan Sully 2006-08-07 17:31:59 UTC
Andy, Triode - I believe this is related to the recent changes in slimproto wrt disconnecting clients.
Comment 2 Andy Grundman 2006-08-07 17:33:07 UTC
I will take a look.
Comment 3 Chris Owens 2006-08-07 17:33:54 UTC
I forgot to mention: the update completes correctly if performed using a wired connection.  It only seems to effect wireless connected SB3s.
Comment 4 Chris Owens 2006-08-07 17:35:16 UTC
Created attachment 1399 [details]
Log file showing attempted firmware upgrade

Here's the log I captured.
Comment 5 Andy Grundman 2006-08-07 17:40:29 UTC
I don't understand how our slimproto code could cause problems only on wireless?  Can you also post a log from an older version where there aren't any problems?
Comment 6 Chris Owens 2006-08-08 09:09:41 UTC
Created attachment 1402 [details]
log file showing successful fw upgrade over wired connxn

Well the most obvious thing that occurs to me is the wired connection seems to complete the firmware more quickly than the wireless.  Is there a timeout that the wired connection just slips under?
Comment 7 Chris Owens 2006-08-08 09:20:34 UTC
Created attachment 1403 [details]
log file showing successful fw upgrade using ss6.3
Comment 8 Andy Grundman 2006-08-08 10:31:43 UTC
Fixed in change 8859.