IVT Export

These options allow the user to export different images.

The currently available export options are:

• Exporting IVT Image as binary
• Exporting IVT Image as C code
• Exporting Blob Image as binary
• Exporting Application Bootloader sub-image as binary
• Exporting DDRC init app image
• Exporting Device Initialization Firmware image
• Exporting FSS Firmware image

The export options are different from the other tools like Pins, Clocks and Peripherals. The import/export options for IVT image, along with export Blob image option can be found under the Interface selection menu, while the export of Application Bootloader can be found in the sub-image menu of the Application Bootloader pointer.

1. Exporting IVT Image

   To proceed, click on export and a pop-up window will appear on screen.

   This window allows the user to choose one of the available formats and shows a preview of the data that will be exported.

   For the binary format, the export data is represented by the raw bytes of the IVT image.

   The export preview design is similar to hexdump for increased legibility.

   The sections of the exported binary image are highlighted using different colors and hovering over each byte will display the image section name that the byte is part of.

   For the C format, the exported value will be a C code that contains an array of bytes, the same bytes as in the binary format.

   This format takes advantage of the linker to export the image to the board, so it does not need to be manually flashed.

   The bytes will be separated in groups, corresponding to different components, with comment descriptions for increased legibility.

   After choosing the desired format, press "OK" to proceed.

   You will see a file chooser dialog where you can specify the name and location for the file you want to save.

2. Exporting Blob Image

   Exporting the Blob image means exporting the IVT Image as binary along with all the images of the pointers which have a valid loaded file assigned.

   Loading images to pointers example:

   Load the images you desire to export in the corresponding IVT Pointers as described below:

   • Make sure the Pointer is in “On” state, not “Reserved”, as it appears in the upper left corner of the DCD pointer. To do so, simply click on the Radio button to toggle between these states.
   • Click on the “Browse” button to load a saved DCD Image.
   • Because the “Size in bytes” may change, solve the eventual incoming problems.

   Repeat this process with as many pointers as you want.

   Finally, click on the “Export Blob Image” button to proceed. A file saving dialog will appear on the screen.

   Note: When You set multiple images to export in the blob, the memory gaps between them will automatically be filled with the default value 0xFF.

   Configuration example:

   In the configuration above (Figure: IVT configuration with loaded image files) there are 4 available (“On”) pointers: DCD, DCD (Backup), HSE and HSE (Backup) of which just two have images set : DCD and DCD (Backup).

   The exported blob image will contain the following:

   [ 0x0 – 0xFF ] : IVT Image binary

   [ 0x100 – 0x127 ] : DCD Image binary (loaded from “C:\S32CT_Workspace\dcd”)

   [ 0x128 – 0x14F ] : Empty (0xFF) as HSE and HSE Backup have no loaded images

   [ 0x150 – 0x177 ] : DCD (backup) Image binary (loaded from “C:\S32CT_Workspace\dcd”)

3. Exporting Application Bootloader sub-images

   The IVT tool has an option for exporting the Application Bootloader (and Application Bootloader backup) images.

   To work with the export option of the Application Bootloader you can either:

   • Load an existing image, the same as you would with another IVT Pointer, using the “Browse” button.

     Modify the desired fields (ex. RAM start pointer), then click “Export Image” which will bring a pop-up of a file chooser dialog.

   • Set the desired RAM start pointer, RAM entry pointer and Code length then export the image.

     After pressing the “Export Image” button, the tool will show a warning pop-up, telling you that the image that is going to be created will have no attached code, and the code segment will automatically be empty (filled with 0xFF/0x00, depending on interface selection).

   Later, you can load the exported image back using the “Browse” button.

   To export the application bootloader image in serial boot format:

   • Check "Serial Boot Image"
   • "Include Transmission Marker" option will allow you to include the marker FEED_FACE_CAFE_BEEFh on the exported image. Boot ROM polls sequentially for activity on the transmission channel until this marker is received and any incorrect data received is discarded.
   Note: Even if the "Serial Boot Image" setting is selected, the exported Blob image will not contain the application in serial boot format. The header tag of the application that is included in the Blob image is always 0xD5.
