Other Parts Discussed in Thread: SYSCONFIG
Problem Description:
1. Configure bootmode pins as UART Boot Mode
2. Send tiboot3.bin (OTP keywriter bin) over xmodem protocol
3. After download is done, no any output in the UART console.
And we did the comparison test by sending the tiboot3.bin (Not the OTP keywriter, which is our normal bin file), after loading, it can load successfully, and output the expected debug info as below:
02000000011a0000616d3634780000000000000048534653000002000000020002a6000000000000b018658ad99dc903c8c9bfb27b12751099920a042ad1dfea7b7ba57369f15546de285edde6a7b39a8bdc40a27b237f8fb1e57f245e80b929c1e28b024aa2ecc6ad0bc40b000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000c47566ead6915dc71812ec6c8e3b71a9f300fc49abee32c0564ccea883c10800C
U-Boot SPL 2021.01-t3_ubuntu_v0.00.00_0-dirty (Mar 19 2024 - 11:35:54 +0000)
EEPROM not available at 80, trying to read at 81
ti_i2c_eeprom_am6_get: Invalid device info head!
Reading on-board EEPROM at 0x51 failed -22
CCCCCCCCCC
So we have tried to re-build the OTP keywriter by replacing the key/scripts with ours, not the default. The loading is still failure.
And here is my software build environment and test board information for your ref as below.
Software build environment (Installation path: ~/ti):
OTP Keywriter Packages: otp_keywriter_am64x_am243x_08.02-linux-installer.run
MCU+SDK: mcu_plus_sdk_am64x_08_06_00_43-linux-x64-installer.run
CCS: CCS12.6.0.00008_linux-x64.tar.gz
sysconfig: sysconfig-1.14.0_2667-setup.run
TI_ARM_CLANG: ti_cgt_armllvm_2.1.2.LTS_linux-x64_installer.bin
Test board: similar with am64x-evm, using our own board
The device type is HS_FS
