Jon Baker <jon@HAYSEED.NET> said:

> Well, I don't know what AVR chips have to offer in regards to onboard
> eeproms, but you could just hard code a counter into the chip.. so it can
> only be powered on xxx many times before it ceases to function. So each time
> it noots it reads the counter, subtracts 1 and writes it back again .. that
> kind of thing.

Code protection, counters and the like are fine if you're only providing
chips -- I think his problem is how to ensure the customer will continue to
pay if you provide source code.  I suspect it would be rare for a customer to
not want source code for a non-trivial project; it protects them from you not
being able to maintain or modify the code.

I don't have any ideas right off hand.  Wish I did.

Dale
--

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads