Re: [concordance-devel] Firmware Upgrade 525
That looks like the serial number (aka GUID). At 04:59 PM 12/29/2008, you wrote: >For those that care, the hex is: > >000 >020 0bd912c2 48b0073c b093b382 75866920 >040 423626f5 4fe972d5 ab2b4686 580a84df >060 -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Firmware Upgrade 525
Steffen Sieg wrote: > I have another problem: while setting up my remote, there came up a file > named LearnIr.EZTut. And congruity does not recognize this. It was to > learn some instructions from an original remote control. The most recent actual release of congruity doesn't support IR learning. However, if you check out the latest code from SVN, then it should work fine (with the lastest libconcord from CVS too) > So I did it completely in windows in a virtual box machine, and it went > relatively good, but not perfect. > > Regards > > Steffen Sieg -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Firmware Upgrade 525
Michael Frase wrote: > Am Montag, den 29.12.2008, 22:59 +0100 schrieb Phil Dibowitz: >> Michael Frase wrote: >>> You'll find the the binary file attached! >> Thanks. I'm retarded, it didn't need to be bzip2'd, it's 48 bytes. >> >> For those that care, the hex is: >> >> 000 >> 020 0bd912c2 48b0073c b093b382 75866920 >> 040 423626f5 4fe972d5 ab2b4686 580a84df >> 060 >> >> Would you mind doing this on 2 or 3 revs of the firmware (2.5, 2.6, 3.0)? >> You can either send the binary, or the output of 'od -X' on them (that's the >> above). I meant to ask before and forgot. > > One question... just to be sure that we don't talk at cross-purposes. > This hex is readout off the remote, right? So it doesn't matter wich > firmware I use for generating the tout binary... just the current fw of > the remote matters. Correct. > I have flashed fw2.5, 2.6 and 3.0 with RemoteCore and after each flash I > ran concordance to readout the binary. But I got every time the same hex > output! No change at all, same as stated above. Erm. Eh. > Does that make sense? It runs me out of ideas... -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Firmware Upgrade 525
Am Montag, den 29.12.2008, 22:59 +0100 schrieb Phil Dibowitz: > Michael Frase wrote: > > You'll find the the binary file attached! > > Thanks. I'm retarded, it didn't need to be bzip2'd, it's 48 bytes. > > For those that care, the hex is: > > 000 > 020 0bd912c2 48b0073c b093b382 75866920 > 040 423626f5 4fe972d5 ab2b4686 580a84df > 060 > > Would you mind doing this on 2 or 3 revs of the firmware (2.5, 2.6, 3.0)? > You can either send the binary, or the output of 'od -X' on them (that's the > above). I meant to ask before and forgot. One question... just to be sure that we don't talk at cross-purposes. This hex is readout off the remote, right? So it doesn't matter wich firmware I use for generating the tout binary... just the current fw of the remote matters. I have flashed fw2.5, 2.6 and 3.0 with RemoteCore and after each flash I ran concordance to readout the binary. But I got every time the same hex output! No change at all, same as stated above. Does that make sense? -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Firmware Upgrade 525
Steffen Sieg wrote: > Hi, > > I have another problem: while setting up my remote, there came up a file > named LearnIr.EZTut. And congruity does not recognize this. It was to > learn some instructions from an original remote control. > > So I did it completely in windows in a virtual box machine, and it went > relatively good, but not perfect. This shouldn't be a problem at all. Re-run it with debug mode on and send the output, please. Also, try it with the latest CVS. -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Firmware Upgrade 525
Hi, I have another problem: while setting up my remote, there came up a file named LearnIr.EZTut. And congruity does not recognize this. It was to learn some instructions from an original remote control. So I did it completely in windows in a virtual box machine, and it went relatively good, but not perfect. Regards Steffen Sieg 2008/12/29 Phil Dibowitz > Michael Frase wrote: > > You'll find the the binary file attached! > > Thanks. I'm retarded, it didn't need to be bzip2'd, it's 48 bytes. > > For those that care, the hex is: > > 000 > 020 0bd912c2 48b0073c b093b382 75866920 > 040 423626f5 4fe972d5 ab2b4686 580a84df > 060 > > Would you mind doing this on 2 or 3 revs of the firmware (2.5, 2.6, 3.0)? > You can either send the binary, or the output of 'od -X' on them (that's > the > above). I meant to ask before and forgot. > > -- > Phil Dibowitz p...@ipom.com > Open Source software and tech docsInsanity Palace of Metallica > http://www.phildev.net/ http://www.ipom.com/ > > "Never write it in C if you can do it in 'awk'; > Never do it in 'awk' if 'sed' can handle it; > Never use 'sed' when 'tr' can do the job; > Never invoke 'tr' when 'cat' is sufficient; > Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming > > > > > -- > > ___ > concordance-devel mailing list > concordance-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/concordance-devel > > -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Firmware Upgrade 525
Michael Frase wrote: > You'll find the the binary file attached! Thanks. I'm retarded, it didn't need to be bzip2'd, it's 48 bytes. For those that care, the hex is: 000 020 0bd912c2 48b0073c b093b382 75866920 040 423626f5 4fe972d5 ab2b4686 580a84df 060 Would you mind doing this on 2 or 3 revs of the firmware (2.5, 2.6, 3.0)? You can either send the binary, or the output of 'od -X' on them (that's the above). I meant to ask before and forgot. -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Firmware Upgrade 525
Steffen Sieg wrote: > Hi Phil, > > I'm a little bit unsure how to apply this patch? I never down this > before. Could you give me an advise? Steffan, Don't sweat it - I only need one copy of the dump and Michael got it. Thanks. -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Firmware Upgrade 525
Hi Phil, I'm a little bit unsure how to apply this patch? I never down this before. Could you give me an advise? Regards Steffen 2008/12/29 Phil Dibowitz > Phil Dibowitz wrote: > > Hmmm. OK, well, there's no difference in the actual write-out of the > flash > > this time. That's good. I guess. > > > > That leaves a much smaller part of the logs to analyze... > > Phew. > > OK, so the differences left are pretty small. The most obvious one is the > read of 48 bytes at 0x200010. > > Apply this patch, and attempt a firmware upgrade. It'll exit before it ever > does the firmware upgrade and will write out a binary file to /tmp/tout. > > Take /tmp/tout, bzip2 it up and email it to me. > > I'll forward it off to Stephen and Kevin as well - they're better at > reverse > engineering that stuff than I am... but I'll take a crack at it. > > -- > Phil Dibowitz p...@ipom.com > Open Source software and tech docsInsanity Palace of Metallica > http://www.phildev.net/ http://www.ipom.com/ > > "Never write it in C if you can do it in 'awk'; > Never do it in 'awk' if 'sed' can handle it; > Never use 'sed' when 'tr' can do the job; > Never invoke 'tr' when 'cat' is sufficient; > Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming > > > > -- > > ___ > concordance-devel mailing list > concordance-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/concordance-devel > > -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Firmware Upgrade 525
Phil Dibowitz wrote:
> Hmmm. OK, well, there's no difference in the actual write-out of the flash
> this time. That's good. I guess.
>
> That leaves a much smaller part of the logs to analyze...
Phew.
OK, so the differences left are pretty small. The most obvious one is the
read of 48 bytes at 0x200010.
Apply this patch, and attempt a firmware upgrade. It'll exit before it ever
does the firmware upgrade and will write out a binary file to /tmp/tout.
Take /tmp/tout, bzip2 it up and email it to me.
I'll forward it off to Stephen and Kevin as well - they're better at reverse
engineering that stuff than I am... but I'll take a crack at it.
--
Phil Dibowitz p...@ipom.com
Open Source software and tech docsInsanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
"Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming
Index: libconcord/libconcord.cpp
===
RCS file: /cvsroot/concordance/concordance/libconcord/libconcord.cpp,v
retrieving revision 1.38
diff -u -r1.38 libconcord.cpp
--- libconcord/libconcord.cpp 14 Oct 2008 19:35:01 - 1.38
+++ libconcord/libconcord.cpp 29 Dec 2008 20:53:37 -
@@ -1106,6 +1106,11 @@
return 0;
}
+int read_arbitrary_flash(int addr, uint32_t size, uint8_t **out)
+{
+ return _read_fw_from_remote(*out, size, addr, NULL, NULL);
+}
+
int read_firmware_from_remote(uint8_t **out, uint32_t *size, lc_callback cb,
void *cb_arg)
{
Index: libconcord/libconcord.h
===
RCS file: /cvsroot/concordance/concordance/libconcord/libconcord.h,v
retrieving revision 1.21
diff -u -r1.21 libconcord.h
--- libconcord/libconcord.h 14 Oct 2008 19:35:01 - 1.21
+++ libconcord/libconcord.h 29 Dec 2008 20:53:38 -
@@ -464,6 +464,9 @@
int post_new_code(uint8_t *data, uint32_t size,
char *key_name, char *encoded_signal);
+/* debug */
+int read_arbitrary_flash(int addr, uint32_t size, uint8_t **out);
+
#ifdef __cplusplus
}
#endif
Index: concordance/concordance.c
===
RCS file: /cvsroot/concordance/concordance/concordance/concordance.c,v
retrieving revision 1.35
diff -u -r1.35 concordance.c
--- concordance/concordance.c 20 Dec 2008 21:18:55 - 1.35
+++ concordance/concordance.c 29 Dec 2008 20:53:38 -
@@ -569,6 +569,15 @@
uint8_t *firmware_bin;
uint32_t firmware_bin_size;
+ uint8_t *blob = 0;
+ uint32_t blobsize = 48;
+
+ read_arbitrary_flash(0x200010, blobsize, &blob);
+
+ write_firmware_to_file(blob, blobsize, "/tmp/tout", 1);
+
+ exit(0);
+
err = 0;
firmware_bin = 0;
signature.asc
Description: OpenPGP digital signature
--
___
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Model Logitech Harmony 525 not supported for firmware update
Steffen Sieg wrote: > Hi everybody! > > I want to submit, that the Model Harmony 525 is not supported in case > firmware update. So I was not able to proceed programming, because the > Logitechs website would not give me access to further files. Yes, we know: http://www.phildev.net/concordance/supported_models.shtml We're working on it. > Regards, I hope for updates. Till they come, I have to use Windows. No, just use windows for the firmware upgrade, and the you should be able to use Linux from then on. -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming signature.asc Description: OpenPGP digital signature -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
[concordance-devel] Model Logitech Harmony 525 not supported for firmware update
Hi everybody! I want to submit, that the Model Harmony 525 is not supported in case firmware update. So I was not able to proceed programming, because the Logitechs website would not give me access to further files. Regards, I hope for updates. Till they come, I have to use Windows. Steffen Sieg -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Harmony One Support
On Mon, Dec 29, 2008 at 12:07:29PM -, Kevin Wright wrote: > Oh definitely, getting these to work would be a big win for concordance :) Yup, it's definitely high on my list. I had a contact at Logitech for a while I was hoping was going to be able to get specs for them, but that fell through last week, unfortunately. Since firmware support for non-zwave remotes is *mostly* working, I wanted to just finish that up, get the final bugs worked out, and then I can concentrate all my time on making the basics (read: config updates) work on the zwave remotes. The z-wave remotes definitely need to be supported, no question. We've just had a lot of trouble reverse-engineering the protocol. Anything you can find is welcome! -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming signature.asc Description: Digital signature -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Harmony One Support
Oh definitely, getting these to work would be a big win for concordance :) -Original Message- From: Phil Dibowitz [mailto:p...@ipom.com] Sent: 29 December 2008 11:33 To: concordance-devel@lists.sourceforge.net Subject: Re: [concordance-devel] Harmony One Support On Mon, Dec 29, 2008 at 10:44:29AM -, Kevin Wright wrote: > Personally, I'm not so bothered about firmware updates for the > 1000/1000i/one/etc, but particularly keen to see these modules being > configurable via concordance. > > My personal goal is a near-complete replacement of the existing > harmony software which, quite frankly, sucks and does a great > disrespect to the otherwise fantastic hardware. > > > I guess the current hurdle is to support the tcp-over-usb > communications that these newer models support. I'm an experienced > developer looking to contribute, and planned to start by > decompiling/analysing some of the java classes used by the "official" > drivers. Obviously, I'd first like to know what progress has already > been made in this direction so that I don't have to re-invent the wheel! I managed to get one of them to DHCP and get the basic tcp-over-usb working. It's not a pleasant experience, but it's possible. I can find the notes on that if you're interested. The problem is we've had little or no luck getting beyond that - understanding the actual protocol that's used within the TCP packets... -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Harmony One Support
On Mon, Dec 29, 2008 at 10:44:29AM -, Kevin Wright wrote: > Personally, I'm not so bothered about firmware updates for the > 1000/1000i/one/etc, but particularly keen to see these modules being > configurable via concordance. > > My personal goal is a near-complete replacement of the existing harmony > software which, quite frankly, sucks and does a great disrespect to the > otherwise fantastic hardware. > > > I guess the current hurdle is to support the tcp-over-usb communications > that these newer models support. I'm an experienced developer looking to > contribute, and planned to start by decompiling/analysing some of the java > classes used by the "official" drivers. Obviously, I'd first like to know > what progress has already been made in this direction so that I don't have > to re-invent the wheel! I managed to get one of them to DHCP and get the basic tcp-over-usb working. It's not a pleasant experience, but it's possible. I can find the notes on that if you're interested. The problem is we've had little or no luck getting beyond that - understanding the actual protocol that's used within the TCP packets... -- Phil Dibowitz p...@ipom.com Open Source software and tech docsInsanity Palace of Metallica http://www.phildev.net/ http://www.ipom.com/ "Never write it in C if you can do it in 'awk'; Never do it in 'awk' if 'sed' can handle it; Never use 'sed' when 'tr' can do the job; Never invoke 'tr' when 'cat' is sufficient; Avoid using 'cat' whenever possible" -- Taylor's Laws of Programming signature.asc Description: Digital signature -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] Harmony One Support
Personally, I'm not so bothered about firmware updates for the 1000/1000i/one/etc, but particularly keen to see these modules being configurable via concordance. My personal goal is a near-complete replacement of the existing harmony software which, quite frankly, sucks and does a great disrespect to the otherwise fantastic hardware. I guess the current hurdle is to support the tcp-over-usb communications that these newer models support. I'm an experienced developer looking to contribute, and planned to start by decompiling/analysing some of the java classes used by the "official" drivers. Obviously, I'd first like to know what progress has already been made in this direction so that I don't have to re-invent the wheel! -Original Message- From: concorda...@pivert.org [mailto:concorda...@pivert.org] Sent: 25 December 2008 19:49 To: concordance-devel@lists.sourceforge.net Subject: Re: [concordance-devel] Harmony One Support On Thursday 25 December 2008 20:18:55 Phil Dibowitz wrote: > concorda...@pivert.org wrote: > > Hi, > > > > I just received an harmony one for Christmas. > > > > Could someone give me the status of the harmony one support by > > concordance ? > > We've had almost no luck on the z-wave serious remotes (890, 1000, Harmony > One, Harmony XBox, etc.), unfortunately. I'm trying to wrap up the final > bits of support on the older non-zwave remotes, and then I'll be turning > all my attention to the z-waves, but so far we haven't had much luck. Thanks for the quick answer... I can't hide my deception from Logitech to not provide the tool for Linux. I don't know yet if I'll put it back to the shop. I'm just trying to download a Windows XP CD, so I can at least give it a try in a kvm virtual machine :-(. Many thanks, François. -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel -- ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
