[LG, GM INFO3.5] lifecycle change failed from NXP closed to OEM closed.

[Jessie_Lee]

Hi @frank_zhang  and @Tia_Lan 

Customer is LG GM Info3.5 with i.MX8QXP.

LG's BSP is QNX.

LGe updated SCFW+SECO SW last year. And LGe failed lifecycle changed with this new combination with same QNX code which call SECO_FUNC_FORWARD_LIFECYCLE(0x3).

Older SCFW+ SECO version, this works well. 

Below is  SW version which have issue.

SCFW build version: 3374, SCFW commit: 06BBA0FA

SECO version: 2.3.1, commit: D7523FE8

So, Could you please help us how we could debug this issue? 

I noticed this scfw+ seco version do not have any function description for lifecycle changed part .So, we could not add any log properly.

So, could you help use to share scfw's object file which add log to see QNX SW call sc_seco_forward_lifecycle() of scfw correctly? 

BRs

jessie

[Tia_Lan]

Hi @Jessie_Lee ， as we discussed offline, please check with customer if there is any SECO events before they closing the chip, and also check the SECO events again after they try to close the chip . Thanks

[Jessie_Lee]

Hi @Tia_Lan  @frank_zhang 

Could you please help current (new )SCFW code support fuse write function as below?

This sc_fw_port.pdf from SCFW 1.2.9.  you could see Deprecated. 

If this is true, the SCFW 1.2.9 should not  have routine for sc_misc_seco_fuse_write() and also sc_misc_seco_forward_lifecycle(). 

Could you please confirm SCFW1.2.9 support sc_misc_seco_fuse_write() , sc_seco_fuse_write() ,  sc_misc_seco_forward_lifecycle(),  sc_seco_forward_lifecycle() all? 

LGe's current situation : new SCFW + misc SRK fusing fuction + misc lifecycle change trial ==> but only srk is fused but not lifecycle changed correctly. So, LGe need to confirm what API is supported for fusing srk and also change lifecycle. 

BRs

jessie

[Tia_Lan]

Hi @Jessie_Lee ,

As we discussed offline.

The  sc_misc_seco_forward_lifecycle() API should can still be used in SCFW 1.2.9, it still in SCFW source code.

Please check with customer: if they still use this API and also reboot after burning SRK, can it work?

For fuse writing, sc_seco_fuse_write() is only used for secure fuse, another API  sc_misc_otp_fuse_write() is used for SRK writing.

Best Regards,

Tia

[Richard_Kim]

Please let me correct the API as below that customer verified properly.

MISC_SECO_FUNC_FORWARD_LIFECYCLE

Same function worked well with beta SCFW(build v.2419), and it returns no error but cannot get expected "OEM closed" result when we read fuse value with SCFW v3374.

[Tia_Lan]

Hi @Jessie_Lee ， we will check it tomorrow.