openocd\-esp32 (full) in projects: hal_espressif-3.4.0

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched +full:openocd +full:- +full:esp32 (Results 1 – 25 of 56) sorted by relevance

12 3

/hal_espressif-3.4.0/tools/
D	zephyr_tools.json	`4 "description": "OpenOCD for ESP32", 7 "openocd-esp32", 12 "OPENOCD_SCRIPTS": "${TOOL_PATH}/openocd-esp32/share/openocd/scripts" 14 "info_url": "https://github.com/espressif/openocd-esp32", 16 "license": "GPL-2.0-only", 17 "name": "openocd-esp32", 22 "linux-i686" 30 "openocd", 31 "--version" 33 "version_regex": "Open On-Chip Debugger\\s+([a-z0-9.-]+)\\s+", [all …]`
D	tools.json	`4 "description": "Toolchain for Xtensa (ESP32) based on GCC", 7 "xtensa-esp32-elf", 12 "info_url": "https://github.com/espressif/crosstool-NG", 14 "license": "GPL-3.0-with-GCC-exception", 15 "name": "xtensa-esp32-elf", 17 "esp32" 20 "xtensa-esp32-elf-gcc", 21 "--version" 23 … "version_regex": "\$crosstool-NG\\s+(?:crosstool-ng-)?([0-9a-zA-Z\\.\\-_]+)\$\\s*([0-9\\.]+)", 24 "version_regex_replace": "\\1-\\2", [all …]`
/hal_espressif-3.4.0/docs/en/api-guides/jtag-debugging/
D	esp32.inc	2 .. It contains target-specific snippets. 3 .. Comments and '---' lines act as delimiters. 7 .. These code blocks can be moved back to the main .rst files, with target-specific 11 .. run-openocd 15 openocd -f board/esp32-wrover-kit-3.3v.cfg 17 .. \|run-openocd-device-name\| replace:: ESP-WROVER-KIT with ESP32-WROOM-32 module 19 --- 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32-wrover-kit-3.3v.cfg 26 Open On-Chip Debugger v0.10.0-esp32-20190708 (2019-07-08-11:04) [all …]
D	building-openocd-macos.rst	2 Building OpenOCD from Sources for MacOS 6 …OpenOCD from `Espressif GitHub <https://github.com/espressif/openocd-esp32/releases>`_. To quickly… 10 Download Sources of OpenOCD 13 …he {IDF_TARGET_NAME}-enabled variant of OpenOCD are available from Espressif GitHub under https://… 16 git clone --recursive https://github.com/espressif/openocd-esp32.git 18 The clone of sources should be now saved in ``~/esp/openocd-esp32`` directory. 24 Install packages that are required to compile OpenOCD using Homebrew:: 26 brew install automake libtool libusb wget gcc@4.9 pkg-config 28 Build OpenOCD 31 Proceed with configuring and building OpenOCD:: [all …]
D	building-openocd-linux.rst	2 Building OpenOCD from Sources for Linux 6 …OpenOCD from `Espressif GitHub <https://github.com/espressif/openocd-esp32/releases>`_. To quickly… 11 Download Sources of OpenOCD 14 …he {IDF_TARGET_NAME}-enabled variant of OpenOCD are available from Espressif GitHub under https://… 17 git clone --recursive https://github.com/espressif/openocd-esp32.git 19 The clone of sources should be now saved in ``~/esp/openocd-esp32`` directory. 25 Install packages that are required to compile OpenOCD. 33 sudo apt-get install make 34 sudo apt-get install libtool 35 sudo apt-get install pkg-config [all …]
D	esp32c3.inc	2 .. It contains target-specific snippets. 3 .. Comments and '---' lines act as delimiters. 7 .. These code blocks can be moved back to the main .rst files, with target-specific 10 .. run-openocd 14 openocd -f board/esp32c3-builtin.cfg 16 .. \|run-openocd-device-name\| replace:: ESP32-C3 through built-in USB connection 18 --- 20 .. run-openocd-output 24 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32c3-builtin.cfg 25 Open On-Chip Debugger v0.10.0-esp32-20201202-26-g05a036c2 (2021-03-15-17:18) [all …]
D	building-openocd-windows.rst	2 Building OpenOCD from Sources for Windows 6 …OpenOCD from `Espressif GitHub <https://github.com/espressif/openocd-esp32/releases>`_. To quickly… 18 Install packages that are required to compile OpenOCD:: 20 pacman -S --noconfirm --needed autoconf automake git make \ 21 mingw-w64-i686-gcc \ 22 mingw-w64-i686-toolchain \ 23 mingw-w64-i686-libtool \ 24 mingw-w64-i686-pkg-config \ 25 mingw-w64-cross-winpthreads-git \ 29 Download Sources of OpenOCD [all …]
D	esp32s3.inc	`2 .. It contains target-specific snippets. 3 .. Comments and '---' lines act as delimiters. 7 .. These code blocks can be moved back to the main .rst files, with target-specific 11 .. run-openocd 15 openocd -f board/esp32s3-builtin.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S3 19 --- 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s3-builtin.cfg 26 Open On-Chip Debugger v0.10.0-esp32-20210902 (2021-10-05-23:44) [all …]`
D	esp32s2.inc	`2 .. It contains target-specific snippets. 3 .. Comments and '---' lines act as delimiters. 7 .. These code blocks can be moved back to the main .rst files, with target-specific 11 .. run-openocd 15 openocd -f board/esp32s2-kaluga-1.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S2-Kaluga-1 board 19 --- 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s2-kaluga-1.cfg 26 Open On-Chip Debugger v0.10.0-esp32-20200420 (2020-04-20-16:15) [all …]`
D	tips-and-quirks.rst	2 --------------- 7 .. _jtag-debugging-tip-breakpoints: 12 …OpenOCD: flash (up to 32) and IRAM (up to 32) breakpoints. Currently GDB can not set software brea… 15 .. _jtag-debugging-tip-where-breakpoints: 20 …oftware flash breakpoints is used. The same rule applies to ``b myFunction``-like commands. In thi… 23 .. _jtag-debugging-tip-flash-mappings: 28 …OpenOCD needs to know their flash addresses. To accomplish conversion from the {IDF_TARGET_NAME} a… 32 Offset should be in hex format. To reset to the default behaviour you can specify ``-1`` as offset. 36 … map from OpenOCD only once when connecting to it, this command should be specified in one of the … 41 :start-after: run-openocd-appimage-offset [all …]
D	index.rst	5 This document provides a guide to installing OpenOCD for {IDF_TARGET_NAME} and debugging using GDB.… 7 :ref:`jtag-debugging-introduction` 9 :ref:`jtag-debugging-how-it-works` 10 …Description how {IDF_TARGET_NAME}, JTAG interface, OpenOCD and GDB are interconnected and working … 11 :ref:`jtag-debugging-selecting-jtag-adapter` 13 :ref:`jtag-debugging-setup-openocd` 14 Procedure to install OpenOCD and verify that it is installed. 15 :ref:`jtag-debugging-configuring-target` 16 …Configuration of OpenOCD software and setting up of JTAG adapter hardware, which together make up … 17 :ref:`jtag-debugging-launching-debugger` [all …]
/hal_espressif-3.4.0/docs/zh_CN/api-guides/jtag-debugging/
D	esp32.inc	2 .. It contains target-specific snippets. 3 .. Comments and '---' lines act as delimiters. 7 .. These code blocks can be moved back to the main .rst files, with target-specific 11 .. run-openocd 15 openocd -f board/esp32-wrover-kit-3.3v.cfg 17 .. \|run-openocd-device-name\| replace:: 板载 ESP32-WROOM-32 模组的 ESP-WROVER-KIT 开发板 19 --- 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32-wrover-kit-3.3v.cfg 26 Open On-Chip Debugger v0.10.0-esp32-20190708 (2019-07-08-11:04) [all …]
D	building-openocd-macos.rst	2 MacOS 环境下从源码编译 OpenOCD 6 …ressif/openocd-esp32/releases>`_ 直接下载 OpenOCD 可执行文件，你还可以选择从源码编译得到 OpenOCD。如果想要快速设置 OpenOCD 而不是自行编译… 10 下载 OpenOCD 源码 13 支持 {IDF_TARGET_NAME} 的 OpenOCD 源代码可以从乐鑫官方的 GitHub 获得，网址为 https://github.com/espressif/openocd-esp32… 16 git clone --recursive https://github.com/espressif/openocd-esp32.git 18 克隆后的源代码被保存在 ``~/esp/openocd-esp32`` 目录中。 24 使用 Homebrew 安装编译 OpenOCD 所需的软件包:: 26 brew install automake libtool libusb wget gcc@4.9 pkg-config 28 构建 OpenOCD 31 配置和构建 OpenOCD 的流程如下:: [all …]
D	building-openocd-windows.rst	2 Windows 环境下从源码编译 OpenOCD 6 …ressif/openocd-esp32/releases>`_ 直接下载 OpenOCD 可执行文件，你还可以选择从源码编译得到 OpenOCD。如果想要快速设置 OpenOCD 而不是自行编译… 11 下载 OpenOCD 源码 14 支持 {IDF_TARGET_NAME} 的 OpenOCD 源代码可以从乐鑫官方的 GitHub 获得，网址为 https://github.com/espressif/openocd-esp32… 17 git clone --recursive https://github.com/espressif/openocd-esp32.git 19 克隆后的源代码被保存在 ``~/esp/openocd-esp32`` 目录中。 25 安装编译 OpenOCD 所需的软件包。 33 pacman -S libtool 34 pacman -S autoconf 35 pacman -S automake [all …]
D	building-openocd-linux.rst	2 Linux 环境下从源码编译 OpenOCD 6 …ressif/openocd-esp32/releases>`_ 直接下载 OpenOCD 可执行文件，你还可以选择从源码编译得到 OpenOCD。如果想要快速设置 OpenOCD 而不是自行编译… 11 下载 OpenOCD 源码 14 支持 {IDF_TARGET_NAME} 的 OpenOCD 源代码可以从乐鑫官方的 GitHub 获得，网址为 https://github.com/espressif/openocd-esp32… 17 git clone --recursive https://github.com/espressif/openocd-esp32.git 19 克隆后的源代码被保存在 ``~/esp/openocd-esp32`` 目录中。 25 安装编译 OpenOCD 所需的软件包。 33 sudo apt-get install make 34 sudo apt-get install libtool 35 sudo apt-get install pkg-config [all …]
D	esp32s3.inc	`2 .. It contains target-specific snippets. 3 .. Comments and '---' lines act as delimiters. 7 .. These code blocks can be moved back to the main .rst files, with target-specific 11 .. run-openocd 15 openocd -f board/esp32s3-builtin.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S3 19 --- 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s3-builtin.cfg 26 Open On-Chip Debugger v0.10.0-esp32-20210902 (2021-10-05-23:44) [all …]`
D	tips-and-quirks.rst	2 ------------------ 7 .. _jtag-debugging-tip-breakpoints: 12 …OpenOCD 实现了两种软件断点：闪存断点（最多 32 个）和 IRAM 断点（最多 32 个）。目前 GDB 无法在闪存中设置软件断点，因此除非解决此限制，否则这些断点只能由 OpenOCD … 15 .. _jtag-debugging-tip-where-breakpoints: 23 .. _jtag-debugging-tip-flash-mappings: 28 …OpenOCD 需要知道它们在闪存中的地址。为了完成从 {IDF_TARGET_NAME} 的地址空间到闪存地址的转换，OpenOCD 使用闪存中程序代码区域的映射。这些映射被保存在程序映像的头部… 32 偏移量应为十六进制格式，如果要恢复默认行为，可以将偏移地址设置为 ``-1`` 。 36 由于 GDB 在连接 OpenOCD 时仅仅请求一次内存映射，所以可以在 TCL 配置文件中指定该命令，或者通过命令行传递给 OpenOCD。对于后者，命令行示例如下： 41 :start-after: run-openocd-appimage-offset 42 :end-before: --- [all …]
D	esp32c3.inc	`2 .. It contains target-specific snippets. 3 .. Comments and '---' lines act as delimiters. 7 .. These code blocks can be moved back to the main .rst files, with target-specific 11 .. run-openocd 15 openocd -f board/esp32s2-kaluga-1.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S2-Kaluga-1 开发板 19 --- 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s2-kaluga-1.cfg 26 Open On-Chip Debugger v0.10.0-esp32-20200420 (2020-04-20-16:15) [all …]`
D	esp32s2.inc	`2 .. It contains target-specific snippets. 3 .. Comments and '---' lines act as delimiters. 7 .. These code blocks can be moved back to the main .rst files, with target-specific 11 .. run-openocd 15 openocd -f board/esp32s2-kaluga-1.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S2-Kaluga-1 开发板 19 --- 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s2-kaluga-1.cfg 26 Open On-Chip Debugger v0.10.0-esp32-20200420 (2020-04-20-16:15) [all …]`
D	index.rst	5 本文将介绍如何安装 {IDF_TARGET_NAME} 的 OpenOCD 调试环境，以及如何使用 GDB 来调试 {IDF_TARGET_NAME} 的应用程序。本文结构如下： 7 :ref:`jtag-debugging-introduction` 9 :ref:`jtag-debugging-how-it-works` 10 …介绍 {IDF_TARGET_NAME}、JTAG（Joint Test Action Group）接口、OpenOCD 和 GDB 如何相互连接，从而实现 {IDF_TARGET_NAME} 的… 11 :ref:`jtag-debugging-selecting-jtag-adapter` 13 :ref:`jtag-debugging-setup-openocd` 14 介绍如何安装官方预编译好的 OpenOCD 软件包并验证是否安装成功。 15 :ref:`jtag-debugging-configuring-target` 16 介绍如何设置 OpenOCD 软件并安装 JTAG 硬件，两项共同构成调试目标. 17 :ref:`jtag-debugging-launching-debugger` [all …]
/hal_espressif-3.4.0/examples/system/gcov/
D	README.md	1 \| Supported Targets \| ESP32 \| ESP32-S2 \| 2 \| ----------------- \| ----- \| -------- \| 8 …-IDF project to generate code coverage data, and how generate a code coverage report using Gcov or… 12 * Various methods of dumping code coverage data (e.g. Instant Run-Time Dump and Hard-coded Dump). 21 …-WROVER-KIT](https://docs.espressif.com/projects/esp-idf/en/latest/hw-reference/modules-and-boards… 22 …ESP32 or ESP32-S2 core board (e.g. ESP32-DevKitC, [ESP32-S2-Saola-1](https://docs.espressif.com/pr… 24 This example will assume that that an ESP-WROVER-KIT is used. 26 …ESP32 board, and power up both the JTAG and ESP32. For details about how to set up JTAG interface,… 28 …ce, you need to [Run OpenOCD](https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jta… 30 …lnet by entering the command below. The telnet terminal window is used to feed commands to OpenOCD: [all …]
/hal_espressif-3.4.0/tools/test_idf_tools/
D	test_idf_tools.py	`3 # SPDX-FileCopyrightText: 2019-2021 Espressif Systems (Shanghai) CO LTD 4 # SPDX-License-Identifier: Apache-2.0 39 ESP32ULP = 'esp32ulp-elf' 40 ESP32ULP_ARCHIVE = 'binutils-esp32ulp' 41 ESP32S2ULP = 'esp32s2ulp-elf' 42 ESP32S2ULP_ARCHIVE = 'binutils-esp32s2ulp' 43 OPENOCD = 'openocd-esp32' variable 44 RISCV_ELF = 'riscv32-esp-elf' 45 XTENSA_ESP32_ELF = 'xtensa-esp32-elf' 46 XTENSA_ESP32S2_ELF = 'xtensa-esp32s2-elf' [all …]`
/hal_espressif-3.4.0/examples/system/app_trace_to_host/
D	README.md	1 \| Supported Targets \| ESP32 \| ESP32-S2 \| 2 \| ----------------- \| ----- \| -------- \| 8 …tion Level Tracing Library](https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/app_t… 10 …-critical functions. Logging to host via JTAG is significantly faster and can be used in time-crit… 14 This example utilizes the following ESP-IDF features: 15 * [DAC driver](https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/peripherals/dac.… 16 * [ADC driver](https://docs.espressif.com/projects/esp-idf/en/latest/api-reference/peripherals/adc.… 17 * [Application Level Tracing Library](https://docs.espressif.com/projects/esp-idf/en/latest/api-gui… 18 * [OpenOCD](https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jtag-debugging/index.h… 26 …-WROVER-KIT](https://docs.espressif.com/projects/esp-idf/en/latest/hw-reference/modules-and-boards… [all …]
/hal_espressif-3.4.0/examples/storage/semihost_vfs/
D	README.md	5 This example demonstrates how to use semihosting VFS driver with ESP32. Example does the following … 19 …is example requires [OpenOCD](https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/jta… 20 NOTE: In order to run this example you need OpenOCD version `v0.10.0-esp32-20190313` or later. 22 Run OpenOCD using command: 24 bin/openocd -s share/openocd/scripts -c 'set ESP_SEMIHOST_BASEDIR '$IDF_PATH/examples/storage/semih… 26 This command also configures OpenOCD to expose example project `data` subdirectory to the target's … 33 idf.py -p PORT flash monitor 36 (To exit the serial monitor, type ``Ctrl-]``.) 38 See the Getting Started Guide for full steps to configure and use ESP-IDF to build projects. 63 The following are the graphical (non-control) characters defined by [all …]
/hal_espressif-3.4.0/examples/system/sysview_tracing/
D	README.md	1 \| Supported Targets \| ESP32 \| ESP32-S2 \| ESP32-C3 \| 2 \| ----------------- \| ----- \| -------- \| -------- \| 3 # Example: Application Level Tracing - SystemView Tracing (sysview_tracing) 5 … to perform system-wide behavioral analysis of the program using [SEGGER SystemView tool](https://… 7 …if.com/projects/esp-idf/en/latest/api-guides/app_trace.html#system-behaviour-analysis-with-segger-… 22 if (tim_arg->thnd != NULL) { 23 if (tim_arg->count++ < 10) { 25 …if (xTaskNotifyFromISR(tim_arg->thnd, tim_arg->count, eSetValueWithOverwrite, &xHigherPriorityTask… 26 ESP_EARLY_LOGE(TAG, "Failed to notify task %p", tim_arg->thnd); 34 // re-start timer [all …]

12 3

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