bootdelay at x-loader stage on omap4430

Hello,

You can change the delay by modifying u-boot sources.

Boot delay is defined as CONFIG_BOOTDELAY in include/configs/<your_platform>.h file (for example for OMAP44xx Blaze tablet the file you need to modify is: include/configs/omap4XXtablet.h).

Best Regards,

Yordan

Hi Yordan,

Thanks for the reply !
 but the problem is related to x-loader, can't we reduce the delay when its loading to u-boot at the initial x-loader stage only..
some 3 sec delay is given before loading the u-boot.. plz ask if u need more info/patch.

with Regards
-Kaushal

Have you done any modification to the above mentioned header file in include/configs folder in x-loader?

The official TI Android releases for Blaze & Blaze Tablet (http://omappedia.org/wiki/Android:_Working_with_pre-built_binaries) do not have any delay between x-loader & u-boot, see the output of my console:

I suggest you have a look at the x-loader sources from the link above.

Best Regards,

Yordan

Hi Yordan,

I didnt modify header file mention in include/configs folder of x-loader.. see the console logs and attached header file for my board.
7723.omap4430goldeni.h

The problem is, after printing "Texas Instruments Inc X-Loader 1.41.0-GoldenI_jb_xloader_Releas5.2-dirty (Jan 20 2014 - 19:00:53)" line, it waits for 3 Sec then print the next line.
"Starting OS Bootloader from MMC/SD1 ..." I'm booting out of SD card...
Suggest me what to change in my header file so that this initial delay could be reduced.

with regards
-Kaushal

Sorry I misunderstood your question.  I thought that there is a defined countdown between x-loader and u-boot stages.  Your header file is ok; udelay() line is commented & does not execute. 

It is normal behaviour if your console takes a couple of seconds between printing "Starting OS bootloader from .." & "U-boot 1.1.4- xxxxxx...  ". It is due to initializing stage in xloader, that is setting the initial pinmux of omap device; configuring power  requirements, etc.; You can check Section 27.2 Preinitialization in device TRM to see the whole procedure. 

You can try cutting some of the settings in x-loader stage in order to reduce this time, but I would not recommend it, since it may result in faulty MLO or problems in u-boot stage.

Best Regards,

Yordan

Hi yordan,

Thanks for the info.
but i was asking the delay between "Texas InstrumentsTexas Instruments Inc X-Loader 1.41.0-GoldenI_" & "Starting OS bootloader from ..". Can we reduce this?? In TRM sheet, nothing is mention related to this :(

regards
-kaushal

Hi,

As I said right until printing "U-boot 1.1.4- xxxxxx...  " the first stage of booting the device takes place (that is ROM Code & loading x-loader). 

After "U-boot 1.1.4- xxxxxx... "  starts loading and executing the u-boot configuration takes place (http://omappedia.org/wiki/Bootloader_Project)

To reduce time for x-loader you may try cut some of the initial configurations that are not needed, but be ware of the consequences I mentioned in my previous post. 

Best Regards,

Yordan

Hi yordan,

Thank you for all this info. that means we need not to change anything at x-loader stage.
Another thing is, it takes more than 10 sec till boot logo appears..

First thing is, we can reduce the CONFIG_BOOTDELAY.. apart from this, what else can we do to reduce the overall time ??

with regards
-Kaushal

You can try some of the techniques described in: http://processors.wiki.ti.com/index.php/Android_Boot_Time_Optimization , for optimizing your x-loader, u-boot, kernel.

However, I get similar results with the latest  TI Android release for OMAP44xx, 4AJ.2.5 (http://omappedia.org/wiki/4AJ.2.5P2_OMAP4_Jelly_Bean_Release_Notes) on my Blaze Board.

At about the 20th second from "Uncompressing Linux... done, booting the kernel.",   I get the " [   21.084594]  init: Boot Animation exit "  print on my debug console. So you are achieving good results, regarding boot time.  At about the 10th second,  printed on the console, after the uncompressing linux message I see the ANDROID boot animation.

Best Regards,

Yordan

Hi Yordan,

I'm getting the boot logo only at 10th sec, not the android display (Boot Animation Exit).
for boot animation exit, it takes around 50 sec from the starting when we turn on the power switch..
this is pathetic that's why i want to reduce the time.

with the prebuilt binaries of blaze board, it takes 3-4 sec to appear the boot logo..
i want to reduce the time delay which is around 10 sec... if we could reduce upto 6-7 sec. it would be great achieve.

after "uncompressing linux... done..... " it is ok.

regards
-Kaushal