RT1021 secure boot: Why do both BEE_KEY_0SEL and BEE_KEY_1SEL need to be set?

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

RT1021 secure boot: Why do both BEE_KEY_0SEL and BEE_KEY_1SEL need to be set?

647件の閲覧回数
rshipman
Contributor V

Hi,

See document: Security Reference Manual for the i.MX RT102x Processor, Rev. 0, 07/2020
Section: 3.6.2.1 Encrypted XIP on Serial NOR via FlexSPI Interface 

It says:

 "Both BEE_KEY_SEL fuses needs to be blown with valid value (2 or 3) even though one of them is not used."

Questions:

  1. Is this sentence correct?
  2. If so, what is the reason please? E.g. is it to prevent security attacks/hacks, or a silicon limitation?
  3. Can BEE_KEY_0SEL and BEE_KEY_1SEL be different?

Many thanks and kind regards,

Ronnie

ラベル(1)
0 件の賞賛
返信
1 返信

642件の閲覧回数
kerryzhou
NXP TechSupport
NXP TechSupport

Hi @rshipman ,

    About the BEE, you also can check my document:

https://community.nxp.com/t5/i-MX-RT-Knowledge-Base/RT1015-APP-BEE-encryption-operation-method/ta-p/...

  Now answer your questions:

  1. Is this sentence correct?

--Answer:No, use which engine, enable which engine.

   Eg, use Engine 0, then just burn fuse BEE_KEY_0SEL, to BEE_KEY_1SEL, leave it as default.

  As the fuse area is the special area, bit just can be modified from 0 to 1, can't write back to 0.

   2. If so, what is the reason please? E.g. is it to prevent security attacks/hacks, or a silicon limitation?   

--Answer: No, don't need to burn both when you just use one engine.

   3. Can BEE_KEY_0SEL and BEE_KEY_1SEL be different?

--Answer:  BEE_KEY_0SEL for engine0, BEE_KEY_1SEL for engine1

BEE_KEY_0SEL for engine 0

kerryzhou_0-1639024185065.png

 

BEE_KEY_1SEL for engine 1:

kerryzhou_1-1639024219854.png

 

Wish it helps you!

Best Regards,

Kerry

 

 

0 件の賞賛
返信