The firmware is provided in encrypted form as a binary file. Yes, HSE FW installation package contains only the binary (pink) file and corresponding API headers.
For Lauterbach users, there's also HSE DEMOAPP which helps to install the firmware and examine HSE features:
But notice that the demo works with Lauterbach debugger only. It won't work with Pemicro.
As you can read in the mentioned application note or in HSE FW RM, the firmware can be installed with or without IVT.
Installation without IVT is easier but you need a tool which is able to load raw binary file to the flash which is not the case of Pemicro debugger. In this case, "with IVT" method is more convenient.
We do not provide S32K344_HSE_FW_INSTALL for each derivative. This is just an example showing how it can be done and it's up to users to create own solution (each customer has different requirements and production tools/capabilities).
What to do:
You can create new application project directly for S32K312 in S32 Design Studio. Then copy the source files from S32K344_HSE_FW_INSTALL, update HseFwHeader_StartAddress in boot_header.c. Then modify the linker file - use linker file from S32K344_HSE_FW_INSTALL as a template. If you read the readme.md file as I suggested earlier, there must be a link to the bin/pink file, so it is linked to the project.
Then, the code will only enable HSE feature flag by programming any value different from 0xFFFFFFFFFFFFFFFF at address 0x1B000000. Then all the conditions for installation are satisfied - HSE feature flag is enabled, IVT points to valid pink image in flash, so SBAF will install the firmware after next reset.
Regards,
Lukas
Hi,
I am just following the example code given for the s32k344, so i created same project for the s32k312 and imported the binary from the linker file, i see the 0xAABBCCDD at 0x1B000000 location in memory window, what can be the problem. Every thing is same as per the example code as s32k344, only i changed the memory location in linker file. Can you please help on urgent basis, or can we connect online for debugging purpose on small call.
please find the snippet of the linker file and program.
Hi,
kindly check the image attached, the header of the AB_Swap is also there in the memory so it means the firmware is flashed in the memory, the utest area has value AABBCCDDDDCCBBAA it means utest is enabled, the HSE GPR register bit 0 is not getting set, i dont know why? it means after reset the SBAF is not installing the hse firmware in secure memory region.
kindly help on urgent basis.
I got new board right now. Here's the result of my test:
I was able to successfully install the firmware using your project. I just uncommented checking of the HSE feature flag. That was the only change I did.
After that, I could successfully erase the firmware using service HSE_SRV_ID_ERASE_FW.
I'm still not sure why it does not work on your side. Do you have more boards? Are all of them showing the same behavior?
Regards,
Lukas
This is new feature and I didn't find API for that in RTD or in HSE DEMO examples. So, I used minimalist option and I simply triggered the service via MU in debugger. Here is the description of the service from API manual:
c:\NXP\HSE_FW_S32K312_0_2_40_0\docs\S32K312_HSE_Service_API_Reference_Manual.pdf
So, the service ID is 0x57 and no parameters are needed.
Just write 0x57 somewhere to RAM and then write address of this RAM word to Message Unit MU_0, register TR[1]. That's all. Then you will see the response in RR[1]. If the HSE FW was installed, you should get HSE_SRV_RSP_OK which is value 0x55A5AA33.
Here's how it looks in my debugger:
HI Lucas,
I tried with different board with same firmware project what you shared but the result is same as earlier. Last bit of the HSE GPR register is not getting set.
Can you please try with PE Micro debugger and try to find the root cause of the problem.
We dont have lauterbach debugger here.
i am sharing the picture of the memory with different board.
