to (reference) in projects: hal_espressif-3.7.0

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:to (Results 1 – 25 of 357) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...15

/hal_espressif-3.7.0/tools/esptool_py/flasher_stub/
D	README.md	3 esptool.py loads the flasher stub into memory and executes it to: 7 * Add features to the ESP8266 bootloader ROM which are only in the ROM of newer chips. 13 Thanks to [Cesanta](http://cesanta.com/) who provided the original ESP8266 stub loader upon which t… 17 … already automatically integrated into esptool.py. You don't need to do anything special to use it. 21 If you want to build the stub to test modifications or updates, here's how: 23 …32-esp-elf-) on your PATH. If you are developing the stub flasher and plan to send a pull request,… 25 * Set the environment variables SDK_PATH to the path to an ESP8266 IoT NON-OS SDK directory (last s… 27 * Set the environment variable IDF_PATH to the path to an ESP-IDF directory. 29 * Set any other environment variables you'd like to override in the Makefile. 33 …akes care of most of these steps (only the ESP8266 gcc toolchain has to be manually added to PATH). [all …]
/hal_espressif-3.7.0/tools/esptool_py/
D	LICENSE	6 Everyone is permitted to copy and distribute verbatim copies 11 The licenses for most software are designed to take away your 12 freedom to share and change it. By contrast, the GNU General Public 13 License is intended to guarantee your freedom to share and change free 14 software--to make sure the software is free for all its users. This 15 General Public License applies to most of the Free Software 16 Foundation's software and to any other program whose authors commit to 18 the GNU Lesser General Public License instead.) You can apply it to 21 When we speak of free software, we are referring to freedom, not 22 price. Our General Public Licenses are designed to make sure that you [all …]
/hal_espressif-3.7.0/tools/esptool_py/docs/en/advanced-topics/
D	serial-protocol.rst	12 …The {IDF_TARGET_NAME} ROM loader serial protocol is similar to ESP8266, although {IDF_TARGET_NAME}… 14 …to the IRAM of the chip. The stub loader then replaces the ROM loader for all future interactions.… 18 …There are differences in the serial protocol between ESP chips! To switch to documentation for a d… 23 The host computer sends a SLIP encoded command request to the ESP chip. The ESP chip responds to th… 32 …laced with ``0xDB 0xDC`` and ``0xDB 0xDD``, respectively. The replacing is to be done after th… 61 Each received command will result in a response SLIP packet sent from the ESP chip to the host. Con… 128 \| ``0x06`` \| "Failed to act on received message" \| 132 \| ``0x08`` \| "Flash write error" - after writing a block of data to flash, \| 134 \| \| to the data read from flash. If they don't match, this error is returned. \| 149 - Stub loader error codes are entirely different to the ROM loader codes. They all take the form `… [all …]
D	spi-flash-modes.rst	10 …ecuting code and data from the SPI flash chip. Data is read and then cached internally to the chip. 46 …. In single SPI mode, data is sent from the device to the host using the MISO pin and from the hos… 53 …are both used to read or write data simultaneously with two bits per clock cycle. This doubles the… 55 …"Dual Output Fast Read" (3BH) command to read data. Each read command and the read address is sent… 56 This doubles the data transfer rate compared to single SPI which only uses MISO to read data. 58 …d" (BBH) command to read data. Each read command is sent from the host to the flash chip via norma… 63 Consult the datasheet for your particular SPI flash chip to determine if it supports either or both… 70 …not all ESP chips have these pins wired up to the SPI flash chip. Some flash chips require special… 72 In ``qout`` mode, the host uses the "Quad Output Fast Read" (6BH) command to read data. This comman… 74 In ``qio`` mode, the host uses the "Quad I/O Fast Read" (EBH) command to read data. This command is… [all …]
/hal_espressif-3.7.0/tools/esptool_py/docs/en/espefuse/
D	index.rst	6 … one-time-programmable eFuses. Burning occurs only in one direction from 0 to 1 (never cleared 1->… 10 …Because eFuse is one-time-programmable, it is possible to permanently damage or "brick" your {IDF_… 50 …to see a summary of all available commands and command line options. To see all options for a part… 51 …nd the default chip is ``esp32``, please specify the specific type of chip to get the correct help… 54 - ``--before`` - What to do before connecting to the chip: ``default_reset``, ``no_reset``, ``esp3… 56 - ``--virt`` - For host tests. The tool will work in the virtual mode (without connecting to a chip… 57 …The tool will work in the virtual mode (without connecting to a chip) and save eFuse memory to a g… 58 …is not used, a manual confirmation step is required, you need to enter the word ``BURN`` to contin… 63 …to specify chip with ``--chip``). This helps to test commands without physical access to the chip.… 68 …anual confirmation, you need to type the word ``BURN`` to continue burning. Using the ``--do-not-c… [all …]
D	burn-efuse-cmd.rst	6 The ``espefuse.py burn_efuse`` command burns eFuses. The arguments to ``burn_efuse`` are eFuse name… 15 …to 1, attempting to set any back to 0 will have no effect. Most eFuses have a limited bit width (m… 24 The efuses to burn: 32 - 'VDD_SPI_AS_GPIO' (Set this bit to vdd spi pin function as gpio) 0b0 -> 0b1 39 Type 'BURN' (all capitals) to continue. 41 …`espefuse.py`` will ask you to type ``BURN`` before it permanently sets eFuses. The ``--do-not-con… 56 The following efuses configure the SPI flash pins which are used to boot: 85 …ory. This causes the default GPIO pins (shown in the summary output above) to be used for the SPI … 87 …with integrated internal SPI flash, these eFuses are burned in the factory to the GPIO numbers whe… 89 …to change the SPI flash pin configuration, these eFuses can be burned to the GPIO numbers where th… [all …]
/hal_espressif-3.7.0/tools/esptool_py/docs/en/espsecure/
D	index.rst	6 ``espsecure.py`` is a tool for manipulating data that relates to the secure boot and flash encrypti… 8 For more details, see the ESP-IDF documentation which explains this tool and how to use it to enabl… 20 …e command ``pip install 'esptool[hsm]'`` to use this feature. ``esp_hsm_sign`` provides a PKCS #11… 22 The following command should be used to get an image signed using an external HSM. :: 26 …age using the HSM, and then creates a signature block and appends it to the image to generate a si… 28 If the public key is not stored in the external HSM, you can specify the ``--pub-key`` argument to … 42 If the public key is not stored in the external HSM, you can specify the ``--keyfile`` argument to … 51 populated corresponding to the HSM used. 53 …token of a selected slot, you will also need to pass in the token User PIN and thus you will be pr… 54 …d also add a ``credentials`` field in the HSM config file to store the (plaintext) User PIN to aut… [all …]
/hal_espressif-3.7.0/components/bt/esp_ble_mesh/mesh_common/tinycrypt/include/tinycrypt/
D	utils.h	`61 unsigned int _copy(uint8_t to, unsigned int to_len, 71 void _set(void to, uint8_t val, unsigned int len); 87 extern void _set_secure(void to, uint8_t val, unsigned int len); 89 static inline void _set_secure(void to, uint8_t val, unsigned int len) in _set_secure() argument 91 (void) memset(to, val, len); in _set_secure() 93 __asm__ __volatile__("" :: "g"(to) : "memory"); in _set_secure()`
/hal_espressif-3.7.0/tools/esptool_py/docs/en/esptool/
D	advanced-commands.rst	17 The ``verify_flash`` command allows you to verify that data in flash matches a local file. 19 …to flash, so additional verification is not usually needed. However, if you wish to perform a byte… 26 …s`` option specifies that if the files are different, the details should be printed to the console. 32 …_size`` and ``--flash_freq`` arguments which were passed to `write_flash` must also be passed to `… 33 …* Another way to compare flash contents is to use the ``read_flash`` command, and then use binary … 37 Dump a Memory Region to File: dump_mem 40 The ``dump_mem`` command will dump a region from the chip's memory space to a file. For example, to… 48 Load a Binary to RAM: load_ram 59 … and the image will probably crash. The ``image_info`` command can be used to check the binary ima… 60 …oader in RAM. Older esptool versions may hang. Pass ``esptool.py --no-stub`` to avoid this problem. [all …]
D	advanced-options.rst	13 …to hard reset the chip into bootloader mode before it starts and hard resets the chip to run the n… 18 …`--before`` argument allows you to specify whether the chip needs resetting into bootloader mode b… 22 …ses DTR & RTS serial control lines (see :ref:`entering-the-bootloader`) to try to reset the chip i… 23 …signal assignments and just start sending a serial synchronisation command to the chip. This is us… 24 …our chip is already running the :ref:`stub bootloader <stub>` and you want to avoid resetting the … 25 …erial peripheral). Usually, this option doesn't have to be used directly. Esptool should be able t… 30 The ``--after`` argument allows you to specify whether the chip should be reset after the esptool o… 34 …* ``--after hard_reset`` is the default. The DTR serial control line is used to reset the chip int… 35 …_reset`` This runs the user firmware, but any subsequent reset will return to the serial bootloade… 44 …software "stub loader" that manages flash operations, and only talks directly to the loader in ROM. [all …]
D	remote-serial-ports.rst	4 …to connect to any networked remote serial port that supports `RFC2217 <http://www.ietf.org/rfc/rfc… 16 …rs can run on any OS that supports pyserial, and are the simplest way to connect to an Espressif S… 18 …sue with `automatic resetting due to network latency <https://github.com/espressif/esptool/issues/… 36 …/serial adapters which don't support the full RFC2217, it is also possible to specify ``--port soc… 38 …to esptool. You need to set the baud rate manually on the server, and manually reset the chip into… 62 …en/latest/url_handlers.html>`__. (Please keep in mind that the link points to documentation for th…
D	basic-commands.rst	6 Write Binary Data to Flash: write_flash 9 Binary data can be written to the ESP's flash chip via the serial ``write_flash`` command: 21 …--chip`` argument is optional when writing to flash, esptool will detect the type of chip when it … 27 …The next arguments to ``write_flash`` are one or more pairs of offset (address) and file name. Whe… 28 …For other types of images, consult your SDK documentation to determine the files to flash at which… 32 …arguments to ``write_flash`` are one or more pairs of offset (address) and file name. Consult your… 34 Numeric values passed to write_flash (and other commands) can be specified either in hex (ie 0x1000… 36 …leshooting` section if the ``write_flash`` command is failing, or the flashed module fails to boot. 41 You may also need to specify arguments for :ref:`flash mode and flash size <flash-modes>`, if you w… 47 Since esptool v2.0, these options are not often needed as the default is to keep the flash mode and… [all …]
/hal_espressif-3.7.0/tools/esptool_py/docs/en/
D	troubleshooting.rst	8 Flashing problems can be fiddly to troubleshoot. Try the suggestions here if you're having problems: 13 If you see errors like "Failed to connect" then your chip is probably not entering the bootloader p… 16 … Check you have permissions to access the serial port, and other software (such as modem-manager … 18 …each pin with a multimeter, "high" pins should be close to 3.3V and "low" pins should be close to … 19 * If you have connected other devices to GPIO pins, try removing them and see if esptool starts wo… 20 * Try using a slower baud rate (``-b 9600`` is a very slow value that you can use to verify it's n… 22 Writing to Flash Fails Part Way Through 29 Writing to Flash Succeeds but Program Doesn't Run 37 …to flash with ``qio`` mode will succeed but the chip can't read the flash back to run - so nothing… 39 See the :ref:`spi-flash-modes` page for a full description of the flash modes and how to determine … [all …]
/hal_espressif-3.7.0/components/esp_system/port/soc/esp32s2/
D	Kconfig.cache	7 Instruction cache size to be set on application startup. 9 then the other 8KB will be added to the heap. 21 Instruction cache line size to be set on application startup. 33 Data cache size to be set on application startup. 34 If you use 0KB data cache, the other 16KB will be added to the heap 35 … If you use 8KB data cache rather than 16KB data cache, the other 8KB will be added to the heap 50 Data cache line size to be set on application startup. 62 If enabled, instruction cache will use wrap mode to read spi flash (maybe spiram). 63 The wrap length equals to INSTRUCTION_CACHE_LINE_SIZE. 70 If enabled, data cache will use wrap mode to read spiram (maybe spi flash). [all …]
/hal_espressif-3.7.0/components/esp_wifi/
D	Kconfig	21 WiFi hardware use these buffers to receive all 802.11 frames. 23 … is enabled, this value is recommended to set equal or bigger than ESP_WIFI_RX_BA_WIN in order to 36 … For each received data frame, the WiFi driver makes a copy to an RX buffer and then delivers 37 … it to the high layer TCP/IP stack. The dynamic RX buffer is freed after the higher layer has 52 when WiFi is de-initialized. The size of each static TX buffer is fixed to about 1.6KB. 55 … delivered to the Wifi driver from the TCP/IP stack. The buffer is freed after the data frame 59 If PSRAM is enabled, "Static" should be selected to guarantee enough WiFi TX buffers. 60 If PSRAM is disabled, "Dynamic" should be selected to improve the utilization of RAM. 97 … For each TX packet from uplayer, such as LWIP etc, WiFi driver needs to allocate a static TX 98 … buffer and makes a copy of uplayer packet. If WiFi driver fails to allocate the static TX buffer, [all …]
/hal_espressif-3.7.0/tools/esptool_py/docs/en/espefuse/inc/
D	summary_ESP32-S3.rst	14 …DIS_ICACHE (BLOCK0) Set this bit to disable Icache … 15 …DIS_DCACHE (BLOCK0) Set this bit to disable Dcache … 16 …DIS_TWAI (BLOCK0) Set this bit to disable CAN function … 35 …FLASH_ECC_EN (BLOCK0) Set 1 to enable ECC for flash boot … 36 …FORCE_SEND_RESUME (BLOCK0) Set this bit to force ROM code to send a resume… 54 …SOFT_DIS_JTAG (BLOCK0) Set these bits to disable JTAG in the soft way … 57 …DIS_PAD_JTAG (BLOCK0) Set this bit to disable JTAG in the hard way. J… 59 …STRAP_JTAG_SEL (BLOCK0) Set this bit to enable selection between usb_to… 62 l to 0 71 …DIS_DOWNLOAD_ICACHE (BLOCK0) Set this bit to disable Icache in download mode… [all …]
/hal_espressif-3.7.0/components/esp_pm/
D	Kconfig	10 longer time to enter idle state), and it also reduces accuracy of 20 Max CPU frequency is set to DEFAULT_CPU_FREQ_MHZ setting, 21 min frequency is set to XTAL frequency. 33 This feature can be used to analyze which locks are preventing the chip 43 If enabled, some GPIOs will be used to signal events such as RTOS ticks, 44 frequency switching, entry/exit from idle state. Refer to pm_trace.c 46 This feature is intended to be used when analyzing/debugging behavior 56 This feature is intended to be used when lower power consumption is needed 57 while there is enough place in IRAM to place source code. 65 This feature is intended to be used when lower power consumption is needed [all …]
/hal_espressif-3.7.0/components/spi_flash/
D	Kconfig	23 bool "Log warning if writing zero bits to ones" 27 … If this option is enabled, any SPI flash write which tries to set zero bits in the flash to 29 … in flash once written, as SPI NOR flash can only set bits to one when an entire sector is erased. 30 After erasing, individual bits can only be written from one to zero. 46 These APIs may be used to collect performance data for spi_flash APIs 47 and to help understand behaviour of libraries which use SPI flash. 53 Enable this flag to use patched versions of SPI flash ROM driver functions. 54 This option should be enabled, if any one of the following is true: (1) need to write 55 to flash on ESP32-D2WD; (2) main SPI flash is connected to non-default pins; (3) main 63 Enable this flag to use new SPI flash driver functions from ROM instead of ESP-IDF. [all …]
/hal_espressif-3.7.0/components/esp_netif/
D	README.md	44 * `........` Initialization line from user code to esp-netif and comm driver 46 * `--<--->--` Data packets going from communication media to TCP/IP stack and back 48 * `*******` Events agregated in ESP-NETIP propagates to driver, user code and network stack 72 glue IO layer: adapt the input/output functions to use esp-netif transmit/input/free_rx 73 - install driver_transmit to appropriate ESP-NETIF object, so that outgoing packets from 74 network stack are passed to the IO driver 75 - calls esp_netif_receive to pass incoming data to network stack 92 The ESP-NETIF L2 TAP interface is ESP-IDF mechanism utilized to access Data Link Layer (L2 per OSI/… 101 …ce the ESP-NETIF L2 TAP interface can be understood as generic entry point to the NETIF internal s… 102 …configuration of particular file descriptor. It can be configured to give an access to specific Ne… [all …]
/hal_espressif-3.7.0/components/log/
D	README.rst	10 …t this is the same as the default level, but it can be set higher in order to compile more optiona… 11 …enabled by default. The function :cpp:func:`esp_log_level_set` can be used to set a logging level … 26 How to use this library 35 Then use one of logging macros to produce output, e.g: 49 …to be used explicitly in the early startup code only, before heap allocator and syscalls have been… 55 …to use ``ESP_DRAM_LOGx`` (preferred) or ``ESP_EARLY_LOGx``. Even though it's possible to log in th… 72 To configure logging output per module at runtime, add calls to the function :cpp:func:`esp_log_lev… 76 esp_log_level_set("*", ESP_LOG_ERROR); // set all components to ERROR level 84 Logging to Host via JTAG 87 …to write formatted output to the dedicated UART. By calling a simple API, all log output may be ro…
/hal_espressif-3.7.0/components/esp_hw_support/
D	Kconfig	13 update the version field in eFuse, you can enable this option to force the 53 … and you still want to use this chip, you can enable this option to bypass such an error. 54 This applies to both MAC_FACTORY and CUSTOM_MAC efuses. 65 … If enabled, chip will try to power down flash as part of esp_light_sleep_start(), which costs 68 … option will power down flash under a strict but relatively safe condition. Also, it is possible to 69 …power down flash under a relaxed condition by using esp_sleep_pd_config() to set ESP_PD_DOMAIN_VDD… 70 …to ESP_PD_OPTION_OFF. It should be noted that there is a risk in powering down flash, you can refer 78 All IOs will be set to isolate(floating) state by default during sleep. 82 … Select this option will set the CS pin of Flash to PULL-UP state during sleep, but this will 85 … with chips, you can also pull up the CS pin of SPI Flash in the external circuit to save power [all …]
/hal_espressif-3.7.0/components/esp_system/
D	system_init_fn.txt	4 # keep this file up to date. This is checked in CI. 6 # they need to be updated to be consistent with the changes you are making. 8 # Entries are ordered by the order of execution (i.e. from low priority values to high ones). 10 # prio: function_name in path/to/source_file on affinity_expression 16 # esp_timer has to be initialized early, since it is used by several other components 24 # app_trace has to be initialized before systemview 32 # usb_console needs to create an esp_timer at startup. 36 # usb_serial_jtag needs to create and acquire a PM clock at startup. 37 # This makes more sense to be done after esp_pm_impl_init, which is initialized in init_components0.
/hal_espressif-3.7.0/components/bt/esp_ble_mesh/
D	Kconfig.in	20 Enable this option to allow using specific duplicate scan filter 29 Allocation strategy for BLE Mesh stack, essentially provides ability to 58 Enable this option to use the default memory allocation strategy when 65 Allows to use IRAM memory region as 8bit accessible region. Every 76 Enable this option to use FreeRTOS static allocation APIs for BLE Mesh, 77 which provides the ability to use different dynamic memory (i.e. SPIRAM 86 Choose the memory to be used for FreeRTOS objects. 111 If enabled, users can use the function esp_ble_mesh_deinit() to de-initialize 150 Enable this option to allow BLE Mesh fast provisioning solution to be used. 154 into a node successfully, it can be changed to a temporary Provisioner. [all …]
/hal_espressif-3.7.0/
D	LICENSE	19 "control" means (i) the power, direct or indirect, to cause the 28 including but not limited to software source code, documentation 33 not limited to compiled object code, generated documentation, 34 and conversions to other media types. 38 copyright notice that is included in or attached to the work 46 separable from, or merely link (or bind by name) to the interfaces of, 51 to that Work or Derivative Works thereof, that is intentionally 52 submitted to Licensor for inclusion in the Work by the copyright owner 53 or by an individual or Legal Entity authorized to submit on behalf of 56 to the Licensor or its representatives, including but not limited to [all …]
/hal_espressif-3.7.0/zephyr/blobs/
D	license.txt	19 "control" means (i) the power, direct or indirect, to cause the 28 including but not limited to software source code, documentation 33 not limited to compiled object code, generated documentation, 34 and conversions to other media types. 38 copyright notice that is included in or attached to the work 46 separable from, or merely link (or bind by name) to the interfaces of, 51 to that Work or Derivative Works thereof, that is intentionally 52 submitted to Licensor for inclusion in the Work by the copyright owner 53 or by an individual or Legal Entity authorized to submit on behalf of 56 to the Licensor or its representatives, including but not limited to [all …]

12 3 4 5 6 7 8 9 10 >>...15

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