run (full) in projects: hal_espressif-3.6.0

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:run (Results 1 – 25 of 1060) sorted by relevance

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

/hal_espressif-3.6.0/tools/test_idf_size/
D	test.sh	10 …&& python -m coverage run -a $IDF_PATH/tools/idf_size.py --json build/hello_world.map > size_outpu… 12 …&& python -m coverage run -a $IDF_PATH/tools/test_idf_size/mem_test.py size_output.json esptool_ou… 18 …&& python -m coverage run -a $IDF_PATH/tools/idf_size.py --json app_$1.map \| python $IDF_PATH/tool… 19 …&& python -m coverage run -a $IDF_PATH/tools/idf_size.py --json --archives app_$1.map \| python $ID… 20 …&& python -m coverage run -a $IDF_PATH/tools/idf_size.py --json --files app_$1.map \| python $IDF_P… 21 …&& python -m coverage run -a $IDF_PATH/tools/idf_size.py --json --archive_details libdriver.a app_… 31 && python -m coverage run -a $IDF_PATH/tools/idf_size.py app.map &>> output \ 33 && python -m coverage run -a $IDF_PATH/tools/idf_size.py bootloader.map &>> output \ 35 && python -m coverage run -a $IDF_PATH/tools/idf_size.py overflow.map &>> output \ 37 && python -m coverage run -a $IDF_PATH/tools/idf_size.py --archives app.map &>> output \ [all …]
/hal_espressif-3.6.0/components/esptool_py/esptool/
D	.gitlab-ci.yml	60 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_imagegen.py 61 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_espsecure.py 62 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_merge_bin.py 63 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_image_info.py 64 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_modules.py 65 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_espefuse.py --chip esp32 66 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_espefuse.py --chip esp32c2 67 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_espefuse.py --chip esp32c3 68 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_espefuse.py --chip esp32s2 69 - coverage run --parallel-mode -m pytest ${CI_PROJECT_DIR}/test/test_espefuse.py --chip esp32s3 [all …]
D	CONTRIBUTING.rst	16 Development mode allows you to run the latest development version from the `esptool.py repository o… 24 …cutable script wrappers in the user’s ``bin`` directory. The wrappers will run the scripts found i… 26 It’s also possible to run the scripts directly from the working directory with this Development Mod… 28 To also install additional tools needed for actually developing and testing ``esptool.py``, run thi… 100 … tools will be automatically run by ``pre-commit`` if that is configured. To check your code manua… 102 When you submit a Pull Request, the GitHub Actions automated build system will run automated checks… 109 …`esptool.py`` installed (see `Development Setup`_) in your environment in order to run these tests. 111 The following tests run automatically by GitHub Actions for each Pull Request. You can run them loc… 119 …lowing tests are not run automatically by GitHub Actions, because they need real connected hardwar… 121 * ``test_esptool.py`` contains integration tests for ``esptool.py`` and needs to be run against re… [all …]
/hal_espressif-3.6.0/examples/build_system/cmake/idf_as_lib/
D	README.md	7 in this example can run on either host or on an ESP32, and the appropriate libraries are linked 10 is meant to be run on the host to simulate the same application behavior. 17 application that can run on the target without relying on the typical ESP-IDF application template. 39 To build this example, the user can either run [build-esp32.sh](./build-esp32.sh) to build for the … 40 or run [build.sh](./build.sh) to build for the host: 52 # Builds the example to run on host 58 To flash and run the example, users can run either [run-esp32.sh](./run-esp32.sh) or [run.sh](./ru… 59 on what the example was built for. In the case of ``run-esp32.sh``, the port needs to be specified: 62 # Run the example on device connected to /dev/ttyUSB1 63 ./run-esp32.sh /dev/ttyUSB1 [all …]
/hal_espressif-3.6.0/tools/unit-test-app/
D	README.md	3 ESP-IDF unit tests are run using Unit Test App. The app can be built with the unit tests for a spec… 14 * Follow the printed instructions to flash, or run `idf.py -p PORT flash`. 24 * Follow the printed instructions to flash, or run `make flash`. 31 If building unit tests to run on a smaller flash size, edit `partition_table_unit_tests_app.csv` an… 35 The unit test loader will prompt by showing a menu of available tests to run: 37 * Type a number to run a single test. 38 * `` to run all tests. 39 `[tagname]` to run tests with "tag" 40 * `![tagname]` to run tests without "tag" (`![ignore]` is very useful as it runs all CI-enabled tes… 41 * `"test name here"` to run test with given name [all …]
/hal_espressif-3.6.0/examples/storage/nvs_rw_blob/
D	README.md	8 …* blob - contains a table with module run times. The table is read from NVS to dynamically allocat… 20 This example can be run on most common development boards which have an active button connected to … 24 Build the project and flash it to the board, then run monitor tool to view serial output: 36 First run: 39 Run time: 49 After booting again, restart counter and run time array will be printed: 53 Run time: 61 Run time: 66 To reset the counter and run time array, erase the contents of flash memory using `idf.py erase-fla…
/hal_espressif-3.6.0/components/freertos/
D	Kconfig	4 bool "Run FreeRTOS only on first core" 40 the main tick source to increase counters, run timers and do 283 Use this constant to define the priority that the timer task will run at. 344 bool "Enable FreeRTOS to collect run time stats" 351 usage of processor time amongst FreeRTOS tasks. Run time stats are 353 source (Note that run time stats are only valid until the clock source 357 display the run time of each task as a % of the total run time of all 358 CPUs (task run time / no of CPUs) / (total run time / 100 ) 362 prompt "Choose the clock source for run time stats" 366 Choose the clock source for FreeRTOS run time stats. Options are CPU0's [all …]
/hal_espressif-3.6.0/docs/zh_CN/api-guides/jtag-debugging/
D	esp32c3.inc	11 .. run-openocd 17 .. \|run-openocd-device-name\| replace:: ESP32-S2-Kaluga-1 开发板 21 .. run-openocd-output 39 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s2-kaluga-1.cfg`` 43 .. run-openocd-upload 51 .. run-openocd-src-linux 59 .. run-openocd-src-win 73 .. run-openocd-appimage-offset 125 .. run-openocd-d3 133 .. run-openocd-d3-tee [all …]
D	esp32s2.inc	11 .. run-openocd 17 .. \|run-openocd-device-name\| replace:: ESP32-S2-Kaluga-1 开发板 21 .. run-openocd-output 39 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s2-kaluga-1.cfg`` 43 .. run-openocd-upload 51 .. run-openocd-src-linux 59 .. run-openocd-src-win 73 .. run-openocd-appimage-offset 125 .. run-openocd-d3 133 .. run-openocd-d3-tee [all …]
D	esp32s3.inc	11 .. run-openocd 17 .. \|run-openocd-device-name\| replace:: ESP32-S3 21 .. run-openocd-output 46 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s3-builtin.cfg`` 50 .. run-openocd-upload 58 .. run-openocd-src-linux 66 .. run-openocd-src-win 80 .. run-openocd-appimage-offset 134 .. run-openocd-d3 142 .. run-openocd-d3-tee [all …]
D	esp32.inc	11 .. run-openocd 17 .. \|run-openocd-device-name\| replace:: 板载 ESP32-WROOM-32 模组的 ESP-WROVER-KIT 开发板 21 .. run-openocd-output 40 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32-wrover-kit-3.3v.cfg`` 44 .. run-openocd-upload 52 .. run-openocd-src-linux 60 .. run-openocd-src-win 74 .. run-openocd-appimage-offset 141 .. run-openocd-d3 149 .. run-openocd-d3-tee [all …]
/hal_espressif-3.6.0/docs/en/api-guides/jtag-debugging/
D	esp32c3.inc	10 .. run-openocd 16 .. \|run-openocd-device-name\| replace:: ESP32-C3 through built-in USB connection 20 .. run-openocd-output 42 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32c3-builtin.cfg`` 46 .. run-openocd-upload 54 .. run-openocd-src-linux 62 .. run-openocd-src-win 76 .. run-openocd-appimage-offset 133 .. run-openocd-d3 141 .. run-openocd-d3-tee [all …]
D	esp32s2.inc	11 .. run-openocd 17 .. \|run-openocd-device-name\| replace:: ESP32-S2-Kaluga-1 board 21 .. run-openocd-output 39 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s2-kaluga-1.cfg`` 43 .. run-openocd-upload 51 .. run-openocd-src-linux 59 .. run-openocd-src-win 73 .. run-openocd-appimage-offset 125 .. run-openocd-d3 133 .. run-openocd-d3-tee [all …]
D	esp32s3.inc	11 .. run-openocd 17 .. \|run-openocd-device-name\| replace:: ESP32-S3 21 .. run-openocd-output 46 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32s3-builtin.cfg`` 50 .. run-openocd-upload 58 .. run-openocd-src-linux 66 .. run-openocd-src-win 80 .. run-openocd-appimage-offset 137 .. run-openocd-d3 145 .. run-openocd-d3-tee [all …]
D	esp32.inc	11 .. run-openocd 17 .. \|run-openocd-device-name\| replace:: ESP-WROVER-KIT with ESP32-WROOM-32 module 21 .. run-openocd-output 40 .. \|run-openocd-cfg-file-err\| replace:: ``Can't find board/esp32-wrover-kit-3.3v.cfg`` 44 .. run-openocd-upload 52 .. run-openocd-src-linux 60 .. run-openocd-src-win 74 .. run-openocd-appimage-offset 141 .. run-openocd-d3 149 .. run-openocd-d3-tee [all …]
/hal_espressif-3.6.0/examples/bluetooth/esp_ble_mesh/ble_mesh_coex_test/
D	README.md	19 * ble_dev : Run only the BLE program. 20 * coex_dev: Run BLE and Wi-Fi program. 21 * wifi_dev: Run only the Wi-Fi program. 23 …WiFi coexistence, you should use a development board with PSRAM that could run a coexistence progr… 45 ## Run Test Case Manually 46 Configure to Manual Mode via `Example Configuration --->run mode (manual) ` 80 ## Run Test Case By Automation 81 Configure to Automatic Mode via `Example Configuration --->run mode (auto) ` 84 1. Select a development board as coexistence role by `Example Configuration --->select role (run d… 93 1. Select a development board as bluetooth role by `select role (run device as bluetooth role) ` [all …]
/hal_espressif-3.6.0/docs/en/api-guides/
D	unit-tests-legacy.rst	31 …Y_END()`` in each test case. ``unity_platform.c`` will run ``UNITY_BEGIN()`` autonomously, and run… 111 …out reset (or only need to check if reset happens). Sometimes we expect to run some specific tests… 129 …ons to users. It need user interactions (select cases and select different stages) to run the case. 146 When the build finishes, it will print instructions for flashing the chip. You can simply run ``mak… 148 You can also run ``make flash TESTS_ALL=1`` or ``make TEST_COMPONENTS='xxx'`` to build and flash. E… 169 (10) "global initializers run in the correct order" [cxx] 187 Test cases can be run by inputting one of the following: 189 - Test case name in quotation marks (for example, ``"esp_ota_begin() verifies arguments"``) to run … 191 - Test case index (for example, ``1``) to run a single test case. 193 - Module name in square brackets (for example, ``[cxx]``) to run all test cases for a specific modu… [all …]
D	freertos-smp.rst	48 …run on a particular core. Therefore, threads in an SMP systems will also have a core affinity that… 50 - A thread that is pinned to a particular core will only be able to run on that core 92 - ``tskNO_AFFINITY`` which allows the task to be run on both CPUs 149 …run, it will always select the current highest priority ready state task. In ESP-IDF FreeRTOS, eac… 152 - The task is not currently being run by another core 154 However, users should not assume that the two highest priority ready state tasks are always run by … 160 …will have Task A running on CPU0 and Task C running on CPU1. Task B is not run even though it is t… 165 …pted by the scheduler if the scheduler determines that a higher priority task can run on that core. 167 However, there are some instances where a higher priority task that becomes ready can be run on mul… 180 …bin time slicing due to the fact that a particular task may not be able to run on a particular cor… [all …]
/hal_espressif-3.6.0/tools/
D	check_python_dependencies.py	61 … # we're using this script to check non-default requirements.txt, so tell the user to run pip 62 …print('Please check the documentation for the feature you are using, or run "%s -m pip install -r … 65 # ask the user to run install.bat again. 70 …print('To install the missing packages, please run "%s"' % os.path.join(idf_path, install_script))… 72 …print("The recommended way to install a packages is via \"pacman\". Please run \"pacman -Ss <packa… 75 …print("NOTE: You may need to run \"pacman -Syu\" if your package database is older and run twice i… 76 "previous run updated \"pacman\" itself.") 84 … "you run \"pacman -Syu\" followed by \"pacman -S mingw-w64-i686-python{}-cryptography\"." 88 … print("Please run the following command to install MSYS2's MINGW Python setuptools package:")
/hal_espressif-3.6.0/components/app_update/test/
D	test_switch_ota.c	171 /* @brief Copies a current app to next partition (OTA0-15), after that ESP is rebooting and run thi… 181 …TA0-15) using esp_ota_write_with_offest(), after that ESP is rebooting and run this (the next) OTA… 359 // 2 Stage: run factory -> check it -> copy factory to OTA0 -> reboot --//-- 360 // 3 Stage: run OTA0 -> check it -> copy OTA0 to OTA1 -> reboot --//-- 361 // 4 Stage: run OTA1 -> check it -> copy OTA1 to OTA0 -> reboot --//-- 362 // 5 Stage: run OTA0 -> check it -> erase OTA_DATA for next tests -> PASS 397 // 2 Stage: run factory -> check it -> copy factory to OTA0 -> reboot --//-- 398 // 3 Stage: run OTA0 -> check it -> corrupt ota data -> reboot --//-- 399 // 4 Stage: run factory -> check it -> erase OTA_DATA for next tests -> PASS 440 // 2 Stage: run factory -> check it -> copy factory to OTA0 -> reboot --//-- [all …]
/hal_espressif-3.6.0/examples/system/freertos/real_time_stats/
D	README.md	5 … of FreeRTOS (i.e. run time stats). Furthermore, statistics of `vTaskGetRunTimeStats()` are on… 13 This example should be able to run on any commonly available ESP32 development board. 21 * Select `Enable FreeRTOS to collect run time stats` under `Component Config > FreeRTOS` (this shou… 23 * `Choose the clock source for run time stats` configured under `Component Config > FreeRTOS`. The … 27 Build the project and flash it to the board, then run monitor tool to view serial output: 46 \| Task \| Run Time \| Percentage
/hal_espressif-3.6.0/docs/en/api-guides/tools/
D	idf-docker-image.rst	47 In the project directory, run:: 49 docker run --rm -v $PWD:/project -w /project espressif/idf idf.py build 54 - ``docker run``: runs a Docker image. It is a shorter form of the command ``docker container run``. 62 docker run --rm -v $PWD:/project -w /project espressif/idf:release-v4.0 idf.py build 72 docker run --rm -v $PWD:/project -w /project espressif/idf make defconfig all -j4 81 …docker run --rm -v $PWD:/project -v kconfig:/opt/esp/idf/tools/kconfig -w /project espressif/idf m… 83 If you need clean up the ``kconfig`` volume, run ``docker volume rm kconfig``. 92 docker run --rm -v $PWD:/project -w /project -it espressif/idf
/hal_espressif-3.6.0/examples/system/unit_test/
D	README.md	11 …the program are automatically collected into a list, and run-time facilities are provided to run f… 52 This example doesn't require any special hardware, and can run on any ESP32 development board. 64 …s not of much value to run. Application project is provided mainly to illustrate the layout of all… 66 * Run `idf.py -p PORT flash monitor` in the current directory (`unit_test`). 71 * Enter `test` directory (`unit_test/test`), and run `idf.py -p PORT flash monitor`. 157 * Run specific test by its index: type the number and press ENTER. 158 * Run a group of tests with a certain tag: type the tag, including square brackets, and press ENTER. 159 * Run all tests except the ones with a certain tag: press `!`, then type the tag, including the squ… 160 * Run test with a specific name: type the name of the test, including quotes, and press ENTER. 161 * Run all the tests: press `*` and then ENTER.
/hal_espressif-3.6.0/docs/en/get-started/
D	windows-setup.rst	62 …f the installation process you can check out option ``Run ESP-IDF PowerShell Environment`` or ``Ru… 64 ``Run ESP-IDF PowerShell Environment``: 68 :alt: Completing the ESP-IDF Tools Setup Wizard with Run ESP-IDF PowerShell Environment 71 Completing the ESP-IDF Tools Setup Wizard with Run ESP-IDF PowerShell Environment 80 ``Run ESP-IDF Command Prompt (cmd.exe)``: 84 :alt: Completing the ESP-IDF Tools Setup Wizard with Run ESP-IDF Command Prompt (cmd.exe) 87 Completing the ESP-IDF Tools Setup Wizard with Run ESP-IDF Command Prompt (cmd.exe) 107 2. Alternatively, run ``cmd.exe``, then change to the ESP-IDF directory you wish to use, and run ``…
/hal_espressif-3.6.0/examples/system/ota/
D	README.md	24 … reads the contents of the `ota_data` partition to determine which application is selected to run. 34 "ESP-Dev-Board" is necessary to run the OTA examples. Make sure Ethernet is configured correctly if… 49 …106`) must match the CN field used when [generating the certificate and key](#run-https-server) 53 Run `idf.py -p PORT flash monitor` to build and flash the project. This command checks if the part… 61 ### Run HTTPS Server 63 After a successful build, we need to create a self-signed certificate and run a simple HTTPS server… 68 * To create a new self-signed certificate and key, run the command `openssl req -x509 -newkey rsa:2… 70 * To start the HTTPS server, run the command `openssl s_server -WWW -key ca_key.pem -cert ca_cert.p… 76 …nssl binary to your path: `set PATH=%LocalAppData%\Git\usr\bin;%PATH%` and run openssl's http serv… 96 …o the first OTA partition in case the `factory` partition does not exist), run the command `idf.py… [all …]

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

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