Re: Xwisp2 1.7.2 released

Hi Xiaofan,

Xiaofan Chen wrote:
> I have a question regarding the "verify" function.
> 
> I found that it does not differentiate two hex files with different user ID
> and the EEPROM. Maybe this is a bug.

I could not reproduce this behaviour. When I do a verify with a hex file 
with different contents I get a verify error report.

Your report is somewhat incomplete: did you verify with really different 
contents or did you verify with a hexfile with no ID or data memory?

The Verify function in Xwisp2 compares if memory in the target PIC 
matches the contents of the hex file. The compare is restricted to the 
range of addresses which are 'covered' by the hex file. So positions in 
memory which are not addressed in the hex file are not compared (with 
some minor excpetions). To my opinion this is OK for normal practice 
when you erase a PIC before loading a new program.

An alternative would be to read all memory regions completely and check 
if the areas not addressed in the hex file are blank. This is time 
consuming and the question is if it is an error when these areas are not 
blank.  Maybe the program writes to other memory areas or even to areas 
addressed in the hex file before you do a verify!

When you have a different view of the required verify process, feel free..

Regards, Rob.

-- 
Rob Hamerling, Vianen, NL phone +31-347-322822
homepage: http://www.robh.nl/