i.MX6ULL bootRom doesn't invalidate d-cache issue (ERR010449) and CAAM engine

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 
已解决

i.MX6ULL bootRom doesn't invalidate d-cache issue (ERR010449) and CAAM engine

跳至解决方案
1,266 次查看
nvbolhuis2
Contributor II

i.MX6ULL ERR010449 states that :
When authenticating image, DCP write the result HASH value of the boot image into OCRAM,
but ROM does not invalidate D-Cache when reading back the HASH. Thus getting wrong value,
and finally wrongly ‘think’ the image is invalid.

There are two workarounds:
- Disable MMU/D-Cache using in BootROM by setting Boot_Config “BT_MMU_DISABLE”, or
- Specify engine as “HAB_ENG_SW” instead of “HAB_ENG_DCP” by SCT tool. This will force HAB use the software hash engine.

We use the CAAM (HAB_ENG_CAAM) engine, in other words, the "[Header]" section of our CSF file contains:
"Engine = CAAM"

Does the issue also occur for the CAAM engine or does it *only* occur with the DCP (HAB_ENG_DCP) engine ?

0 项奖励
回复
1 解答
1,261 次查看
igorpadykov
NXP Employee
NXP Employee

Hi Norbert

 

>Does the issue also occur for the CAAM engine or does it *only* occur with the DCP (HAB_ENG_DCP) engine ?

 

it only occur with the i.MX6ULL DCP (HAB_ENG_DCP) engine.

 

Best regards
igor

在原帖中查看解决方案

0 项奖励
回复
1 回复
1,262 次查看
igorpadykov
NXP Employee
NXP Employee

Hi Norbert

 

>Does the issue also occur for the CAAM engine or does it *only* occur with the DCP (HAB_ENG_DCP) engine ?

 

it only occur with the i.MX6ULL DCP (HAB_ENG_DCP) engine.

 

Best regards
igor

0 项奖励
回复