From: Guillaume Gardet <guillaume.gardet@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Upstream uboot and Arndale 5250 support
Date: Wed, 08 Oct 2014 10:00:44 +0200 [thread overview]
Message-ID: <5434EF2C.90504@free.fr> (raw)
In-Reply-To: <CAMmgNdboH4xbVp0xwp4-2bw9K3Re5nzpzHKek0-H3v5+4virVQ@mail.gmail.com>
I used the following values with 2014.10-rc2:
kerneladdr=0x44000000
ramdiskaddr=0x45000000
fdtaddr=0x4c000000
But I used a zImage. If you use a uImage, you need to modify the kernel load addr.
Guillaume
Le 07/10/2014 17:02, Paolo Pisati a ?crit :
> those are the addresses suggested by u-boot and yes, i already tried
> moving stuff around but it didn't fix it: what's the working config
> with your board? u-boot version?
>
> On Tue, Oct 7, 2014 at 4:34 PM, Guillaume Gardet
> <guillaume.gardet@free.fr> wrote:
>> Hi,
>>
>> Le 07/10/2014 14:58, Paolo Pisati a ?crit :
>>
>>> Hi,
>>>
>>> i've been trying to update the u-boot on my board (sd booting), from the
>>> Linaro
>>> one (2012.10) to a v2014.X, but so far had no luck:
>>>
>>> make arndale_config
>>> export CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf-
>>> make
>>>
>>> ...
>>>
>>> dd if=arndale-bl1.bin of=/dev/sdc bs=512 skip=1
>>> dd if=arndale-spl.bin of=/dev/sdc bs=512 skip=17
>>> dd if=./u-boot-dtb.bin of=/dev/sdc bs=512 skip=49
>>>
>>> ...
>>>
>>> u-boot 3.10rc3 (same happens with v2014.07 or 2014.04):
>>>
>>> U-Boot 2014.10-rc3 (Oct 07 2014 - 13:26:48) for ARNDALE
>>>
>>> CPU: Exynos5250 at 1000MHz
>>>
>>> Board: Arndale
>>> I2C: i2c_init: failed to init bus 0 for speed = 100000
>>> ready
>>> DRAM: 2 GiB
>>> trace: copying 00086db4 bytes of early data from 50000000 to beff0000
>>> trace: enabled
>>> WARNING: Caches not enabled
>>> MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
>>> dwmci_send_cmd: DATA ERROR!
>>> i2c_init: failed to init bus 0 for speed = 100000
>>> In: serial
>>> Out: serial
>>> Err: serial
>>> Net: Net Initialization Skipped
>>> No ethernet found.
>>> Hit any key to stop autoboot: 0
>>> ARNDALE # printenv
>>> baudrate=115200
>>> bootargs=console=ttySAC2,115200n8 root=/dev/mmcblk1p1 rw rootwait debug
>>> earlyprintk
>>> bootcmd=run bootcmd_ubuntu
>>> bootcmd_ubuntu=run loadk; run loadf; run loadr; bootm ${kernel_addr_r}
>>> ${ramdisk_addr_r}:${filesize} ${fdt_addr_r}
>>> bootdelay=3
>>> fdt_addr_r=0x41000000
>>> filesize=5b9902
>>> kernel_addr_r=0x40007000
>>> loadf=ext2load mmc 1:1 ${fdt_addr_r} /boot/exynos5250-arndale.dtb
>>> loadk=ext2load mmc 1:1 ${kernel_addr_r} /boot/uImage
>>> loadr=ext2load mmc 1:1 ${ramdisk_addr_r} /boot/uInitrd
>>> ramdisk_addr_r=0x42000000
>>> stderr=serial
>>> stdin=serial
>>> stdout=serial
>>>
>>> Environment size: 589/16380 bytes
>>> ARNDALE # run loadk
>>> 6002946 bytes read in 1117 ms (5.1 MiB/s)
>>> ARNDALE # bootm ${kernel_addr_r}
>>> ## Booting kernel from Legacy Image at 40007000 ...
>>> Image Name: kernel 3.16.0-20-generic
>>> Image Type: ARM Linux Kernel Image (uncompressed)
>>> Data Size: 6002882 Bytes = 5.7 MiB
>>> Load Address: 40008000
>>> Entry Point: 40008000
>>> Verifying Checksum ... OK
>>> Loading Kernel Image ... OK
>>>
>>> Starting kernel ...(fake run for tracing)
>>>
>>> Starting kernel ...
>>>
>>> [stuck here]
>>
>> I faced this problem some times ago. Try to modify kernel, initrd and fdt
>> addresses.
>>
>>
>> Guillaume
>>
>
>
next prev parent reply other threads:[~2014-10-08 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 12:58 [U-Boot] Upstream uboot and Arndale 5250 support Paolo Pisati
2014-10-07 14:34 ` Guillaume Gardet
2014-10-07 15:02 ` Paolo Pisati
2014-10-08 8:00 ` Guillaume Gardet [this message]
2014-10-08 10:16 ` Paolo Pisati
2014-10-08 13:13 ` Guillaume Gardet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5434EF2C.90504@free.fr \
--to=guillaume.gardet@free.fr \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox