Other Parts Discussed in Thread: OMAPL138
i'm a newbie, currently i have OMAP-L138 secure boot chip, the bootmode we use is SPI, my requirement is
1. Unlock JTAG to debug the device.
2. Load custom SBL that i currently have which is working fine in the non secure version of OMAP-L138.
so far from the documents and previous discussions i read what i understood is that, to unlock JTAG the ini file should be configured as
bootExitType = NONSECURE TAPCFG= 0x0000FFFF BOOTMODE=SPIMASTER (since our boodmode is SPI) and generate ais file using SecureHexAIS_OMAP-L138.exe
i got the command to generate ais file from some of the previous discussions in the forum
SecureHexAIS_OMAP-L138.exe -ini <file name>.ini -otype binary -o <file name >.ais <file name>.out
After the ais file is created connect the UART0 to pc and write this ais file to the device using OMAP-L138 Secure UART BOOT Host Tool, and i can unlock the JTAG
The ini file that i got from forum is attached here, https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/4048.spi_5F00_test.ini
my questions are
1. The steps mentioned above is right or wrong ?
2. Does this ini file meet my requirement to unlock jtag or should i configure something else in this file ?
3. will my custom BL which runs on non secure omapl138 suit this secure boot omapl138 if not what changes i have to make it suit the secure boot device?
(if you tell me what to do exactly rather than providing some links or pdf it would be nice)