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 properly and (2) on some devices we end up rebooting into safe mode afterwards. Michael Frase sent me a snoopy dump of a firmware upgrade from windows and it's quite different from Kevin's. It reads a bunch of state variables before it writes things out. I suspect somewhere in those writes are hidden 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. One thing that's interesting that he pointed out was that it reports it's USB Product ID with the version number in it: /proc/bus/usb/devices: > P: Vendor=046d ProdID=c111 Rev= 9.30 > S: Manufacturer=Harmony Remote 0-2.5.0 > S: Product=Harmony Remote 0-2.5.0 vs. > S: Manufacturer=Harmony Remote 0-2.6.0 > S: Product=Harmony Remote 0-2.6.0 Clearly this is in a state variable or something similar somewhere. -- Phil Dibowitz p...@ipom.com Open Source software and tech docs Insanity 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
