From: Jorge Ramirez-Ortiz, LDTS <ldts.mailing.lists@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools/imximage: fix reported DCD information for MX7ULP
Date: Mon, 2 Dec 2019 10:44:23 +0100 [thread overview]
Message-ID: <20191202094423.GA16086@trex> (raw)
In-Reply-To: <20191128103321.7285-1-jorge@foundries.io>
On 28/11/19 11:33:21, Jorge Ramirez-Ortiz wrote:
> On the MX7ULP, OCRAM for DCD is at 0x2f010000
any comments?
do notice that this is not trivial debug information: this is required
for security puposes so images can then be signed and booted via
SDP. Dumping the wrong information here is important stuff.
>
> Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io>
> ---
> tools/imximage.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/tools/imximage.c b/tools/imximage.c
> index d7c0b6e883..762a06d468 100644
> --- a/tools/imximage.c
> +++ b/tools/imximage.c
> @@ -11,6 +11,7 @@
> #include "imagetool.h"
> #include <image.h>
> #include "imximage.h"
> +#include <generated/autoconf.h>
>
> #define UNDEFINED 0xFFFFFFFF
>
> @@ -524,8 +525,13 @@ static void print_hdr_v2(struct imx_header *imx_hdr)
> printf("HAB Blocks: 0x%08x 0x%08x 0x%08x\n",
> (uint32_t)fhdr_v2->self, 0,
> (uint32_t)(fhdr_v2->csf - fhdr_v2->self));
> +#ifndef CONFIG_MX7ULP
> printf("DCD Blocks: 0x00910000 0x%08x 0x%08x\n",
> offs, be16_to_cpu(dcdlen));
> +#else
> + printf("DCD Blocks: 0x2f010000 0x%08x 0x%08x\n",
> + offs, be16_to_cpu(dcdlen));
> +#endif
> }
> } else {
> imx_header_v2_t *next_hdr_v2;
> --
> 2.17.1
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
next prev parent reply other threads:[~2019-12-02 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 10:33 [U-Boot] [PATCH] tools/imximage: fix reported DCD information for MX7ULP Jorge Ramirez-Ortiz
2019-12-02 9:44 ` Jorge [this message]
2019-12-02 13:42 ` Fabio Estevam
2019-12-03 14:07 ` Jorge
2019-12-03 16:32 ` Fabio Estevam
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=20191202094423.GA16086@trex \
--to=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