Origen boot arguments missing

[Botao]

The latest version of Linaro image tools can't set the boot arguments for Samsung Origen build correctly, therefore, the end users have to set them manually when they try to boot up their boards at the first time.

The boot arguments which should be set are:

setenv bootargs "console=ttySAC2,115200n8 root=/dev/ram init=/init rootwait ro"
setenv bootcmd "fatload mmc 0:2 0x40007000 uImage; fatload mmc 0:2 0x42000000 uInitrd; bootm 0x40007000 0x42000000"

[James Westby (james-w)]

On Thu, 08 Sep 2011 00:34:21 -0000, Botao Sun <email address hidden> wrote:
> Public bug reported:
>
> The latest version of Linaro image tools can't set the boot arguments
> for Samsung Origen build correctly, therefore, the end users have to set
> them manually when they try to boot up their boards at the first time.
>
> The boot arguments which should be set are:
>
> setenv bootargs "console=ttySAC2,115200n8 root=/dev/ram init=/init rootwait ro"
> setenv bootcmd "fatload mmc 0:2 0x40007000 uImage; fatload mmc 0:2 0x42000000 uInitrd; bootm 0x40007000 0x42000000"

Is the change root=/dev/ram?

If so, why is that needed?

Thanks,

James

[Botao (botao-sun)]

If those 2 boot arguments are not set, the board will be stuck at the "ORIGEN #" during the boot process. This is an old issue, and Angus had fixed it before, but he forgot a patch when he updated the u-boot, so it comes out again.

He will fix it in these 2 days, and you can also refer to this bug:

https://bugs.launchpad.net/linaro-landing-team-samsung/+bug/844041

[James Westby (james-w)]

On Thu, 08 Sep 2011 05:15:16 -0000, Botao Sun <email address hidden> wrote:
> If those 2 boot arguments are not set, the board will be stuck at the
> "ORIGEN #" during the boot process. This is an old issue, and Angus had
> fixed it before, but he forgot a patch when he updated the u-boot, so it
> comes out again.
>
> He will fix it in these 2 days, and you can also refer to this bug:
>
> https://bugs.launchpad.net/linaro-landing-team-samsung/+bug/844041

Hi,

So this would be a workaround for a problem in u-boot?

If so it's not appropriate for us to make this change in
linaro-image-tools. We should only be changing this if it's something
that is required in the long-term and can't be done any other way.

Thanks,

James

[Angus Ainslie (angus-akkea)]

I missed adding the patch that reads the boot.scr from the FAT patrition.

I've rebased on upstream u-boot added the config patch and push out a new version of origen-2011.09 u-boot

[Zach Pfeffer (pfefferz)]

Is origen-2011.09 u-boot different than git://git.linaro.org/boot/u-boot-linaro-stable.git master branch?

[James Westby (james-w)]

Hi,

As this is going to be fixed by changing u-boot, please re-assign the bug to
whichever project corresponds to the u-boot that needs to be fixed.

At the moment it says that it is "Fix Committed" in linaro-image-tools, which
is wrong as nothing was committed in that project to fix this.

Thanks,

James

[Zach Pfeffer (pfefferz)]

Moving back to in progress until we have a good build.

[Fathi Boudra (fboudra)]

reaffect to linaro-landing-team-samsung. There's nothing to do on linaro-image-tools side.

[Botao (botao-sun)]

Verified. This bug has been fixed.