Home
last modified time | relevance | path

Searched refs:write (Results 1 – 25 of 118) sorted by relevance

12345

/hal_espressif-latest/tools/esptool_py/docs/en/espefuse/
Dburn-key-digest-cmd.rst24 :esp32: - ``--no-protect-key``. Disable default read and write protecting of the key.
25 …write-protect``. Disable write-protecting of the key. The key remains writable. The keys use the R…
27 …-write-always``. Write the eFuse key even if it looks like it is already been written, or is write…
38 The secure boot v2 key(s) will be readable and write protected.
52 Disabling write to efuse BLOCK2...
62 BURN BLOCK2 - OK (write block == read block)
63 BURN BLOCK0 - OK (write block == read block)
84 Disabling write to key block
94 BURN BLOCK3 - OK (write block == read block)
95 BURN BLOCK0 - OK (write block == read block)
[all …]
Dread-write-protections-cmd.rst1 .. _read-write-protections-cmd:
9 - ``espefuse.py write_protect_efuse``. It sets write protection for given eFuse names.
19 Not all eFuses have read and write protections. See the help for these commands for the eFuse names…
21 eFuses are often read/write protected as a group, so protecting one of eFuse will result in some re…
35 - ``R/-`` indicates that write protection is set. No further bits can be set.
36 - ``-/-`` means both read and write protection are set.
58 BURN BLOCK0 - OK (write block == read block)
68 Permanently write-disabling efuse WR_DIS
69 Permanently write-disabling efuses FLASH_CRYPT_CNT, UART_DOWNLOAD_DIS
78 BURN BLOCK0 - OK (write block == read block)
Dburn-key-cmd.rst37 …:esp32: - ``--no-protect-key``. Disable default read and write protecting of the key. If this opti…
38 …write-protect``. Disable write-protecting of the key. The key remains writable. The keys use the R…
40 …-write-always``. Write the eFuse key even if it looks like it is already been written, or is write…
50 …Keys for ``flash_encryption`` and ``secure_boot_v1`` will be burned as read and write protected. T…
52 …Key for ``secure_boot_v2`` will be burned only as write protected. The key must be readable becaus…
60 …rn operation this eFuse key purpose is burned as well with write protection (the ``--no-write-prot…
68 … key is extracted from the given file and written into a eFuse block with write and read protectio…
77 …his is a virtual key purpose for flash encryption key. This allows you to write a whole 512-bit ke…
116 All keys will be burned with write protection if ``--no-write-protect`` is not used.
133 By default, when an encryption key block is burned it is also read and write protected.
[all …]
Dburn-custom-mac-cmd.rst14 …-write-always``. Write the eFuse key even if it looks like it is already been written, or is write…
16 …write new data without breaking the encoding. The correct way is to contact Espressif to order chi…
42 BURN BLOCK3 - OK (write block == read block)
75 (to write): 0x0400000000000000
82 BURN BLOCK1 - OK (write block == read block)
83 BURN BLOCK0 - OK (all write block bits are set)
112 BURN BLOCK3 - OK (write block == read block)
Dburn-bit-cmd.rst15 …force-write-always``. Burn it even if it looks like it is already been written, or is write protec…
38 BURN BLOCK2 - OK (write block == read block)
72 BURN BLOCK3 - OK (write block == read block)
73 BURN BLOCK2 - OK (write block == read block)
Dburn-block-data-cmd.rst19 …-write-always``. Write the eFuse key even if it looks like it is already been written, or is write…
38 BURN BLOCK3 - OK (write block == read block)
Dsummary-cmd.rst24 3. This column has human readable value, read/write protection status, raw value (hexadecimal or bi…
38 - ``R/-`` indicates that write protection is set. No further bits can be set.
39 - ``-/-`` means both read and write protection are set.
41 Some eFuses have no protection at all, and some eFuses have only one read or write protection. Ther…
Dcheck-error-cmd.rst84 BURN BLOCK3 - OK (write block == read block)
88 BURN BLOCK2 - OK (write block == read block)
92 BURN BLOCK1 - OK (write block == read block)
/hal_espressif-latest/tools/idf_monitor/idf_monitor_base/
Dansi_color_converter.py74 self.output.write(data.decode()) # type: ignore
76 self.output.write(data) # type: ignore
87 self.output.write('?') # type: ignore
89 def write(self, data): # type: ignore member in ANSIColorConverter
Doutput_helpers.py46 sys.stderr.write('%s%s%s%s' % (color, message, ANSI_NORMAL, newline))
50 sys.stderr.write(ANSI_NORMAL + message)
/hal_espressif-latest/tools/esptool_py/esp_rfc2217_server/
Dredirector.py56 self.write(b"".join(self.rfc2217.escape(data)))
64 def write(self, data): member in Redirector
76 self.serial.write(b"".join(self.rfc2217.filter(data)))
/hal_espressif-latest/components/bt/host/bluedroid/btc/profile/std/gatt/
Dbtc_gattc.c830 tBTA_GATTC_WRITE *write = &arg->write; in btc_gattc_cb_handler() local
834 gattc_if = BTC_GATT_GET_GATT_IF(write->conn_id); in btc_gattc_cb_handler()
835 param.write.conn_id = BTC_GATT_GET_CONN_ID(write->conn_id); in btc_gattc_cb_handler()
836 param.write.status = write->status; in btc_gattc_cb_handler()
837 param.write.handle = write->handle; in btc_gattc_cb_handler()
838 param.write.offset = write->offset; in btc_gattc_cb_handler()
891 tBTA_GATTC_WRITE *write = &arg->write; in btc_gattc_cb_handler() local
893 gattc_if = BTC_GATT_GET_GATT_IF(write->conn_id); in btc_gattc_cb_handler()
894 param.write.conn_id = BTC_GATT_GET_CONN_ID(write->conn_id); in btc_gattc_cb_handler()
895 param.write.status = write->status; in btc_gattc_cb_handler()
[all …]
/hal_espressif-latest/components/spi_flash/sim/
Dflash_mock.cpp122 return spiflash.write(target, src, len); in esp_rom_spiflash_write()
127 return spiflash.write(address, buffer, length); in esp_flash_write()
132 return spiflash.write(flash_addr, data, len); in esp_rom_spiflash_write_encrypted()
/hal_espressif-latest/components/mbedtls/esp_crt_bundle/
Dgen_crt_bundle.py47 sys.stderr.write('gen_crt_bundle.py: ')
48 sys.stderr.write(msg)
49 sys.stderr.write('\n')
208 f.write(crt_bundle)
/hal_espressif-latest/zephyr/scripts/pinctrl/
Desp_genpinctrl.py130 f.write(file_out_head.replace('{SOC}', soc.upper()))
144 f.write(pinmux)
146 f.write(file_out_tail.replace('{SOC}', soc.upper()))
/hal_espressif-latest/tools/esptool_py/espsecure/
D__init__.py151 f.write(iv)
154 f.write(word[::-1]) # swap word order in the result
155 f.write(b"\xFF" * (0x1000 - f.tell())) # pad to 0x1000
156 f.write(plaintext_image)
163 f.write(sk.to_pem())
189 f.write(private_key)
392 outfile.write(binary_content)
393 outfile.write(
396 outfile.write(signature)
536 f.write(contents + signature_sector)
[all …]
/hal_espressif-latest/tools/esptool_py/esptool/
Dbin_image.py296 f.write(struct.pack("<II", segment.addr, len(segment_data)))
297 f.write(segment_data)
336 f.write(struct.pack(b"B", checksum))
339 f.write(
485 f.write(irom_segment.data)
583 f.write(
616 f.write(struct.pack(b"<I", crc))
892 f.write(bytes([len(ram_segments)]))
894 f.write(bytes([total_segments]))
901 f.write(digest.digest())
[all …]
/hal_espressif-latest/components/bt/host/bluedroid/btc/profile/std/spp/
Dbtc_spp.c885 slot = spp_find_slot_by_handle(arg->write.handle); in btc_spp_write()
907 BTA_JvRfcommWrite(arg->write.handle, slot->id, item_size, data); in btc_spp_write()
910 if (fixed_queue_enqueue(slot->tx.queue, arg->write.p_data, 0)) { in btc_spp_write()
911 BTA_JvRfcommWrite(arg->write.handle, slot->id, arg->write.len, arg->write.p_data); in btc_spp_write()
921 param.write.status = ret; in btc_spp_write()
922 param.write.handle = 0; in btc_spp_write()
923 param.write.len = -1; in btc_spp_write()
924 param.write.cong = false; in btc_spp_write()
947 dst->write.p_data = (uint8_t *)osi_malloc(src->write.len); in btc_spp_arg_deep_copy()
948 if (dst->write.p_data) { in btc_spp_arg_deep_copy()
[all …]
/hal_espressif-latest/components/spi_flash/
DKconfig21 When brownout happens during flash erase/write operations,
87 bool "Auto suspend long erase/write operations (READ DOCS FIRST)"
135 If this option is enabled, if SPI flash write verification fails then a log error line
144 … If this option is enabled, any SPI flash write which tries to set zero bits in the flash to
149 … Note that some software (such as SPIFFS) which is aware of SPI NOR flash may write one bits as an
171 This option should be enabled, if any one of the following is true: (1) need to write
202 It is not recommended to ever write to these regions from an IDF app,
268 int "Flash write chunk size"
272 Flash write is broken down in terms of multiple (smaller) write operations.
273 This configuration options helps to set individual write chunk size, smaller
[all …]
Desp_flash_api.c105 … time=%8ldus bytes=%8ld\n", esp_flash_stats.write.count, esp_flash_stats.write.time, esp_flash_st… in esp_flash_dump_counters()
1013 VERIFY_CHIP_OP(write); in esp_flash_write()
1076 err = chip->chip_drv->write(chip, write_buf, write_addr, write_len); in esp_flash_write()
1079 COUNTER_ADD_BYTES(write, write_len); in esp_flash_write()
1111 COUNTER_STOP(write); in esp_flash_write()
1117 COUNTER_STOP(write); in esp_flash_write()
1227 VERIFY_CHIP_OP(write); in esp_flash_write_encrypted()
1379 COUNTER_ADD_BYTES(write, encrypt_byte); in esp_flash_write_encrypted()
1401 COUNTER_STOP(write); in esp_flash_write_encrypted()
1409 COUNTER_STOP(write); in esp_flash_write_encrypted()
/hal_espressif-latest/tools/esptool_py/docs/en/
Dindex.rst8 * Read, write, erase, and verify binary data stored in flash.
10 * Read and write the one-time-programmable efuses.
/hal_espressif-latest/components/spi_flash/include/
Desp_spi_flash_counters.h31 esp_flash_counter_t write; member
/hal_espressif-latest/components/bt/host/nimble/port/src/
Dnvs_port.c36 cache_fn.write = nvs_set_blob; in link_storage_fn()
/hal_espressif-latest/tools/esptool_py/test/
Dtest_merge_bin.py211 f.write(hex)
257 hex.write(merged)
272 f.write(b":")
328 f.write(data)
336 f.write(struct.pack("B", random.randrange(0, 1 << 7)))
/hal_espressif-latest/components/xtensa/trax/
Dtraceparse.py280 … sys.stderr.write('Failed to parse message #%03d (at %d bytes): %s\n' % (msg_cnt, i, str(e)))
316 sys.stderr.write('Loaded %d messages in %d bytes\n' % (len(messages), len(data)))
333 sys.stderr.write('Usage: %s <dump_file>\n')

12345