master (reference) in projects: hal_espressif-3.6.0

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:master (Results 1 – 25 of 132) sorted by relevance

12 3 4 5 6

/hal_espressif-3.6.0/docs/zh_CN/
D	versions.rst	6 ESP-IDF 的 GitHub 仓库时常更新，特别是用于开发新特性的 master 分支。 18 * 最新版 ESP-IDF（即 master 分支）：https://docs.espressif.com/projects/esp-idf/zh_CN/latest/ 42 - 如需尝试/测试 ESP-IDF 的最新特性，请使用 `最新版本（在 master 分支上） <https://docs.espressif.com/projects/esp-idf/zh_CN/… 44 - 如需使用稳定版本中没有的新特性，但同时又不希望受到 master 分支更新的影响，您可以将一个最适合您的稳定版本 :ref:`更新至一个预发布版本` 或 :ref:`更新至一个发布分支`。 135 ``v3.2-dev-306-gbeb3611ca`` \| master 分支上的预发布版本。 154 - 新的改动总是在 master 分支（最新版本）上进行。master 分支上的 ESP-IDF 版本总带有 ``-dev`` 标签，表示“正在开发中”，例 ``v3.1-dev``。 156 - 新版本一旦完成特性开发（在 ``master`` 分支上进行）并达到进入 beta 测试的标准，则将该版本切换至一个新分支（例 ``release/v3.1``）。此外，该分支还打上预发布标签… 157 - 随着对 beta 版本的不断测试，bug 修复将同时增加至该发布分支和 ``master`` 分支。而且，``master`` 分支可能也已经开始为下个版本开发新特性了。 172 - 如需测试/研发/尝试最新特性，建议参考 :ref:`更新至 master 分支` 。 209 .. _`更新至 master 分支`: [all …]
/hal_espressif-3.6.0/docs/en/api-reference/protocols/
D	esp_spi_slave_protocol.rst	33 In the half duplex mode, the master has to use the protocol defined by the slave to communicate 37 - Command: 8-bit, master to slave 41 - Address: 8-bit, master to slave, optional 49 This phase is the turn around time between the master and the slave on the bus, and also 50 provides enough time for the slave to prepare the data to send to master. 54 This may be a data OUT phase, in which the direction is slave to master, or a data IN phase, 55 in which the direction is master to slave. 57 The direction means which side (master or slave) controls the MOSI, MISO, WP and HD pins. 83 Normally, which mode is used is determined is determined by the command sent by the master (See 89 The QPI mode is a special state of the SPI Slave. The master can send ENQPI command to put the [all …]
D	esp_serial_slave_link.rst	9 designed for the master to communicate with ESP slave devices through those protocols over the 33 - ESSL device: a virtual device on the master associated with an ESP slave device. The device 39 communication state, data shared by master and slave, etc. 42 master application operates on the ESSL device through this handle. 47 - Bus: The bus over which the master and the slave communicate with each other. 51 - TX buffer num: a counter, which is on the slave and can be read by the master, indicates the 53 master. 55 - RX data size: a counter, which is on the slave and can be read by the master, indicates the 56 accumulated data size that the slave has loaded to the hardware to send to the master. 63 1. Tohost Interrupts: The slave can inform the master about certain events by the interrupt line. (… [all …]
D	modbus.rst	20 …master(s) and slave devices (multiple masters are allowed on using Modbus TCP/IP). The slave devic… 30 …hat the number of slaves and their register maps are known by the Modbus master before the start o… 44 …us`. The sections cover initialization of a Modbus port, and the setup a master or slave device ac… 55 …e used to create and then initialize Modbus controller interface (either master or slave) over a p… 68 // Initialization of Modbus master for serial port 91 The following overview describes how to setup Modbus master communication. The overview reflects a … 109 The Data Dictionary is the list in the Modbus master which shall be defined by user to link each CI… 112 .. list-table:: Table 1 Modbus master Data Dictionary description 199 // Enumeration of modbus slave addresses accessed by master device 238 :cpp:func:`mbc_master_set_descriptor`: Initialization of master descriptor. [all …]
/hal_espressif-3.6.0/examples/cxx/experimental/experimental_cpp_component/test/
D	test_i2c.cpp	55 master(new I2CMaster(I2C_MASTER_NUM, I2C_MASTER_SCL_IO, I2C_MASTER_SDA_IO, 400000)), 58 std::shared_ptr<I2CMaster> master; member 204 future<vector<uint8_t> > fut = fix.master->transfer(reader, ADDR); in i2c_master_read_raw_byte() 224 future<void> fut = fix.master->transfer(writer, ADDR); in i2c_master_write_raw_byte() 242 future<vector<uint8_t> > fut = fix.master->transfer(reader, ADDR); in i2c_master_read_multiple_raw_bytes() 263 future<void> fut = fix.master->transfer(writer, ADDR); in i2c_master_write_multiple_raw_bytes() 279 vector<uint8_t> data = fix.master->sync_read(ADDR, 1); in i2c_master_sync_read() 296 fix.master->sync_write(ADDR, fix.data); in i2c_master_sync_write() 312 vector<uint8_t> read_data = fix.master->sync_transfer(ADDR, fix.data, READ_SIZE); in i2c_master_sync_transfer() 336 future<vector<vector<uint8_t> > > result = fix.master->transfer(composed_transfer, ADDR); in i2c_master_composed_trans() [all …]
/hal_espressif-3.6.0/examples/protocols/modbus/tcp/
D	README.md	5 These two projects illustrate the communication between Modbus master and slave device in the segme… 8 Once master reads the alarm it stops communication and destroy driver. 12 * `examples/protocols/modbus/tcp/mb_tcp_master` - Modbus TCP master 22 The master and slave boards should be connected to the same network (see the README.md file in exam… 27 This example test requires communication mode setting for master and slave be the same and slave ad… 32 …common" one level above includes definitions of parameter structures for master and slave device (… 37 Refer to README.md file in the appropriate example folder for more information about master and sla… 41 If the examples do not work as expected and slave and master boards are not able to communicate cor… 42 The most important errors are described in master example output and formatted as below: 45 E (1692332) MB_CONTROLLER_MASTER: mbc_master_get_parameter(111): SERIAL master get parameter failur… [all …]
/hal_espressif-3.6.0/docs/en/api-reference/peripherals/
D	spi_slave_hd.rst	9 …master, while the direction of the data phase depends on the command. The data phase can be either… 11 About the details of how master should communicate with the SPI Slave, see :doc:`/api-reference/pro… 13 By these different transactions, the slave provide these services to the master: 15 - A DMA channel for the master to write a great amount of data to the slave. 16 - A DMA channel for the master to read a great amount of data from the slave. 17 - Several general purpose registers, shard between the master and the slave. 18 - Several general purpose interrupts, for the master to interrupt the SW of slave. 32 - Transaction read/write by master in segments 54 …master through the sending DMA channel, the application should properly wrap the data to send by a… 56 …. This function will block until the transaction with command RDDMA from master successfully compl… [all …]
D	i2c.rst	15 …ponsible for handling communications on I2C bus. The I2C controller can operate as master or slave. 19 …2C bus. Each I2C controller can operate as master or slave. As an example, one controller can act … 28 - Reading and writing to registers which are in turn read/written by the master 36 1. :ref:`i2c-api-configure-driver` - set the initialization parameters (master or slave mode, GPIO … 37 2. :ref:`i2c-api-install-driver`- activate the driver on one of the two I2C controllers as a master… 38 3. Depending on whether you configure the driver for a master or slave, choose the appropriate item 40 a) :ref:`i2c-api-master-mode` - handle communications (master) 41 b) :ref:`i2c-api-slave-mode` - respond to messages from the master (slave) 56 - Set I2C mode of operation - slave or master from :cpp:type:`i2c_mode_t` 70 Configuration example (master): [all …]
/hal_espressif-3.6.0/examples/protocols/modbus/serial/
D	README.md	5 These two projects illustrate the communication between Modbus master and slave device in the segme… 8 Once master reads the alarm it stops communication and destroy driver. 12 * `examples/protocols/modbus/serial/mb_master` - Modbus serial master ASCII/RTU 22 The master and slave boards should be connected to each other through the RS485 interface line driv… 27 This example test requires communication mode setting for master and slave be the same and slave ad… 32 The folder "mb_example_common" includes definitions of parameter structures for master and slave de… 52 I (399) MASTER_TEST: Modbus master stack initialized... 60 E (949) MB_CONTROLLER_MASTER: mbc_master_get_parameter(111): SERIAL master get parameter failure er… 62 E (1029) MB_CONTROLLER_MASTER: mbc_master_get_parameter(111): SERIAL master get parameter failure e… 68 If the examples do not work as expected and slave and master boards are not able to communicate cor… [all …]
/hal_espressif-3.6.0/examples/peripherals/twai/twai_network/
D	README.md	7 Note that concept of master/slave in this example refers to which node initiates 145 I (366) TWAI Listen Only: Received master ping 147 I (1866) TWAI Listen Only: Received master ping 149 I (2116) TWAI Listen Only: Received master start command 153 I (4566) TWAI Listen Only: Received master stop command 155 I (5606) TWAI Listen Only: Received master ping 156 I (5856) TWAI Listen Only: Received master ping 158 I (6106) TWAI Listen Only: Received master start command 162 I (8556) TWAI Listen Only: Received master stop command 164 I (9596) TWAI Listen Only: Received master ping [all …]
/hal_espressif-3.6.0/examples/peripherals/spi_slave_hd/segment_mode/
D	README.md	`80 this is master's transaction 0 82 this is master's transaction 1 84 this is master's transaction 2 86 this is master's transaction 3 88 this is master's transaction 4 90 this is master's transaction 5 92 this is master's transaction 6 94 this is master's transaction 7 96 this is master's transaction 8 98 this is master's transaction 9 [all …]`
/hal_espressif-3.6.0/examples/wifi/espnow/main/
D	Kconfig.projbuild	`16 string "ESPNOW primary master key" 19 …ESPNOW primary master for the example to use. The length of ESPNOW primary master must be 16 bytes. 22 string "ESPNOW local master key" 25 … ESPNOW local master for the example to use. The length of ESPNOW local master must be 16 bytes.`
/hal_espressif-3.6.0/examples/protocols/modbus/mb_example_common/
D	README.md	3 This directory contains component that is common for Modbus master and slave examples. The componen… 6 * `examples/protocols/modbus/serial/mb_master` Modbus serial master implementation (RTU and ASCII) 8 * `examples/protocols/modbus/serial/mb_master` Modbus serial master implementation (RTU and ASCII) 10 * `examples/protocols/modbus/tcp/mb_tcp_master` Modbus serial master implementation (TCP)
/hal_espressif-3.6.0/docs/en/
D	versions.rst	6 The ESP-IDF GitHub repository is updated regularly, especially the master branch where new developm… 18 Documentation for the latest version (master branch) can always be found at this URL: 42 …e `latest version (master branch in Git) <https://docs.espressif.com/projects/esp-idf/en/latest/>`… 44 …is not yet available in a stable release, but you do not want to use the master branch, it is poss… 154 - New work is always added on the master branch (latest version) first. The ESP-IDF version on ``ma… 156 - When a new version (developed on ``master``) becomes feature complete and "beta" quality, a new b… 157 …be added to both the ``master`` branch and the release branch. New features for the next release m… 172 - :ref:`updating-master` is recommended for the latest features, development use, and testing. 209 .. _`updating-master`: 216 To use the latest version on the ESP-IDF master branch, this is the process to follow: [all …]
/hal_espressif-3.6.0/examples/cxx/experimental/sensor_mcp9808/main/
D	sensor_mcp9808.cpp	`44 …shared_ptr<I2CMaster> master(new I2CMaster(I2C_MASTER_NUM, I2C_MASTER_SCL_IO, I2C_MASTER_SDA_IO, 4… in app_main() local 45 master->sync_write(ADDR, {MCP_9808_TEMP_REG}); in app_main() 46 vector<uint8_t> data = master->sync_read(ADDR, 2); in app_main()`
/hal_espressif-3.6.0/examples/peripherals/spi_slave/
D	README.md	`3 …ll use the spi master and spi slave driver to communicate with eachother. The example also include… 16 Please run wires between the following GPIOs between the slave and master to make the example funct… 26 …o change the GPIO settings by editing defines in the top of main.c in the master/slave source code.`
/hal_espressif-3.6.0/examples/protocols/modbus/serial/mb_master/
D	README.md	6 This example demonstrates using of FreeModbus stack port implementation for ESP32 as a master devic… 7 …l parameters to be accessed are defined in data dictionary of the modbus master example source fil… 10 The instances for the modbus parameters are common for master and slave examples and located in `ex… 25 …it can be changed in the ```Example Data (Object) Dictionary``` table of master example to address… 68 RS485 example circuit schematic for connection of master and slave devices into segment: 95 …the communication mode parameter for master and slave in Kconfig - CONFIG_MB_COMM_MODE (must be th… 116 Configure the external Modbus master software according to port configuration parameters used in th… 121 ### Build and flash software of master device 151 I (10175) MASTER_TEST: Destroy master...
/hal_espressif-3.6.0/examples/peripherals/i2c/i2c_self_test/
D	README.md	10 2. Use one of the ESP device's I2C port (master mode) to read and write another I2C port (slave mod… 33 - master: 34 - GPIO18 is assigned as the data signal of I2C master port 35 - GPIO19 is assigned as the clock signal of I2C master port 57 - master: 58 - GPIO1 is assigned as the data signal of I2C master port 59 - GPIO2 is assigned as the clock signal of I2C master port 77 - master: 78 - GPIO5 is assigned to the data signal of the I2C master port 79 - GPIO6 is assigned to the clock signal of the I2C master port [all …]
/hal_espressif-3.6.0/examples/protocols/modbus/tcp/mb_tcp_master/
D	README.md	3 This example demonstrates using of FreeModbus stack port implementation for ESP32 as a TCP master d… 4 …l parameters to be accessed are defined in data dictionary of the modbus master example source fil… 7 The instances for the modbus parameters are common for master and slave examples and located in `ex… 22 …but it can be changed in the `Example Data (Object) Dictionary` table of master example to address… 74 There are three ways to configure how the master example will obtain slave IP addresses in the netw… 88 Configure the external Modbus master software according to port configuration parameters used in th… 93 ### Build and flash software of master device 116 I (5704) MASTER_TEST: Modbus master stack initialized... 117 I (5704) MB_TCP_MASTER_PORT: TCP master stack initialized. 140 I (47094) MASTER_TEST: Destroy master...
/hal_espressif-3.6.0/docs/zh_CN/api-reference/peripherals/
D	i2c.rst	40 a) :ref:`i2c-api-master-mode` - 发起通信（主机模式） 81 .master.clk_speed = I2C_MASTER_FREQ_HZ, // select frequency specific to your project 211 .. _i2c-api-master-mode: 228 .. blockdiag:: ../../../_static/diagrams/i2c-command-link-master-write-blockdiag.diag 230 :caption: I2C command link - master write example 256 .. blockdiag:: ../../../_static/diagrams/i2c-command-link-master-read-blockdiag.diag 258 :caption: I2C command link - master read example
/hal_espressif-3.6.0/components/freemodbus/
D	Kconfig	24 This is used by Modbus master and slave port layer to establish connections. 55 … If master sends a frame which is not broadcast, it has to wait sometime for slave response. 56 if slave is not respond in this time, the master will process timeout error. 63 If master sends a broadcast frame, it has to wait conversion time to delay, 64 then master can send next frame. 106 Thus the timeout will expire and allow the master program to handle the error. 215 Modbus master Timer group number that is used for timeout measurement. 222 Modbus master Timer Index in the group that is used for timeout measurement. 223 … Note: Modbus master and slave should have different timer index to be able to work simultaneously.
/hal_espressif-3.6.0/docs/zh_CN/get-started/
D	vscode-setup.rst	12 …，或根据 `快速安装指南 <https://github.com/espressif/vscode-esp-idf-extension/blob/master/docs/tutorial/inst… 14 查看 ESP-IDF VS Code 插件 `教程 <https://github.com/espressif/vscode-esp-idf-extension/blob/master/docs/t… 23 * `调试 <https://github.com/espressif/vscode-esp-idf-extension/blob/master/docs/tutorial/debugging.md…
D	eclipse-setup.rst	9 …南，请见 `ESP-IDF Eclipse 插件 <https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md>`_。 13 …`ESP-IDF Eclipse 插件 <https://github.com/espressif/idf-eclipse-plugin/blob/master/README.md>`_ 中使用的…
/hal_espressif-3.6.0/docs/zh_CN/api-guides/
D	unit-tests-legacy.rst	`89 去支持同步操作。如上例中的场景，slave 应该在在 master 设置好 GPIO 93 DUT1（master）终端： 201 (13) "gpio master/slave test example" [ignore][misc][test_env=UT_T2_1][multi_device] 235 Running gpio master/slave test example... 236 gpio master/slave test example`
/hal_espressif-3.6.0/components/esptool_py/esptool/
D	README.md	`5 …master)](https://github.com/espressif/esptool/actions/workflows/test_esptool.yml) [![Build esptool… 21 …he accompanying [LICENSE file](https://github.com/espressif/esptool/blob/master/LICENSE) for a cop…`

12 3 4 5 6

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