All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Simon Glass <sjg@chromium.org>
Cc: u-boot@lists.denx.de, git@xilinx.com, neal.frager@amd.com,
	Charlie Johnston <charlie.johnston@loftorbital.com>,
	Jonas Karlman <jonas@kwiboo.se>,
	Kever Yang <kever.yang@rock-chips.com>,
	Marek Vasut <marex@denx.de>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	Oliver Gaskell <Oliver.Gaskell@analog.com>,
	Prasad Kummari <prasad.kummari@amd.com>,
	Sumit Garg <sumit.garg@linaro.org>,
	Tejas Bhumkar <tejas.arvind.bhumkar@amd.com>,
	Tom Rini <trini@konsulko.com>, Tony Dinh <mibodhi@gmail.com>,
	Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
Subject: Re: [RFC PATCH] zynqmp: Add binman description for SOM
Date: Fri, 1 Nov 2024 14:09:38 +0100	[thread overview]
Message-ID: <178d29b0-d82c-4b18-a3ed-3d46dcc02446@amd.com> (raw)
In-Reply-To: <1048553d-4818-4aba-8bd1-c958dc0b7c5e@amd.com>

Hi Simon,

On 11/1/24 09:27, Michal Simek wrote:
> 
> 
> On 10/31/24 19:03, Simon Glass wrote:
>> Hi Michal,
>>
>> On Wed, 9 Oct 2024 at 10:33, Michal Simek <michal.simek@amd.com> wrote:
>>>
>>> There is necessary to do some steps to compose boot images. These steps
>>> were in scripts in layers for a while. That's why introduce description via
>>> binman to simplify wiring and remove all scripting around.
>>> This should make sure that everybody is up2date with the latest versions.
>>>
>>> The first step is to create fit image with DTBs with descriptions in
>>> configuration node which is written as regular expression to match all SOM
>>> versions.
>>> Description is there for k24 and k26 in spite of low level psu_init
>>> configuration is different. The reason is that it goes to u-boot.itb image
>>> which is the same for k24 and k26.
>>> u-boot.itb is another image which is generated. It is normally generated
>>> via arch/arm/mach-zynqmp/mkimage_fit_atf.sh but this script is supposed to
>>> be deprecated.
>>> FIT image by purpose is using 64bit addresses to have default option to
>>> move images to high DDR (above 4GB). TF-A and TEE are optional components
>>> but in the most cases TF-A is present all the time and TEE(OP-TEE) is used
>>> by some configurations too.
>>>
>>> 3rd generated image is boot.bin with updated user field which contains
>>> version number. This image can be used with updated Image Selector
>>> which supports A/B update mechanisms with rollback protection.
>>>
>>> 4th image is image.bin which binary file which contains boot.bin and
>>> u-boot.itb together and can be programmed via origin Image Selector.
>>> This image can be also used for creating one capsule which contains both
>>> boot images (in SPL boot flow).
>>>
>>> Signed-off-by: Michal Simek <michal.simek@amd.com>
>>> ---
>>>
>>> Currently I have this for testing purpose only to find missing bits and
>>> pieces in binman for cases I want to support.
>>>
>>> This patch depends on
>>> https://lore.kernel.org/r/ 
>>> fbed0251437b61a2f7a85596d7403b5b9c8237c1.1728306322.git.michal.simek@amd.com
>>>
>>> ---
>>>   arch/arm/dts/Makefile                |   1 +
>>>   arch/arm/dts/zynqmp-som-binman.dts   | 224 +++++++++++++++++++++++++++
>>>   arch/arm/mach-zynqmp/Kconfig         |  17 ++
>>>   configs/xilinx_zynqmp_kria_defconfig |   2 +
>>>   4 files changed, 244 insertions(+)
>>>   create mode 100644 arch/arm/dts/zynqmp-som-binman.dts
>>
>> I'm pleased to see this. My only suggestion is to use '/bits/ 64'
>> instead of the macros, for 64-bit values.
> 
> When I was playing with it some time ago it didn't work but it works now that's 
> why no issue with it.

One more thing on this one. I pretty much dislike that images are generated to 
u-boot root folder. Isn't there a way that they will be written to separate 
folder (deploy for example)?

Thanks,
Michal

  reply	other threads:[~2024-11-01 13:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09  8:32 [RFC PATCH] zynqmp: Add binman description for SOM Michal Simek
2024-10-31 18:03 ` Simon Glass
2024-11-01  8:27   ` Michal Simek
2024-11-01 13:09     ` Michal Simek [this message]
2024-11-01 13:52       ` Tom Rini
2024-11-02 16:28         ` Simon Glass
2024-11-04  8:32           ` Michal Simek
2024-12-06 19:17             ` Simon Glass
2024-12-09 15:26               ` Michal Simek

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=178d29b0-d82c-4b18-a3ed-3d46dcc02446@amd.com \
    --to=michal.simek@amd.com \
    --cc=Oliver.Gaskell@analog.com \
    --cc=charlie.johnston@loftorbital.com \
    --cc=git@xilinx.com \
    --cc=jonas@kwiboo.se \
    --cc=kever.yang@rock-chips.com \
    --cc=marex@denx.de \
    --cc=mibodhi@gmail.com \
    --cc=neal.frager@amd.com \
    --cc=neil.armstrong@linaro.org \
    --cc=prasad.kummari@amd.com \
    --cc=sjg@chromium.org \
    --cc=sumit.garg@linaro.org \
    --cc=tejas.arvind.bhumkar@amd.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=venkatesh.abbarapu@amd.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.