openocd (full) in projects: hal_espressif-3.4.0

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:openocd (Results 1 – 25 of 98) sorted by relevance

12 3 4

/hal_espressif-3.4.0/docs/zh_CN/api-guides/jtag-debugging/
D	index.rst	5 本文将介绍如何安装 {IDF_TARGET_NAME} 的 OpenOCD 调试环境，以及如何使用 GDB 来调试 {IDF_TARGET_NAME} 的应用程序。本文结构如下： 10 …介绍 {IDF_TARGET_NAME}、JTAG（Joint Test Action Group）接口、OpenOCD 和 GDB 如何相互连接，从而实现 {IDF_TARGET_NAME} 的… 13 :ref:`jtag-debugging-setup-openocd` 14 介绍如何安装官方预编译好的 OpenOCD 软件包并验证是否安装成功。 16 介绍如何设置 OpenOCD 软件并安装 JTAG 硬件，两项共同构成调试目标. 21 :ref:`jtag-debugging-building-openocd` 22 …`Windows <building-openocd-windows>`，:doc:`Linux <building-openocd-linux>` 和 :doc:`macOS <building… 24 介绍使用 OpenOCD 和 GDB 通过 JTAG 接口调试 {IDF_TARGET_NAME} 时的注意事项和补充内容。 43 乐鑫已完成 OpenOCD 移植，以支持 {IDF_TARGET_NAME} 处理器和多核 FreeRTOS 架构（此作为大多数 {IDF_TARGET_NAME} 应用程序的基础）。此外，乐鑫还提… 45 本文将介绍如何在 Linux、Windows 和 macOS 环境下为 {IDF_TARGET_NAME} 安装 OpenOCD，并使用 GDB 进行软件调试。除部分安装流程有所不同外，所有操作系统… [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 所需的软件包。 42 …安装 ``pkg-config`` 会破坏 esp-idf 的工具链，因而在 OpenOCD 构建完成后，应将其卸载。详见文末进一步说明。如果想要再次构建 OpenOCD，你需要再次运行 ``pa… 45 构建 OpenOCD 48 配置和构建 OpenOCD 的流程如下:: [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 所需的软件包:: 28 构建 OpenOCD 31 配置和构建 OpenOCD 的流程如下:: 33 cd ~/esp/openocd-esp32 [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 所需的软件包。 50 构建 OpenOCD 53 配置和构建 OpenOCD 的流程如下:: 55 cd ~/esp/openocd-esp32 [all …]
D	tips-and-quirks.rst	12 …OpenOCD 实现了两种软件断点：闪存断点（最多 32 个）和 IRAM 断点（最多 32 个）。目前 GDB 无法在闪存中设置软件断点，因此除非解决此限制，否则这些断点只能由 OpenOCD … 28 …OpenOCD 需要知道它们在闪存中的地址。为了完成从 {IDF_TARGET_NAME} 的地址空间到闪存地址的转换，OpenOCD 使用闪存中程序代码区域的映射。这些映射被保存在程序映像的头部… 36 由于 GDB 在连接 OpenOCD 时仅仅请求一次内存映射，所以可以在 TCL 配置文件中指定该命令，或者通过命令行传递给 OpenOCD。对于后者，命令行示例如下： 41 :start-after: run-openocd-appimage-offset 44 另外还可以通过 OpenOCD 的 telnet 会话执行该命令，然后再连接 GDB，不过这种方式似乎没有那么便捷。 56 OpenOCD 支持的编译时的选项 59 ESP-IDF 有一些针对 OpenOCD 调试功能的选项可以在编译时进行设置： 61 …PREFIX}_DEBUG_OCDAWARE` 默认会被使能。如果程序抛出了不可修复或者未处理的异常，并且此时已经连接上了 JTAG 调试器（即 OpenOCD 正在运行），那么 ESP-IDF … 72 OpenOCD 完全支持 ESP-IDF 自带的 FreeRTOS 操作系统，GDB 会将 FreeRTOS 中的任务当做线程。使用 GDB 命令 ``i threads`` 可以查看所有的线程，使… 78 在 OpenOCD 的配置文件中设置 SPI 闪存的工作电压 [all …]
D	esp32c3.inc	11 .. run-openocd 15 openocd -f board/esp32s2-kaluga-1.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S2-Kaluga-1 开发板 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s2-kaluga-1.cfg 29 http://openocd.org/doc/doxygen/bugs.html 39 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s2-kaluga-1.cfg`` 43 .. run-openocd-upload 47 openocd -f board/esp32s2-kaluga-1.cfg -c "program_esp filename.bin 0x10000 verify exit" 51 .. run-openocd-src-linux [all …]
D	esp32s2.inc	11 .. run-openocd 15 openocd -f board/esp32s2-kaluga-1.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S2-Kaluga-1 开发板 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s2-kaluga-1.cfg 29 http://openocd.org/doc/doxygen/bugs.html 39 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s2-kaluga-1.cfg`` 43 .. run-openocd-upload 47 openocd -f board/esp32s2-kaluga-1.cfg -c "program_esp filename.bin 0x10000 verify exit" 51 .. run-openocd-src-linux [all …]
D	esp32s3.inc	11 .. run-openocd 15 openocd -f board/esp32s3-builtin.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S3 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s3-builtin.cfg 29 http://openocd.org/doc/doxygen/bugs.html 46 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s3-builtin.cfg`` 50 .. run-openocd-upload 54 openocd -f board/esp32s3-builtin.cfg -c "program_esp filename.bin 0x10000 verify exit" 58 .. run-openocd-src-linux [all …]
D	esp32.inc	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 开发板 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32-wrover-kit-3.3v.cfg 29 http://openocd.org/doc/doxygen/bugs.html 40 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32-wrover-kit-3.3v.cfg`` 44 .. run-openocd-upload 48 openocd -f board/esp32-wrover-kit-3.3v.cfg -c "program_esp filename.bin 0x10000 verify exit" 52 .. run-openocd-src-linux [all …]
D	configure-ft2232h-jtag.rst	28 安装和配置 USB 驱动，这样 OpenOCD 才能够与 \|devkit-name\| 板上的 JTAG 接口通信，并且使用 UART 接口上传待烧写的镜像文件。请根据你的操作系统按照以下步骤进行安装… 59 现在，\|devkit-name\| 的 JTAG 接口应该可以被 OpenOCD 使用了，想要进一步设置调试环境，请前往 :ref:`jtag-debugging-run-openocd` 章节。 78 3. 根据 `OpenOCD README 文档 <https://sourceforge.net/p/openocd/code/ci/master/tree/README>`_ 中 “Permi… 92 现在，\|devkit-name\| 的 JTAG 接口应该可以被 OpenOCD 使用了，想要进一步设置调试环境，请前往 :ref:`jtag-debugging-run-openocd` 章节。 98 …同的操作。但是，这两个通道中只有一个是被用作串口，而另一个用于 JTAG，如果操作系统已经为用于 JTAG 的通道加载了 FTDI 串口驱动的话，OpenOCD 将无法连接到芯片。有两个方法可以解… 100 1. 在启动 OpenOCD 之前手动卸载 FTDI 串口驱动程序，然后启动 OpenOCD，再加载串口驱动程序。 129 4. 运行 OpenOCD:: 132 :start-after: run-openocd 141 如果你需要重启 OpenOCD，则无需再次卸载 FTDI 驱动程序，只需停止 OpenOCD 并再次启动它。只有在重新连接 \|devkit-name\| 或者切换了电源的情况下才需要再次卸载驱动。 199 想要进一步设置调试环境，请前往 :ref:`jtag-debugging-run-openocd` 章节。
/hal_espressif-3.4.0/docs/en/api-guides/jtag-debugging/
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 …_TARGET_NAME}-enabled variant of OpenOCD are available from Espressif GitHub under https://github.… 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:: 28 Build OpenOCD 31 Proceed with configuring and building OpenOCD:: 33 cd ~/esp/openocd-esp32 [all …]
D	index.rst	5 This document provides a guide to installing OpenOCD for {IDF_TARGET_NAME} and debugging using GDB.… 10 …Description how {IDF_TARGET_NAME}, JTAG interface, OpenOCD and GDB are interconnected and working … 13 :ref:`jtag-debugging-setup-openocd` 14 Procedure to install OpenOCD and verify that it is installed. 16 …Configuration of OpenOCD software and setting up of JTAG adapter hardware, which together make up … 21 :ref:`jtag-debugging-building-openocd` 22 … build OpenOCD from sources for :doc:`Windows <building-openocd-windows>`, :doc:`Linux <building-o… 24 … collection of tips and quirks related to JTAG debugging of {IDF_TARGET_NAME} with OpenOCD and GDB. 43 …OpenOCD to support the {IDF_TARGET_NAME} processor and the multi-core FreeRTOS （which is the found… 45 This document provides a guide to installing OpenOCD for {IDF_TARGET_NAME} and debugging using GDB … [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 …_TARGET_NAME}-enabled variant of OpenOCD are available from Espressif GitHub under https://github.… 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. 50 Build OpenOCD 53 Proceed with configuring and building OpenOCD:: 55 cd ~/esp/openocd-esp32 [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:: 29 Download Sources of OpenOCD 32 …_TARGET_NAME}-enabled variant of OpenOCD are available from Espressif GitHub under https://github.… 35 git clone --recursive https://github.com/espressif/openocd-esp32.git 38 The clone of sources should be now saved in ``~/esp/openocd-esp32`` directory. 44 Build and export variables for a following OpenOCD compilation:: 53 Build OpenOCD 56 Proceed with configuring and building OpenOCD:: [all …]
D	esp32c3.inc	10 .. run-openocd 14 openocd -f board/esp32c3-builtin.cfg 16 .. \|run-openocd-device-name\| replace:: ESP32-C3 through built-in USB connection 20 .. run-openocd-output 24 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32c3-builtin.cfg 28 http://openocd.org/doc/doxygen/bugs.html 42 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32c3-builtin.cfg`` 46 .. run-openocd-upload 50 openocd -f board/esp32c3-builtin.cfg -c "program_esp filename.bin 0x10000 verify exit" 54 .. run-openocd-src-linux [all …]
D	esp32s2.inc	11 .. run-openocd 15 openocd -f board/esp32s2-kaluga-1.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S2-Kaluga-1 board 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s2-kaluga-1.cfg 29 http://openocd.org/doc/doxygen/bugs.html 39 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s2-kaluga-1.cfg`` 43 .. run-openocd-upload 47 openocd -f board/esp32s2-kaluga-1.cfg -c "program_esp filename.bin 0x10000 verify exit" 51 .. run-openocd-src-linux [all …]
D	esp32s3.inc	11 .. run-openocd 15 openocd -f board/esp32s3-builtin.cfg 17 .. \|run-openocd-device-name\| replace:: ESP32-S3 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32s3-builtin.cfg 29 http://openocd.org/doc/doxygen/bugs.html 46 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s3-builtin.cfg`` 50 .. run-openocd-upload 54 openocd -f board/esp32s3-builtin.cfg -c "program_esp filename.bin 0x10000 verify exit" 58 .. run-openocd-src-linux [all …]
D	esp32.inc	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 21 .. run-openocd-output 25 user-name@computer-name:~/esp/esp-idf$ openocd -f board/esp32-wrover-kit-3.3v.cfg 29 http://openocd.org/doc/doxygen/bugs.html 40 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32-wrover-kit-3.3v.cfg`` 44 .. run-openocd-upload 48 openocd -f board/esp32-wrover-kit-3.3v.cfg -c "program_esp filename.bin 0x10000 verify exit" 52 .. run-openocd-src-linux [all …]
D	tips-and-quirks.rst	12 …OpenOCD: flash (up to 32) and IRAM (up to 32) breakpoints. Currently GDB can not set software brea… 28 …OpenOCD needs to know their flash addresses. To accomplish conversion from the {IDF_TARGET_NAME} a… 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 44 …Another option is to execute that command via OpenOCD telnet session and then connect GDB, but it … 56 Support options for OpenOCD at compile time 59 ESP-IDF has some support options for OpenOCD debugging which can be set at compile time: 61 …c or unhandled exception is thrown and a JTAG debugger is connected (ie OpenOCD is running), ESP-… 72 OpenOCD has explicit support for the ESP-IDF FreeRTOS. GDB can see FreeRTOS tasks as threads. Viewi… 78 Why to set SPI flash voltage in OpenOCD configuration? [all …]
D	configure-ft2232h-jtag.rst	28 Install and configure USB drivers, so OpenOCD is able to communicate with JTAG interface on \|devkit… 59 …ld be available to the OpenOCD. To carry on with debugging environment setup, proceed to section :… 78 3. Following section "Permissions delegation" in `OpenOCD's README <https://sourceforge.net/p/open… 92 …ld be available to the OpenOCD. To carry on with debugging environment setup, proceed to section :… 98 …the OS has loaded FTDI serial port driver for the channel used for JTAG, OpenOCD will not be able … 100 1. Manually unload the FTDI serial port driver before starting OpenOCD, start OpenOCD, then load th… 130 4. Run OpenOCD: 133 :start-after: run-openocd 142 …If you need to restart OpenOCD, there is no need to unload FTDI driver again — just stop OpenOCD a… 200 To carry on with debugging environment setup, proceed to section :ref:`jtag-debugging-run-openocd`.
/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", 17 "name": "openocd-esp32", 30 "openocd", 39 …"url": "https://github.com/espressif/openocd-esp32/releases/download/v0.11.0-esp32-20220411/openoc… 44 …"url": "https://github.com/espressif/openocd-esp32/releases/download/v0.11.0-esp32-20220411/openoc… 49 …"url": "https://github.com/espressif/openocd-esp32/releases/download/v0.11.0-esp32-20220411/openoc… 54 …"url": "https://github.com/espressif/openocd-esp32/releases/download/v0.11.0-esp32-20220411/openoc… [all …]
/hal_espressif-3.4.0/tools/idf_py_actions/
D	debug_ext.py	33 …message = ('Please check if another process uses the mentioned ports. OpenOCD already running, per… 34 …'Please list all processes to check if OpenOCD is already running; if so, terminate it before star… 41 if 'openocd' in processes and processes['openocd'] is not None: 42 p = processes['openocd'] 44 # watch OpenOCD (for 5x500ms) to check if it hasn't terminated or outputs an error 47 print('OpenOCD exited with {}'.format(p.poll())) 54 # expect OpenOCD has started successfully - stop watching 59 # OpenOCD exited or error message detected -> print possible output and terminate 60 …raise FatalError('Action "{}" failed due to errors in OpenOCD:\n{}'.format(target, _check_for_comm… 78 if target == 'openocd': [all …]
/hal_espressif-3.4.0/docs/zh_CN/api-guides/
D	app_trace.rst	32 …据覆盖旧数据。该模式在用户仅对最新的跟踪数据感兴趣时会很有用，例如分析程序在崩溃之前的行为。主机可以稍后根据用户的请求来读取数据，例如通过特殊的 OpenOCD 命令（假如使用了 JTAG 接口）。 42 1. 主机端：应用程序跟踪是通过 JTAG 来完成的，因此需要在主机上安装并运行 OpenOCD。相关详细信息请参阅 :doc:`JTAG Debugging <../api-guides… 97 /* in case of error host tracing tool (e.g. OpenOCD) will report incomplete user buffer / 150 / in case of error host tracing tool (e.g. OpenOCD) will report incomplete user buffer */ 156 3. 运行 OpenOCD（参见 :doc:`JTAG 调试 <../api-guides/jtag-debugging/index>`）。 157 4. 连接到 OpenOCD 的 telnet 服务器，在终端执行如下命令 ``telnet <oocd_host> 4444``。如果在运行 OpenOCD 的同一台机器上打开 159 5. 使用特殊的 OpenOCD 命令开始收集待跟踪的命令，此命令将传输跟踪数据并将其重定向到指定的文件或套接字（当前仅支持文件作为跟踪数据目标）。相关命令的说明请参阅 :ref:`jtag-deb… 162 OpenOCD 应用程序跟踪命令 165 …添加一个数据头，其中包含有分配的用户缓冲区的大小（2 字节）和实际写入的数据长度（2 字节），也就是说数据头总共长 4 字节。负责读取跟踪数据的 OpenOCD 命令在读取到不完整的用户数据块时会… 167 下面是 OpenOCD 应用程序跟踪命令的使用说明。 [all …]
/hal_espressif-3.4.0/docs/en/api-guides/
D	app_trace.rst	32 …ash. Host can read the data later on upon user request, e.g. via special OpenOCD command in case o… 42 1. Host side: Application tracing is done over JTAG, so it needs OpenOCD to be set up and runni… 97 … /* in case of error host tracing tool (e.g. OpenOCD) will report incomplete user buffer / 150 … / in case of error host tracing tool (e.g. OpenOCD) will report incomplete user buffer */ 156 3. Run OpenOCD (see :doc:`JTAG Debugging <../api-guides/jtag-debugging/index>`). 157 …OpenOCD telnet server. It can be done using the following command in terminal ``telnet <oocd_host>… 158 …OpenOCD command. This command will transfer tracing data and redirect them to specified file or so… 162 OpenOCD Application Level Tracing Commands 165 …tually written data (2 bytes). So total length of the header is 4 bytes. OpenOCD command which rea… 167 Below is the description of available OpenOCD application tracing commands. [all …]
/hal_espressif-3.4.0/examples/system/gcov/
D	README.md	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: 46 * Enable OpenOCD Debug Stubs under `Component config -> ESP System Settings -> OpenOCD debug stubs` 66 …s `Ready to dump GCOV data...`, users should execute the `esp gcov dump` OpenOCD command. The exam… 81 …inue looping through it's main blink function. Users can call `esp gcov` OpenOCD command to trigge… 123 ### OpenOCD Out of Sync 125 …OpenOCD command via telnet, it could indicate that OpenOCD and the ESP32 are out of sync. This occ… 142 * Restart OpenOCD

12 3 4

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