mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v1 2/2] Documentation: user: Add OTP support and parameter descriptions
Date: Fri, 31 Jan 2025 14:03:11 +0100	[thread overview]
Message-ID: <Z5zKD-5ovqoQfDzu@pengutronix.de> (raw)
In-Reply-To: <20250130120814.1053382-2-o.rempel@pengutronix.de>

On Thu, Jan 30, 2025 at 01:08:14PM +0100, Oleksij Rempel wrote:
> Provide an overview of OTP support in Barebox.
> 
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
>  Documentation/user/otp.rst         | 199 +++++++++++++++++++++++++++++
>  Documentation/user/user-manual.rst |   1 +
>  2 files changed, 200 insertions(+)
>  create mode 100644 Documentation/user/otp.rst
> 
> diff --git a/Documentation/user/otp.rst b/Documentation/user/otp.rst

...

> +    bsec0.permanent_write_enable=1
> +
> +    # Write directly to an OTP register (bypasses shadow)
> +    mw -l -d /dev/stm32-bsec 0x00000170+4 0x12345678
> +
> +    # Disable OTP write mode (future writes go to shadow, if available)
> +    bsec0.permanent_write_enable=0
> +
> +Example 2: Using Shadow Memory Without Committing
> +::
> +
> +    # Ensure shadow writes are enabled
> +    bsec0.permanent_write_enable=0
> +
> +    # Write to shadow memory (not permanent yet)
> +    mw -l -d /dev/imx-ocotp 0x20+4 0xAABBCCDD

Please drop the '+4' from the mw commands. The length is detected from
the number of words written and the '+4' has no meaning for mw.

Sascha

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |



  reply	other threads:[~2025-01-31 13:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-30 12:08 [PATCH v1 1/2] nvmem: bsec: Add support for OTP permanent write lock Oleksij Rempel
2025-01-30 12:08 ` [PATCH v1 2/2] Documentation: user: Add OTP support and parameter descriptions Oleksij Rempel
2025-01-31 13:03   ` Sascha Hauer [this message]
2025-01-31 13:07 ` [PATCH v1 1/2] nvmem: bsec: Add support for OTP permanent write lock 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=Z5zKD-5ovqoQfDzu@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=o.rempel@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