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: > > 0000000 eeeeeeee eeeeeeee eeeeeeee eeeeeeee > 0000020 0bd912c2 48b0073c b093b382 75866920 > 0000040 423626f5 4fe972d5 ab2b4686 580a84df > 0000060 > > Would you mind doing this on 2 or 3 revs of the firmware (2.5, 2.6, 3.0)? > You can either send the binary, or the output of 'od -X' on them (that's the > above). I meant to ask before and forgot.
One question... just to be sure that we don't talk at cross-purposes. This hex is readout off the remote, right? So it doesn't matter wich firmware I use for generating the tout binary... just the current fw of the remote matters. I have flashed fw2.5, 2.6 and 3.0 with RemoteCore and after each flash I ran concordance to readout the binary. But I got every time the same hex output! No change at all, same as stated above. Does that make sense? ------------------------------------------------------------------------------ _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
