Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
Question: When I try to verify the program in the already programmed PSoC devices; the Verify operation fails to verify the program. What can be the reason?
During the Verify operation, the PSoC Programmer reads the flash blocks from the target device and compares it with the hex file. This can happen only when the flash blocks are unprotected. That is why during the normal programming sequence, the verify operation occurs before the Secure operation. When you try to do a Verify operation on a programmed device, the security of the flash blocks would have been set to Read / Write Protect. Because of this the programmer will not be able to read the flash data and will produce a Verify error. If the same hex file was used to program the device, you can use the "Verify Checksum" operation instead of the "Verify" operation.