Boot Configurations Update – eFuse#

This section provides the commands to read and write eFuse data along with the list of the available configurations in eFuse that can be programmed by the user.

Once all the development and testing work is complete, the next step would be to program the eFuses. It is important to note that this is a permanent and one-time operation.

SiWG917 has eFuse memory of 1024 bytes. This memory is divided into four sections with control to enable write locks for each of these sections.

Note: You cannot write to eFuse through the M4 application image or through NWP via APIs. You must have an active JTAG connection to write the eFuse bits.

Read eFuse Data#

You can read the eFuse data/contents to an .json (for example, efuse_value.json) file. The command to read eFuse data is as follows.

Syntax:

commander manufacturing read efuse --out efuse_value.json -d <full opn>

Example:

commander manufacturing read efuse –out efuse_value.json -d SiWG917M111MGTBA

Write eFuse Data#

In the case of eFuse (one time programmable) data, simplicity commander CLI first checks whether the requested update is possible (since bits can only be set to 1 and never cleared). Then it will ask for your confirmation.

The possible eFuse configurations are mentioned in the section Possible Boot Configurations.

You can modify the eFuse bits in the efuse_value.json file which is read in the section Read eFuse Data and use the following command which are used to write efuse data into flash.

Syntax:

commander manufacturing write efuse --data efuse_value.json -d <OPN Number> [--skipload] [--pinset n] [-s jlinkserialno] [--noprompt] [--dryrun]

• --noprompt: It is possible to skip the confirmation, although users need to note that this is a one-time operation.

• --dryrun: It is possible to check the results of the operation before physically going ahead with the one-time programming.

Example:

commander manufacturing write efuse --data efuse_value.json -d SiWG917M111MGTBA -skipload --dryrun

Possible Boot Configurations#

The following table shows the available user configurable eFuse bits.

Note: The following fields can also be configured in MBR, you can modify them during development in the MBR and program in the eFuse once all the development and testing is completed.