On 14 May 2012 15:24, Mathieu Poirier mathieu.poirier@linaro.org wrote:
All,
In our ongoing effort to move to an upstream-supported code base and booting the snowball with a device tree (DT) I have change the boot loader in the following android builds [1][2][3] to u-boot-linaro-stable [4].
Once the linaro-uboot is installed in a system it won't be able to boot images that were created at an earlier time.
Say that build #500 has the new linaro-uboot and the image has been installed on the emmc. Once powered this uboot will not be able to boot build #499 that is installed on the mmc. To fix the problem, simply install build #500 on the mmc. This is because the mmc commands in the IK-uboot and the linaro-uboot differ.
Mathieu, would you sync with Fathi and get this info up on android-build?
To install the linaro-uboot you *must* use the latest android-linaro-media-create found here [5] until the changes get merged in the official repository [6].
Something like:
$ bzr branch lp:~mathieu.poirier/linaro-image-tools/linaro-image-tools
Last but not least, the linaro-uboot is currently not able to save the environment variable block to the emmc card. That work is ongoing and the functionality expected to be part of 12.05.
What problem does this cause?
Find me on IRC if you have any questions.
Regards, Mathieu.
[1]. https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc47-i... [2]. https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc47-i... [3]. https://android-build.linaro.org/builds/~linaro-android/snowball-ics-gcc46-i... [4]. http://git.linaro.org/git/boot/u-boot-linaro-stable.git [5]. https://code.launchpad.net/~mathieu.poirier/linaro-image-tools/linaro-image-... [6]. https://code.launchpad.net/linaro-image-tools
linaro-android mailing list linaro-android@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-android