Searched refs:protect (Results 1 – 10 of 10) sorted by relevance
42 bool protect = rtc_wdt_get_protect_status(); in rtc_wdt_disable() local43 if (protect) { in rtc_wdt_disable()53 if (protect) { in rtc_wdt_disable()60 bool protect = rtc_wdt_get_protect_status(); in rtc_wdt_feed() local61 if (protect) { in rtc_wdt_feed()65 if (protect) { in rtc_wdt_feed()
37 …:esp32: - ``--no-protect-key``. Disable default read and write protecting of the key. If this opti…38 …:not esp32: - ``--no-write-protect``. Disable write-protecting of the key. The key remains writabl…39 …protect``. Disable read-protecting of the key. The key remains readable software. The key with key…60 …se key purpose is burned as well with write protection (the ``--no-write-protect`` flag has no eff…116 All keys will be burned with write protection if ``--no-write-protect`` is not used.118 Only flash encryption key is read protected if ``--no-read-protect`` is not used.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 …212 > espefuse.py burn_key flash_encryption 256bit_fe_key.bin --no-protect-key220 Key is left unprotected as per --no-protect-key argument.[all …]
24 :esp32: - ``--no-protect-key``. Disable default read and write protecting of the key.25 …:not esp32: - ``--no-write-protect``. Disable write-protecting of the key. The key remains writabl…26 …:not esp32: - ``--no-read-protect``. Disable read-protecting of the key. This option does not chan…
855 BLOCK3 {IMAGES_DIR}/256bit_2 --no-protect-key"1022 BLOCK3 {IMAGES_DIR}/192bit_2 --no-protect-key"1048 XTS_AES_256_KEY --no-read-protect --no-write-protect"1076 XTS_AES_256_KEY --no-read-protect --no-write-protect"1080 BLOCK_KEY5 {IMAGES_DIR}/256bit USER --no-read-protect --no-write-protect"1113 XTS_AES_256_KEY --no-read-protect --no-write-protect"1171 --no-read-protect"1519 BLOCK2 {S_IMAGES_DIR}/rsa_public_key_digest.bin --no-protect-key"1794 secure_boot_v1 {IMAGES_DIR}/256bit_1 --no-protect-key"1828 secure_boot_v2 {IMAGES_DIR}/256bit_1 --no-protect-key"[all …]
290 … esp_flash_set_protected_region(esp_flash_t *chip, const esp_flash_region_t *region, bool protect);
815 UINT8 protect = 0; in btc_a2dp_source_enc_update() local904 protect |= 1; in btc_a2dp_source_enc_update()912 protect |= 2; in btc_a2dp_source_enc_update()915 protect |= 3; in btc_a2dp_source_enc_update()921 if (protect == 3) { in btc_a2dp_source_enc_update()
821 …R esp_flash_set_protected_region(esp_flash_t *chip, const esp_flash_region_t *region, bool protect) in esp_flash_set_protected_region() argument840 if (protect) { in esp_flash_set_protected_region()
28 To protect your rights, we need to make restrictions that forbid39 We protect your rights with two steps: (1) copyright the software, and
128 To protect from BIAS attack during Legacy authentication,
943 … Boot is enabled. This may allow an attacker to read-protect the BLK2 efuse (for ESP32) and
