[U-Boot] Dynamically define which Kernel image to boot during SPL execution - U-Boot - denx.biz

newer
[U-Boot] [PATCH] ARM: arch-mx6:...

[U-Boot] Dynamically define which Kernel image to boot during SPL execution

older
[U-Boot] [PATCH] omap5_common:...

0xbin4ry

6 Oct 2013 6 Oct '13

6:14 p.m.

Hi there,

I want to chose from two different Android kernel images to be booted during SPL execution. Thus, I guess I need to a) pass u-boot.img two different parameters or b) call two different u-boot.img files, which in turn call the corresponding kernel images?

Thanks in advance, -b

Reply

Show replies by date

Wolfgang Denk

6 Oct 6 Oct

9:31 p.m.

New subject: [U-Boot] Dynamically define which Kernel image to boot during SPL execution

Dear 0xbin4ry,

don't you have a real name?

In message 52518C7E.3010704@gmail.com you wrote:

I want to chose from two different Android kernel images to be booted during SPL execution. Thus, I guess I need to a) pass u-boot.img two

What would "u-boot.img" be here - the full U-Boot image loaded by the SPL? If you load and start that, then this would be the place where you determine which kernel image to load and start. However, if you're uysing Falcon mode, then you would not load any u-boot.img at all, and the SPL would include the code to determine which kernel image to load and start.

different parameters or b) call two different u-boot.img files, which in turn call the corresponding kernel images?

No, this would never be the case.

Best regards,

Wolfgang Denk

-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de To get something done, a committee should consist of no more than three men, two of them absent.

Reply

bin4ry

10 Oct 10 Oct

4:48 p.m.

New subject: [U-Boot] Dynamically define which Kernel image to boot during SPL execution

Am 06.10.2013 21:31, schrieb Wolfgang Denk:

Dear 0xbin4ry,

don't you have a real name?

Yes indeed, Peter.

What would "u-boot.img" be here - the full U-Boot image loaded by the SPL? If you load and start that, then this would be the place where you determine which kernel image to load and start.

The only code I found in the SPL regarding the call of u-boot.img were the following functions:

mmc_load_image_fat() -> file_fat_read() -> do_fat_read() [here, the u-boot.img file is copied to DDR memory] -> jump_to_image_no_args() [here, we excute the u-boot.img code].

However, I could not find any signs of any boot parameters (except for CONFIG_EXTRA_ENV_SETTINGS in omap4_common.) but I could not figure how to dynamically alter these parameters.

However, if you're uysing Falcon mode, then you would not load any u-boot.img at all, and the SPL would include the code to determine which kernel image to load and start.

I guess I have to read about falcon mode. Did not know about this before.

Basically, I want to determine which Android kernel to boot based upon a calculation executed by the SPL. Maybe you know if more elegant ways then the ones I am thinking of.

A little bit off-topic, however it could help my in this scenario anyways: Is it possible to show a splash screen in the SPL or the loaded u-boot.img on an OMAP4460? I browsed the web and found several statements that this is not supported. However, these statements seemed to be rather vague..

Best regards, Peter

Reply

4235

Age (days ago)

4239

Last active (days ago)

Download

2 comments

3 participants

tags (0)

participants (3)

0xbin4ry
bin4ry
Wolfgang Denk