PROCESSOR-SDK-AM62X: OTP keywriter error：0x42000800

Pengfei Lu

Part Number: PROCESSOR-SDK-AM62X
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

The relevant versions of my packages are as follows:
ccs1270
OpenSSL 1.1.1f 31 Mar 2020
mcu_plus_sdk_am62x_09_00_00_19
otp_keywriter_am62x_09_00_00
ti-cgt-armllvm_2.1.3.LTS
sysconfig_1.16.1

I run the following commands according to the steps in AM62X_OTP_Keywriter_User_Guide_09_00_00

./gen_keywr_cert.sh -g
cp ./keys/* ./keys_devel
./gen_keywr_cert.sh -t tifek/ti_fek_public.pem --msv 0xC0FFE -b keys_devel/bmpk.pem --bmek keys_devel/bmek.key -s keys_devel/smpk.pem --smek keys_devel/smek.key --keycnt 2 --keyrev 1
cd ../../x509cert/
python3 ../../../../../tools/bin2c/bin2c.py final_certificate.bin keycert.h KEYCERT
cd ../../am62x-sk/r5fss0-0_nortos/ti-arm-clang/
make -sj clean PROFILE=debug
make -sj PROFILE=debug

I then used dfu to burn tiboot3.bin to the board
The results are shown below

But when I switched back to emmc mode to run, I was still able to verify and start normally

My board does not have uart boot mode, so I used the following method to verify that the current state of the board is HS-SE,The otp_revsion_readSwrev function verifies that keyrev and keycount are 0.

When burned again, the following results are displayed

TISCI error results are described as follows

After that, how to burn to convert to HS-SE? Is my board no longer able to burn?

over 1 year ago

0 Prashant Shivhare over 1 year ago

TI__Guru* 77721 points

Hello,

Pengfei Lu said:
./gen_keywr_cert.sh -t tifek/ti_fek_public.pem --msv 0xC0FFE -b keys_devel/bmpk.pem --bmek keys_devel/bmek.key -s keys_devel/smpk.pem --smek keys_devel/smek.key --keycnt 2 --keyrev 1

With this command, the SoC should have converted to HSSE successfully when the keywriter tiboot3.bin even reported SUCCESS. Probably you didn't boot the correct tiboot3.bin which contains the certificate generated by above command or something went wrong while programming keys.

I would like to know if you collected the TIFS logs?

If you did not, could you run the keywriter even if it is reporting failure (0x42000800) and collect the TIFS logs?

Regards,

Prashant

0 Pengfei Lu over 1 year ago in reply to Prashant Shivhare

Prodigy 120 points

Hello,

Currently, I can only see R5 Logs. How should I view M4 Logs? My board does not have Uart Boot

I need to use the incremental Programming to operate once?

0 Prashant Shivhare over 1 year ago in reply to Pengfei Lu

TI__Guru* 77721 points

Hello,

Pengfei Lu said:
Currently, I can only see R5 Logs. How should I view M4 Logs?

The M4 logs are dumped on the MAIN_UART1 port. You should connect to all UART ports associated with your board and should see R5 and M4 logs on separate ports.

Regards,

Prashant

+1 Pengfei Lu over 1 year ago in reply to Prashant Shivhare

Prodigy 120 points

I successfully converted from FS to SE state using the following command:
./gen_keywr_cert.sh -t tifek/ti_fek_public.pem -b keys_devel/bmpk.pem -b-ovrd --bmek keys_devel/bmek.key --bmek-ovrd -s keys_devel/smpk.pem -s-ovrd --smek keys_devel/smek.key --smek-ovrd --keycnt 2 --keyrev 1

However, when I recompiled and burned using dfu after replacing my keys at uboot/board/ti/keys, I found that the burn did not execute

These files are placed under the dfu_flash_tool file, 'tiboot3-am62x-hs-evm.bin' is also changed to 'tiboot3.bin', and SMPKH is the same as burned in

0 Prashant Shivhare over 1 year ago in reply to Pengfei Lu

TI__Guru* 77721 points

Pengfei Lu said:
These files are placed under the dfu_flash_tool file, 'tiboot3-am62x-hs-evm.bin'

What is this flashing tool? Could you share the corresponding flashing logs?

0 Pengfei Lu over 1 year ago in reply to Prashant Shivhare

Prodigy 120 points

dfu-util 0.11-dev

0 Prashant Shivhare over 1 year ago in reply to Pengfei Lu

TI__Guru* 77721 points

Do you not see any UART logs?

Please note, the R5 SPL (tiboot3.bin) must be built with USB DFU defconfig for booting over DFU.

diff --git a/Rules.make b/Rules.make
index 8aeeef4..d2be40c 100644
--- a/Rules.make
+++ b/Rules.make
@@ -60,7 +60,7 @@ export CC=$(CROSS_COMPILE)gcc --sysroot=$(SDK_PATH_TARGET)
 
 # u-boot machine configs for A53 and R5
 UBOOT_MACHINE=am62x_evm_a53_defconfig
-UBOOT_MACHINE_R5=am62x_evm_r5_defconfig
+UBOOT_MACHINE_R5=am62x_evm_r5_usbdfu_defconfig
 MKIMAGE_DTB_FILE=a53/arch/arm/dts/k3-am625-sk.dtb
 
 # Update platform, defconfig if PLATFORM=am62xx-lp-evm

If you have not done this already then this will explain the reason of failure.

0 Pengfei Lu over 1 year ago in reply to Prashant Shivhare

Prodigy 120 points

Can you tell us under which configuration file UBOOT_MACHINE_R5 is changed

0 Prashant Shivhare over 1 year ago in reply to Pengfei Lu

TI__Guru* 77721 points

It's in Rules.make file. This file can be found at the root directory of your Processor SDK installation.

❯ pwd
/home/p-shivhare/ti/psdk/am62x/09.02.01.10
❯ /usr/bin/ls -l Rules.make
-rw-r--r-- 1 p-shivhare p-shivhare 3168 Jul 16 16:10 Rules.make

0 Pengfei Lu over 1 year ago in reply to Prashant Shivhare

Prodigy 120 points

This is the log message from the previous burn

Then I changed UBOOT_MACHINE_R5 according to your instructions, but when setting the environment variable, I got the following error

0 Prashant Shivhare over 1 year ago in reply to Pengfei Lu

TI__Guru* 77721 points

Why are you sourcing the Rules.make file?

The Rules.make file is included in the necessary makefiles and so you only need to update the UBOOT_MACHINE_R5 value and then follow the usual procedure of building the U-Boot.

More specifically,