Hi All,
Currently I am planning to develop the flash utility develoment for OMAP processor similar to DVflasher utility for DM644x processor. (This is for some customer)
As a part of that I have developed an application on Windows PC which does transfer of Image from PC to OMAP over UART3 port during the processor boot up. I was able to download the Image over UART and this was confirmed by checking the Internal RAM (IRAM) of OMAP through CCS tool.
ROM booloader code (running on OMAP which takes care of UART3 boot up) downloads the image from PC and start storing it in IRAM with starting address as 0x40200000. RBL assumes that execution point is same as starting address and hence after the Image is downloaded, Image execution starts from 0x4020000.
In my set up I am using X-loader.bin (raw) file as an Image which gets downloaded during boot up but I do not see X-loader getting executed (Some prints appear on Console Terminal when PC is connected to OMAP over UART1/2 port). Digging deep into the X-loader code I found out that X-loader is built to execute from address 0x40200800.
I have tried modifying config.mk file present in "OMAP3EVM" of X-loader to the required address but Issue still exists
My Questions:
1. Is it possible to change the execution address of X-loader from 0x40200800 to 0x40200000? If yes How?
2. Which all files require modification?
It will be great if any one of you can give us the clue as this is bit urgent.
Thanks in advance.
Ajit