On Thu, Feb 12, 2009 at 12:32:28PM +0100, Michael Frase wrote:
> Sorry that I didn't answer earlier. But I was not at home for several
> weeks and wasn't able to check my private Mails.
>
> Now that I'm back again I have tried the patch with my harmony 555 and
> can confirm Simons experience! Firm
Sorry that I didn't answer earlier. But I was not at home for several
weeks and wasn't able to check my private Mails.
Now that I'm back again I have tried the patch with my harmony 555 and
can confirm Simons experience! Firmware upgrade works now.
Phil, do you need some more logs to check the de
Simon Budig wrote:
> Phil Dibowitz (p...@ipom.com) wrote:
>> Ping? Can you try a firmware update with this patch? (Or anyone else with a
>> 5x remote)?
>
> I just tried with a 525 - seems to work great!
Aha!! Woo! Thanks for testing Simon.
And thanks Stephen for that great catch.
With that I th
Phil Dibowitz (p...@ipom.com) wrote:
> Ping? Can you try a firmware update with this patch? (Or anyone else with a
> 5x remote)?
I just tried with a 525 - seems to work great!
--
r...@legends:/tmp# /unstable/bin/concordance -i
Concordance 0.20+CVS
Copyright 2007 Ke
Phil Dibowitz wrote:
> Michael,
>
> Can you give the attached patch a try?
Michael,
Ping? Can you try a firmware update with this patch? (Or anyone else with a
5x remote)?
Thanks,
--
Phil Dibowitz p...@ipom.com
Open Source software and tech docsInsanity Pala
Michael,
Can you give the attached patch a try?
[Note for those interested, this patch has a fix to the bug Steven found, a
fix to the max_chunk_len previous sent out (but not yet committed) and a
debug function not currently used, but I'm too lazy to take out at the moment.]
--
Phil Dibowitz
Stephen Warren wrote:
> Phil Dibowitz wrote:
>> 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 p
Phil Dibowitz wrote:
> 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 obviou
Stephen Warren wrote:
> Phil Dibowitz wrote:
>> Stephen,
>>
>> Have you been looking at any of the firmware-on-525 stuff? I've poured over
>> it several times and sent several debug patches to folks and looked through
>> the dumps a lot...
>
> I haven't looked at it at all. I thought the thing you
Phil Dibowitz wrote:
> Stephen,
>
> Have you been looking at any of the firmware-on-525 stuff? I've poured over
> it several times and sent several debug patches to folks and looked through
> the dumps a lot...
I haven't looked at it at all. I thought the thing you were missing was
answered by Ke
Stephen,
Have you been looking at any of the firmware-on-525 stuff? I've poured over
it several times and sent several debug patches to folks and looked through
the dumps a lot...
But I don't see anything we're doing differently. We're getting the firmware
to update, but we're missing some magic
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
--
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.
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 eee
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
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,
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
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
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 So
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.
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 0
[+concordance-devel]
Michael Frase wrote:
> Am Sonntag, den 28.12.2008, 21:05 +0100 schrieb Phil Dibowitz:
>> I don't expect this patch to make a difference one way or the other, but
>> reverse the last patch and try this one.
>>
>
> As expected, no difference. You'll find the usbmon-log attached
[+concordance-devel]
Michael Frase wrote:
> Hi Phil,
>
> now I have collected all data you requested. I have also done a firmware
> upgrade from v2.6 to v3.0.
So I've been digging through these tonight. There's some odd things:
1. The official software doesn't seem to read the config (GetIdenti
It's great to see that you are working on that upgrade problem!
Unfortunately I don't have my remote here at the moment. But I will be
back at home next week. Then I'll try to give you all requested logs.
Best regards
Michael
Am Dienstag, den 23.12.2008, 00:24 +0100 schrieb Phil Dibowitz:
> P
Phil Dibowitz wrote:
> some extra bits. I haven't really dug through it yet, but if anyone's
> interested (Stephen, weren't you the hero last time? =) drop me an email and
> I can send you the USB dumps from Michael's windows box.
OK, I kept tweaking consnoop.c and realized I needed to really fix
OK, so I finally have gotten back to playing with 525 firmware upgrades.
Sorry to all for the delay.
It took me half an hour just to re-read all the old email and remember where
we were.
To refresh your memory: we upgrade the firmware just fine but (1) the remote
doesn't report the new version p
Michael Frase wrote:
> Now I did a firmware updrade (v2.5 -> v2.6) with the logitech windows
> software and dumped the firmware again with concordance... The firmware
> dump is exactly the same as the old one (that reported the wrong
> version). But now the firmware version is correctly recognised
On Tue, April 15, 2008 9:35 am, Michael Frase wrote:
> Any Suggestions? Is it possible to log the usb transfer (firmware
> upgrade) in windows (like usbmon in linux)?
Yes. Use SnoopyPro, available from:
http://sourceforge.net/project/showfiles.php?group_id=34567
Once you have the captures in the
Now I did a firmware updrade (v2.5 -> v2.6) with the logitech windows
software and dumped the firmware again with concordance... The firmware
dump is exactly the same as the old one (that reported the wrong
version). But now the firmware version is correctly recognised as v2.6.
I tried to downgrad
Stephen Warren wrote:
> On Thu, April 10, 2008 1:25 pm, Phil Dibowitz wrote:
>> Michael Frase wrote:
>>> Hi Phil,
>>>
>>> thanks for your quick replies and changes in cvs. I'm back again and
>>> tested latest cvs with my harmony 555.
>> ...
>>> Here's whats REALLY odd. I massaged the LatestUpdate.E
On Thu, April 10, 2008 1:25 pm, Phil Dibowitz wrote:
> Michael Frase wrote:
>> Hi Phil,
>>
>> thanks for your quick replies and changes in cvs. I'm back again and
>> tested latest cvs with my harmony 555.
>
> ...
> > Here's whats REALLY odd. I massaged the LatestUpdate.EZUp to be in the
> format we
Michael Frase wrote:
> Hi Phil,
>
> thanks for your quick replies and changes in cvs. I'm back again and
> tested latest cvs with my harmony 555.
Michael sent me, off-list, a his LatestUpdate.EZUp, and a firmware dump from
both before and after the upgrade.
Here's whats REALLY odd. I massaged th
Am Donnerstag, den 10.04.2008, 10:44 -0700 schrieb Phil Dibowitz:
> Michael Frase wrote:
> > Hi Phil,
> >
> > thanks for your quick replies and changes in cvs. I'm back again and
> > tested latest cvs with my harmony 555.
> >
> > Unfortunately firmware update doesn't work as expected. The update
Michael Frase wrote:
> Hi Phil,
>
> thanks for your quick replies and changes in cvs. I'm back again and
> tested latest cvs with my harmony 555.
>
> Unfortunately firmware update doesn't work as expected. The update
> process itself seems to be ok... But firmware version remains the same
> (Upda
Hi Phil,
thanks for your quick replies and changes in cvs. I'm back again and
tested latest cvs with my harmony 555.
Unfortunately firmware update doesn't work as expected. The update
process itself seems to be ok... But firmware version remains the same
(Update from v2.5 to v2.6).
> $ sudo conc
Stefan Arndt wrote:
>>> OK, updated cvs.
>>>
>>> But it is still Firmware 2.1 after all...
>> It looks like you may have a 2.1 firmware file. You may want to remove it
>> and then try downloading it through the site again. For what it's worth,
>> someone else with your remote was just able to upgra
Stefan,
The firmware capture you sent me appears to be truncated or stopped before
the firmware bits. This line near the end:
c570d3c0 3743697519 C Ci:003:00 0 33 = 0600ff09 01a10115 0026ff00 7508a102
09029540 8102c0a1 02090595 409102c0
is a control transfer very early on, and your file doesn't
Stefan Arndt wrote:
> Hello,
>
> well, it is getting better.
>
> But only sort of...
Yeah, I didn't expect that'd lead to much good.
Can you send me the firmware file you're using? I'm at a bit of a loss at
this point...
--
Phil Dibowitz [EMAIL PROTECTED]
Open Sour
Hello,
well, it is getting better.
But only sort of...
It looks like it does not really writes the firmware.
It is still 2.1
localhost:/home/arndt/Documents # concordance -F LatestFirmware\(3\).EZUp
Concordance 0.13+CVS
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distribu
Stefan Arndt wrote:
> Hello,
>
> got the files all new from cvs.
>
> Furthermore only 2 of my three usb ports on my
> laptop work. If the remote is attached to one of them, concordance
> did not find the remote.
Well, then make sure you're always using a good one!
> DEBUG (HID_ReadReport): Fail
Hello,
got the files all new from cvs.
Furthermore only 2 of my three usb ports on my
laptop work. If the remote is attached to one of them, concordance
did not find the remote.
localhost:/home/arndt/Documents/concordance # concordance -F firmware.EZUp
Concordance 0.13+CVS
Copyright 2007 Kevin T
Stefan Arndt wrote:
> Hello,
>
> I reversed the former patch and patched with the new one.
OK, I see the problem (or at least *a* problem). Looking back at the USB
logs, we need to write a 0, not a 1 to address 20. I've committed a fix
to CVS, reverse the patch, cvs update, and try again.
--
Hello,
I reversed the former patch and patched with the new one.
localhost:/home/arndt/Documents/concordance/concordance # concordance -F
firmware.EZUp
Concordance 0.13+CVS
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distributed under the GPLv3.
DEBUG (FindRemote): bNumEn
Stefan Arndt wrote:
> Hello,
>
> reversed patch and patched again.
> It took longer but failed.
Taking longer is expected, there was a 10-second sleep in there.
OK, I uploaded a patch that will attempt to re-init the harmony after the
config reset (which I wouldn't think is necessary based on th
Hello,
reversed patch and patched again.
It took longer but failed.
I ran it twice, slightly different error message (HID_ReadReport).
localhost:/home/arndt/Documents/concordance/concordance # concordance -F
firmware.EZUp
Concordance 0.13+CVS
Copyright 2007 Kevin Timmerman and Phil Dibowitz
Thi
Stefan Arndt wrote:
> Hello,
>
> applied patch to latest cvs tree.
OK, this is helpful.
Reverse that patch (patch -p0 -R < libconcord-fw-debug.patch) and apply this
new one (same URL):
http://www.phildev.net/concordance/libconcord-fw-debug.patch
Either we need to wait a bit after to se a Res
Hello,
applied patch to latest cvs tree.
localhost:/home/arndt/Documents/concordance/concordance # concordance -F
firmware.EZUp
Concordance 0.13+CVS
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distributed under the GPLv3.
DEBUG (FindRemote): bNumEndpoints 2
DEBUG (check_ep
Stefan Arndt wrote:
>
> I think therefore I could not get the a proper version of the patch you
> sent to me.
Well, that would explain the lack of new output.
Do another CVS update and then get an updated patch from here:
http://www.phildev.net/concordance/libconcord-fw-debug.patch
And apply
Hello Phil
I just receive a summary of the mailing list.
I think therefore I could not get the a proper version of the patch you
sent to me.
Regards
Stefan
--
GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
Jetzt dabei sein: http://www.shortview.de/[EMAIL PRO
Hello,
thanks for the patch.
To me, nothing changed.
localhost:/home/arndt/Documents/concordance/concordance # concordance -F
firmware.EZUp
Concordance 0.13+CVS
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distributed under the GPLv3.
DEBUG (FindRemote): bNumEndpoints 2
DEB
Phil Dibowitz wrote:
> Phil Dibowitz wrote:
>>> bNumEndpoints 2
>>> address 81 attrib 03 max_length 64
>>> address 02 attrib 03 max_length 64
>>> Requesting Identity: 100% done
>>> Failed to read from device: -110 (could not detach kernel driver from
>>> interface 0: No data availa
Phil Dibowitz wrote:
>> bNumEndpoints 2
>> address 81 attrib 03 max_length 64
>> address 02 attrib 03 max_length 64
>> Requesting Identity: 100% done
>> Failed to read from device: -110 (could not detach kernel driver from
>> interface 0: No data available)
>> Failed to prepare rem
Stefan Arndt wrote:
> Hi,
>
>
> thanks a lot for the answer.
>
> I did delete the serial number.
Ohhh. OK, well that makes me feel better.
> bNumEndpoints 2
> address 81 attrib 03 max_length 64
> address 02 attrib 03 max_length 64
> Requesting Identity: 100% done
> Failed to r
Hi,
thanks a lot for the answer.
I did delete the serial number.
But here is the output of concordancve -i -v compiled with
your requested FLAG:
localhost:/home/arndt/Documents/concordance/concordance # concordance -i -v
Concordance 0.13+CVS
Copyright 2007 Kevin Timmerman and Phil Dibowitz
Th
Stefan Arndt wrote:
> Hello,
>
> first thank you for this excellent software.
>
> I do have a problem with
> a firmware upgrade on my remote.
>
> localhost:/home/arndt/Documents # concordance -i -v
> Concordance 0.13+CVS
...
> Serial Number: {}
> {}
> {}
Well, that's certainly
Hello,
first thank you for this excellent software.
I do have a problem with
a firmware upgrade on my remote.
localhost:/home/arndt/Documents # concordance -i -v
Concordance 0.13+CVS
Copyright 2007 Kevin Timmerman and Phil Dibowitz
This software is distributed under the GPLv3.
Requesting Identi
56 matches
Mail list logo
