From: "Barisani, Andrea" <andrea.barisani@f-secure.com>
To: Stefan Agner <stefan@agner.ch>
Cc: "peng.fan@nxp.com" <peng.fan@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"pure.logic@nexus-software.ie" <pure.logic@nexus-software.ie>,
"festevam@gmail.com" <festevam@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"richard.leitner@skidata.com" <richard.leitner@skidata.com>
Subject: Re: nvmem: imx-ocotp: fusing write tools
Date: Wed, 18 Dec 2019 10:18:51 +0000 [thread overview]
Message-ID: <20191218101846.GC4754@lambda.inversepath.com> (raw)
In-Reply-To: <2d527ebfde26459b7fa57e519610a8a5@agner.ch>
On Wed, Dec 18, 2019 at 11:10:59AM +0100, Stefan Agner wrote:
> Hi,
>
> We are looking to replace the NXP downstream OTP driver (CONFIG_FSL_OTP)
> with the new upstream nvmem based driver. I was wondering if there is
> user-space tooling around which can be used to write fuses. The NXP
> driver had the fuse map as part of the API, so fusing was rather simple
> and only required an echo into the right file. The new driver requires a
> seek to the right offset.
>
> I found this tool which provides fuse maps as yaml files and makes
> fusing rather simple:
> https://github.com/inversepath/crucible
>
> At this point it seems to miss i.MX 8 series fuse maps. Also we so far
> have no go runtime on our production system, we consider writing a
> (probably simpler) C implementation thereof.
>
Go runtime is not needed to execute crucible which can be compiled like any C
application to generate a binary which requires no supporting files (other
than the fusemap YAML).
Crucible does support NVMEM based drivers and therefore I think it can be
adapted also to include i.MX8 support.
If would like to sponsor it we would be happy to generate the fusemap file
for the i.MX8. If you send us a development board, or we can purchase one as
part of the sponsorship, it would be ideal to test it.
Cheers
> What is generally used to write fuses using the nvmem driver?
>
> --
> Stefan
--
Andrea Barisani | Head of Hardware Security | F-Secure
www.f-secure.com • foundry.f-secure.com • andrea.bio
0A76 074A 02CD E989 CE7F AC3F DA47 578E 864C 9B9E
"Pluralitas non est ponenda sine necessitate"
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-12-18 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 10:10 nvmem: imx-ocotp: fusing write tools Stefan Agner
2019-12-18 10:18 ` Barisani, Andrea [this message]
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=20191218101846.GC4754@lambda.inversepath.com \
--to=andrea.barisani@f-secure.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peng.fan@nxp.com \
--cc=pure.logic@nexus-software.ie \
--cc=richard.leitner@skidata.com \
--cc=stefan@agner.ch \
/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;
as well as URLs for NNTP newsgroup(s).