All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: a-m1@ti.com
Cc: meta-ti@lists.yoctoproject.org, praneeth@ti.com, reatmon@ti.com,
	nikhil.nd@ti.com, devarsht@ti.com, nsekhar@ti.com
Subject: Re: [meta-ti][dunfell][PATCH] conf: machine: am64xx-hs-evm: Fix naming of u-boot.img
Date: Fri, 25 Feb 2022 16:17:42 -0500	[thread overview]
Message-ID: <20220225211742.GZ26229@denix.org> (raw)
In-Reply-To: <20220225100830.g7xa5qg7nyafix36@ti.com>

On Fri, Feb 25, 2022 at 03:38:30PM +0530, Aparna M via lists.yoctoproject.org wrote:
> On 19:41-20220221, Denys Dmytriyenko wrote:
> > On Mon, Feb 21, 2022 at 01:43:31PM +0530, Aparna M via lists.yoctoproject.org wrote:
> > > All the HS platforms generate the u-boot binary as u-boot.img_HS
> > > but the bootloader expects the binary to be named as u-boot.img
> > > 
> > > Due to this mismatch, script cannot find the required image to
> > > be added in the WIC image. Fix this by overwriting the
> > > UBOOT_IMAGE variable via conf file.
> > 
> > Can you please clarify which script cannot find the image? Thanks!
> 
> The wic file generation scripts that pick up files for the boot
> partition from the IMAGE_BOOT_FILES variable is unable to find
> u-boot.img. As a result, the generated wic image does not package the
> uboot binary and fails.

I don't see the failure. wic image picks up everything listed in 
IMAGE_BOOT_FILES variable and it is set right there to contain UBOOT_BINARY, 
which is set to u-boot.img_HS

HS platforms boot differently and they use FIT image along with other 
artifacts. I don't believe wic image was ever used for HS platforms...

So, I believe you have some other problem and this is not the right fix for 
it.


> > Also, how does it work for am65xx HS, j721e HS, j7200 HS? Why only
> > am64xx HS?
> 
> The previous releases for these three platforms did not include wic
> images. I believe this issue might be present in these platforms as
> well.
> 
> > 
> > > Signed-off-by: Nikhil Devshatwar <nikhil.nd@ti.com>
> > > 
> > > Signed-off-by: Aparna M <a-m1@ti.com>
> > > ---
> > >  conf/machine/am64xx-hs-evm.conf | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/conf/machine/am64xx-hs-evm.conf b/conf/machine/am64xx-hs-evm.conf
> > > index 44e81463..781b8318 100644
> > > --- a/conf/machine/am64xx-hs-evm.conf
> > > +++ b/conf/machine/am64xx-hs-evm.conf
> > > @@ -17,6 +17,7 @@ UBOOT_DTBO_OFFSET =      "0x00010000"
> > >  SPL_BINARY = "tispl.bin_HS"
> > >  SPL_BINARYNAME = "tispl.bin"
> > >  UBOOT_BINARY = "u-boot.img_HS"
> > > -IMAGE_BOOT_FILES = "${UBOOT_BINARY}"
> > > +UBOOT_IMAGE = "u-boot.img"
> > > +IMAGE_BOOT_FILES = "${UBOOT_IMAGE}"
> > >  
> > >  TI_SECURE_DEV_PKG = "${TI_SECURE_DEV_PKG_K3}"
> > > -- 
> > > 2.17.1

  reply	other threads:[~2022-02-25 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21  8:13 [meta-ti][dunfell][PATCH] conf: machine: am64xx-hs-evm: Fix naming of u-boot.img Aparna M
2022-02-22  0:41 ` Denys Dmytriyenko
2022-02-25 10:08   ` Aparna M
2022-02-25 21:17     ` Denys Dmytriyenko [this message]
2022-02-25 20:51   ` Aparna M

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=20220225211742.GZ26229@denix.org \
    --to=denis@denix.org \
    --cc=a-m1@ti.com \
    --cc=devarsht@ti.com \
    --cc=meta-ti@lists.yoctoproject.org \
    --cc=nikhil.nd@ti.com \
    --cc=nsekhar@ti.com \
    --cc=praneeth@ti.com \
    --cc=reatmon@ti.com \
    /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.