On Tuesday, March 26, 2013 10:28:39 PM, Benoît Thébaudeau wrote:

On Tuesday, March 26, 2013 10:24:52 PM, Benoît Thébaudeau wrote:

...

This can be useful for fuse-like hardware, OTP SoC options, etc.

Signed-off-by: Benoît Thébaudeau benoit.thebaudeau@advansee.com

Changes in v3:

• Rebase against latest u-boot-imx/master.
• Update copyright years.
• Rename the "ovride" command to "override" as it is nicer to read.
• For obvious safety reasons, ask the user to confirm each fuse

programming operation, unless the '-y' command line option was given, which can be used in scripts.

• Rename "row" to "word" since it is less confusing and it is vocabulary

common to iim and ocotp in the reference manuals.

• Add doc/README.fuse.

Changes in v2:

• Rebase against latest master.

README | 1 + common/Makefile | 1 + common/cmd_fuse.c | 214 ++++++++++++++++++++++++++++++++++++++++++++++ doc/README.fuse | 73 ++++++++++++++++ include/config_cmd_all.h | 1 + include/fuse.h | 49 +++++++++++ 6 files changed, 339 insertions(+) create mode 100644 common/cmd_fuse.c create mode 100644 doc/README.fuse create mode 100644 include/fuse.h

FYI, I have started to work on the OCOTP stuff too with this API. I attach the corresponding README that I made.

I will resume my work on this subject in about two weeks. This will be either a v4 or a new series, depending on what the v3 became in the meantime.

Forget this v3. I will drop the bit interface in v4. It is redundant and not very useful, except to reduce the human error factor when playing with a single fuse, and people are supposed to know what they're doing, so...

Best regards, Benoît