| ??? 04/09/07 03:54 Read: times |
#136826 - might I suggest... Responding to: ???'s previous message |
Michael Karas said:
1) Use the protect mode features offered by the MCU that you intend to use.
good idea, but don't some controllers have an unprotect mode? 2) Include some simple things in your code that make it harder to simply blot out things like a copyright string. One example is to place a CRC-32 value into the image of the FLASH and have that be checked at bootup across the whole flash space image. Thats good as well, but it requires more time from the programmer, and the program speed might be slower because of the time it takes to decode the special data (like crc-32 values). 3) Make your products so that the MCU cannot be used without the hardware... thanks for condensing my point. My method to achieve this effect is to rip out the pins of the micro that you don't need to use in your hardware. 4) Write the code in C language. I dont think that this will help him resolve his problem. It isn't the programming language that counts, it is the location the bytes are written to in the EEPROM and the data that is being written to in the EEPROM that counts. |
