Part Number: AM62L
Old case:https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1619993/am62l-enable-secure-boot-in-am62l
Hi,
Going back to the last thread,
I am facing an issue when writing the bin file. Please see the logs below.
NOTICE: bl1_plat_arch_setup arch setup
NOTICE: Booting Trusted Firmware
NOTICE: BL1: v2.12.0(release):11.02.08-dirty
NOTICE: BL1: Built : 19:27:42, Dec 4 2025
NOTICE: BL1: dram_class: 11
NOTICE: lpddr4: post start - PI training status=0x27c0a000
NOTICE: bl1_platform_setup DDR init done
NOTICE: k3_bl1_handoff ENTERING WFI - end of bl1
NOTICE: BL31: v2.12.0(release):11.02.08-dirty
NOTICE: BL31: Built : 19:27:42, Dec 4 2025
NOTICE: SYSFW ABI: 4.0 (firmware rev 0x000b '11.2.5-v11.02.05a (Fancy Rat)')
get_device_type a0a
ERROR: Agent 0 Protocol 0x10 Message 0x7: not supported
U-Boot SPL 2025.01-00766-g7493977a537f-dirty (Dec 03 2025 - 15:20:36 +0000)
SPL initial stack usage: 1984 bytes
Trying to boot from MMC1
ERROR: Agent 0 Protocol 0x10 Message 0x7: not supported
U-Boot 2025.01-00766-g7493977a537f-dirty (Dec 03 2025 - 15:20:36 +0000)
SoC: AM62LX SR1.1 HS-FS
Model: Texas Instruments AM62L3 Evaluation Module
DRAM: 1 GiB
ERROR: Agent 0 Protocol 0x10 Message 0x7: not supported
Core: 85 devices, 32 uclasses, devicetree: separate
MMC: mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from MMC... Reading from MMC(0)... OK
In: serial@2800000
Out: serial@2800000
Err: serial@2800000
Net: Could not get PHY for mdio@f00: addr 0
am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed
Could not get PHY for mdio@f00: addr 1
am65_cpsw_nuss_port ethernet@8000000port@2: phy_connect() failed
No ethernet found.
Hit any key to stop autoboot: 0
=>
=> mw 0x82000000 0 0x400
=> ext2load mmc 0:1 0x82000000 /root/keywrlite.bin
636 bytes read in 1 ms (621.1 KiB/s)
=> dcache flush
=> md 0x82000000
82000000: 00000001 00009045 02209012 00000100 ....E..... .....
82000010: 00000000 00000000 00000000 00004a7e ............~J..
82000020: a5a5a55a 00000000 00000000 00000000 Z...............
82000030: 00001234 a5a5a55a b002601f b7b0d97c 4...Z....`..|...
82000040: a89c7dc4 7be5aad1 a184878e 2b6b632f .}.....{..../ck+
82000050: 987d0d76 97188fa1 f2d0df60 b10c2b3e v.}.....`...>+..
82000060: c7edc70e 3dacedc6 e0efdf9b ff3fdced .......=......?.
82000070: 87ade97f 7d529551 00000000 00000000 ....Q.R}........
82000080: 00009ffc a5a5a55a b002601f b7b0d97c ....Z....`..|...
82000090: a89c7dc4 7be5aad1 a184878e 2b6b632f .}.....{..../ck+
820000a0: 987d0d76 97188fa1 f2d0df60 b10c2b3e v.}.....`...>+..
820000b0: c7edc70e 3dacedc6 e0efdf9b ff3fdced .......=......?.
820000c0: 87ade97f 7d529551 00000000 00000000 ....Q.R}........
820000d0: 00005678 a5a5a55a 00000001 00000000 xV..Z...........
820000e0: 00000000 000062c8 a5a5a55a 00000001 .....b..Z.......
820000f0: 00000000 00000000 00008bad a5a5a55a ............Z...
=> gpio set gpio@600000_72
gpio: pin gpio@600000_72 (gpio 72) value is 1
Warning: value of pin is still 0
=> fuse writebuff -y 0x82000000
Programming fuses using a structured buffer in memory starting at addr 0x82000000
NOTICE: Writebuff version info: 0x1
ERROR: Failed to get response (-19)
ERROR: Transfer send failed (-19)
ERROR: Keywriter Lite Failed: (-19)
SMC call failed: Error code -1
ERROR
=>
Thanks,
Dharmik