This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

application image generation for use with a UBL secondary bootloader on C674x device

Other Parts Discussed in Thread: TMS320C6747, OMAP-L137

Hi,

I am using the flashandbootutils 2.15 / CCS3.3 / CGT 6.1.18 / Cygwin / DSP/BIOS5.41/ NDK2.0

Our board is very close to OMAP_L137 EVM

I patched the UBL NOR to manage  a 32MB NOR flash  with a TMS320C6747 device using extended address GPIO.

I use sfh_omap-l137 to put the UBL and a binary application that uses DSP/BIOS / NDK.

I put most of the GEL file init in the ais config file to generate the UBL_NOR_C6747.bin file which boot fines.

I used the HexAis program to encode the application eth1.out into eth1.bin.

Serial Flasher tools put the UBL and the App in the flash device correctly.

UBL starts on powerup and loads the app in SDRAM but the app doesn't start cause the app binary image I am using is , my understanding, improper.

C6747 initialization passed!
Booting TI User Boot Loader
 UBL Version: 1.65 patched by MS
 UBL Flashtype: NOR
Starting NOR Copy...
CFI Query...passed.
NOR Initialization:
 Command Set: AMD
 Manufacturer: AMD
 Size: 0x00000020 MB
Valid magicnum, 0xA1ACED00, found..
   DONE
Jumping to entry point at 0xC00D7D40.

But at 0xc00d7d40 there is the Nor header with AIS sections, not the instructions entry point !!! 

Using the debug mode, I can see that the UBL find the application and copy everything to SDRAM. But it seems the entrypoint is not handled automaticaly.

I read a lot of wiki and application notes but i certainly missed something somewhere...

Can someone explain me step by step how to generate a binary file that can be used by the secondary bootloader UBL to boot a big app from a parallel flash ?

Best regards,

Frederic