From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Bastian Krause <bst@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] arch: arm: mach-imx: document field return in CSF template
Date: Fri, 25 Feb 2022 11:55:44 +0100 [thread overview]
Message-ID: <20220225105544.pbptljj3tt3tv6aw@pengutronix.de> (raw)
In-Reply-To: <7013be85-751c-b20c-6dff-469ce7401a54@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1917 bytes --]
On 25.02.2022 11:46:04, Bastian Krause wrote:
> On 2/25/22 11:25, Marc Kleine-Budde wrote:
> > On 25.02.2022 11:03:44, Bastian Krause wrote:
> > > Activating the field return configuration returns a locked-down board
> > > (nearly) to its open state. In order to burn the FIELD_RETURN fuse, the
> > > CSF must contain a specific unlock command with the device's UID.
> > >
> > > Signed-off-by: Bastian Krause <bst@pengutronix.de>
> > > ---
> > > .../include/mach/habv4-imx6-gencsf-template.h | 12 ++++++++++++
> > > 1 file changed, 12 insertions(+)
> > >
> > > diff --git a/arch/arm/mach-imx/include/mach/habv4-imx6-gencsf-template.h b/arch/arm/mach-imx/include/mach/habv4-imx6-gencsf-template.h
> > > index a60b485292..45da2981cb 100644
> > > --- a/arch/arm/mach-imx/include/mach/habv4-imx6-gencsf-template.h
> > > +++ b/arch/arm/mach-imx/include/mach/habv4-imx6-gencsf-template.h
> > > @@ -39,6 +39,18 @@ hab Engine = SETUP_HABV4_ENGINE
> > > hab Features = SETUP_HABV4_FEATURES
> > > #endif
> > > +/*
> > > +// allow fusing FIELD_RETURN
> > > +// # ocotp0.permanent_write_enable=1
> > > +// # mw -l -d /dev/imx-ocotp 0xb8 0x1
> > > +hab [Unlock]
> > > +hab Engine = OCOTP
> > > +hab Features = FIELD RETURN
> > > +// device-specific UID:
> > > +// $ dd if=/sys/bus/nvmem/devices/imx-ocotp0/nvmem bs=4 skip=1 count=2 status=none | hexdump -ve '1/1 "0x%.2x, "' | sed 's/, $//'
> > > +hab UID = 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07, 0x08
> >
> > You probably want to comment this all out in the template...
>
> I don't get it, that's all inside the /* commented section */.
Doh!
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2022-02-25 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 10:03 Bastian Krause
2022-02-25 10:25 ` Marc Kleine-Budde
2022-02-25 10:46 ` Bastian Krause
2022-02-25 10:55 ` Marc Kleine-Budde [this message]
2022-02-28 9:30 ` Sascha Hauer
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=20220225105544.pbptljj3tt3tv6aw@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=bst@pengutronix.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