Tool/software:
Hi,
I'm currently using yocto krikstone for development and also i converted a device EVK(am62b-p1) to HS-SE ,By using keys from am62x/keys_devel folder.
Q1. Then I didn't change anything in my yocto build and flashed tiboot3-am62x-hs-evm.bin,tispl.bin,u-boot.img then successfully booted till uboot why ? is the development .pem are same ?
Q2. In my yocto build path u-boot-ti-staging/1_2023.04+gitAUTOINC+8366064208-r0/git/board/ti/keys/ there are
1. custMpk.crt
2. custMpk.key
3. custMpk.pem
4.ti-degenerate-key.pem
What is the purpose of each, which should i replace from key writer , (smek,smpk )? which would compare with OTP /? ,
Q3, I didn't sign my FitImage ,but it also booted till linux in HS-SE why ?
already gone through several documents , can point out exactly !
attaching boot logs below
U-Boot SPL 2023.04-ti-g836606420854 (May 09 2024 - 05:42:45 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.8--v09.02.08 (Kool Koala)')
SPL initial stack usage: 13408 bytes
Trying to boot from DFU
##########################################################DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 10 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...
NOTICE: BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE: BL31: Built : 16:09:05, Feb 9 2024
U-Boot SPL 2023.04-ti-g836606420854 (May 09 2024 - 05:42:45 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.8--v09.02.08 (Kool Koala)')
SPL initial stack usage: 1856 bytes
MMC: no card present
** Bad device specification mmc 1 **
Couldn't find partition mmc 1:1
Error: could not access storage.
Trying to boot from DFU
####DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed
U-Boot 2023.04-ti-g836606420854 (May 09 2024 - 05:42:45 +0000)
SoC: AM62X SR1.0 HS-SE
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Board: AM62B-SKEVM-P1 rev A
DRAM: no bloblist found!2 GiB
Core: 72 devices, 32 uclasses, devicetree: separate
MMC: mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In: serial
Out: serial
Err: serial
Net: eth0: ethernet@8000000port@1
Hit any key to stop autoboot: 0
------------------------------------
=> bootm 0x90000000
## Loading kernel from FIT Image at 90000000 ...
Using 'conf-ti_k3-am625-XXX.dtb' configuration
Verifying Hash Integrity ... sha512,rsa4096:custMpk+ OK
Trying 'kernel-1' kernel subimage
Description: Linux kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x900000f4
Data Size: 8246853 Bytes = 7.9 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x81000000
Entry Point: 0x81000000
Hash algo: sha512
Hash value: 1b42c827f92afac2653db3a482937882904f2c2daceab0f3bc6215f89f22395939a98442e560403acf43a915311552a8c78fdb2182e65993234c2a54ef8209db
Verifying Hash Integrity ... sha512+ OK
## Loading ramdisk from FIT Image at 90000000 ...
Using 'conf-ti_k3-am625-XXX.dtb' configuration
Verifying Hash Integrity ... sha512,rsa4096:custMpk+ OK
Trying 'ramdisk-1' ramdisk subimage
Description: artemis-image-dev
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x907ec444
Data Size: 19734856 Bytes = 18.8 MiB
Architecture: AArch64
OS: Linux
Load Address: 0x84000000
Entry Point: 0x84000000
Hash algo: sha512
Hash value: be307e738f462572b9cb84044113a30d0281eb550b17c7cf7163f353f4651f671c2057cf819ed53b72e76682d1d440942316d81489de72f04ec097b32a5d10b4
Verifying Hash Integrity ... sha512+ OK
Loading ramdisk from 0x907ec444 to 0x84000000
## Loading fdt from FIT Image at 90000000 ...
Using 'conf-ti_k3-am625-XXX.dtb' configuration
Verifying Hash Integrity ... sha512,rsa4096:custMpk+ OK
Trying 'fdt-ti_k3-am625-XXX.dtb' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x907dd870
Data Size: 60118 Bytes = 58.7 KiB
Architecture: AArch64
Load Address: 0x83000000
Hash algo: sha512
Hash value: 7bf126eefc13ccad05daf33f6e7554653e8ffab051a1baf70219f9a339d9ae0d6718cc6a660d991f83ffa6b3046cad148b7a08a7f05a18312518988170e36fe6
Verifying Hash Integrity ... sha512+ OK
Loading fdt from 0x907dd870 to 0x83000000
Booting using the fdt blob at 0x83000000
Working FDT set to 83000000
Uncompressing Kernel Image
Loading Ramdisk to 8ed2d000, end 8ffff148 ... OK
Loading Device Tree to 000000008ed1b000, end 000000008ed2cad5 ... OK
Working FDT set to 8ed1b000
Starting kernel ...
Regards,
-RJ
