Hi experts :
I using RTOS SDK 7.3 and evm HS board.
Knowing that OTP keywrite version 8.0 can be well supported, so the OTP keywrite image compiled with sdk8.0 version is used。Other images, all use SDK 7.3
With ti local support, I got the two files required by OTP ti_fek_public.pem ti-fs-keywriter.bin
I have completed the burning, and the Debug response: 0x0, but according to this, it is not completely sure whether the burning is ok, please check the following log for help to confirm
The ti dummy key used for this burn。
MCU log:
OTP Keywriter Version: 02.00.00.00 (Sep 7 2022 - 20:44:30)
OTP Keywriter ver: 21.5.2--v2021.05b (Terrific Lla
OTP_VppEn
**************
Debug:func:test_pmic_appInit,line=1139, pmicConfigData->commMode = 0
***************
test_pmic_i2c_lld_intf_setup(): 493: PMIC_MAIN_INST I2C Setup...
test_pmic_i2c_lld_intf_setup(): 533: done...
**************
Debug:func:Pmic_init,line=581, regVal = 82
***************
I2C1: Passed for address 0x4c !!!
I2C1: Passed for address 0x13 !!!
**************
Debug:func:test_pmic_appInit,line=1189, pmicStatus = 0
***************
INT STAT[0]: 0x00000000
INT STAT[1]: 0x00002002
INT STAT[2]: 0x00000000
INT STAT[3]: 0x00000000
**************
Debug:func:OTP_VppEn,line=98, test_pmic_appInit status = 0
***************
Key programming sequence initialted
Taking OTP certificate from 0x41c73004
Debug response: 0x0
M3 log:
debug_response: 0x10000
0x400002
0x800004
0x4003005
0x4401552
0x40000B
0x800004
0x4003005
0x4401552
0x40000D
0x800004
0x20800000
0x20800001
0x400002
0x800004
0x4003005
0x4401552
0x409031
0x800004
#
# Decrypting extensions..
#
MPK Options: 0x0
MEK Options: 0x0
MPK Opt P1: 0x0
MPK Opt P2: 0x0
MEK Opt : 0x0
* SMPKH Part 1 BCH code: e050cadb
* SMPKH Part 2 BCH code: c099dd36
* SMPK Hash (part-1,2):
1f6002b07cd9b0b7c47d9ca8d1aae57b8e8784a12f636b2b760d7d98a18f189700
60dfd0f23e2b0cb10ec7edc7c6edac3d9bdfefe0eddc3fff7fe9ad875195527d00
* SMEK BCH code: a0c6de4e
* SMEK Hash: 92785809a3dfefea57f6bbed642d730ba5d05e601222a72e815bf01ceb3a50f96ab85d282425f684436fabd4c7da624b791da411615035314103cc64e611f532
EXT OTP extension disabled
MSV extension disabled
* KEY CNT: 01010000
* KEY REV: 01010000
SWREV extension disabled
FW CFG REV extension disabled
* KEYWR VERSION: 0x20000
#
# Programming Keys..
#
* MSV:
[u32] bch + msv: 0x0
MSV extension disabled
[u32] bch + msv: 0x0
* SWREV:
[u32] SWREV-SYSFW: 0x1
[u32] SWREV-SBL : 0x1
SWREV extension disabled
[u32] SWREV-SYSFW: 0x1
[u32] SWREV-SBL : 0x1
* FW CFG REV:
[u32] SWREV-FW-CFG-REV: 0x1
SWREV SEC BCFG extension disabled
[u32] SWREV-FW-CFG-REV: 0x1
* EXT OTP:
EXT OTP extension disabled
* BMPKH, BMEK:
BMPKH extension disabled
BMEK extension disabled
* SMPKH, SMEK:
Programmed 11/11 rows successfully
Programmed 2/2 rows successfully
Programmed 11/11 rows successfully
Programmed 2/2 rows successfully
Programmed 11/11 rows successfully
Programmed 2/2 rows successfully
* KEYCNT:
[u32] keycnt: 0x0
Programmed 2/2 rows successfully
[u32] keycnt: 0x1
* KEYREV:
[u32] keyrev: 0x0
Programmed 2/2 rows successfully
[u32] keyrev: 0x1
I'm not entirely sure the burn is ok because I'm running into a problem。
compiler sbl through make -s -j4 BOARD=j721e_evm CORE=mcu1_0 BUILD_PROFILE=release sbl_mmcsd_img_hlos_hs and copy to SD
Power on and start, sbl can start normally, but cannot load tifs.bin correctly
I tried the tifs*.bin under packages/ti/drv/sciclient/soc/V1, but it doesn't solve the problem
Generating the corresponding tifs*.bin through the script firmwareHeaderGen.sh also does not work
I can't understand very well, what kind of tifs.bin is needed(dual signed or single signed)
please give a reasonable solution,thanks a lot!