Reply by glen herrmannsfeldt●February 2, 20092009-02-02
SYL <syanli@gmail.com> wrote:
> We have a design that uses C67x and a cheap MCU. The C6747 will boot
> from serial flash. What is the best strategy for doing code protection
> (protecting the code from being ripped out)? Or if the code is ripped,
> it won't run properly.
Have you looked at the DS2432?
http://www.maxim-ic.com/quick_view2.cfm/qv_pk/2914
That may or may not provide the needed protection, but
you should know about it. I believe it protects against bit
copies, but not against disassembly and reassembly of the code.
(It is used with FPGA designs, to protect against bit copies.)
-- glen
Reply by Vladimir Vassilevsky●February 2, 20092009-02-02
SYL wrote:
> Hi,
>
> We have a design that uses C67x and a cheap MCU. The C6747 will boot
> from serial flash. What is the best strategy for doing code protection
> (protecting the code from being ripped out)?
If you are asking about the STRATEGY, then the copy protection is an
administrative problem and it should be handled by managerial methods.
If you are asking about the minor technicalities, then you should use
the flash memory with the unique ID register.
Vladimir Vassilevsky
DSP and Mixed Signal Design Consultant
http://www.abvolt.com
Reply by SYL●February 2, 20092009-02-02
Hi,
We have a design that uses C67x and a cheap MCU. The C6747 will boot
from serial flash. What is the best strategy for doing code protection
(protecting the code from being ripped out)? Or if the code is ripped,
it won't run properly.
I found one interesting feature on SHARC-213xx called "ROM-based
security", which is close to what we are looking for.
Thanks a lot.