Dear VIP expert,
I received this report issue from Elektrobit when using GrayVIP_IVT_Enablement_Blob.bin in S32N board.
GRAYVIP package: SW32N5_GRAYVIP_1_0_22_0
RTD package: SW32N_RTD_R21-11_1.8.0_CD05
Step to reproduce:
1. used CMM: "C:\NXP\SW32N5_GRAYVIP_1_0_22_0\framework\S32N5\platform\ivt\deploy\Write_IVT_Blob.cmm"
used bin: "C:\NXP\SW32N5_GRAYVIP_1_0_22_0\prebuilt\gcc\binaries\GrayVIP_IVT_Enablement_Blob.bin"
2. After flashed IVT Blob image, compile a RTD project and flash to S32N board by CMM file (example Mcu_Example_S32N55_CRS):
After SYStem.Attach, Trace32 showed core powered down:
I attached the debug folder in MCU example. They ran make run -> trigger run.cmm -> device.cmm
The line shows in image above is from device.cmm
I disscussed with RTD team, this issue can because of FSS FW didn't flashed successfully on this board, or the PMIC chip doesn't map with the GrayVIP_IVT_Enablement_Blob.bin file.
(VR55 or FS04)
Hi @RaduBraga
Is there any action from VIP team to process on this issue?
This is a blocker in integration between NXP and Elektrobit. I just want to make sure this team be noticed about the important of this ticket and provide support actively.
I get 1 more important info that Elektrobit received the S32N 5 B0 board with PMIC chip label "FS04 P0", which seems that cannot work with SW32N5_GRAYVIP_1_0_22_0\prebuilt\gcc\binaries\GrayVIP_IVT_Enablement_Blob.bin
Seems that we need to create another GrayVIP_IVT_Enablement_Blob.bin with type of PMIC as PMIC_EXTERNAL. Could you transfer this infomation to the team and provide me a new blob image for PMIC FS04 P0 please. I attached a loop mail that discuss about this topic also
Hello @cuongnguyenphu,
The team has picked up the case and will provide an answer as soon as possible.
Best regards,
Radu