Quantcast
Channel: Processors forum - Recent Threads
Viewing all articles
Browse latest Browse all 17527

OMAP-L138 secure AIS boot does not complete when writing to DDR

$
0
0

Hi, all.  I'm hoping for a little debugging help.  I've been caught off-guard when our production boards came back with secure boot OMAP-L138 chips on them, whereas the development boards had the non-secure boot variety.  As you might guess, the tools and images I had ready for the production boards did me no good, and now I'm having to use all new tools and develop all new boot images.

I've gotten as far as generating valid secure AIS images with whatever code I care to put in them.  I did a test where I put a DSP UBL that turns on the ARM and points it in the right direction into the AIS along with a super-minimal ARM binary that just spits stuff out the UART so I can verify it's running, and it worked.  The OMAP booted the DSP, the DSP turned on the ARM, and the ARM said Hi through the UART.  Great.  Now, bear in mind I shoehorned both of those code images into the L138's internal L2RAM.

Now I'd like to get a U-boot running on the ARM.  U-boot doesn't fit into L2RAM, so I've got it configured to load into DDR.  But anytime I execute an AIS image that has sections destined to load into DDR, it doesn't complete.  The Secure AIS loader tool stops at "Waiting for DONE", and DONE never comes.

My ini file has the following in it...

[EMIF3DDR]
PLL1CFG0 = 0x18010001
PLL1CFG1 = 0x00000002
DDRPHYC1R = 0x00000044
SDCR = 0x02034621
SDTIMR = 0x14912A09
SDTIMR2 = 0x38111120
SDRCR = 0x00000492
CLK2XSRC = 0x00000000

[PSCCONFIG]
LPSCCFG = 0x01060003


I've double-checked the mDDR timings against the part's datasheet; all the timing parameters should be good.  I'm about out of ideas.  Any pointers as to what else I should check would be greatly appreciated.  Thanks!


Viewing all articles
Browse latest Browse all 17527

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>