Searched +full:- +full:- +full:non +full:- +full:interactive (Results 1 – 10 of 10) sorted by relevance
/hal_espressif-3.5.0/tools/docker/ |
D | Dockerfile | 7 && apt-get update \ 8 && apt-get install -y \ 9 apt-utils \ 11 ca-certificates \ 19 libffi-dev \ 20 libncurses-dev \ 22 libusb-1.0-0-dev \ 24 ninja-build \ 26 python3-pip \ 29 xz-utils \ [all …]
|
/hal_espressif-3.5.0/ |
D | .gitlab-ci.yml | 2 - pre_check 3 - build 4 - assign_test 5 - build_doc 6 - target_test 7 - host_test 8 - test_deploy 9 - deploy 10 - post_deploy 14 # Disable those non-protected push triggered pipelines [all …]
|
/hal_espressif-3.5.0/make/ |
D | project_config.mk | 12 # kconfiglib requires Windows-style paths for kconfig files 13 COMPONENT_KCONFIGS := $(shell cygpath -m $(COMPONENT_KCONFIGS)) 14 COMPONENT_KCONFIGS_PROJBUILD := $(shell cygpath -m $(COMPONENT_KCONFIGS_PROJBUILD)) 15 COMPONENT_SDKCONFIG_RENAMES := $(shell cygpath -m $(COMPONENT_SDKCONFIG_RENAMES)) 16 COMPONENT_KCONFIGS_SOURCE_FILE := $(shell cygpath -m $(COMPONENT_KCONFIGS_SOURCE_FILE)) 17 COMPONENT_KCONFIGS_PROJBUILD_SOURCE_FILE := $(shell cygpath -m $(COMPONENT_KCONFIGS_PROJBUILD_SOURC… 30 # overrides (usually used for esp-idf examples) 33 # Workaround to run make parallel (-j). mconf-idf and conf-idf cannot be made simultaneously 34 $(KCONFIG_TOOL_DIR)/mconf-idf: $(KCONFIG_TOOL_DIR)/conf-idf 37 $(KCONFIG_TOOL_DIR)/mconf-idf $(KCONFIG_TOOL_DIR)/conf-idf: $(wildcard $(KCONFIG_TOOL_DIR)/*.c) $(w… [all …]
|
D | common.mk | 1 # Functionality common to both top-level project makefile (project.mk) 12 -include $(SDKCONFIG_MAKEFILE) 13 export SDKCONFIG_MAKEFILE # sub-makes (like bootloader) will reuse this path 15 # BATCH_BUILD flag disables interactive terminal features, defaults to verbose build 34 MAKEFLAGS += --silent 38 MAKEFLAGS += --warn-undefined-variables 56 # macro to keep an absolute path as-is, but resolve a relative path 60 # $(2) directory to resolve non-absolute path against 77 # This allows you to have something like an "order-only phony prerequisite", 80 # Because normal order-only prerequisites don't work with phony targets. [all …]
|
D | project.mk | 9 # This makefile requires the environment variable IDF_PATH to be set to the top-level esp-idf direc… 13 …PHONY: build-components menuconfig defconfig all build clean all_binaries check-submodules size si… 21 # target can build everything without triggering the per-component "to 27 @echo "make menuconfig - Configure IDF project" 28 @echo "make defconfig - Set defaults for all new configuration options" 30 @echo "make all - Build app, bootloader, partition table" 31 @echo "make flash - Flash app, bootloader, partition table to a chip" 32 @echo "make clean - Remove all build output" 33 @echo "make size - Display the static memory footprint of the app" 34 @echo "make size-components, size-files - Finer-grained memory footprints" [all …]
|
/hal_espressif-3.5.0/docs/en/contribute/ |
D | documenting-code.rst | 6 …on is to provide quick summary on documentation style used in `espressif/esp-idf`_ repository and … 9 ------------ 21 .. image:: ../../_static/doc-code-documentation-inline.png 29 --------------- 35 .. image:: ../../_static/doc-code-documentation-rendered.png 41 ---------- 51 .. image:: ../../_static/doc-code-function.png 57 .. image:: ../../_static/doc-code-void-function.png 63 .. image:: ../../_static/doc-code-member.png 71 * - ESP_OK if erase operation was successful [all …]
|
/hal_espressif-3.5.0/docs/en/api-guides/jtag-debugging/ |
D | using-debugger.rst | 2 -------------- 7 * from :ref:`jtag-debugging-using-debugger-eclipse` 8 * from :ref:`jtag-debugging-using-debugger-command-line` 9 * using :ref:`jtag-debugging-with-idf-py` 12 .. _jtag-debugging-using-debugger-eclipse: 19 …eck if debugger works using :ref:`jtag-debugging-with-idf-py` or from :ref:`jtag-debugging-using-d… 25 …<../../get-started/eclipse-setup>`. The source of :example:`get-started/blink` application is ava… 33 …een build yet. See :doc:`Build and Flash with Eclipse IDE <../../get-started/eclipse-setup>` how t… 37 A sample window with settings entered in points 1 - 5 is shown below. 39 .. figure:: ../../../_static/hw-debugging-main-tab.jpg [all …]
|
/hal_espressif-3.5.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' 44 RISCV_ELF = 'riscv32-esp-elf' 45 XTENSA_ESP32_ELF = 'xtensa-esp32-elf' 46 XTENSA_ESP32S2_ELF = 'xtensa-esp32s2-elf' [all …]
|
/hal_espressif-3.5.0/tools/ |
D | idf_tools.py | 2 # coding=utf-8 4 # SPDX-FileCopyrightText: 2019-2022 Espressif Systems (Shanghai) CO LTD 6 # SPDX-License-Identifier: Apache-2.0 8 # This script helps installing tools required to use the ESP-IDF, and updating PATH 25 # * To install the Python environment, run `idf_tools.py install-python-env`. 80 IDF_ENV_FILE = 'idf-env.json' 93 PYTHON_PLATFORM = platform.system() + '-' + platform.machine() 99 PLATFORM_MACOS_ARM64 = 'macos-arm64' 100 PLATFORM_LINUX32 = 'linux-i686' 101 PLATFORM_LINUX64 = 'linux-amd64' [all …]
|
/hal_espressif-3.5.0/docs/en/api-guides/ |
D | build-system-legacy.rst | 5 .. include:: ../gnu-make-legacy.rst 9 Read this document if you want to know how to organise an ESP-IDF project using GNU Make build syst… 11 We recommend using the esp-idf-template_ project as a starting point for your project. 16 The esp-idf README file contains a description of how to use the build system to build your project. 21 An ESP-IDF project can be seen as an amalgamation of a number of components. For example, for a web… 23 - The {IDF_TARGET_NAME} base libraries (libc, rom bindings etc) 24 - The Wi-Fi drivers 25 - A TCP/IP stack 26 - The FreeRTOS operating system 27 - A webserver [all …]
|