Hi Team ,
as mentioned in otp_keywriter_am263px_SR_10_10_01_00_00 I have followed below steps:
Step1 : started generating keys , keys generation successfully completed .
Step2 : Certificate generated.
Step3 : Inorder to bulid application we run clean command as mentioned and then run make command inorder to generate .tiimage .
First time it shown some error , again without cleaning we tried running the same commnad now .tiimage is generated .
Query : Why there is need of entering command 2 times .
Step4: UART MODE :
We tried running generated .tiimage in UART mode , we entered command as per the document . After cleaning and running it is now priniting nothing like hash values etc.,
In general as per the document it will print some commands in dry run mode .
Query : What is the issue for not printing anything in dry run mode.
UART MODE with TERA TERM :
we have used tera term application inorder to send file as mentioned in the document , video of this attached below .
Query : After transfering file by selecting XMODEM it is not showing any transfer indication.
Step 5 : Dev BOOT MODE : Since UART MODE NOT SUCCEDED we tried of running in Dev BOOT MODE.
we created .ccxml file and then launch configurations done , and then we made changes in the load_sbl.js file as mentioned in the document , now we entered command in scripting console . After running it . it is automatically running the sbl_keywriter firmware . and also it not printing SUCCESS in the console .
Query : In console only starting bootloader is printed , and also code started running automatically after doing above steps . when clicked on pause , it is routing to HSM Clients reated .c file.
tidrive.ext.ti.com/.../
