FRDM-RW612 EL2GO Provisioning Fails with STATUS_ATTR_RKTH_DEVICE_LCS_FAIL

[Rajan10]

I am working with the FRDM-RW612 board and trying to test EdgeLock 2GO provisioning using SEC Provisioning Tool v26.03 by following the procedure from AN14624 (EdgeLock 2GO Provisioning via SEC for MCUs).

I am using the following commands successfully:

1. get-secure-objects

2. prepare-device

However, during the run-provisioning step (even with --dry-run), I get the following error:

SPSDKError: SPSDK: Provisioning failed with status:
0xa50ab900 STATUS_ATTR_RKTH_DEVICE_LCS_FAIL:
Invalid OEM FW Authentication Key Hash Secure Object's device lifecycle value.

Commands used:

el2go-host.exe dev get-secure-objects -p COM24,57600 -c el2go_config.yaml --output secure_objects.bin --force

el2go-host.exe dev prepare-device -p COM24,57600 -c el2go_config.yaml --secure-objects-file secure_objects.bin -w el2go_tmp

el2go-host.exe dev run-provisioning -p COM24,57600 -c el2go_config.yaml --dry-run

The secure object being provisioned is:

"type": "OEM_FW_AUTH_KEY_HASH",
"name": "FRDM_RTKH"

Additional details:

• I do not want to permanently burn fuses at this stage.

• I only want to understand and test the provisioning flow on the FRDM-RW612.

• The board is currently accessible through ISP mode and UART communication works correctly.

• get-secure-objects and prepare-device complete successfully.

I also noticed that:

• In the SEC Provisioning Tool, there are 5 lifecycle options:

  • InField, shadow regs

  • InFieldLocked, shadow regs

  • Develop, OTP

  • InField, OTP

  • InFieldLocked, OTP

• In EdgeLock 2GO cloud, there are only 3 lifecycle options:

  • OPEN

  • CLOSED

  • CLOSED/LOCKED

I selected OPEN for all secure objects in EL2GO cloud. I also tried both OPEN and CLOSED lifecycle settings, but then I started getting correlation errors.

Currently, in SEC tool, I am using:

Develop, OTP

I would like to understand:

1. Which lifecycle state is expected for provisioning OEM_FW_AUTH_KEY_HASH on RW612?

   

2. What is the mapping between SEC tool lifecycle states and EL2GO cloud lifecycle states?

3. Is Develop, OTP expected to correspond to OPEN lifecycle in EL2GO?

4. Is there a recommended EL2GO provisioning profile for development/testing without secure boot or permanent lifecycle transition?

5. Can this error occur if the board is still in OPEN lifecycle state?

Any guidance regarding the correct provisioning flow for development boards would be very helpful.