Can we try same image with the LAVA bootloader version to confirm that it's a bootloader thing? Also CCed jcriby for bootloader support.
Check with Dave in case we can't find the bootloader installed in LAVA case.
On 3 September 2012 05:41, Botao Sun <botao.sun@linaro.org> wrote:
> + Zach
>
> Sorry, I mean another Amit, Mr. Amit Pundir, he's working on Samsung related
> stuff I remembered.
>
> Also, here is more information, I have tried several previous image, the
> last good one is build 47:
>
> https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-samsunglt-stable-blob/#build=47
>
> Therefore, I'm going to use this one as our weekly test target. However,
> please dig more on why build 48, 49 & 50 failed - bad thing started at build
> 48.
>
> Thank you!
Botao,
Just had a second to look at this, I see:
U-Boot 2012.07-00053-gbf30cf4 (Sep 03 2012 - 07:03:03) for ORIGEN
CPU: Exynos4210@1000MHz
Board: ORIGEN
DRAM: 1 GiB
WARNING: Caches not enabled
MMC: SAMSUNG SDHCI: 0
Timeout for status update!
mmc fail to send stop cmd
Using default environment
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
reading boot.scr
397 bytes read
Running bootscript from mmc0:2 ...
## Executing script at 42000000
reading uImage
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Timeout for status update!
mmc fail to send stop cmd
Transfer data timeout
Error reading cluster
** Unable to read "uImage" from mmc 0:2 **
** Can't read partition table on 0:0 **
** Partition 2 not valid on device 0 **
** Unable to use mmc 0:2 for fatload **
## Booting kernel from Legacy Image at 40007000 ...
Image Name: Linux-3.4.8
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3879160 Bytes = 3.7 MiB
Load Address: 40008000
Entry Point: 40008000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
ORIGEN #
on,
https://android-build.linaro.org/builds/~linaro-android/origen-jb-gcc47-samsunglt-stable-blob/#build=50
This would explain why it works in LAVA (since LAVA doesn't update the
bootloader) but it doesn't work locally (since we do update the
bootloader). Is this what you see?
>
>
> BR
> Botao Sun
>
> On Mon, Sep 3, 2012 at 8:25 PM, amit khare <amit.khare@linaro.org> wrote:
>>
>> on it....
>>
>> Regards,
>> Amit
>>
>>
>> On 3 September 2012 15:21, Botao Sun <botao.sun@linaro.org> wrote:
>>>
>>> Hi Amit,
>>>
>>> Would you take a look at this issue?
>>>
>>> Origen Jelly Bean boot failed.:
>>> https://bugs.launchpad.net/linaro-android/+bug/1045244
>>>
>>> The weird thing is LAVA shows that it works well:
>>> http://validation.linaro.org/lava-server/dashboard/image-reports/origen-jb-gcc47-samsunglt-stable-blob
>>>
>>> Is there anything I missed during SD card flashing?
>>>
>>> Thank you!
>>>
>>>
>>> BR
>>> Botao Sun
>>
>>
>
--
Zach Pfeffer
Android Platform Team Lead, Linaro Platform Teams
Linaro.org | Open source software for ARM SoCs
Follow Linaro: http://www.facebook.com/pages/Linaro
http://twitter.com/#!/linaroorg - http://www.linaro.org/linaro-blog