* Determining Load Addresses
@ 2017-07-12 5:23 Kenny Koller
2017-07-12 16:00 ` Leonardo Sandoval
2017-07-12 18:03 ` Robert Berger
0 siblings, 2 replies; 3+ messages in thread
From: Kenny Koller @ 2017-07-12 5:23 UTC (permalink / raw)
To: yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 357 bytes --]
I'm trying to piece together the various load addresses used in the boot
sequence. I have built core-image-minimal for a Beaglebone. How can I
determine which load address and entry point is used when mkimage is called
for the kernel? Should I dig in to the recipe? Search some log files? I've
tried a few difference things without results.
Thanks.
[-- Attachment #2: Type: text/html, Size: 404 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Determining Load Addresses
2017-07-12 5:23 Determining Load Addresses Kenny Koller
@ 2017-07-12 16:00 ` Leonardo Sandoval
2017-07-12 18:03 ` Robert Berger
1 sibling, 0 replies; 3+ messages in thread
From: Leonardo Sandoval @ 2017-07-12 16:00 UTC (permalink / raw)
To: Kenny Koller; +Cc: yocto@yoctoproject.org
On Wed, 2017-07-12 at 05:23 +0000, Kenny Koller wrote:
> I'm trying to piece together the various load addresses used in the
> boot sequence. I have built core-image-minimal for a Beaglebone. How
> can I determine which load address and entry point is used when
> mkimage is called for the kernel? Should I dig in to the recipe?
> Search some log files? I've tried a few difference things without
> results.
>
>
This type of info usually comes in the machine definition, thus look
there. Diong a simple git grep ^UBOOT shows the following related
variables
meta/conf/documentation.conf:UBOOT_ENTRYPOINT[doc] = "Specifies the
entry point for the U-Boot image."
meta/conf/documentation.conf:UBOOT_LOADADDRESS[doc] = "Specifies the
load address for the U-Boot image."
> Thanks.
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Determining Load Addresses
2017-07-12 5:23 Determining Load Addresses Kenny Koller
2017-07-12 16:00 ` Leonardo Sandoval
@ 2017-07-12 18:03 ` Robert Berger
1 sibling, 0 replies; 3+ messages in thread
From: Robert Berger @ 2017-07-12 18:03 UTC (permalink / raw)
To: Kenny Koller, yocto@yoctoproject.org
Hi,
On 2017-07-12 08:23, Kenny Koller wrote:
> I'm trying to piece together the various load addresses used in the boot
> sequence. I have built core-image-minimal for a Beaglebone. How can I
> determine which load address and entry point is used when mkimage is
> called for the kernel? Should I dig in to the recipe? Search some log
> files? I've tried a few difference things without results.
You don't need to bake a board specific address into uImage.
Like this you could create an uImage without a baked in address. Check
here between lines 98 and 112
https://github.com/RobertBerger/meta-mainline/blob/pyro-training-v4.9.x/multi-v7-ml/conf/machine/multi-v7-ml.conf#L98
>
> Thanks.
>
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-07-12 18:03 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-07-12 5:23 Determining Load Addresses Kenny Koller
2017-07-12 16:00 ` Leonardo Sandoval
2017-07-12 18:03 ` Robert Berger
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.