Lines Matching refs:read
37 …key``. Disable default read and write protecting of the key. If this option is not set, once the k…
39 …read-protect``. Disable read-protecting of the key. The key remains readable software. The key wit…
50 …Keys for ``flash_encryption`` and ``secure_boot_v1`` will be burned as read and write protected. T…
56 …cryption and secure boot v2 keys because byte order will be incorrect and read protection will not…
68 …tracted from the given file and written into a eFuse block with write and read protection enabled.…
103 …s of this key will be burned to the low part of the eFuse block. These bits will be read protected.
118 Only flash encryption key is read protected if ``--no-read-protect`` is not used.
133 By default, when an encryption key block is burned it is also read and write protected.
137 …The ``--no-protect-key`` option will disable this behaviour (you can separately read or write prot…
141 …The ``--no-read-protect`` and ``--no-write-protect`` options will disable this behaviour (you can …
153 …reverses the bytes when writing. For this reason, an unprotected key will read back in the reverse…
176 Disabling read to key block
180 The key block will be read and write protected
190 BURN BLOCK1 - OK (write block == read block)
191 BURN BLOCK0 - OK (write block == read block)
231 BURN BLOCK1 - OK (write block == read block)
248 This example uses ``--no-read-protect`` to expose the byte order written into eFuse blocks.
259 … espefuse.py burn_key BLOCK_KEY0 ~/esp/tests/efuse/512bits_0.bin XTS_AES_256_KEY --no-read-protect
276 Keys will remain readable (due to --no-read-protect)
287 BURN BLOCK5 - OK (write block == read block)
288 BURN BLOCK4 - OK (write block == read block)
289 BURN BLOCK0 - OK (write block == read block)
329 Disabling read to key block
343 BURN BLOCK3 - OK (write block == read block)
344 BURN BLOCK0 - OK (write block == read block)