Lines Matching refs:written

40 …e-always``. Write the eFuse key even if it looks like it is already been written, or is write prot…
41 …data). Enabled if --debug is used. Use this option to see the byte order of the data being written.
68 … or NIST256p curve. The private key is extracted from the given file and written into a eFuse bloc…
81 …e ``PEM`` file and writes the private key into a eFuse block. The key is written to the block in r…
88         ECDSA NIST192p private key in PEM format written to ecdsa192.pem
93         ECDSA NIST256p private key in PEM format written to ecdsa256.pem
120 …h encryption, will be burned in direct byte order. The encryption key is written in reverse byte o…
127 …s are 192-bits (24 bytes) long and an additional 64 bits of error correction data are also written.
153 …dware flash encryption and secure boot v1 features require the key to be written to the eFuse bloc…
158 Normally, a key will only be burned if the efuse block has not been previously written to. The ``--…
248     This example uses ``--no-read-protect`` to expose the byte order written into eFuse blocks.