IVT Problems View

IVT tool checks for invalid values and overlapping segments and reports any found error in the Problems View.

Figure 1. Problems View

The tool performs the following verifications:

  • Empty value used in the start address or size text field
    Figure 2. Empty field error

    In this case, a field value is mandatory, if it will be set to empty the tool will show this error:

    ERROR: The text field cannot be empty, please insert a value

  • Invalid value used in the start address or size text field
    Figure 3. Invalid format error

    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

  • Images memory overlapping
    Figure 4. Overlapping memory pointers error highlight
    Figure 5. Overlapping memory pointers Memory Layout highlight

    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

  • Either smaller or bigger size in text field than in the actual loaded pointer image
    Figure 6. Image size greater than specified size error

    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).

    Figure 7. Image size smaller than specified size error

    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).

  • Pointer end address overflows the 32bit address range
    Figure 8. Pointer end address overflow error

    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.

  • Overlapping with reserved memory segments
    Figure 9. Reserved memory segments error pointer highlight

    The current processor has a reserved space between [ 0x200 – 0x3FF ]. By trying to set a pointer into that area I get errors.

    Figure 10. Reserved memory segments error memory layout highlight

    The Memory Layout view will also indicate that the pointer end address overlaps with the reserved segment. 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.

  • Empty image in pointer (file with size 0)

    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.

    Figure 11. Empty image loaded error pop-up
  • Address alignment constraints
    Figure 12. Alignment error highlight

    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.

  • Application bootloader code field value out of range
    Figure 13. Code length out of range error highlight

    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.

  • Advanced Life-Cycle requires HSE pointer to be configured
    Figure 14. Advanced Life-Cycle requires HSE pointer to be configured

    In case the Boot Secure Mode is enabled and the life-cycle is advanced, the HSE pointer is required. In case no binary is imported for HSE, an error will be shown and the configuration can't be exported.