HSE FW A_B SWAP dead

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

HSE FW A_B SWAP dead

2,522 Views
ovidiubriscan
Contributor IV

Hi NXP team, we have a S32K344 uC with HSE FW 0.2.40 A_B Swap installed, and SBAF 0.15.0 in place. During some time this was working fine. But now we see HSE core is dead (MU FSR is all 0s and MU is not responsive at all, we cannot read FW version of HSE). We see we the active bank is B (although nobody asked for a bank switch which is kind of weird). UTEST install pattern is already written , and flash sectors where HSE FW is installed 0x5d,4000 and 0x7d,4000 are "hidden". Any ideas to exit this dead loop are welcomed as now there is no booting into APPL on the host side as FBL is checking if HSE-B is "present and responsive". 

#HSE #crypto #ota

Thanks!,

Ovidiu

0 Kudos
Reply
3 Replies

2,401 Views
ovidiubriscan
Contributor IV

[Update]

Doing some steps to try the installation from the MU , seems that the SBAF finds a valid firmware in the passive region or backup. 

&mu0_rx_data = 0xAA55A55A
&mu0_rx_addr = 0x4038C280
&dcmrwp1 = 0x402AC400

I was able to recover the FW by writing the command to tell SBAF to recover from backup. 

0 Kudos
Reply

2,407 Views
ovidiubriscan
Contributor IV

Hi, sorry i was out the previous week. We had a debug session with NXP and basically what was seen is that seems the HSE FW is not installed anymore (somehow magically disappeared and it seems it is needed to be installed again). Unfortunately it is very hard to do some back track of what happened inside the ECU, a priori there was no erased issued. Here a snapshot of the 0x4039_C028.  

Thanks

 

0 Kudos
Reply

2,463 Views
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @ovidiubriscan 

What is the content of HSE GPR Register 3 at address 0x4039C028? It's possible that the firmware was somehow corrupted and it is erased now. See section "14.6.7 HSE Firmware Handshake" section in the HSE FW RM for more details. And then section "3.3 Installation process in AB_SWAP configuration" which explains how to install the firmware again in this situation.

Regards,
Lukas

0 Kudos
Reply