Skip to contentSkip to conversation

mxs: HAB experiments

U-Boot Florian Achleitner 2 participants 11 messages Nov 17, 2015 – Nov 26, 2015

lore
Share & tools
lore
#0 lore raw

Hi Marek,

thanks for you contributions to support mxs HAB v4 in u-boot. I'm currently experimenting with HAB on my imx28 board. I think I put everything together quite well.

But examining the HAB event log I see two successful authentications for the u-boot.bin and the IVT followed by a FAILURE with "unsupported command" in the "CSF Context". It is the same for both the SPL and the main u-boot. Did you see something similar? It suggests a wrong command in the CSF file, but I think there is not a lot that can be wrong in the CSF input file for the cst tool. But probably the cst output is different between versions? I use version BLN_CST_MAIN_02.03.00.

I use u-boot's mkimage, which can generate a signed boot stream, together with your hand-crafted IVT generator in the Makefile.

I wonder if the image size field, which is appended to IVT is critical. In 9c2c8a3 you mention that the HAB Rom accepts a not exact size field value of your SPL image layout. So it seems to be not that critical.
I found that my .sig file created by freescale's cst tool is 3372B, while yours seems to have been 3904B. Currently, I am experimenting with the image memory layout and the size field.

My CSF file is virtually identical to the example in the freescale's application notes, which uses sha256. I programmed the SRK fuses, but did not set any lock bits.
HAB is in the open configuration. The SRK seems to be ok, otherwise there would be no SUCCESS events in the log.

Did HAB work without FAILURE events for you? Did anybody else on the list see something similar? Below, you can find the HAB event log.

Thanks!
Florian

Status: Operation failed (0x33)
Config: Non-secure IC (0xf0)
State: No security state machine (0xf0)
-------- HAB Event 0 --------
event data:
db 00 10 40 f0 00 db 00
00 00 10 00 00 00 26 c0
status: HAB_STATUS_SUCCESS reason: HAB_RSN_ANY context: HAB_CTX_AUT_DAT

-------- HAB Event 1 --------
event data:
db 00 10 40 f0 00 db 00
00 00 80 00 00 00 00 40
status: HAB_STATUS_SUCCESS reason: HAB_RSN_ANY context: HAB_CTX_AUT_DAT

-------- HAB Event 2 --------
event data:
db 00 08 40 33 03 cf 00
status: HAB_STATUS_FAILURE reason: HAB_UNS_COMMAND context: HAB_CTX_CSF

-------- HAB Event 3 --------
event data:
db 00 10 40 f0 00 db 00
40 00 20 00 00 06 ef 00
status: HAB_STATUS_SUCCESS reason: HAB_RSN_ANY context: HAB_CTX_AUT_DAT

-------- HAB Event 4 --------
event data:
db 00 10 40 f0 00 db 00
40 00 10 00 00 00 00 40
status: HAB_STATUS_SUCCESS reason: HAB_RSN_ANY context: HAB_CTX_AUT_DAT

-------- HAB Event 5 --------
event data:
db 00 08 40 33 03 cf 00
status: HAB_STATUS_FAILURE reason: HAB_UNS_COMMAND context: HAB_CTX_CSF

#1 lore raw
Quoted 1 line · Florian Achleitner

Hi Marek,

Hi,

Quoted 12 lines

thanks for you contributions to support mxs HAB v4 in u-boot. I'm currently experimenting with HAB on my imx28 board. I think I put everything together quite well.

But examining the HAB event log I see two successful authentications for the u-boot.bin and the IVT followed by a FAILURE with "unsupported command" in the "CSF Context". It is the same for both the SPL and the main u-boot. Did you see something similar? It suggests a wrong command in the CSF file, but I think there is not a lot that can be wrong in the CSF input file for the cst tool. But probably the cst output is different between versions? I use version BLN_CST_MAIN_02.03.00.

Quoted 2 lines

I use u-boot's mkimage, which can generate a signed boot stream, together with your hand-crafted IVT generator in the Makefile.

Can you share your CSF files (make sure to blank out the private material) ?

Quoted 57 lines

I wonder if the image size field, which is appended to IVT is critical. In 9c2c8a3 you mention that the HAB Rom accepts a not exact size field value of your SPL image layout. So it seems to be not that critical. I found that my .sig file created by freescale's cst tool is 3372B, while yours seems to have been 3904B. Currently, I am experimenting with the image memory layout and the size field.

My CSF file is virtually identical to the example in the freescale's application notes, which uses sha256. I programmed the SRK fuses, but did not set any lock bits.
HAB is in the open configuration. The SRK seems to be ok, otherwise there would be no SUCCESS events in the log.

