AIS image size issue

Bakir

Other Parts Discussed in Thread: OMAP-L138, OMAPL138

Hi Tech-Support!

I read, that I can create combined image for OMAP-L138. This is a link: processors.wiki.ti.com/index.php/Boot_Images_for_OMAP-L138.

But when I make an image within AISgen Tool, its size is less than sum of source files. I merge ARM and DSP images in one ".ais" image. ARM image is u-boot. DSP image consist of SYS/BIOS application and about 2 MBytes.

My question: Why this happens?

FX16_Config_with_DSP.cfg

Best regards,

Bakir Khaybullin

over 9 years ago

0 Sivaraj Kuppuraj over 9 years ago

TI__Mastermind 35645 points

Hi,

We will work on it and will let you know the update shortly.

Thanks & regards,
Sivaraj K

0 Shankari G over 9 years ago

TI__Mastermind 43955 points

Hi Bakir,

Actually, when you convert a *.out file into *.ais file, the size of the binary will get reduced. Because, AIS is a format of storing the boot image.AIS is a binary language, accessed in terms of 32-bit (4-byte) words in little endian format. AIS starts with a magic word (0x41504954) and contains a series of AIS commands, which are executed by the bootloader in sequential manner. The Jump & Close (J&C) command marks the end of AIS.Each AIS command consists of an opcode, optionally followed by one or more arguments, followed byoptional data.The opcode and its arguments are each one word (4 bytes) wide. If the length of data is not a multiple of 4 bytes, it is padded with zeros to make it so.

As well the size of the *.ais file depends on the size of the binary you use.That's the reason why the size of the .ais is reduced and smaller than the *.out file.

For more details please refer to Bootloader app notes of OMAPL138: http://www.ti.com/lit/an/sprab41e/sprab41e.pdf Section 4.

Bakir said:
But when I make an image within AISgen Tool, its size is less than sum of source files. I merge ARM and DSP images in one ".ais" image. ARM image is u-boot.

I guess, something wrong here. You cannot merge u-boot + DSP app.

1. Do you want to flash and run the u-boot on the ARM core? After running the u-boot, usually people will boot the Linux and the filesystem on the ARM core.

You can flash the u-boot.ais like below:

./sfh_OMAP-L138.exe -flash_noubl u-boot.ais -targetType OMAPL138_LCDK -flashType NAND -p COM3

2. Do you want to just run the DSP app on the DSP core ?

If yes, you can flash the UBL ( boot.ais ) + DSP app ( gpioLed.bin )

$>sfh_OMAP-L138.exe -flash boot.ais gpioLed.bin -targetType OMAPL138_LCDK -flashType NAND -p COM3

3. Do you want to run the ARM app on the ARM core?

If yes, you can flash the UBL ( boot.ais ) + ARM app ( rasterDisplay.bin )

$>sfh_OMAP-L138.exe -flash boot.ais rasterDisplay.bin -targetType OMAPL138_LCDK -flashType NAND -p COM3

For more information on flashing and booting the ARM/DSP application on OMAP138LCDK, please visit :

http://processors.wiki.ti.com/index.php/OMAPL138_StarterWare_Booting_And_Flashing#How_to_flash_and_boot_the_sample_ARM_starterware_app_on_OMAPL138_LCDK_board

http://processors.wiki.ti.com/index.php/OMAPL138_StarterWare_Booting_And_Flashing#How_to_flash_and_boot_the_sample_DSP_starterware_app_on_OMAPL138_LCDK_board

0 Bakir over 9 years ago in reply to Shankari G

Intellectual 585 points

Hi Shankari!

I search the method to load DSP CCS image (file with ".out" extesion) within linux running on ARM core. I want to run DSP in parallel with ARM core loading. So, I tried to boot DSP image with u-boot simultaneously using AISgen utility. But evidently AISgen for D800K008 utility has some restriction on output file size.

I know about DSP images loading through the syslink. But this method have some difficulties to convert CCS project (output ".out" file) to syslink project. That is why I am searching some other method to load ".out" file.

Best regards,
Bakir

0 Bakir over 9 years ago in reply to Shankari G

Intellectual 585 points

Thank you very much Shankari for a such detailed answer!

I read Bootloader app notes of OMAPL138 (sprab41e.pdf). But the link processors.wiki.ti.com/.../Boot_Images_for_OMAP-L138 tells us that we can load ARM and DSP images simultaneously. So, I tried. I took u-boot (151KB) and DSP image (2.01MB). DSP image has SYS/BIOS inside. I used AISgen D800K008 that generated combined ais image with size 286KB. How it's possible?

I'm sorry for disturbing you, but you said that: "You cannot merge u-boot + DSP app. " - Why I can't do so?

Regards,
Bakir

0 Shankari G over 9 years ago in reply to Bakir

TI__Mastermind 43955 points

Hi Bakir,

Bakir said:
I'm sorry for disturbing you, but you said that: "You cannot merge u-boot + DSP app. " - Why I can't do so?

It is not that we can't do. It is just that it is not required to do. I mean to say, if you are using a bare metal DSP app, it is sufficient to use just the UBL ( not u-boot), U- user B- Boot L -Loader.

U-boot is usually used to load and boot Linux. And once the Target machine is up and running with Linux, they run ARM Application on top of Linux.

If they want to communicate with the DSP core, they will opt for SYSLINK.

For more info on SYSlink, visit

http://processors.wiki.ti.com/index.php/SysLink_Install_Guide_-_2.00_and_2.10#Running_Sample_Applications

http://processors.wiki.ti.com/index.php/SysLink_Notify_Drivers_and_Transports

http://processors.wiki.ti.com/index.php/SysLink_UserGuide#MessageQ

http://processors.wiki.ti.com/index.php/SysLink_Install_Guide#Installing_Examples