S32DS3.5 IVT Tool: Unable to generate blob image for SD

Suyeon · ‎06-13-2023

Hi,

I would like to generate the blob image for SDcard.

The problem is that IVT Tool always displays "The current value if out of range" whenever I set the start address filed in the Application bootloader section. I've tried values from 0 to 4096 and 0x1200 (After IVT image + 512 bytes alignment). All values were not accepted.

And the automatic align shows "The current automatic align start address is causing overflow. The automatic align process is not possible."

My settings are below:

- Processor: S32E270, Green Box3

- Boot target: System Manager M33

- Boot device type: SD/MMC/eMMC

- Turned off all the items in the Image Table section except the Application bootloader.

- IVT image start address 0x1000 => As I know this is fixed.

- In application bootloader section

* Start address : Any value shows "The current value is out of range" in Problem tab.

* Size in bytes: I've entered a value aligned to 8 bytes

What value should I use for the Start address of Application bootloader section.

Daniel-Aguirre · ‎06-13-2023

Hi,

S32E/Z is under control of distribution, hence specific information of regards of the platforms cannot be shared under public communities. We do apologize.

As for generic IVT tool handling, we could explain using what it is available under the S32G platform. On regards of the "Start address of Application bootloader", this should automatically be moved/changed when clicking the "Align" button under the "Automatic Align" section (where the 0x1000 value is shown). This does not need to be input manually, the tool should provide it to you.

If you require specific information on regards of the S32E/Z platforms, help us contacting your local NXP representative/FAE, for them to provide the required support.

Please, let us know.

Suyeon · ‎06-21-2023

Hi

The problem happens whenever I use S32DS3.5 with update 2.

Would you please check if IVT tool work properly with the update 2.

Thank you,

Daniel-Aguirre · ‎06-21-2023

Hi,

Thanks for your feedback.

We are using S32DS v3.5 with update 2:

We are not having the same problem you are mentioning. As said before, if this relates specific to S32Z/E, help us send this inquiry to your local NXP representative/FAE, for them to channel this information in the correct manner.

Please, let us know.