Re: [concordance-devel] New "feature" that we should probably have
Stephen Warren wrote: > My *suspicion* (which is purely a guess) is that libconcord attempts to > always acquire a ton of information at attach time, some of which may be > impossible to acquire if the config is invalid, but the Logitech > application probably only doesn't bother with getting all that info > (probably, a bunch of it is only useful for concordance -v -i, and not a > "simple" action like config programming?) Well INITIALLY the logitech software requests *exactly* what we request... but if it fails, it looks like it backs off, (see my previous post) and just reads 6 bytes... but not 6 bytes contained in the usual 48 - some SEPARATE 6 bytes. -- Phil Dibowitz [EMAIL PROTECTED] 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 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] New "feature" that we should probably have
Phil Dibowitz wrote: > Stephen Warren wrote: >> I've sent the logs to you directly off-list, due to size. > > Thanks. A few questions - your tarball had log2 and log3 (with 3 being > empty), but no log1 - was that on purpose? Also, is this writing a config, > or firmware? It looks like config. Seems simple, though... TOO simple. Write config. When the USB sniffer starts up, it starts capturing log1, but automatically creates a new log when you plug/replug the device, so log2 started when I actually plugged in the Harmony, and log3 due to the reboot that the Logitech software does at the end of the programming. My *suspicion* (which is purely a guess) is that libconcord attempts to always acquire a ton of information at attach time, some of which may be impossible to acquire if the config is invalid, but the Logitech application probably only doesn't bother with getting all that info (probably, a bunch of it is only useful for concordance -v -i, and not a "simple" action like config programming?) - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] New "feature" that we should probably have
Stephen Warren wrote: > I've sent the logs to you directly off-list, due to size. Thanks. A few questions - your tarball had log2 and log3 (with 3 being empty), but no log1 - was that on purpose? Also, is this writing a config, or firmware? It looks like config. Seems simple, though... TOO simple. It tries the usual thing: Get Version Get Version Response 40 18 49 01 80 0F 08 Read Flash 000110 48 Then it tries again with the Get Version and gets a response: Get Version Get Version Response 40 18 49 01 80 0F 08 But this time instead of reading 48 bytes of Flash, it reads 6 - the first 3, it reads twice: Read Flash 02000C 3 Read Flash 02000C 3 Read Flash 020014 3 And then it repeats that whole bit: Get Version Get Version Response 40 18 49 01 80 0F 08 Read Flash 02000C 3 Read Flash 02000C 3 Read Flash 020014 3 And then it invalidates flash, and erases it and writes out the config, and then: Read Flash 020014 3 Read Flash 03CC26 8 Erase Flash 1E Erase Flash 1F Read Flash 02 256 and then reboots the remote. I'll play with this tomorrow - I'm guessing the repeated attempts is just it waiting for an acceptable response to get those bytes and then those bytes have some bare minimum of information. I have no idea how it'll be packed, but I'll post what I find. -- Phil Dibowitz [EMAIL PROTECTED] 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 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] New "feature" that we should probably have
Phil Dibowitz wrote: > ... I ctrl-c'd a config update in the middle of erasing the config. This > left the remote in a state in which the get_identity() calls could were > failing... > > My guess is that the official software has either some way of getting the > minimal identity data from the remote in the event it can't get all the > data, or perhaps some backup way of requesting the data in the event the > main method doesn't work. > > ... but if someone wants to reproduce this and > send me some USB dumps of what the official software does, it shouldn't be > too hard to reproduce this... I've sent the logs to you directly off-list, due to size. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace ___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
[concordance-devel] New "feature" that we should probably have
So today while I was testing Stephen's patch, I ctrl-c'd a config update in the middle of erasing the config. This left the remote in a state in which the get_identity() calls could were failing. As such I could not being a config update again, or a firmware update, or anything else. I tried booting into safemode, and still no-go. I was, as I always am, able to connect my remote to my mac, and use the official software to do a firmware upgrade, and a config update, and my remote was back to normal. My guess is that the official software has either some way of getting the minimal identity data from the remote in the event it can't get all the data, or perhaps some backup way of requesting the data in the event the main method doesn't work. I'm heading out for some good ol' fashion birthday drinking, so I don't really have time to look into it, but if someone wants to reproduce this and send me some USB dumps of what the official software does, it shouldn't be too hard to reproduce this... -- Phil Dibowitz [EMAIL PROTECTED] 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 - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace___ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
