how to use FP-CLD-AWS1 in B-L4s5i-iot01 board?

[devicegate]

I am using the B-l4s5i -iot01 board to test connecting to the AWS platform. I started from FP-CLD-AWS1 packet. when I test "bootloader_stsafe" and "cloud", terminal always show as below:

"

======================================================================
= (C) COPYRIGHT 2017 STMicroelectronics =
= =
= Secure Boot and Secure Firmware Update =
======================================================================

= [SBOOT] SECURE ENGINE INITIALIZATION SUCCESSFUL
= [SBOOT] STATE: CHECK STATUS ON RESET
INFO: A Reboot has been triggered by a Hardware reset!
Consecutive Boot on error counter = 0
INFO: Last execution detected error was:No error. Success.
= [SBOOT] STATE: CHECK NEW FIRMWARE TO DOWNLOAD
= [SBOOT] STATE: CHECK KMS BLOB TO INSTALL
= [SBOOT] STATE: CHECK USER FW STATUS
= [SBOOT] LOADING CERTS FROM SECURE ENGINE
= [SBOOT] FAILED TO LOAD FW SIGNING ROOT CA CERT
= [SBOOT] Initializing x509 scheme FAILED
= [SBOOT] LOADING CERTS FROM SECURE ENGINE
= [SBOOT] ERROR CALLING C_Initialize: 401
= [SBOOT] FAILED TO OPEN PKCS11 SESSION (8161 0 0)
= [SBOOT] Initializing x509 scheme FAILED
= [SBOOT] LOADING CERTS FROM SECURE ENGINE
= [SBOOT] ERROR CALLING C_Initialize: 401
= [SBOOT] FAILED TO OPEN PKCS11 SESSION (8161 0 0)
= [SBOOT] Initializing x509 scheme FAILED
= [SBOOT] LOADING CERTS FROM SECURE ENGINE
= [SBOOT] ERROR CALLING C_Initialize: 401
= [SBOOT] FAILED TO OPEN PKCS11 SESSION (8161 0 0)
= [SBOOT] Initializing x509 scheme FAILED
Check for header at 0x080db000
Check for header at 0x080d0000
Check for header at 0x080c5000
Check for header at 0x080ba000
Check for header at 0x080af000
Check for header at 0x080a4000
Check for header at 0x08099000
Check for header at 0x0808e000
Check for header at 0x08083000
Check for header at 0x08078000
Check for header at 0x0806d000
Check for header at 0x08062000
Check for header at 0x08057000
Check for header at 0x0804c000
Check for header at 0x08041000
Check for header at 0x08036000
Header not found
No valid FW found in the active slot nor new encrypted FW found in the UserApp download area
Waiting for the local download to start...
= [SBOOT] STATE: DOWNLOAD NEW USER FIRMWARE
File> Transfer> YMODEM> Send ..................

"

Has anyone encountered this issue before? Would you mind sharing some tips?