IVT tool checks for invalid values and overlapping segments and reports any found error in the Problems View.
The tool performs the following verifications:
In this case, a field value is mandatory, if it will be set to empty the tool will show this error:
ERROR: The textfield cannot be empty, please insert a value
In this case, the string contains characters that cannot be interpreted as any of the available formats ( HEX as it doesn’t start with ‘0x’ and also ‘o’ is not a valid character , DEC as both ‘f’ and ‘o’ characters are not valid ), the tool with show this error:
ERROR: Input value is invalid! The character is invalid for the considered format
The DCD pointer spans from 0x100 to 0x103 and the DCD Backup pointer from 0x101 to 0x104 so [ 0x101 – 0x103 ] segment is overlapping. The tool will show two errors, one for each segment that overlaps, so the user can edit their start address by clicking on “Show problem”. The shown errors:
ERROR: DCD segment overlaps with: DCD (backup)
ERROR: DCD (backup) segment overlaps with: DCD
After loading a file (ex. “C:\S32CT_Workspace\dcd”) modify the size that was calculated by the tool into a smaller one will result into a truncated image, so an error will be raised:
ERROR: The length of the selected binary file (40 bytes) is greater than the new IVT pointer size (30 bytes).
When increasing the size manually, the tool will instead generate a warning because, the image will still be complete, and the extra space appeared will be filled with the default reserved space value ( 0xFF ).
WARNING: The length of the selected binary file (40 bytes) is smaller than the new IVT pointer size (50 bytes).
When adding 17 (0x11) to the actual pointer 0x FF FF FF FF the end address will become 0x10 00 00 00 F, which cannot fit anymore on 32 bits. The tool will generate the error:
ERROR: The end address overflows 32-bit value.
The current processor has a reserved space between [ 0x200 – 0x3FF ]. By trying to set a pointer into that area I get errors.
The Memory Layout view will also indicate that the pointer lives in a reserved area. And the tool will raise errors for overlapping with the reserved spaces for the pointer start and end addresses (by case). In this case, both 0x210 and 0x220 are in the reserved area so the tool will generate the following errors :
ERROR: The current value is reserved.
ERROR: The current end address value is reserved.
While loading an empty file in the “Browse” section of the pointer, the tool will immediately pop this error window telling the user that the file size is 0.
In this case, the context forces me to align start addresses to multiples of 512, if I try to modify to an unaligned value the tool will show this problem:
ERROR: The address value must be aligned to 512 bytes.

In the Application bootloader sub-image editor, when trying to set the Code length above the maximum limit (16 MB or 16777216) ex. 16777224 the tool will show this error:
ERROR: The current value is out of range.