Michael Frase wrote: > 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.
Correct. > 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. Erm. Eh. > Does that make sense? It runs me out of ideas... -- Phil Dibowitz [email protected] 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 [email protected] https://lists.sourceforge.net/lists/listinfo/concordance-devel
