Part Number:OMAP-L138
Hello Everyone,
In our custom board we decided to change the OMAP L138 processor into a version with secure boot support. To increase credibility, we soldered the secure OMAP into two boards.
After that, the boundary scan were performed to be sure that connections are OK. All problems are occur on both boards.
The host was connected to the target by CodeComposer 7.1.0 with the latest plugins and JTAG( Blackhawk USB560 v2 ). The following message was returned:
Error connecting to the target:
Connect to PRSC failed
Based on
e2e.ti.com/.../261612
I applicated lower JTAG frequency ( 2MHz )
based on
e2e.ti.com/.../200342
I checked if every pull down and pull up registers are set.
In the reference manual is written that JTAG in secured OMAP is locked down by default.
Q1: Should I expect some other type error message from JTAG for example that the processor is lock down by the software or some security issues?
Q2: Is any way to erase the NAND Flash memory using JTAG without connection to the target from CodeComposer ?
The next step was attempt to flash the device using UART. After setting the boot mode sequence to UART2 and connect taget, and running
SecuredHexAIS_OMAP_L138.exe I generate *.ais file. After using GenericSecureUartHost.exe I get the following message:
Read magic word 0x41504954.
Waiting for BOOTME... (power on or reset target now)
Read invalid BOOTME string.
Boot aborted.
In this stage of the project, we need to just close the JTAG connection. Of course the other security features are usefull but not necessery now.
Q3: Is any way to run the OMAP L138 E with no secure features ?
Q4: Somewhere I read that UART2's clock has to limited to 12MHz. It is true ? ( can't find the link )
Best regards.
Peter