This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VL-Q1: Sign and Encrypt app image error for HS device

Part Number: TDA4VL-Q1
Other Parts Discussed in Thread: TDA4VL

Hi expert,

      In SDK V8.05,I based on "mcusw/mcuss_demos/boot_app_mcu_rtos” to develop app application(you can verify it in TDA4VL SDK v8.04 for boot_app_mcu_rtos isn't maintained in SDK v8.05). and I referred Application Note(sprad04) to develop HS device. When I sign the app image, it shows some errors,please help to check it:

tte@p5452:/media/tda4vl/tda4vl_rtos_0805/mcusw/build$ /media/tda4vl/tda4vl_rtos_0805/pdk_j721s2_08_05_00_36/packages/ti/build/makerules/x509CertificateGen.sh -b /media/tda4vl/tda4vl_rtos_0805/mcusw/binary/can_boot_app_mcu_rtos/bin/j721s2_evm/can_boot_app_mcu_rtos_mcu1_0_release.appimage -o /media/tda4vl/tda4vl_rtos_0805/mcusw/binary/can_boot_app_mcu_rtos/bin/j721s2_evm/can_boot_app_mcu_rtos_mcu1_0_release.appimage.signed -c R5 -l 0x41C00100 -k /media/tda4vl/tda4vl_rtos_0805/pdk_j721s2_08_05_00_36/packages/ti/build/makerules/k3_dev_mpk.pem -y ENCRYPT -e ~/TIDummyKey/smek.txt -d DEBUG -j DBG_FULL_ENABLE -m SPLIT_MODE
/media/tda4vl/tda4vl_rtos_0805/mcusw/build /media/tda4vl/tda4vl_rtos_0805/mcusw/build

Debug Extension is Enabled :
SoC UID not specified for Debug Extension. Using UID 0
	UID = 0000000000000000000000000000000000000000000000000000000000000000
	DBG_TYPE = 4

Image Encryption is enabled :
Generating Random Encryption IV of 16 bytes:
Generating Random Tail String of 32 bytes:
ENC_KEY = /home/tte/TIDummyKey/smek.txt
ENC_IV  = cfe31e357a605a6e3f6ec1b44a1194b2
ENC_RS  = abcc791b4547151ad742aa1cf9131cb525ff7ea1549c99643245784809f80f85
/media/tda4vl/tda4vl_rtos_0805/mcusw/binary/can_boot_app_mcu_rtos/bin/j721s2_evm/can_boot_app_mcu_rtos_mcu1_0_release.appimage-ENC-R5
BINARY ENCRYPTION SUCCESS: Generated /media/tda4vl/tda4vl_rtos_0805/mcusw/binary/can_boot_app_mcu_rtos/bin/j721s2_evm/can_boot_app_mcu_rtos_mcu1_0_release.appimage-ENC-R5


tr: read error: Permission denied
R5 Certificate being generated :
	X509_CFG = ./x509-temp.cfg
	KEY = /media/tda4vl/tda4vl_rtos_0805/pdk_j721s2_08_05_00_36/packages/ti/build/makerules/k3_dev_mpk.pem
	BIN = /media/tda4vl/tda4vl_rtos_0805/mcusw/binary/can_boot_app_mcu_rtos/bin/j721s2_evm/can_boot_app_mcu_rtos_mcu1_0_release.appimage-ENC-R5
	CERT TYPE = R5, 1
	CORE ID = 16
	LOADADDR = 0x41c00100
	IMAGE_SIZE = 
	BOOT_OPTIONS = 2
Error Loading extension section v3_ca
140490385834432:error:0F076041:common libcrypto routines:OPENSSL_hexstr2buf:malloc failure:../crypto/o_str.c:157:
140490385834432:error:0D0B30B2:asn1 encoding routines:asn1_str2type:illegal hex:../crypto/asn1/asn1_gen.c:698:string=
140490385834432:error:22074074:X509 V3 routines:v3_generic_extension:extension value error:../crypto/x509v3/v3_conf.c:246:value=SEQUENCE:sysfw_image_integrity
cat: R5-cert.bin: No such file or directory
SUCCESS: Image /media/tda4vl/tda4vl_rtos_0805/mcusw/binary/can_boot_app_mcu_rtos/bin/j721s2_evm/can_boot_app_mcu_rtos_mcu1_0_release.appimage.signed generated. Good to boot

best regards!

wl.wang