From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 06/11] imx: imx-common: introduce boot auxiliary core
Date: Thu, 14 Jan 2016 12:15:46 -0500 [thread overview]
Message-ID: <20160114171546.GC3359@bill-the-cat> (raw)
In-Reply-To: <d97fb27f73c0fc034128eae81786660b@agner.ch>
On Wed, Jan 13, 2016 at 12:45:05PM -0800, Stefan Agner wrote:
> Hi,
>
> I would like to keep the discussion going and shed some light on the
> image format introduced here, see below...
>
> On 2016-01-07 00:38, Peng Fan wrote:
> > Hi Stefan,
> > On Wed, Jan 06, 2016 at 10:59:17PM -0800, Stefan Agner wrote:
> >>On 2016-01-04 21:56, Peng Fan wrote:
> >>> From: Peng Fan <peng.fan@nxp.com>
> >>>
> >>> To boot a auxiliary core in asymmetric multicore system, introduce the
> >>> new command "bootaux" to do it. Example of boot auxliary core from
> >>> 0x70000000 where stores the boot head information that should be
> >>> parsed by auxiliary core, "bootaux 0x70000000".
> >>
> >>This reminds me of a question which was nagging me lately:
> >>Is the M4 core of SoloX/MX7 running a boot ROM? Or who/what is "parsing
> >>the boot head information"?
> >
> > There is no bootrom for m4 core. The bootimage for M4 contains stack
> > info and pc info. bootaux command will use the info extracted from bootimage.
>
>
> So the image expected by bootaux is really a raw binary image, with the
> only notion that the first two words need to be the stack pointer and
> the reset handler (firmware entry point).
>
> U-Boot has other commands which work with "raw" images, such as the
> bootz command. The bootz command also expects a certain "raw" format,
> hence I guess it is ok to introduce something like that also for the
> auxiliary core.
I suppose my only contribution right now is that for another project
where we have U-Boot (on the M4) kicking off NuttX we've had to do a
custom command to stack pointer thing, I agree with the need to add some
way to easily kick these cases off.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160114/cdf6952c/attachment.sig>
next prev parent reply other threads:[~2016-01-14 17:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 5:56 [U-Boot] [PATCH 00/11] imx: introduce rdc and boot auxiliary core Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 01/11] imx: mx6: introduce rdc regs Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 02/11] imx: imx-common: introduce Resource Domain Controller support Peng Fan
2016-01-07 6:52 ` Stefan Agner
2016-01-07 7:34 ` Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 03/11] imx: mx6sx Add RDC mappings of masters and peripherals Peng Fan
2016-01-07 6:55 ` Stefan Agner
2016-01-05 5:56 ` [U-Boot] [PATCH 04/11] imx: mx7d: Add RDC support Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 05/11] imx: mx7d: clock support for RDC Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 06/11] imx: imx-common: introduce boot auxiliary core Peng Fan
2016-01-07 6:59 ` Stefan Agner
2016-01-07 8:38 ` Peng Fan
2016-01-08 1:51 ` Ye Li
2016-01-13 20:45 ` Stefan Agner
2016-01-14 17:15 ` Tom Rini [this message]
2016-01-14 17:54 ` Stefan Agner
2016-01-14 18:07 ` Tom Rini
2016-01-18 4:07 ` Peng Fan
2016-01-14 17:17 ` Simon Glass
2016-01-18 4:14 ` Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 07/11] imx: mx6: implement functions to " Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 08/11] imx: mx6sxsabresd: add command and macros for boot m4 core Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 09/11] imx: mx7: implement functions to boot auxiliary core Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 10/11] imx: mx7dsabresd: add command and macros for boot m4 core Peng Fan
2016-01-05 5:56 ` [U-Boot] [PATCH 11/11] imx: mx7d: isolate resources to domain 0 for A7 core Peng Fan
2016-01-07 7:04 ` Stefan Agner
2016-01-07 10:42 ` Peng Fan
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=20160114171546.GC3359@bill-the-cat \
--to=trini@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.