imx6 HAB, getting invalid values from HAB API's

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

imx6 HAB, getting invalid values from HAB API's

1,087件の閲覧回数
deepakjohnpaulr
Contributor I

Hi,

I am able to boot a signed image in IMX6 DQ eval board (SCH - 26662 REV E) in Open configuration without any HAB events as well as HAB API's are returning correct status for device open configuration (0xf0 - open) and non-secure state(0x66).

When trying the same solution with a IMX6 Dual Lite board(SCH -28605 REV B) as well as IMX6 Dual Quad Plus board (SCH -28615 REV A1) in Open configuration , I am  facing below problems for both signed and unsigned image:

1. HAB API's are returning device status as invalid value  for device configuration and security status. These values do not match with the values defined in HAB Manual.

2. HAB report event is reporting continuously same event as the failure event. The header and data from this even also does not match with anything defined in the HAB Manual.

Event log :-

The Configuration of security is: 0xc0 HAB Status: 0x50

=============== HAB Event 1 ===============
HAB Audit data:
 0x00 0x80 0x0d 0x02 0x98 0x00 0x00 0x00
 0x50 0x00 0x00 0x00 0xc0 0x40 0x91 0x00
 0x00 0x80 0x0d 0x02 0x98 0x00 0x00 0x00
 0x00 0x00 0x00 0x00 0x10 0x05 0x91 0x00
 0xe1 0x40 0x91 0x00 0x2f 0x00 0x00 0x00
 0x0a 0x00 0x67 0x20 0xc8 0x7f 0x91 0x00
 0xc8 0x7f 0x91 0x00 0xb3 0xc6 0x90 0x00
 0x0a 0x2d 0x2d 0x2d 0x2d 0x3e 0x20 0x43
 0x41 0x4c 0x4c 0x45 0x44 0x20 0x42 0x69
 0x6e 0x61 0x72 0x79 0x20 0x43 0x68 0x65
 0x63 0x6b 0x20 0x3c 0x2d 0x2d 0x2d 0x2d
 0x0a 0x00 0x20 0x34 0x2e 0x30 0x20 0x73
 0x74 0x61 0x72 0x74 0x65 0x64 0x20 0x3d
 0x3d 0x3d 0x3d 0x3d 0x3d 0x3d 0x3d 0x3d
 0x3d 0x3d 0x3d 0x0a 0x0a 0x00 0x80 0x1c
 0xf7 0xf5 0x90 0x00 0xc0 0x02 0x80 0x1c

We have tried this in multiple DL and DQ plus but still facing same problem. Can you please help us in understanding why HAB is not able to even return the correct value  for device security configuration and status? Also, why this event with undefined values is getting reported continuously?

Regards,

Deepak

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

779件の閲覧回数
deepakjohnpaulr
Contributor I

Hello,

Thanks for the support! We are using a different bootloader than U-boot. However, we have now got the reason for our query. This problem is occurring because DQ Plus and DL chips which we have with us are silicon revised and hence, HAB API address have been changed. Due to improper address, it was giving invalid response.

Regards,

Deepak

0 件の賞賛
返信

779件の閲覧回数
Yuri
NXP Employee
NXP Employee

Thanks for the info !

~Yuri.

0 件の賞賛
返信

779件の閲覧回数
Yuri
NXP Employee
NXP Employee

Hello,

  Do You use recent NXP U-boot, Linux ?

Are i.MX6s (DQ, Dual Lite, Dual Quad Plus) are detected correctly in U-boot ?

 

Have a great day,

Yuri

 

------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer

button. Thank you!

0 件の賞賛
返信