4. Export DDRC:

   The IVT tool has an option for exporting the DDRC (and DDRC backup) images.

   To work with the export option of the DDRC you can either:

   • Load an existing image, the same as you would with another IVT Pointer, using the “Browse” button.

   Modify the desired fields (ex. RAM start pointer), then click “Export Image” which will bring a pop-up of a file chooser dialog to select a location where the image will be saved.

   • Set the desired RAM start pointer, Entry/Execution pointer, Code length, BootROM Timeout for Status Polling, Pre-defined Data then export the image.

   After pressing the “Export Image” button, the tool will show a warning pop-up, telling you that the image that is going to be created will have no attached code, and the code segment will automatically be empty (filled with 0xFF/0x00, depending on interface selection).

   Later, you can load the exported image back using the “Browse” button.

5. Export Device Initialization Firmware:

   The IVT tool has an option for exporting the Device Initialization Firmware (and Device Initialization Firmware backup) images.

   To work with the export option of the Device Initialization Firmware you can either:

   • Load an existing image, the same as you would with another IVT Pointer, using the “Browse” button.

   Modify the desired fields (ex. Rollback Counter), then click “Export Image” which will bring a pop-up of a file chooser dialog to select a location where the image will be saved.

   • Set the desired RAM start pointer, Entry/Execution pointer, Code length, Rollback Counter, FRB threshold reg 0, FRB threshold reg 1, FRB threshold reg 2, Pre-defined Data then export the image.

   After pressing the “Export Image” button, the tool will show a warning pop-up, telling you that the image that is going to be created will have no attached code, and the code segment will automatically be empty (filled with 0xFF/0x00 depending on interface selection).

   Later, you can load the exported image back using the “Browse” button.

6. Export FSS Firmware:

   The IVT tool has an option for exporting the FSS Firmware (and FSS Firmware backup) images.

   FSS Firmware is required to be configured. The tool will generate an error when no file has been loaded.

   Note: Not applicable for FSS Firmware (backup). The export for FSS Firmware backup image is similar to Device Initialization Firmware image export. It allows either loading an existing image and performing fields update or setting the sub-image parameters and exporting the FSS Firmware (backup) image without any pre-loaded file.

   To work with the export option of the FSS Firmware, load an existing image, the same as you would with another IVT Pointer, using the “Browse” button.

   Modify the desired fields (ex. RAM start pointer), then click “Export Image” which will bring a pop-up of a file chooser dialog to select a location where the image will be saved.

   Later, you can load the exported image back using the “Browse” button.

   Note:FSS Firmware image can be exported in a serial boot format.

   To export the application FSS Firmware image in serial boot format:

   • Check "Serial Boot Image"
   • "Include Transmission Marker" option will allow you to include the marker FEED_FACE_CAFE_BEEFh on the exported image. Boot ROM polls sequentially for activity on the transmission channel until this marker is received and any incorrect data received is discarded.

   Even if "Serial Boot Image" setting is selected, the exported Blob image will not contain the FSS Firmware in serial boot format. The header tag of the image that is included in the Blob image is always 0xD5.

   Note:The images can be kept unmodified when exporting blob image, by using the check box “Use Unmodified Binary”. If “Use Unmodified Binary” is enabled, the sub-images fields are disabled and they cannot be modified. The loaded images will be integrated in the exported blob as they are.

   The following picture illustrates the use of “Use Unmodified Binary” in case of FSS Firmware image, but as the above note states, it is applicable for Device Initialization Firmware as well.

Also note that for some processors, for all exporting options, if the QuadSPI Serial Flash boot device type is selected, the reserved bytes in the exported image will have the value of 0xFF and for the SD boot device type, the reserved bytes will be filled with the value 0x0, while for other processors, the reserved bytes will be filled with the value 0x0 regardless of the selected boot device type.