S32G3使用A核访问HSE实现CMAC更新

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

S32G3使用A核访问HSE实现CMAC更新

Jump to solution
279 Views
RoseRice
Contributor II

SOC型号:S32G399A,RTD版本4.0.2,HSE版本:0.2.22.0

您好:
  我们已经在M核的Bootloader中实现了安全启动(安全启动的CMAC值存放在QSpiFlash的指定地址)。现在有一个需求是要通过A核去更新M核中的程序,我想知道的是A核可以访问HSE吗?以及能不能通过A核更新安全启动的CMAC值?A核和M核都访问HSE会不会产生冲突?

Tags (4)
0 Kudos
Reply
1 Solution
228 Views
chenyin_h
NXP Employee
NXP Employee

Hello, @RoseRice 

您好,一般而言,A核和M核会通过不同的MU访问HSE,不会有冲突。

您可以尝试使用libhse/libpkcs 等库在A核端访问HSE, 然后写入QSPI相应位置来尝试实现相应功能

 

BR

Chenyin

View solution in original post

0 Kudos
Reply
1 Reply
229 Views
chenyin_h
NXP Employee
NXP Employee

Hello, @RoseRice 

您好,一般而言,A核和M核会通过不同的MU访问HSE,不会有冲突。

您可以尝试使用libhse/libpkcs 等库在A核端访问HSE, 然后写入QSPI相应位置来尝试实现相应功能

 

BR

Chenyin

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2347916%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3ES32G3%20uses%20A-core%20access%20to%20HSE%20for%20CMAC%20updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2347916%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3ESOC%20model%3A%20S32G399A%2C%20RTD%20version%204.0.2%2C%20HSE%20version%3A%200.2.22.0%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EHello%3A%3CSPAN%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%20%20We%20have%20implemented%20secure%20boot%20in%20Bootloader%20of%20M%20core%20(CMAC%20value%20for%20secure%20boot%20is%20stored%20in%20specified%20address%20in%20QSpiFlash).%20Now%20we%20have%20a%20requirement%20to%20update%20the%20program%20in%20the%20M-core%20via%20the%20A-core%2C%20what%20I%20want%20to%20know%20is%20can%20the%20A-core%20access%20the%20HSE%3F%20I%20would%20like%20to%20know%20if%20the%20A-core%20can%20access%20the%20HSE%20and%20update%20the%20CMAC%20value%20of%20the%20secure%20boot%20via%20the%20A-core%2C%20and%20if%20there%20is%20any%20conflict%20if%20both%20the%20A-core%20and%20the%20M-core%20access%20the%20HSE%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2348921%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32G3%E4%BD%BF%E7%94%A8A%E6%A0%B8%E8%AE%BF%E9%97%AEHSE%E5%AE%9E%E7%8E%B0CMAC%E6%9B%B4%E6%96%B0%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2348921%22%20slang%3D%22zh-CN%22%20mode%3D%22CREATE%22%3E%3CP%3EHello%2C%20%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F225992%22%20target%3D%22_blank%22%3E%40RoseRice%3C%2FA%3E%20%3C%2FP%3E%0A%3CP%3EHi%2C%20in%20general%2C%20the%20A-core%20and%20M-core%20will%20access%20the%20HSE%20through%20different%20MUs%20and%20there%20will%20be%20no%20conflict.%3C%2FP%3E%0A%3CP%3EYou%20can%20try%20to%20use%20libhse%2Flibpkcs%20libraries%20to%20access%20the%20HSE%20on%20the%20A-core%20side%2C%20and%20then%20write%20to%20the%20appropriate%20QSPI%20location%20to%20try%20to%20implement%20the%20function.%3C%2FP%3E%0A%3CBR%20%2F%3E%0A%3CP%3EBR%3C%2FP%3E%0A%3CP%3EChenyin%3C%2FP%3E%3C%2FLINGO-BODY%3E