Reply by Bill Giovino August 3, 20062006-08-03
"PeteS" wrote...
> Bill Giovino wrote: > > Segments code into three protected segments. It looks like they did this
specifically to
> > meet Automotive requirements, but I see it getting a good reception over a broad
range
> > of applications. > > > > Of course, I added a pretty picture because, well, that's the kind of guy I am... > > > > http://www.microcontroller.com/news/microchip_codeguard.asp > > > > Regards, > > > > Bill Giovino > > Executive Editor > > http://Microcontroller.com > > Interesting, but hardly new. Updated to account for current needs, > though. > > Here's an interesting thought: Microchip says all the sections can be > updated using their encryption libs; when that's cracked (we know it's > only a matter of time), will Microchip then tout their new, 'more > secure' version? > > ;) > Cheers > > PeteS >
Typically, to crack things like this, there needs to be some info leaked from the inside the company, like the 68HC05 reset pin hack years ago. Other times, you've got to de-cap the part and start playing with lasers and microscopes, like Samsung used to do with National Semiconductor's GALs oh-so long ago. Nowadays, it's easy for semiconductor manufacturers to make things difficult enough so that it's financially, and legally, unfeasible to break the encryption - just look at SmartCards. Bill Giovino Executive Editor http://Microcontroller.com
Reply by Jim Granville July 28, 20062006-07-28
Bill Giovino wrote:
> Segments code into three protected segments. It looks like they did this specifically to > meet Automotive requirements, but I see it getting a good reception over a broad range > of applications. > > Of course, I added a pretty picture because, well, that's the kind of guy I am... > > http://www.microcontroller.com/news/microchip_codeguard.asp
Sounds good on first scan, but with this scheme, how do they handle version control and debug ?. Or, do those problems just quietly vanish in the Microchip world :) Starts to sounds like 'windows on a chip', with lots of scope for "not our problem, that's in the Boot Segment" - and a uC version of DLL hell, all on one die! -jg
Reply by PeteS July 28, 20062006-07-28
Bill Giovino wrote:
> Segments code into three protected segments. It looks like they did this specifically to > meet Automotive requirements, but I see it getting a good reception over a broad range > of applications. > > Of course, I added a pretty picture because, well, that's the kind of guy I am... > > http://www.microcontroller.com/news/microchip_codeguard.asp > > Regards, > > Bill Giovino > Executive Editor > http://Microcontroller.com
Interesting, but hardly new. Updated to account for current needs, though. Here's an interesting thought: Microchip says all the sections can be updated using their encryption libs; when that's cracked (we know it's only a matter of time), will Microchip then tout their new, 'more secure' version? ;) Cheers PeteS
Reply by Bill Giovino July 28, 20062006-07-28
Segments code into three protected segments. It looks like they did this specifically to
meet Automotive requirements, but I see it getting a good reception over a broad range
of applications.

Of course, I added a pretty picture because, well, that's the kind of guy I am...

http://www.microcontroller.com/news/microchip_codeguard.asp

Regards,

Bill Giovino
Executive Editor
http://Microcontroller.com