Forum : ARM
Original Post
| Post Information | Post |
|---|---|
|
February 15, 2010 - 11:44am
|
I was planning to use the Cortex_pgm.exe for automated flashing and discovered some issues with that. 1. Verifying the flash content against a differed hex file causes sadly a return value = 0 and no "Error" in std_out not allowing a failsafe error detection. 2. Same with blank checking. It causes no error on a flashed target (return value = 0; no "Error" in std_out). 3. And now a mean one. A verify on a not empty target against a "empty" hex file (only with EOF ":00000001FF") leads to no error and "Flash content matches file."! |
Hi,
For points 1 and 2, this is an interesting suggestion.
We will add sub-options for telling the tool to return error codes in these cases, but that will be in a future version and I cannot commit on any date. (not in the next version, as it is being validated right now and does not have the feature. you should have complained last week ;) )
In the meantime, you have to make your calling process analyze the output. The tool does not say "error", but it says "Flash content differs from file" or "Flash is NOT blank", which does allow failsafe detection.
For point 3 it is normal. The Verify operation only verifies the address ranges that are referenced in the hex file. Address not referenced in the file means "don't care", not "should be empty". This is mandatory for customers who program and verify in parts from several hex files, so this cannot change. Use blank-check. ;)
Best Regards,
Vincent
Hi,
In fact the validation has been postponed so I might be able to implement points 1 and 2 for the next release...
I'll see what I can do, but I promise nothing.
Best Regards,
Vincent
Thanks in advance!