Address Pointers used by the Security Engineer (SEC)

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

Address Pointers used by the Security Engineer (SEC)

358件の閲覧回数
rjschirmer
Contributor I

I am using the SEC on both the lx2160a and ls1043a (and will possibly on other SoCs in the future) and noticed that the Address Pointers are different between the two.  The most significant difference is the double word ordering when using 49-bit/40-bit addressing on the lx2160a and lx1043a respectively.  The lx2160a uses most-significant Dword followed by least-significant, and the ls1043a uses least-significant Dword followed by the most-significant.  This appears to be unrelated to the endianness of the engine as defined by SSTA[PLEND].

My question is: is there a way to tell which version of address pointers is being used by a SEC?  (e.g. SEC version range for each type of address pointers)

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

320件の閲覧回数
LFGP
NXP TechSupport
NXP TechSupport

You could use the PS register to stablish the length to 32 bits.

The information regarding SEC block is provided under NDA, so, please open a new private case and share your NDA

0 件の賞賛
返信

310件の閲覧回数
rjschirmer
Contributor I

The use case requires larger than 32-bit addressing, so setting MCFGR[PS] to use 32-bit addressing will not work for me.

Per your suggestion I've opened a new private case to address this. 

0 件の賞賛
返信