Stephen Warren wrote:
> Now, if only I could work out what the heck the checksum algorithm is
> (watch some Logitech employee be reading this and laughing at its
> simplicity:-) I wonder how hard reverse-engineering PIC assembly is.

I had a couple of thoughts which I suspect aren't right (I haven't had time
to look into them, I'm SLAMMED, and I'm on a plane again tomorrow, sorry),
but I bring them up in hopes that maybe they'll give you other ideas that
may be less wrong. :)

   some representation of the size of the actual code (everything up until
the long block of FFs) - it's not big enough to be size, but it could be
size in certain units, or size bigger than X, or any other representation of
size
   some representation of the space between the code and the next bit of
code (there often seems to be code, then lots of FFs and then another block
of code)
   some operation of something static about that arch (like something
remote_info.h or the "cookie" or... something) against some subset of bytes
in the firmware (the first 8 bytes or something)

I suspect it's really computationally simple, but probably not very easy to
spot. I have a few other avenues to pursue as well that may help figure it out.

-- 
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


Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
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

Reply via email to