I have a question about the AISGen tool. I am using the version 1.9, AISgen for D800K008 Bootloader. Our chip is actuall d800k006, as found by reading memory according to section 1 of SPRAB41D, Using the OMAP-L132/L138 Bootloader. I have tried using the tool with both a binary load and an outfile load. The difference in the output seems to be whether the image is transferred all at once, or whether consecutive sections are loaded in small chunks. We have both an ARM and a DSP image. For some reason, when I load each image in a single chunk (ARM to one location, DSP to another) and jump to the ARM code using the entry point check box, the program does NOT run. If I instead use the .out file to load our DSP inage (ARM to one location, DSP to another block of consecutive locations) and jump to the ARM code using the entry point check box, the program WILL run.
The ARM and DSP both run from different sections of RAM. The binary file is generated as a post-build step using the -b option for the hex6x tool. Using a file compare tool, the same binary images are present in the .out files, and each of the AIS files. The CRC functionality was added in case the larger image was having trouble loading, but the behavior is the same without the checks; it runs if the .out is used to load small sections, and it does not run if the bin file is used. We are running out of flash, and the DSP is responsible for most of the initialization. Since it is transferred into shared RAM, I did not think this would be a problem. Again, it works if we use the .out file.
What is the difference in the AIS generated file that could cause this behavior?
I have attached the binary and out files, as well as the AIS files produced.
