| /hal_espressif-3.6.0/components/esptool_py/esptool/docs/en/espefuse/ |
| D | burn-custom-mac-cmd.rst | 1 .. _burn-custom-mac-cmd:
3 Burn Custom Mac
6 The ``espefuse.py burn_custom_mac`` command burns a 48-bit Custom MAC Address.
10 * ``MAC``. Custom MAC Address (``CUSTOM_MAC``) to burn given in hexadecimal format with bytes separ…
32 - 'CUSTOM_MAC' (Custom MAC) 0x000000000000 -> 0x167215926348
33 - 'CUSTOM_MAC_CRC' (CRC of custom MAC) 0x00 -> 0x75
44 Custom MAC Address version 1: 48:63:92:15:72:16 (CRC 0x75 OK)
49 … Version of the MAC field = Custom MAC in BLOCK3 R/W …
50 …CUSTOM_MAC (BLOCK3): Custom MAC …
52 …CUSTOM_MAC_CRC (BLOCK3): CRC of custom MAC …
[all …]
|
| D | get-custom-mac-cmd.rst | 1 .. _get-custom-mac-cmd:
3 Get Custom Mac
6 The ``espefuse.py burn_custom_mac`` command prints the Custom MAC Address (``CUSTOM_MAC``).
17 Custom MAC Address version 1: 48:63:92:15:72:16 (CRC 0x75 OK)
19 …custom MAC address is not burned, then you will see the message "Custom MAC Address is not set in …
28 Custom MAC Address: 48:63:92:15:72:16 (OK)
30 …If the custom MAC address is not burned, then you will see the message "Custom MAC Address: 00:00:…
|
| /hal_espressif-3.6.0/examples/system/efuse/ |
| D | README.md | 5 …t demonstrates read and write operations with fields from the common and custom eFuse tables. For …
20 * The custom table (for custom purposes).
22 The custom table has five fields:
29 CUSTOM_SECURE_VERSION, EFUSE_BLK3, 78, 16, Custom secure version
74 * `CONFIG_EFUSE_CUSTOM_TABLE=y` - It allows using the custom table.
100 I (323) example: Uses common and custom tables
104 I (343) example: 3. read custom fields
112 I (383) example: write custom efuse fields
132 I (327) example: Uses common and custom tables
136 I (347) example: 3. read custom fields
[all …]
|
| /hal_espressif-3.6.0/components/efuse/ |
| D | CMakeLists.txt | 48 # Make custom files project/main/esp_efuse_custom_table.c and project/main/include/esp_efuse_custom…
49 # Path to CSV file is relative to project path for custom CSV files.
51 # Custom filename expands any path relative to the project
55 …add_custom_target(efuse-custom-table COMMAND "${python}" "${CMAKE_CURRENT_SOURCE_DIR}/efuse_table_…
57 add_deprecated_target_alias(efuse_custom_table efuse-custom-table)
59 add_custom_target(efuse-custom-table COMMAND)
60 add_deprecated_target_alias(efuse_custom_table efuse-custom-table)
|
| D | Kconfig | 4 bool "Use custom eFuse table"
10 string "Custom eFuse CSV file"
14 Name of the custom eFuse CSV filename. This path is evaluated
|
| /hal_espressif-3.6.0/examples/protocols/http_server/simple/main/ |
| D | main.c | 206 /* Set some custom headers */ in hello_get_handler()
207 httpd_resp_set_hdr(req, "Custom-Header-1", "Custom-Value-1"); in hello_get_handler()
208 httpd_resp_set_hdr(req, "Custom-Header-2", "Custom-Value-2"); in hello_get_handler()
210 /* Send response with custom headers and body set as the in hello_get_handler()
271 /* This handler allows the custom error handling functionality to be
274 * custom error handler http_404_error_handler() is registered.
275 * Afterwards, when /hello or /echo is requested, this custom error
279 * client to infer if the custom error handler is functioning as expected
318 /* Register the custom error handler */ in ctrl_put_handler()
325 /* Unregister custom error handler */ in ctrl_put_handler()
|
| /hal_espressif-3.6.0/examples/provisioning/legacy/custom_config/ |
| D | README.md | 1 # SoftAP + HTTPD based Provisioning Example featuring Custom configuration (Legacy)
11 …dded feature for configuration of some custom data (just like Wi-Fi configuration) during provisio…
19 …oning` which provides data structures and protocomm endpoint handlers for custom data configuration
68 …ters `--custom_info` and `--custom_ver` with your desired values for the custom configuration). As…
77 I (92734) app_prov_handler: Custom config received :
|
| /hal_espressif-3.6.0/tools/esp_prov/ |
| D | README.md | 22 | custom-config | http://ip:port/custom-config | Optional endpoint for configuring custom credentia…
61 …This flag assumes the provisioning app has an endpoint called `custom-config`. Use `--custom_info`…
64 …For specifying an information string to be sent to the `custom-config` endpoint during provisioning
67 …For specifying a version number (int) to be sent to the `custom-config` endpoint during provisioni…
|
| D | esp_prov.py | 183 response = tp.send_data('custom-config', message)
193 response = tp.send_data('custom-data', message)
377 …parser.add_argument('--custom_info', dest='custom_info', type=str, default='<some custom info stri…
379 … 'Custom Config Info String. "--custom_config" must be specified for using this'))
382 … 'Custom Config Version Number. "--custom_config" must be specified for using this'))
433 print('\n==== Sending Custom config to esp32 ====')
435 print('---- Error in custom config ----')
437 print('==== Custom config sent successfully ====')
440 print('\n==== Sending Custom data to esp32 ====')
442 print('---- Error in custom data ----')
[all …]
|
| /hal_espressif-3.6.0/components/tinyusb/ |
| D | Kconfig | 52 hex "VID: Custom vendor ID"
56 Custom Vendor ID.
65 hex "PID: Custom product ID"
69 Custom Product ID.
|
| /hal_espressif-3.6.0/tools/ci/python_packages/idf_http_server_test/ |
| D | client.py | 63 test_val('Response mismatch', 'Custom-Value-1', resp.getheader('Custom-Header-1')) and
64 test_val('Response mismatch', 'Custom-Value-2', resp.getheader('Custom-Header-2')) and
106 # and set 404 error handler to custom http_404_error_handler()
119 # But the custom error handler http_404_error_handler() will not close the
130 # that the custom error handler http_404_error_handler() would not have closed
137 # The custom error handler http_404_error_handler() will close the session
|
| /hal_espressif-3.6.0/examples/cxx/experimental/experimental_cpp_component/include/ |
| D | esp_event_api.hpp | 14 * custom event loop is used.
72 * @brief API version with custom event loop.
74 * It will direct calls to the custom event loop API.
76 …* This class also provides a run method in case the custom event loop was created without its own …
|
| /hal_espressif-3.6.0/examples/build_system/cmake/idf_as_lib/ |
| D | README.md | 4 # Using ESP-IDF in Custom CMake Projects
6 This example illustrates using ESP-IDF components as libraries in custom CMake projects. The applic…
93 … on using ESP-IDF in custom CMake projects in the programming guide under `API Guides` -> `Build S…
|
| /hal_espressif-3.6.0/components/partition_table/ |
| D | Kconfig.projbuild | 14 will copy one of these CSV files and create a custom partition CSV for
49 bool "Custom partition table CSV"
88 string "Custom partition CSV file" if PARTITION_TABLE_CUSTOM
91 Name of the custom partition CSV filename. This path is evaluated
|
| D | project_include.cmake | 13 # Custom filename expands any path relative to the project
19 "Change custom partition CSV path in menuconfig.")
58 # Add a custom target (see add_custom_target) that checks a given binary built by the build system
92 # Add a custom target (see add_custom_target) that checks a bootloader binary
|
| /hal_espressif-3.6.0/docs/en/api-guides/tools/ |
| D | idf-windows-installer.rst | 43 Custom Python and custom location of Python wheels
48 Following parameters allows to select custom Python and custom location of Python wheels:
|
| /hal_espressif-3.6.0/tools/esp_prov/prov/ |
| D | custom_prov.py | 16 # APIs for interpreting and creating protobuf packets for `custom-config` protocomm endpoint
31 # Form protobuf request packet from custom-config data
50 # Encrypt the custom data
|
| /hal_espressif-3.6.0/docs/en/api-reference/storage/ |
| D | spi_flash_override_driver.rst | 12 …2. Some IDF bug fixes to other chip drivers will not be automatically applied to your own custom c…
14 …hose new chip drivers into your custom chip driver list. Otherwise the driver will only search for…
17 Steps For Creating Custom Chip Drivers and Overriding the IDF Default Driver List
|
| /hal_espressif-3.6.0/components/esp_local_ctrl/include/ |
| D | esp_local_ctrl.h | 245 * This sets protocom security version, sec0/sec1 or custom
246 * If custom, user must provide handle via `proto_sec_custom_handle` below
251 * Custom security handle if security is set custom via `proto_sec` above
352 * @brief Register protocomm handler for a custom endpoint
357 * @note In case of BLE transport the names and uuids of all custom
|
| /hal_espressif-3.6.0/examples/system/sysview_tracing/ |
| D | README.md | 89 2. Using custom SystemView messages. This is more flexible way. It implies extending SystemView wit…
105 …custom events enable them by checking `Example Configuration > Use custom SystemView event IDs`. B…
145 - `Show APIs only` if you compiled example to use custom events.
148 …If you compiled example to use custom events you will also be able to see the values sent by timer…
|
| /hal_espressif-3.6.0/components/esp_hw_support/include/ |
| D | esp_mac.h | 47 * If using a custom base MAC address, call this API before initializing any network interfaces.
67 …* @note If no custom Base MAC has been set, this returns the pre-programmed Espressif base MAC add…
83 * This API returns the custom base MAC address which was previously written to EFUSE BLK3 in
87 * possible to store a custom base MAC address elsewhere, see esp_base_mac_addr_set() for details.
|
| /hal_espressif-3.6.0/examples/system/efuse/main/ |
| D | efuse_main.c | 28 size_t custom_secure_version; /*!< Custom secure version: length 16 bits */
74 ESP_LOGI(TAG, "3. read custom fields"); in read_efuse_fields()
88 ESP_LOGI(TAG, "write custom efuse fields"); in write_efuse_fields()
111 // We use EFUSE_BLK3 (custom block) to verify it. in get_coding_scheme()
|
| /hal_espressif-3.6.0/components/efuse/esp32/ |
| D | esp_efuse_table.csv | 23 # Custom MAC address #
25 MAC_CUSTOM_CRC, EFUSE_BLK3, 0, 8, CRC8 for custom MAC address.
26 MAC_CUSTOM, EFUSE_BLK3, 8, 48, Custom MAC
27 MAC_CUSTOM_VER, EFUSE_BLK3, 184, 8, Custom MAC version
|
| /hal_espressif-3.6.0/components/mqtt/ |
| D | Kconfig | 55 bool "MQTT Using custom configurations"
58 Custom MQTT configurations.
137 bool "Enable custom outbox implementation"
|
| /hal_espressif-3.6.0/examples/custom_bootloader/bootloader_override/bootloader_components/main/ |
| D | Kconfig | 5 default "Custom bootloader message defined in the KConfig file."
7 Message to print by the custom bootloader when booting up.
|