Did HAB work without FAILURE events for you? Did anybody else on the list see something similar? Below, you can find the HAB event log.

Thanks!
Florian

Status: Operation failed (0x33)
Config: Non-secure IC (0xf0)
State: No security state machine (0xf0)
-------- HAB Event 0 --------
event data:
db 00 10 40 f0 00 db 00
00 00 10 00 00 00 26 c0
status: HAB_STATUS_SUCCESS reason: HAB_RSN_ANY context: HAB_CTX_AUT_DAT

-------- HAB Event 1 --------
event data:
db 00 10 40 f0 00 db 00
00 00 80 00 00 00 00 40
status: HAB_STATUS_SUCCESS reason: HAB_RSN_ANY context: HAB_CTX_AUT_DAT

-------- HAB Event 2 --------
event data:
db 00 08 40 33 03 cf 00
status: HAB_STATUS_FAILURE reason: HAB_UNS_COMMAND context: HAB_CTX_CSF

-------- HAB Event 3 --------
event data:
db 00 10 40 f0 00 db 00
40 00 20 00 00 06 ef 00
status: HAB_STATUS_SUCCESS reason: HAB_RSN_ANY context: HAB_CTX_AUT_DAT

-------- HAB Event 4 --------
event data:
db 00 10 40 f0 00 db 00
40 00 10 00 00 00 00 40
status: HAB_STATUS_SUCCESS reason: HAB_RSN_ANY context: HAB_CTX_AUT_DAT

-------- HAB Event 5 --------
event data:
db 00 08 40 33 03 cf 00
status: HAB_STATUS_FAILURE reason: HAB_UNS_COMMAND context: HAB_CTX_CSF

#2 lore raw

Hi,

Quoted 23 lines · Marek Vasut
Quoted 1 line · Florian Achleitner

Hi Marek,

Hi,

Quoted 18 lines

thanks for you contributions to support mxs HAB v4 in u-boot. I'm currently
experimenting with HAB on my imx28 board. I think I put everything together
quite well.

But examining the HAB event log I see two successful authentications for the u-boot.bin and the IVT followed by a FAILURE with "unsupported command" in the "CSF Context". It is the same for both the SPL and the main u-boot. Did you see something similar? It suggests a wrong command in the CSF file, but I think there is not a lot that can be wrong in the CSF input file for the cst tool. But probably the cst output is different between versions? I use version BLN_CST_MAIN_02.03.00.

Quoted 4 lines
Quoted 2 lines

I use u-boot's mkimage, which can generate a signed boot stream, together with your hand-crafted IVT generator in the Makefile.

Can you share your CSF files (make sure to blank out the private material) ?

The CSF follows. It is the same for the spl and the main u-boot.

Anyways, I currently suspect the cst tool in its current version (2.3.1) to produce binaries that are incompatible with the mx28 HAB Rom. However, I couldn't find an older version of the cst yet, so I can't try it at the moment.

Thanks!
Florian

[Header]
Version = 4.0
Hash Algorithm = sha256
Engine Configuration = 0
Certificate Format = X509
Signature Format = CMS
Engine = DCP

[Install SRK]
File = "$SRK_1_2_table.bin"
Source index = 0

[Install CSFK]
File = "$CSF1_1_sha256_2048_65537_v3_usr_crt.pem"

[Authenticate CSF]

[Install Key]
Verification index = 0
Target index = 2
File = "$IMG1_1_sha256_2048_65537_v3_usr_crt.pem"

[Authenticate Data]
Verification index = 2

#3 lore raw
Quoted 43 lines · Florian Achleitner

Hi,

Quoted 24 lines · Marek Vasut
Quoted 1 line · Florian Achleitner

Hi Marek,

Hi,

Quoted 19 lines

thanks for you contributions to support mxs HAB v4 in u-boot. I'm currently
experimenting with HAB on my imx28 board. I think I put everything together
quite well.

But examining the HAB event log I see two successful authentications for the u-boot.bin and the IVT followed by a FAILURE with "unsupported command" in the "CSF Context". It is the same for both the SPL and the main u-boot. Did you see something similar? It suggests a wrong command in the CSF file, but I think there is not a lot that can be wrong in the CSF input file for the cst tool. But probably the cst output is different between versions? I use version BLN_CST_MAIN_02.03.00.

Quoted 5 lines
Quoted 2 lines

I use u-boot's mkimage, which can generate a signed boot stream, together with your hand-crafted IVT generator in the Makefile.

