Lines Matching refs:can
27 It can be list of key blocks and keyfiles (like BLOCK1 file1.bin BLOCK2 file2.bin etc.).
31 …It can be list of key blocks and keyfiles and key purposes (like BLOCK_KEY1 file1.bin USER BLOCK_K…
37 … protecting of the key. If this option is not set, once the key is flashed it can not be read back.
38 … coding scheme that does not support post-write data changes. Forced write can damage RS encoding …
40 …e it is already been written, or is write protected. Note that this option can't disable write pro…
68 …:esp32h2: - ECDSA_KEY. It can be ECDSA private keys based on NIST192p or NIST256p curve. The priva…
81 …ate keys based on the NIST192p or NIST256p curve. These two commands below can be used to generate…
97 …use key block (256 bits long). It is block #3 - ``BLOCK_KEY0``. This block can have user, flash en…
102 …- XTS_AES_128_KEY. 256 bits flash encryption key. The secure boot key can not be used with this op…
106 {IDF_TARGET_NAME} can have in eFuse block the following combination of keys:
137 …The ``--no-protect-key`` option will disable this behaviour (you can separately read or write prot…
141 …tect`` and ``--no-write-protect`` options will disable this behaviour (you can separately read or …
158 …ck has not been previously written to. The ``--force-write-always`` option can be used to ignore t…
160 … hardware - hardware does not allow any eFuse bits to be cleared 1->0, and can not write anything …
208 When the ``no protection`` option is used then you can see the burned key: