I installed HSE_FW_ABSWAP_2.40, and so far I managed to use to services such as random number generation, signature verify; but for some reasons, when I try to read the status register I get only 0s in FSR which is not normal since if it was actually the case I should not even be able to use HSE services.
I don't know what is causing this.
Thank you,
Regards
Ok, I saw MU_1 in your screenshot, so it looked like this is the problem...
In this case, there's obviously something wrong. If you can still use HSE services regardless of the FSR, I would try to erase the firmware by HSE_SRV_ID_ERASE_FW service and then install the firmware again. Because it works as expected on my side, I do not have other ideas right now.
Regards,
Lukas
Hello,
Thank you for you response,
To be honest it does not solve my problem because what is strange is that I am actually using MU0 and not MU1 and I still don't read properly , so it seems like I have some kind of bug.
here SEC_MU0_INSTANCE is 0.
Still thank you for the valuables informations you brought.
Best Regards
Finally I got the board.
The thing is that the status flags (bits 16-31) are visible only in MU0, not in MU1.
Till now, I expected that the status bits are mirrored to all MU instances used for communication with HSE because there's a note in HSE FW RM:
But it's obviously not correct. I will report it. Thanks for pointing this out.
According to this table, MU0 and MU1 are always used for HSE:
So, if you check FSR in MU0, you should see:
For others - I checked this also on S32K344 and S32K312 and it's obviously the same on all S32K3 devices.
So, when checking status of HSE at the beginning of your application, use MU0:
Regards,
Lukas
I'm sorry for delay, I'm not able to check it this week. I should get the board next Monday.
yes, I agree, FSR should not be zero if HSE firmware is installed.
I do not have working S32K358 board here right now but if you can wait, I should get one on Monday. I always saw expected content in FSR on other S32K3 devices, so let me check if I can see the same.
Regards,
Lukas