From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Run a standalone application on a core other than 0
Date: Tue, 2 Jul 2013 16:11:09 -0500 [thread overview]
Message-ID: <1372799469.8183.120@snotra> (raw)
In-Reply-To: <CANFGKe9M4OrusRg233vK531rZgVwWe05-hGYpTNL+9LsSUFHpw@mail.gmail.com> (from joao.fernandes@ist.utl.pt on Tue Jul 2 07:02:21 2013)
On 07/02/2013 07:02:21 AM, Jo?o Fernandes wrote:
> As the subject says, I'm trying to run the "Hello world" standalone
> application example on a core other than 0, on a Freescale QorIQ
> P4080.
>
> I tried through the shell and programmatically by exporting
> cpu_release
> function... nothing. My first thought was that only core 0 has
> register r2
> with the address of the "global_data" structure, so I tried to set it
> on
> the other cores, but still nothing. Help on this matter is highly
> appreciated.
If you mean a U-Boot application, this is not supported. U-Boot
doesn't run on cores other than 0, except for a small stub for the spin
table code.
If you have true standalone code, you can release it on other CPUs
using the "cpu <n> release" command. That code will not have access to
any U-Boot functionality. Its entry state will be as described for
secondary CPUs in ePAPR. It will be the same as if an OS were spinning
up its secondary cores by writing directly to the spin table.
-Scott
next prev parent reply other threads:[~2013-07-02 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 12:02 [U-Boot] Run a standalone application on a core other than 0 João Fernandes
2013-07-02 21:11 ` Scott Wood [this message]
2013-07-08 17:22 ` João Fernandes
2013-07-08 18:16 ` Scott Wood
[not found] <CANFGKe9S1bBbJncFoZGG9wbWk-JL_8AeoxSKyj=GGGyHsiLsCA@mail.gmail.com>
2013-07-08 21:41 ` Scott Wood
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=1372799469.8183.120@snotra \
--to=scottwood@freescale.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