Can you share your CSF files (make sure to blank out the private material) ?

The CSF follows. It is the same for the spl and the main u-boot.

Anyways, I currently suspect the cst tool in its current version (2.3.1) to produce binaries that are incompatible with the mx28 HAB Rom. However, I couldn't find an older version of the cst yet, so I can't try it at the moment.

Thanks!
Florian

Quoted 7 lines

[Header]
Version = 4.0
Hash Algorithm = sha256
Engine Configuration = 0
Certificate Format = X509
Signature Format = CMS
Engine = DCP

I use "Engine = ANY" here, not sure if it matters.

Quoted 10 lines

[Install SRK]
File = "$SRK_1_2_table.bin"
Source index = 0

[Install CSFK]
File = "$CSF1_1_sha256_2048_65537_v3_usr_crt.pem"

[Authenticate CSF]

Quoted 7 lines

[Install Key]
Verification index = 0
Target index = 2
File = "$IMG1_1_sha256_2048_65537_v3_usr_crt.pem"

[Authenticate Data]
Verification index = 2

Here I use "Engine = DCP" (missing in your example)

I am using BLN_CST_MAIN_02.00.00 btw.

Best regards,
Marek Vasut

#4 lore raw
Quoted 9 lines · Marek Vasut
Quoted 7 lines

[Header]
Version = 4.0
Hash Algorithm = sha256
Engine Configuration = 0
Certificate Format = X509
Signature Format = CMS
Engine = DCP

I use "Engine = ANY" here, not sure if it matters.

Makes no difference.

Quoted 25 lines
Quoted 25 lines

[Install SRK]
File = "$SRK_1_2_table.bin"
Source index = 0

[Install CSFK]
File = "$CSF1_1_sha256_2048_65537_v3_usr_crt.pem"

[Authenticate CSF]

[Install Key]
Verification index = 0
Target index = 2
File = "$IMG1_1_sha256_2048_65537_v3_usr_crt.pem"

Quoted 4 lines
Quoted 2 lines

[Authenticate Data]
Verification index = 2

Here I use "Engine = DCP" (missing in your example)

Also no difference.

Quoted 2 lines

I am using BLN_CST_MAIN_02.00.00 btw.

I think I have to try this version..

Quoted 3 lines

Best regards,
Marek Vasut

Thanks!
Florian

#5 lore raw

[U-Boot] mxs: HAB: current CST broken

In reply to Marek Vasut

Hi,

for everybody's information:

Quoted 10 lines · Marek Vasut
Quoted 8 lines · Florian Achleitner

On Wednesday, November 18, 2015 09:55:12 AM Marek Vasut wrote:

[..]
Anyways, I currently suspect the cst tool in its current version (2.3.1) to
produce binaries that are incompatible with the mx28 HAB Rom. However, I couldn't find an older version of the cst yet, so I can't try it at the moment.

Quoted 3 lines

[...]

I am using BLN_CST_MAIN_02.00.00 btw.

I eventually got version BLN_CST_MAIN_02.00.00 from freescale support, and it works nicely with the i.mx28 HAB.

Thus, I'm quite sure that the current version BLN_CST_MAIN_02.03.00 is simply broken at least for i.mx28.

hth,
Florian

#6 lore raw

[U-Boot] mxs: HAB: current CST broken

Quoted 1 line · Florian Achleitner

Hi,

Hi,

Quoted 15 lines

for everybody's information:

Quoted 12 lines · Marek Vasut
Quoted 8 lines · Florian Achleitner

On Wednesday, November 18, 2015 09:55:12 AM Marek Vasut wrote:

[..]
Anyways, I currently suspect the cst tool in its current version (2.3.1) to
produce binaries that are incompatible with the mx28 HAB Rom. However, I couldn't find an older version of the cst yet, so I can't try it at the moment.

[...]

Quoted 7 lines
Quoted 1 line

I am using BLN_CST_MAIN_02.00.00 btw.

I eventually got version BLN_CST_MAIN_02.00.00 from freescale support, and it works nicely with the i.mx28 HAB.

Thus, I'm quite sure that the current version BLN_CST_MAIN_02.03.00 is simply broken at least for i.mx28.

Thanks for the heads up! Would it be possible for you to check what's the problem and submit a patch to make both versions work please?

Best regards,
Marek Vasut

#7 lore raw

[U-Boot] mxs: HAB: current CST broken

Quoted 9 lines · Marek Vasut
Quoted 1 line · Florian Achleitner

Hi,

Hi,

Quoted 4 lines

for everybody's information:

Quoted 1 line · Marek Vasut

