S32K314 HSM key import failed

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

S32K314 HSM key import failed

2,083件の閲覧回数
zmx
Contributor I

Hi NXP HSM Team:

    when i use S32Ds running and download  soft to import key,in my appcode,i can use key normally,

but when i use jflash download hex to mcu to import key ,it marked key empty,I wonder what the difference is between the two,The firmware version I am using is s32k3x4_hse_fw_0.5.0_2.1.0_pb220625.bin.pink

zmx_0-1715740914666.pngzmx_0-1715740914666.png

 

0 件の賞賛
返信
3 返答(返信)

2,048件の閲覧回数
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi @zmx 
first, I would check if the flash content is exactly the same when the application is loaded by S32DS and by jflash.
When an application is loaded and started by S32DS, the debugger initializes whole RAM and sets the program counter manually at the entry point. If there's some problem with RAM initialization or with reset vector, it's possible that it won't work without the debugger.
To check what happend in the code, you can attach a debugger without reset like described here:
https://community.nxp.com/t5/S32-Design-Studio/How-attach-to-running-program/m-p/1030376/highlight/t...
This should help to find the root cause.
Regards,
Lukas

0 件の賞賛
返信

1,976件の閲覧回数
zmx
Contributor I
   The First,I will burn the program through the PE ,through JFLASH read back and then compare with hex, the result is the same

   The Second,use jflash download the hex ,then use attach to Running target can find,when i import key ,HSE respond success,but running appcode still show the key is empty  

   
0 件の賞賛
返信

1,937件の閲覧回数
lukaszadrapa
NXP TechSupport
NXP TechSupport

I'm not really sure what happened. What about this - could you modify the configuration (hex file) a little bit and use the key right after import? Does it work in this case (I mean in this configuration project and also later in application)?

0 件の賞賛
返信