Messages

Thanks a lot for you reply Andy! Now I understand the way you work on verification and CRP. Great help! I believe a reset is needed to enable CRP (if it is enabled without reset, there is no way to verify the flash after write CRP).

By the way, I won't disturb you on the weekends anymore!

Cheers!

Flash Magic is a great tool! I've been using it for half a year and love it very much.  currently, I'm using it (command line) to program LPC2103. It always running smoothly. However, I have a few question and look forwad to a response ASAP?

1) VERIFY:
    I am using VERIFY command right after HEXFILE command. In this case, do you verify the code in RAM before it's written to Flash or read it out from Flash and compare to the data in hex file?

2) CRP:
    For code read protection, how do I know the code is read protected? If my code (hex file) already includes CRP code in 0x1FC (12345678), do I still need to set CODEREADPROCTECTION option when using Flash Magic?

3) SECURITY:
    How to use this command? I am using SECURITY comand right after VERIFY, and it shows CODEREADPROCTECTION: DISABLED. does that mean it's not CRPed or CRP code (12345678) is not in 0x1FC location? Do I need reset the chip to check the security status after flash programming and writing CRP location? Does ENABLED means CRP code is in 0x1FC or all code just cannot be read out?

Any help for these questions will be greatly appreciated!

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

Any update?

Bin

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

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!