On Wednesday, November 18, 2015 at 10:57:13 AM, Florian Achleitner

Quoted 13 lines · wrote:
Quoted 13 lines
Quoted 12 lines
Quoted 8 lines · Marek Vasut

[..]
Anyways, I currently suspect the cst tool in its current version (2.3.1) to
produce binaries that are incompatible with the mx28 HAB Rom. However, I couldn't find an older version of the cst yet, so I can't try it at the moment.

[...]

I am using BLN_CST_MAIN_02.00.00 btw.

Quoted 8 lines
Quoted 5 lines

I eventually got version BLN_CST_MAIN_02.00.00 from freescale support, and it works nicely with the i.mx28 HAB.

Thus, I'm quite sure that the current version BLN_CST_MAIN_02.03.00 is simply broken at least for i.mx28.

Thanks for the heads up! Would it be possible for you to check what's the problem and submit a patch to make both versions work please?

I guess, no. I think there is nothing to be done on u-boot's side. From the outside, the cst still looks the same, all inputs are the same. And this tool is known to be closed-source. I can only compare the output. The binary it produces differs significantly between the two versions. This must bei fixed by freescale in the cst. Their support promised to forward the issue.

Quoted 2 lines

Best regards,
Marek Vasut

Best Regards,
Florian

#8 lore raw

[U-Boot] mxs: HAB: current CST broken

Quoted 34 lines · Florian Achleitner
Quoted 9 lines · Marek Vasut
Quoted 1 line · Florian Achleitner

Hi,

Hi,

Quoted 4 lines

for everybody's information:

Quoted 1 line · Marek Vasut

On Wednesday, November 18, 2015 at 10:57:13 AM, Florian Achleitner

Quoted 13 lines · wrote:
Quoted 13 lines
Quoted 12 lines
Quoted 8 lines · Marek Vasut

[..]
Anyways, I currently suspect the cst tool in its current version (2.3.1) to
produce binaries that are incompatible with the mx28 HAB Rom. However, I couldn't find an older version of the cst yet, so I can't try it at the moment.

[...]

I am using BLN_CST_MAIN_02.00.00 btw.

Quoted 8 lines
Quoted 5 lines

I eventually got version BLN_CST_MAIN_02.00.00 from freescale support, and it works nicely with the i.mx28 HAB.

Thus, I'm quite sure that the current version BLN_CST_MAIN_02.03.00 is simply broken at least for i.mx28.

Thanks for the heads up! Would it be possible for you to check what's the problem and submit a patch to make both versions work please?

Quoted 6 lines

I guess, no. I think there is nothing to be done on u-boot's side. From the outside, the cst still looks the same, all inputs are the same. And this tool is known to be closed-source. I can only compare the output. The binary it produces differs significantly between the two versions. This must bei fixed by freescale in the cst. Their support promised to forward the issue.

Please keep an eye on them at least. Thanks!

Best regards,
Marek Vasut

#9 lore raw

[U-Boot] mxs: HAB: current CST broken

Quoted 15 lines · Marek Vasut
Quoted 6 lines · Florian Achleitner
Quoted 4 lines · Marek Vasut

[...]
Thanks for the heads up! Would it be possible for you to check what's the
problem and submit a patch to make both versions work please?

Quoted 7 lines

I guess, no. I think there is nothing to be done on u-boot's side. From the
outside, the cst still looks the same, all inputs are the same. And this tool is known to be closed-source. I can only compare the output. The binary it produces differs significantly between the two versions. This must bei fixed by freescale in the cst. Their support promised to forward the issue.

Quoted 1 line

Please keep an eye on them at least. Thanks!

I'll keep you up-to-date!
Florian

Quoted 3 lines

Best regards,
Marek Vasut

#10 lore raw

[U-Boot] mxs: HAB: current CST broken

Quoted 17 lines · Florian Achleitner
Quoted 16 lines · Marek Vasut
Quoted 14 lines · Florian Achleitner
Quoted 5 lines · Marek Vasut

[...]

Thanks for the heads up! Would it be possible for you to check what's the
problem and submit a patch to make both versions work please?

I guess, no. I think there is nothing to be done on u-boot's side. From the
outside, the cst still looks the same, all inputs are the same. And this tool is known to be closed-source. I can only compare the output. The binary it produces differs significantly between the two versions. This must bei fixed by freescale in the cst. Their support promised to forward the issue.

Quoted 3 lines
Quoted 1 line

Please keep an eye on them at least. Thanks!

I'll keep you up-to-date!

Thanks!

Best regards,
Marek Vasut