LPC2103 code read protection

[bfang]

Would you please help me out with this issue ASAP?
After selecting "set code read prot" while programming LPC2103, the result turns to be different. The output of P12 shows waveform distortion after filtering. I wonder setting this option has anything to do with the function of program except read protection. If I didn't select this option, the waveform would have no distortion.

Would you please tell me there is any connection between the code read protection option and the software functions?

Looking forward to any quick reply! Urgent!

Any info will be appreciated!

[Andy Ayre]

Code Read Protection on the LPC2xxx is implemented by storing a specific value at a specific memory location. If your firmware also uses those locations then it will be corrupted.

See the user manual for the LPC2xxx for more details.

[bfang]

Thanks for your quick reply Andy!

Is there any other possible reason for this? Because it is not corrupted obviously and other functions are working properly.

Another question is for the checksum byte (0x0000014). Flash Magic  must have programmed it with the 2

[bfang]

Any update?

Bin

[Andy Ayre]

I'm not sure of another cause for code read protection to alter the execution of your firmware.

Flash Magic does program the checksum bytes starting at location 00000014H, otherwise it would be a bit of a pain to get your code to execute.

Also note that if code read protection is enabled, verify will still work. The verify skips the code read protection locations if all four locations match the code read protection value.

[bfang]

Great response Andy!

Yes, we are tracing the overlap on code read protection location. And, I don't need to worry about the checksum bytes now.

In addition, the updated Flash Magic is way faster than before when verifying the written code. Thanks for your great work!

Bin