LAUNCHXL-CC3235SF: Error while flashing OTP file: Operation Failed: (83, 'FS_COMMAND_RET_FAIL_OTP_CONFIRM_SIGNATURE_ERROR)

i’m not sure (never saw this error) but probably the OTP info that you signed is the problem.

if the OTP section was not previously written (which can cause issues), then make sure you are following the instructions precisely (including the self signed key pair).

I have used commands as below:

For vendor catalog generation:

SLImageCreator.exe tools make_cert_catalog --cert_folder "D:\Design\Software\Wifi\Security\Certificates" --out_file "D:\Design\Software\Wifi\Security\Certificates\certificate_Catalog.lst"

Signing vendor catalog with private key. This private key is generated using openssl.

openssl genrsa -out vendor_key.key 1024

vendor_key.key file renamed to vendor_key.pem

BINARY_SHA2 option is used in below command as our module is CC3235SF.

SLImageCreator.exe tools sign --file "D:\Design\Software\Wifi\Security\Certificates\certificate_Catalog.lst" --priv "D:\Design\Software\Wifi\Security\Certificates\vendor_key.pem" --out_file "D:\Design\Software\Wifi\Security\Certificates\certificate_Catalog.lst.signed.bin" --fmt "BINARY_SHA2"

OTP creation:

Meta data generation:

SLImageCreator.exe tools meta --cert "D:\Design\Software\Wifi\Security\Certificates\vendorRootCA.pem" --out_file "D:\Design\Software\Wifi\Security\Certificates\OTP\vendor_otp.meta" --mac "000000000000"

Signing meta data using the same private key which was used above to sign catalog file. Is this correct?

SLImageCreator.exe tools sign --file "D:\Design\Software\Wifi\Security\Certificates\OTP\vendor_otp.meta" --priv "D:\Design\Software\Wifi\Security\Certificates\vendor_key.pem" --out_file "D:\Design\Software\Wifi\Security\Certificates\OTP\vendor_otp.meta.sig" --fmt "BINARY_SHA2"

Generating inf file:

SLImageCreator.exe tools inf --algo 2 --sign1 "D:\Design\Software\Wifi\Security\Certificates\OTP\vendor_otp.meta.sig" --meta "D:\Design\Software\Wifi\Security\Certificates\OTP\vendor_otp.meta" --out_file "D:\Design\Software\Wifi\Security\Certificates\OTP\vendor_otp.inf"

Flashing OTP file through Uniflash

Certificate files in user files folder. Please check the options selected in below image. Are they correct?

Please let me know if you see any errors in above procedure.

how did you create the vendorRootCA.pem? 

It seems that this doesn't work with the OTP metadata signature signed by vendor_key.pem

I referred below threads having similar problems and regenerated all certs.

https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1080045/cc3220sf-uniflash-error-while-flashing-mcu-image-with-root-certificate-catalog

https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/766413/cc3220sf-launchxl-custom-certificates-custom-vendor-catalog-generation-fs_wrong_signature

After regeneration of certificates files, catalog file and OTP files, now I am getting below error:

I am not using any authentication for mcuflashimg.bin. I hope it is ok.

I have included following files in user files folder which are used for creating catalog file.

Can you please suggest possible issues?

the MCU image (mcuflashimg.bin) must be secure (it must be authenticated)!

Please add it with "Select MCU image" so it will include the right configuration.

ok..I will try this. In between, I was referring the link below and there was mention of OTP being blocked during flashing even though it gave error at the end. In my case, how do i know, if OTP of my board is not locked?

https://e2e.ti.com/support/wireless-connectivity/wi-fi-group/wifi/f/wi-fi-forum/1160199/launchxl-cc3235sf-errors-while-programming-the-otp-in-dev-mode

Uniflash should give you a related error message.