On 03/30/2010 09:02 PM, Stephen Warren wrote: > So, I've taken a look at the Harmony 700 logs, and overall it looks > basically similar to other remotes. However, there are definitely some > differences that will take some work.
I got a 700 today via eBay. By correlating some stuff against the HTTP traffic, here are a few more details: Harmony 700 GET_VERSION response 28 GET_VERSION response, length 8 25 Firmware version 2.5 (Region 2 version) # 22 in safe mode on SRW's remote; region 0/1 version? 00 HW version 0.0 1C Flash ID (FW returns these swapped relative to CFI/JEDEC protocol) 15 Flash Manufacturer E0 Architecture (and protocol) 14, fw_type 0 (0=normal, 4=safe mode) 42 Skin 0C ?? Should be protocol, but Logitech's SW reports 14 (0xE) for protocol; is it just using arch instead? 23 Region 0 or 1 version 2.3?? # 22 on SRW's remote; just an earlier version?? i.e. basically the same as the 880, except: * Don't know what the "0C" byte is; perhaps it is protocol and the Logitech SW is buggy and sending architecture in the HTTP commands instead. * One extra byte returned; probably safe mode FW version or something like that. The flash chip is from EON. I can't find the exact model, but this is what's printed on it, and what I could find from Googling: cFeon F16-100HIP Q93F03D 20CDA --- 32Mbit serial flash memory w/ 4KB uniform sector (0x10000 isn't 4KB; either the firmware fakes this, or there are multiple flash chips with the same ID and different sector sizes. I'd bet on the FW myself) http://www.essi.com.tw/products/products.aspx EN25F32/EN25Q32A p2009121811192.pdf I've decoded most of the information for remote_info.h. The firmware downloads are a zip containing: Data.xml: XML file listing which other files to process in which order, and the parameters for the "done" web post. Region_2.EZUpgrade: The actual FW data, in the same format as e.g. for the 880, with the exceptions: a) Doesn't include HTTP parameters since they're in Data.xml b) Includes two sets of data to write; a "static configuration" and a "firmware", the latter being the only thing we'd normally expect on other remotes. Oh, and it looks like the firmware block already has the checksum as "4847" bytes written into it unlike other remotes. Maybe that was a server-side update; I should check my 880 and see... More to come once I've hacked libconcord to do the different/new pre-/post-update commands and actually attempted some write operations. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
