public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [STATUS] Are we ready for v2012.04.1 ??
Date: Tue, 24 Apr 2012 19:00:53 +0200	[thread overview]
Message-ID: <4F96DC45.2060501@googlemail.com> (raw)
In-Reply-To: <CAOMZO5BgvcFzzuCxupsHbUJ9GGO=+5xKW=sAFTtw-ZRqwreh=A@mail.gmail.com>

On 24.04.2012 18:21, Fabio Estevam wrote:
> Dirk,
>
> On Tue, Apr 24, 2012 at 4:58 AM, Dirk Behme<dirk.behme@de.bosch.com>  wrote:
>> I tested the recent master which includes the three patches planned for
>> v2012.04.1 booting a device tree based kernel and it works :)
>
> Have you tested it on a mx6qsabrelite using the latest mainline kernel?

Yes.

Just to make sure: You use the recent mainline with the 4 additional 
patches on top of v2012.04:

http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary

> My kernel did not boot.
>
> This was what I did:
>
> make imx_v6_v7_defconfig
> make
> make imx6q-sabrelite.dtb
>
> cat arch/arm/boot/zImage arch/arm/boot/imx6q-sabrelite.dtb>
> arch/arm/boot/zImage_dtb
>
> mkimage -A arm -O linux -T kernel -C none -a 0x10008000 -e 0x10008000
> -n Linux -d arch/arm/boot/zImage_dtb arch/arm/boot/uImage_dtb
>
> cp arch/arm/boot/uImage_dtb /tftpboot/uImage
>
> It used to work before. Is this still valid?

I don't know ;) Or better: I don't use the device tree append method.

I don't have the details here, but what I do (out of my head, so there 
might be some details wrong):

Use the mainline kernel 3.4-rc4
make imx_v6_v7_defconfig
make LOADADDR=0x10800000 uImage

dd if=u-boot.imx of=/dev/sdd bs=512 skip=2 && sync
dd if=imx6q-sabrelite.dtb of=/dev/sdd bs=512 skip=1024 && sync (<- put 
the dtb to 512kB on the SD card)
dd if=uImage of=/dev/sdd bs=512 skip=2048 && sync (put the uImage to 1MB)

and then in U-Boot:

mmc read 0x12000000 0x800 0x2000 (read the kernel to 0x12000000)
mmc read 0x11ff0000 0x400 0x40 (read the device tree to 0x11ff0000)
bootm 0x12000000 - 0x11ff0000

You could do the same using tftp as proposed by Shawn:

tftpboot 0x12000000 uImage; tftpboot 0x11ff0000 imx6q-sabrelite.dtb; bootm
0x12000000 - 0x11ff0000

Again, this is just out of my head, so sorry if something is wrong.

Best regards

Dirk

  reply	other threads:[~2012-04-24 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24  6:35 [U-Boot] [STATUS] Are we ready for v2012.04.1 ?? Wolfgang Denk
2012-04-24  7:58 ` Dirk Behme
2012-04-24 16:21   ` Fabio Estevam
2012-04-24 17:00     ` Dirk Behme [this message]
2012-04-24 21:12       ` Fabio Estevam
2012-04-24  7:59 ` Thierry Reding
2012-04-24 10:14   ` Wolfgang Denk
2012-04-24 18:02 ` Marek Vasut

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=4F96DC45.2060501@googlemail.com \
    --to=dirk.behme@googlemail.com \
    --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