Home
last modified time | relevance | path

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

/hal_espressif-3.5.0/.gitlab/ci/dependencies/
DREADME.md86 - 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.5.0/components/esptool_py/esptool/docs/en/espefuse/
Dburn-key-cmd.rst20 …binary file. It must contain 256 bits of binary key if the coding scheme is ``None`` and 128 bits …
39 …e-write-always``. Write the eFuse key even if it looks like it is already been written, or is writ…
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.
97 All keys will be burned with write protection if ``--no-write-protect`` is not used.
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.
139 Normally, a key will only be burned if the efuse block has not been previously written to. The ``--…
141 …llow any eFuse bits to be cleared 1->0, and can not write anything to write protected eFuse blocks.
[all …]
Dburn-block-data-cmd.rst19 …e-write-always``. Write the eFuse key even if it looks like it is already been written, or is writ…
45 1. Data is written to the eFuse block in normal byte order (treating the eFuse block as if it was a…
Dburn-bit-cmd.rst15 - ``--force-write-always``. Burn it even if it looks like it is already been written, or is write p…
Dsummary-cmd.rst18 …ditional information: the block name associated with this eFuse field and encoding errors (if any).
27 …gh hardware may use the correct value. In espefuse v2.6 and newer, read-protected eFuse values are…
Dburn-custom-mac-cmd.rst14 …e-write-always``. Write the eFuse key even if it looks like it is already been written, or is writ…
Dburn-key-digest-cmd.rst27 …e-write-always``. Write the eFuse key even if it looks like it is already been written, or is writ…
37 The secure boot v2 key(s) will be readable and write protected.
/hal_espressif-3.5.0/.gitlab/ci/
DREADME.md5 - [What if Expected Jobs ARE NOT Created?](#what-if-expected-jobs-are-not-created)
13 - [How to Add a New `if` Anchor?](#how-to-add-a-new-if-anchor)
16 - [`if` Anchors Naming Rules](#if-anchors-naming-rules)
28 4. if you push a new commit, a new pipeline will be created automatically.
30 ## What if Expected Jobs ARE NOT Created?
80 - `pattern`: Defined in an array. A GitLab job will be created if the changed files in this MR matc…
87 - `label`: Defined in an if clause, similar as the previous bot command. A GitLab job will be creat…
90 .if-label-build_docs: &if-label-build_docs
91 …if: '$BOT_LABEL_BUILD_DOCS || $CI_MERGE_REQUEST_LABELS =~ /^(?:[^,\n\r]+,)*build_docs(?:,[^,\n\r]+…
99 - <<: *if-protected
[all …]
/hal_espressif-3.5.0/
DKconfig26 # It is not updated if environment variable $IDF_TARGET changes later, and
34 default "y" if IDF_TARGET="esp32"
39 default "y" if IDF_TARGET="esp32s2"
45 default "y" if IDF_TARGET="esp32s3"
50 default "y" if IDF_TARGET="esp32c3"
56 default "y" if IDF_TARGET="esp32h2"
62 default "y" if IDF_TARGET="linux"
66 default 0x0000 if IDF_TARGET_ESP32
67 default 0x0002 if IDF_TARGET_ESP32S2
68 default 0x0005 if IDF_TARGET_ESP32C3
[all …]
D.pylintrc58 # disable everything first and then reenable specific checks. For example, if
192 # inconsistent-return-statements if a never returning function is called then
211 # mixin class is detected if its name ends with "mixin" (case insensitive).
301 # Allow the body of a class to be on the same line as the declaration if body
305 # Allow the body of an if to be on the same line as the test if there is no
307 single-line-if-stmt=no
513 # Maximum number of boolean expressions in an if statement (see R0916).
546 # List of member names, which should be excluded from the protected access
548 exclude-protected=_asdict,
/hal_espressif-3.5.0/docs/en/contribute/
Dstyle-guide.rst66 if (condition) { // correct
101 Note however that if someone goes to add new line with a longer identifier as first argument (e.g. …
103 Therefore, use horizontal alignment sparingly, especially if you expect new lines to be added to th…
128 if (condition) {
130 } else if (other_condition) {
161 …#if 0 ... #endif`` blocks. Remove code block completely if it is not used. Otherwise, add comment …
247 …t this. However the function ``do_something()`` must still be called, even if assertions are disab…
255 If the variable is declared separately, for example if it is used for multiple assertions, then it …
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…
[all …]
/hal_espressif-3.5.0/docs/en/security/
Dflash-encryption.rst29 - Secure Boot bootloader digest if Secure Boot is enabled (see below).
100 …- Enables encryption and decryption, when an SPI boot mode is set. Feature is enabled if 1 or 3 bi…
122 …- Enables encryption and decryption, when an SPI boot mode is set. Feature is enabled if 1 or 3 bi…
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…
264 At this stage, if you need to update and re-flash binaries, see :ref:`encrypt-partitions`.
294 …else if :ref:`Size of generated AES-XTS key <CONFIG_SECURE_FLASH_ENCRYPTION_KEYSIZE>` is AES-256 (…
[all …]
Dsecure-boot-v1.rst20 - 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 …E_0 efuse. The software bootloader then becomes protected (the chip will only boot a bootloader im…
55 …:`secure-boot-reflashable`). The Efuse holding this key is read & write protected (preventing soft…
87 4. The first time you run ``make``, if the signing key is not found then an error message will be p…
103 .. note:: ``idf.py flash`` doesn't flash the bootloader if secure boot is enabled.
203 …protected, which prevents software access. For full details of this algorithm see `Secure Bootload…
249 …l automatically sign an app image if secure boot is enabled. ``idf.py bootloader`` will produce a …
Dsecure-boot-v2.rst12 …re Boot <secure-boot-v1>`. It is recommended that users use Secure Boot V2 if they have a chip ver…
154 A signature block is “valid” if the first byte is 0xe7 and a valid CRC32 is stored at offset 1196. …
161 An image is “verified” if the public key stored in any signature block is valid for this device, an…
201 The key(s) must be readable in order to give software access to it. If the key(s) is read-protected…
228 6. The first time you run ``make`` or ``idf.py build``, if the signing key is not found then an err…
242 .. note:: ``idf.py flash`` doesn't flash the bootloader if Secure Boot is enabled.
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.
311 …* The KEY_DIGESTs should be numbered sequentially beginning at key digest #0. (i.e., if key digest…
313 …securely elsewhere), however they may be signed with multiple private keys if some are being revok…
[all …]
/hal_espressif-3.5.0/components/fatfs/
DKconfig62 default 0 if FATFS_CODEPAGE_DYNAMIC
63 default 437 if FATFS_CODEPAGE_437
64 default 720 if FATFS_CODEPAGE_720
65 default 737 if FATFS_CODEPAGE_737
66 default 771 if FATFS_CODEPAGE_771
67 default 775 if FATFS_CODEPAGE_775
68 default 850 if FATFS_CODEPAGE_850
69 default 852 if FATFS_CODEPAGE_852
70 default 855 if FATFS_CODEPAGE_855
71 default 857 if FATFS_CODEPAGE_857
[all …]
/hal_espressif-3.5.0/docs/en/api-guides/
Derror-handling.rst20 - CPU exceptions: access to protected regions of memory, illegal instruction, etc.
42 …https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/errno.h.html>`_, if no matching ``ESP_ER…
83 :cpp:func:`ESP_RETURN_ON_ERROR` macro checks the error code, if the error code is not equal :c:macr…
90 :cpp:func:`ESP_GOTO_ON_ERROR` macro checks the error code, if the error code is not equal :c:macro:…
97 :cpp:func:`ESP_RETURN_ON_FALSE` macro checks the condition, if the condition is not equal `true`, i…
104 :cpp:func:`ESP_GOTO_ON_FALSE` macro checks the condition, if the condition is not equal `true`, it …
119 …ESP_ERROR_CHECK(x); // err message printed if `x` is not `…
120 …ESP_ERROR_CHECK_WITHOUT_ABORT(x); // err message printed if `x` is not `…
121 …ESP_RETURN_ON_ERROR(x, TAG, "fail reason 1"); // err message printed if `x` is not `…
122 …ESP_GOTO_ON_ERROR(x, err, TAG, "fail reason 2"); // err message printed if `x` is not `…
[all …]
Dunit-tests.rst101 …eed to check if reset happens). Sometimes we expect to run some specific tests after certain kinds…
126 #if !TEMPORARY_DISABLED_FOR_TARGETS(ESP32, ESP8266)
134 #if SOC_SDIO_SLAVE_SUPPORTED
135 #if !TEMPORARY_DISABLED_FOR_TARGETS(ESP64)
147 …32`` just to avoid building it on esp32s2, it's hard to make the code tidy if you want to enable t…
149 …if !disabled`` is preferred to white-list style ``#if CONFIG_IDF_TARGET_xxx``, since you will not …
157 …ep in the test process, you can have different implementation code protected by ``#if CONFIG_IDF_T…
246 …s case again and input ``2`` to run the second stage. The case only passes if the last stage passe…
256 However, if the instruction or data is not in cache, it needs to be fetched from external memory (i…
277 …ng its own event counters that are independent of each other. For example, if ``ccomp_timer_start`…
[all …]
/hal_espressif-3.5.0/docs/en/api-reference/peripherals/
Dhmac.rst62 The calculation only proceeds if the provided key purpose matches the purpose stored in the eFuses …
90 The third application is using the HMAC as a key to enable JTAG if it was soft-disabled before.
97 3. Configure the eFuse key block to be read protected using the esp_efuse_set_read_protect(), so th…
126 if (ets_status == ESP_OK) {
145 if (result == ESP_OK) {
/hal_espressif-3.5.0/docs/en/api-reference/provisioning/
Dprovisioning.rst10 …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…
76 …thentication (through proof-of-possession) if the application does not use the transport level sec…
/hal_espressif-3.5.0/components/bootloader/
DKconfig.projbuild5 default 0x1000 if IDF_TARGET_ESP32 || IDF_TARGET_ESP32S2
58 default 0 if BOOTLOADER_LOG_LEVEL_NONE
59 default 1 if BOOTLOADER_LOG_LEVEL_ERROR
60 default 2 if BOOTLOADER_LOG_LEVEL_WARN
61 default 3 if BOOTLOADER_LOG_LEVEL_INFO
62 default 4 if BOOTLOADER_LOG_LEVEL_DEBUG
63 default 5 if BOOTLOADER_LOG_LEVEL_VERBOSE
68 default y if BOOTLOADER_SPI_WP_PIN != 7 # backwards compatibility, can remove in IDF 5
71 … This setting is only used if the SPI flash pins have been overridden by setting the eFuses
76 for external SPIRAM if it is enabled.
[all …]
/hal_espressif-3.5.0/docs/en/api-reference/system/
Dipc.rst28 - The IPC feature is internally protected by a mutex. Therefore, simultaneous IPC calls from two or…
100 …h registers available for use is sufficient for most simple use cases. But if your callback requir…
/hal_espressif-3.5.0/docs/en/api-reference/storage/
Dnvs_flash.rst18 .. note:: if an NVS partition is truncated (for example, when the partition table layout is changed…
43 Data type check is also performed when reading a value. An error is returned if the data type of th…
68 …ash encryption system. However, data can still be stored in encrypted form if NVS encryption is us…
72 … This should not result in loss of data, except for the new key-value pair if it was being written…
80 …quired for NVS encryption are stored in yet another partition, which is protected using :doc:`Flas…
82 …e default NVS partition. It is important to encrypt them as default choice if platform level encry…
167 …The example also shows how to check if a read / write operation was successful, or if a certain va…
176 …The example also shows how to implement the diagnostic procedure to check if the read / write oper…
230 …ommodate flash chips with different sector sizes (although it is not clear if other components in …
253 …tate bitmap are always written to flash unencrypted. Entries are encrypted if flash encryption fea…
[all …]
Dspi_flash.rst23 … implementation before ESP-IDF v4.0. However, the code size may get bigger if you use the new API …
25 Encrypted reads and writes use the old implementation, even if :ref:`CONFIG_SPI_FLASH_USE_LEGACY_IM…
237 Additionally, all API functions are protected with a mutex (``s_flash_op_mutex``).
/hal_espressif-3.5.0/docs/en/api-reference/protocols/
Dmodbus.rst70 if (master_handler == NULL || err != ESP_OK) {
81 if (slave_handler == NULL || err != ESP_OK) {
144 It is optional field and can be set to zero if the parameter is not used in the application.
162 …`param_key`` have to be unique. Please use the prefix to the parameter key if you have several sim…
314 if (err != ESP_OK) {
337 if ((err != ESP_ERR_NOT_FOUND) && (param_descriptor != NULL)) {
339 if (err == ESP_OK) {
367 if (err == ESP_OK) {
459 Direct access to register area from user application must be protected by critical section:
573 if (event & (MB_EVENT_HOLDING_REG_WR | MB_EVENT_HOLDING_REG_RD)) {
[all …]
/hal_espressif-3.5.0/components/freertos/
DHistory.txt189 + Update the method used to detect if a timer is active. Previously the
190 timer was deemed to be inactive if it was not referenced from a list.
206 + Fixed issues in memory protected ports related to different combinations
211 + Change the method used to determine if a timer is active or not from just
212 seeing if it is referenced from the active timer list to storing its
218 in xTaskRemoveFromEventList() if the scheduler is not suspended.
242 struct to be renamed - set configENABLE_BACKWARD_COMPATIBILITY to 1 if
262 configMESSAGE_BUFFER_LENGTH_TYPE default to size_t, but if, for example,
288 + Fix position of "#if defined( __cplusplus )" in stream_buffer.h.
293 + Introduce #error if stream_buffer.c is built without
[all …]