gnupic: Re: [gnupic] How to unprotect your PIC so you can retrieve that code..
Subject:
RE: [gnupic] How to unprotect your PIC so you can retrieve that code..
From:
####@####.####
Date:
7 Aug 2008 17:06:57 -0000
Message-Id: <F92E0D9C183AAB4BBC22DB8B1716ABE4035ADD71@CHN-CL-MAIL01.mchp-main.com>
On Code Security
While no device is 100% secure, the first thing you should do to protect
your IP is program the parts yourself or work with the device
manufacturer to buy preprogrammed devices. There are many cases where a
CM was asked to program the parts as part of the manufacturing and the
CM produces a clone in the factory next door with the stolen hexfile.
This is much more common than cracking code protection.
-----Original Message-----
From: David Barnett ####@####.####
Sent: Thursday, August 07, 2008 5:26 AM
To: ####@####.####
Subject: Re: [gnupic] How to unprotect your PIC so you can retrive that
code..
On Thu, Aug 7, 2008 at 4:27 AM, Rob Pearce ####@####.####
wrote:
> I note the best justification he could come up with for a "legitimate"
> reason
> was that the company were a bunch of complete incompetents who should
be
> first against the wall when the recession comes.
Yep, I think I'd ditch the job if I ever depended on reading the
official
machine code off of the device, not to mention modifying it. Maybe
comparing
against other HEX files to find the exact rev number would be a little
better, but not a lot.
Anyway, I think he was just having a little fun rather than trying to
rescue
the incompetents, and I certainly found the technical details
interesting.
For the unobservant, the blog belongs to Andrew "bunnie" Huang, one of
the
founders of Chumby.
David
