Part Number:OMAP-L138
We are currently implementing the ARM9 side of our software based on the OMAP-L138.
We are able to pack the U-boot and Linux kernel images along with the DSP image into FLASH using the SecureHexAIS_OMAP-L138 utility.
We do this by adding the files with the @<load address> parameter.
The DSP secure FLASH bootloader successfully loads the ARM9 images into the correct DDR addresses and when the DSP starts the ARM9 core it boots correctly.
However, when we also try to place the Linux ramdisk image into the FLASH, the DSP never completes the secure boot. We see brief activity on the FLASH address lines and then nothing. We are also not able to connect to the DSP via JTAG when it is in this state.
The ramdisk is quite small (4MB), and when we use a file containing random binary data of similar or larger size (I tried up to 6MB) it does boot correctly. So it seems as if something in the ramdisk file breaks the boot. The ramdisk is compressed with GZIP.
We suspect that the SecureHexAIS_OMAP-L138 generates a corrupt programming file.
Any insight into this issue would be appreciated.