Zrno, If you read the original post carefully, Hua had one file "good.txt" that programmed and verified correctly, and a second file "bad.txt" the programmed but verification failed. Hua then used KDiff to show what was different between [b][i]the two files on disk[/i][/b]. This is not the same as comparing the file to the target device FLASH or FRAM contents. Programming tools that I know of don't provide straight comparison between 2 files, and your example doesn't show what he was asking about. I hope that this helps to clear up the misunderstanding on this discussion. P.S. - I suppose if your programmer let's you do a verify of target contents against any random file, you could program in one file and then ask the tool to verify against the other file. But this seems to me to be an inefficient, round-about, method. IMHO, any good programmer has a diff tool installed (and it's mandatory in any development environment where you're generating patch files), so why not use the correct tool for the job? KDiff is free after all.
↧