Phil Dibowitz wrote: > Stephen Warren wrote: >> On Wed, March 12, 2008 1:35 am, Phil Dibowitz wrote: >>> All it takes is updating the first 6 bytes. If I take a >>> file from the website, update the first 6 bytes with the >>> first 6 bytes of my firmware and then use it to update my >>> remote, it works like a charm. >> Are you sure those values are always constant? I.e. how do we know that >> one/more of the bytes isn't some kind of firmware-data-specific check-sum >> that'll need to be different for future firmware releases? > > BTW - have you tried updating your firmware with the latest CVS? Does it > work for you now (minus the talking to the website bit)?
I just tried it. The update still fails in the same way. Reading back the firmware with -f doesn't look anything like the firmware file I asked it to program (although the first 6 bytes do look like they got copied from the original flash content). I guess I'll reflash with Windows, and add those debug statements you sent before, and some extra stuff to read-back the "staging" area in flash to check whether my writes to flash are working in the first place, or what's going on. I'll see if I can compare the firmware EZHex file with the Windows USB capture byte for byte too. I won't have time to do this today though. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
