protected (reference) in projects: hal_espressif-3.4.0

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:protected (Results 1 – 25 of 36) sorted by relevance

/hal_espressif-3.4.0/components/esptool_py/esptool/docs/en/espefuse/
D	read-write-protections-cmd.rst	`6 There are two commands (to get the correct list of eFuse fields that can be protected, specify the … 19 …d and write protections. See the help for these commands for the eFuse names that can be protected. 21 …protected as a group, so protecting one of eFuse will result in some related eFuses becoming prote… 28 …gh hardware may use the correct value. In espefuse v2.6 and newer, read-protected eFuse values are…`
D	burn-key-cmd.rst	39 …eFuse key even if it looks like it is already been written, or is write protected. Note that this … 48 …Keys for ``flash_encryption`` and ``secure_boot_v1`` will be burned as read and write protected. T… 50 …Key for ``secure_boot_v2`` will be burned only as write protected. The key must be readable becaus… 84 …s of this key will be burned to the low part of the eFuse block. These bits will be read protected. 99 Only flash encryption key is read protected if ``--no-read-protect`` is not used. 114 By default, when an encryption key block is burned it is also read and write protected. 141 …llow any eFuse bits to be cleared 1->0, and can not write anything to write protected eFuse blocks. 160 The key block will be read and write protected
D	burn-bit-cmd.rst	`15 …. Burn it even if it looks like it is already been written, or is write protected. Note that this …`
D	burn-key-digest-cmd.rst	`27 …eFuse key even if it looks like it is already been written, or is write protected. Note that this … 37 The secure boot v2 key(s) will be readable and write protected.`
D	burn-block-data-cmd.rst	`19 …eFuse key even if it looks like it is already been written, or is write protected. Note that this …`
D	summary-cmd.rst	`27 …gh hardware may use the correct value. In espefuse v2.6 and newer, read-protected eFuse values are…`
D	burn-custom-mac-cmd.rst	`14 …eFuse key even if it looks like it is already been written, or is write protected. Note that this …`
D	dump-cmd.rst	`88 …d to write them back to another chip. Note that some blocks may be read-protected, in which case t…`
/hal_espressif-3.4.0/components/nvs_flash/src/
D	intrusive_list.h	`26 protected: 116 protected: 251 protected:`
/hal_espressif-3.4.0/tools/kconfig/
D	qconf.h	`54 protected: 257 protected: 281 protected: 314 protected:`
/hal_espressif-3.4.0/.gitlab/ci/dependencies/
D	README.md	86 - If a mapping key has postfix `-preview`, no `if-protected-xxx` clause will be added 87 … - else if a mapping key has postfix `-production`, an `if-protected-no_label` clause will be added 88 - else, an `if-protected` clause will be added
/hal_espressif-3.4.0/components/wear_levelling/private_include/
D	WL_Ext_Safe.h	`32 protected:`
D	Partition.h	`30 protected:`
D	WL_Ext_Perf.h	`36 protected:`
D	WL_Flash.h	`50 protected:`
/hal_espressif-3.4.0/components/spi_flash/
D	esp_flash_api.c	`569 uint64_t protected = 0; in esp_flash_erase_region() local 570 err = chip->chip_drv->get_protected_regions(chip, &protected); in esp_flash_erase_region() 571 if (err == ESP_OK && protected != 0) { in esp_flash_erase_region() 574 if ((protected & BIT64(i)) in esp_flash_erase_region()`
/hal_espressif-3.4.0/components/nvs_flash/test_nvs_host/
D	spi_flash_emulation.h	`226 protected:`
/hal_espressif-3.4.0/.gitlab/ci/
D	README.md	99 - <<: *if-protected 185 - `protected`
/hal_espressif-3.4.0/
D	Kconfig	`351 buffers larger than 8 bytes are protected. 354 … to be protected -- those that have local array definitions, or have references to local frame 357 - In OVERALL mode (GCC flag: -fstack-protector-all) all functions are protected.`
/hal_espressif-3.4.0/docs/en/security/
D	flash-encryption.rst	149 …-flash encrypted binaries. Also, the ``{IDF_TARGET_CRYPT_CNT}`` eFuse bits are NOT write-protected. 161 …ne or two `BLOCK_KEYN` eFuses are set. ``KEY_PURPOSE_N`` field is write-protected as well. The fla… 167 …binaries. Also, the ``{IDF_TARGET_CRYPT_CNT}`` eFuse bits are NOT write-protected. In addition, th… 179 …n bits for `BLOCK_KEYN` eFuse are set. ``KEY_PURPOSE_N`` field is write-protected as well. The fla… 185 …binaries. Also, the ``{IDF_TARGET_CRYPT_CNT}`` eFuse bits are NOT write-protected. In addition, th… 704 …the ``flash_encryption`` eFuse internal to the chip and, by default, is protected from software ac… 708 …e or two ``BLOCK_KEYN`` eFuses internal to the chip and, by default, is protected from software ac… 710 …ed in one ``BLOCK_KEYN`` eFuse internal to the chip and, by default, is protected from software ac… 929 …ion key is stored in the ``flash_encryption`` eFuse and, by default, is protected from further wri… 966 …n key is stored in one or two ``BLOCK_KEYN`` eFuses and, by default, is protected from further wri… [all …]
D	secure-boot-v1.rst	20 - Most data is stored in flash. Flash access does not need to be protected from physical access in … 41 …cure bootloader key (generated via hardware RNG, then stored read/write protected in efuse), and a… 44 …t by burning the ABS_DONE_0 efuse. The software bootloader then becomes protected (the chip will o… 55 …:`secure-boot-reflashable`). The Efuse holding this key is read & write protected (preventing soft… 203 … stored in Efuse block 2. The key in Efuse can (& should) be read/write protected, which prevents …
D	secure-boot-v2.rst	201 The key(s) must be readable in order to give software access to it. If the key(s) is read-protected… 257 …protected. (If :doc:`/security/flash-encryption` is enabled then the bootloader will ensure that a… 308 * The KEY_DIGEST eFuses should be write protected after being programmed.
/hal_espressif-3.4.0/docs/en/contribute/
D	style-guide.rst	335 * First put the public members, then the protected, then private ones. Omit public, protected or pr… 367 * Put ``public``, ``protected`` and ``private`` labels at the same indentation level as the corresp…
/hal_espressif-3.4.0/docs/en/api-reference/provisioning/
D	provisioning.rst	`10 …rovisioning process. Some applications may work with SoftAP that's WPA2 protected or BLE with "jus… 75 1. Transport Security: SoftAP provisioning may choose WPA2 protected security with unique per-dev…`
/hal_espressif-3.4.0/components/fatfs/
D	Kconfig	`128 int "Number of simultaneously open files protected by lock function"`

TraceRecorderSource-2.7.6
TraceRecorderSource-3.4.0
Zephyr-Core-2.7.6
Zephyr-Core-3.4.0
Zephyr-Core-3.5.0
Zephyr-Core-3.6.0
Zephyr-Core-3.7.0
acpica-3.5.0
acpica-3.6.0
acpica-3.7.0
babblesim_base-3.4.0
babblesim_base-3.6.0-3.5.0
babblesim_base-3.7.0
babblesim_ext_2G4_channel_NtNcable-3.7.0-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_channel_multiatt-3.4.0
babblesim_ext_2G4_channel_multiatt-3.7.0-3.6.0-3.5.0
babblesim_ext_2G4_device_WLAN_actmod-3.7.0-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_device_burst_interferer-3.7.0-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_device_playback-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_device_playback-3.7.0
babblesim_ext_2G4_libPhyComv1-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_libPhyComv1-3.7.0
babblesim_ext_2G4_modem_BLE_simple-3.4.0
babblesim_ext_2G4_modem_BLE_simple-3.6.0-3.5.0
babblesim_ext_2G4_modem_BLE_simple-3.7.0
babblesim_ext_2G4_modem_magic-3.6.0-3.5.0-3.4.0
babblesim_ext_2G4_modem_magic-3.7.0
babblesim_ext_2G4_phy_v1-3.4.0
babblesim_ext_2G4_phy_v1-3.6.0-3.5.0
babblesim_ext_2G4_phy_v1-3.7.0
babblesim_ext_libCryptov1-3.7.0-3.6.0-3.5.0-3.4.0
bsim-3.4.0
bsim-3.6.0-3.5.0
bsim-3.7.0
canopennode-2.7.6
canopennode-3.5.0-3.4.0
chre-3.4.0
civetweb-2.7.6
cmsis-2.7.6
cmsis-3.4.0
cmsis-3.5.0
cmsis-3.7.0-3.6.0
cmsis-dsp-3.5.0
cmsis-dsp-3.7.0-3.6.0
cmsis-nn-3.6.0-3.5.0
cmsis-nn-3.7.0
edtt-2.7.6
edtt-3.6.0-3.5.0-3.4.0
edtt-3.7.0
fatfs-2.7.6
fatfs-3.7.0-3.6.0-3.5.0-3.4.0
hal_adi-3.7.0
hal_altera-2.7.6
hal_altera-3.6.0-3.5.0-3.4.0
hal_altera-3.7.0
hal_ambiq-3.5.0
hal_ambiq-3.6.0
hal_ambiq-3.7.0
hal_atmel-2.7.6
hal_atmel-3.5.0-3.4.0
hal_atmel-3.6.0
hal_atmel-3.7.0
hal_cypress-2.7.6
hal_espressif-2.7.6
hal_espressif-3.4.0
hal_espressif-3.5.0
hal_espressif-3.6.0
hal_espressif-3.7.0
hal_ethos_u-3.6.0-3.5.0-3.4.0
hal_ethos_u-3.7.0
hal_gigadevice-3.7.0-3.6.0-3.5.0-3.4.0
hal_infineon-2.7.6
hal_infineon-3.4.0
hal_infineon-3.5.0
hal_infineon-3.6.0
hal_infineon-3.7.0
hal_intel-3.5.0
hal_intel-3.6.0
hal_intel-3.7.0
hal_microchip-2.7.6
hal_microchip-3.6.0-3.5.0-3.4.0
hal_microchip-3.7.0
hal_nordic-2.7.6
hal_nordic-3.4.0
hal_nordic-3.5.0
hal_nordic-3.6.0
hal_nordic-3.7.0
hal_nuvoton-2.7.6
hal_nuvoton-3.4.0
hal_nuvoton-3.5.0
hal_nuvoton-3.6.0
hal_nuvoton-3.7.0
hal_nxp-2.7.6
hal_nxp-3.4.0
hal_nxp-3.5.0
hal_nxp-3.6.0
hal_nxp-3.7.0
hal_openisa-2.7.6
hal_openisa-3.5.0-3.4.0
hal_openisa-3.7.0-3.6.0
hal_quicklogic-3.6.0-3.5.0-3.4.0-2.7.6
hal_quicklogic-3.7.0
hal_renesas-3.4.0
hal_renesas-3.5.0
hal_renesas-3.6.0
hal_renesas-3.7.0
hal_rpi_pico-3.4.0
hal_rpi_pico-3.7.0-3.6.0-3.5.0
hal_silabs-2.7.6
hal_silabs-3.4.0
hal_silabs-3.5.0
hal_silabs-3.6.0
hal_silabs-3.7.0
hal_st-2.7.6
hal_st-3.4.0
hal_st-3.5.0
hal_st-3.6.0
hal_st-3.7.0
hal_stm32-2.7.6
hal_stm32-3.4.0
hal_stm32-3.5.0
hal_stm32-3.6.0
hal_stm32-3.7.0
hal_telink-2.7.6
hal_telink-3.6.0-3.5.0-3.4.0
hal_telink-3.7.0
hal_ti-2.7.6
hal_ti-3.4.0
hal_ti-3.7.0-3.6.0-3.5.0
hal_wurthelektronik-3.5.0-3.4.0
hal_wurthelektronik-3.7.0-3.6.0
hal_xtensa-2.7.6
hal_xtensa-3.4.0
hal_xtensa-3.5.0
hal_xtensa-3.6.0
hal_xtensa-3.7.0
hostap-3.6.0
hostap-3.7.0
liblc3-3.5.0-3.4.0
liblc3-3.7.0-3.6.0
libmetal-2.7.6
libmetal-3.5.0-3.4.0
libmetal-3.6.0
libmetal-3.7.0
littlefs-2.7.6
littlefs-3.5.0-3.4.0
littlefs-3.7.0-3.6.0
loramac-node-2.7.6
loramac-node-3.4.0
loramac-node-3.6.0-3.5.0
loramac-node-3.7.0
lvgl-2.7.6
lvgl-3.4.0
lvgl-3.5.0
lvgl-3.6.0
lvgl-3.7.0
lz4-3.4.0-2.7.6
mbedtls-2.7.6
mbedtls-3.4.0
mbedtls-3.5.0
mbedtls-3.6.0
mbedtls-3.7.0
mcuboot-2.7.6
mcuboot-3.4.0
mcuboot-3.5.0
mcuboot-3.6.0
mcuboot-3.7.0
mcumgr-2.7.6
mipi-sys-t-2.7.6
mipi-sys-t-3.4.0
mipi-sys-t-3.6.0-3.5.0
mipi-sys-t-3.7.0
nanopb-2.7.6
nanopb-3.4.0
net-tools-2.7.6
net-tools-3.4.0
net-tools-3.5.0
net-tools-3.6.0
net-tools-3.7.0
nrf_hw_models-2.7.6
nrf_hw_models-3.4.0
nrf_hw_models-3.5.0
nrf_hw_models-3.6.0
nrf_hw_models-3.7.0
open-amp-2.7.6
open-amp-3.4.0
open-amp-3.5.0
open-amp-3.6.0
open-amp-3.7.0
openthread-2.7.6
openthread-3.4.0
openthread-3.5.0
openthread-3.6.0
openthread-3.7.0
percepio-3.5.0
percepio-3.6.0
percepio-3.7.0
picolibc-3.5.0-3.4.0
picolibc-3.7.0-3.6.0
psa-arch-tests-3.4.0
segger-2.7.6
segger-3.4.0
segger-3.6.0-3.5.0
segger-3.7.0
sof-2.7.6
sof-3.4.0
tf-m-tests-3.4.0
tflite-micro-3.4.0-2.7.6
thrift-3.4.0
tinycbor-2.7.6
tinycrypt-3.6.0-3.5.0-3.4.0-2.7.6
tinycrypt-3.7.0
trusted-firmware-a-3.4.0
trusted-firmware-a-3.6.0-3.5.0
trusted-firmware-a-3.7.0
trusted-firmware-m-3.4.0
trusted-firmware-m-3.5.0
trusted-firmware-m-3.6.0
trusted-firmware-m-3.7.0
uoscore-uedhoc-3.4.0
uoscore-uedhoc-3.5.0
uoscore-uedhoc-3.6.0
uoscore-uedhoc-3.7.0
zcbor-3.5.0-3.4.0
zcbor-3.6.0
zcbor-3.7.0
zscilib-3.4.0