harmony 525 / 555 bricked if firmware updated using concordance

Bug #880275 reported by Florian Hiemeyer
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
concordance (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
Oneiric
Fix Released
Undecided
Unassigned
Precise
Fix Released
High
Mathieu Trudel-Lapierre

Bug Description

'lsb_release -rd'
Description: Ubuntu 11.10
Release: 11.1
package:
concordance 0.23-1.2

For harmony 525 / 555 users, if you apply "concordance -i" it shows a negative(!) memory on the device (detailled report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594615).
If you update the firmware using that concordance package, you brick your harmony!

Despite this being reported as a bug for debian, and a patch already given in the above email discussion in November 2010 (see message from Mr. Trudel, subject: Testing a patch to fix the 525), all versions do not apply this patch:
This is clear, as the latest code in source forge is 28 August 2010, meaning all newer versions (at least the 0.22 and 0.23 versions I tried) have the error inside.

Resulting from this, also the 0.23-1.2 version is wrong.
I unbricked my harmony be leaving it on and plugged in the usb port, installing 0.22 source code, editing the header file in "libconcord" as described by Mr. Trudel, compiling & installing it manually.

Due to the risk of bricking your harmony device, I propose to clarify this (very small, it's only one number wrong in source code!)
rather fast ...

tags: added: bricked concordance harmony logitech remote
tags: added: libconcord1 libconcord2
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Yep, we're getting concordance from Debian and still are at a revision prior to the patch being re-introduced.

I'll mark this In Progress/High, and start preparing an SRU fix (applying the patch to the current version in Oneiric)

Changed in concordance (Ubuntu):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Mathieu Trudel-Lapierre (mathieu-tl)
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Hello Florian, or anyone else affected,

Accepted concordance into oneiric-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in concordance (Ubuntu Oneiric):
status: New → Fix Committed
tags: added: verification-needed
Revision history for this message
Florian Hiemeyer (flohiemeyer) wrote :

Have connected my Harmony 555 today, with new libconcord2 lib and the ubuntu concordance package.

Result:
florian@ocelot:/usr/bin$ concordance -i
Concordance 0.23
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distributed under the GPLv3.

Requesting Identity: 100% done
  Model: Logitech Harmony 555 (Mocha Grande)
  Firmware Version: 3.0
  Hardware Version: 3.0
  Config Flash Used: 32% (127 of 384 KiB)

Success!

---
Did not update, but it seems very trustful now!

Revision history for this message
Florian Hiemeyer (flohiemeyer) wrote :

Thank you very much for responding so quickly!!
!

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package concordance - 0.23-1.2ubuntu1

---------------
concordance (0.23-1.2ubuntu1) oneiric-proposed; urgency=low

  * debian/patches/h525-flash-size-detection.patch: fix flash size detection
    for Harmony 525 and 555. (LP: #880275)
 -- Mathieu Trudel-Lapierre <email address hidden> Thu, 27 Oct 2011 13:29:06 -0400

Changed in concordance (Ubuntu Oneiric):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

I saw too late that this wasn't fixed in precise yet. Mathieu, please upload ASAP. Thanks!

Changed in concordance (Ubuntu Precise):
milestone: none → precise-alpha-1
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

In Precise we have concordance 0.23-2, which is where this patch is from; so I'll close this as Fix Released for precise as well.

Changed in concordance (Ubuntu Precise):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.