public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Booting image from ARM for different architecture
Date: Mon, 31 Mar 2014 11:45:22 +0200	[thread overview]
Message-ID: <53393932.5090107@monstr.eu> (raw)

Hi all,

I want to check with you if someone tried this scenario.
Load u-boot on main CPU (for me ARM cortex-a9)
and boot different cpu(for me Microblaze) with FIT image
or old u-boot image format.

IRC I have seen any code regarding this but I am not able
to find it out where. :-(

My current usage is that I do that steps by hand by
tftp 100000 kernel.bin (microblaze kernel in bin format with rootfs and dtb in it)
mwr 0xXXXXXX 0x1 (turn on microblaze via custom logic which jumps to 0x100000)
tftp 10000000 image.ub (download arm kernel)
bootm 0x10000000 (boot arm kernel)

I think that will be much better to have
both kernels in one FIT image and and use two configurations.
One for microblaze kernel and second for arm kernel
and boot it with one bootm command.

Simon: Is this configuration even supported by FIT image?

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140331/d219dfd9/attachment.pgp>

             reply	other threads:[~2014-03-31  9:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31  9:45 Michal Simek [this message]
2014-04-02 19:55 ` [U-Boot] Booting image from ARM for different architecture Simon Glass

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=53393932.5090107@monstr.eu \
    --to=monstr@monstr.eu \
    --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