diff --git a/.github/workflows/examples-nrfconnect.yaml b/.github/workflows/examples-nrfconnect.yaml index 034a532a93f25d..cc2daca2f7c266 100644 --- a/.github/workflows/examples-nrfconnect.yaml +++ b/.github/workflows/examples-nrfconnect.yaml @@ -68,8 +68,6 @@ jobs: - '**/tests/**' shell: - 'examples/shell/nrfconnect/**' - pigweed-app: - - 'examples/pigweed-app/nrfconnect/**' - name: Set up environment for size reports if: ${{ !env.ACT }} env: @@ -149,15 +147,6 @@ jobs: nrfconnect nrf52840dk_nrf52840 shell \ examples/shell/nrfconnect/build/zephyr/zephyr.elf \ /tmp/bloat_reports/ - - name: Build example nRF Connect SDK Pigweed on nRF52840 DK - if: github.event_name == 'push' || steps.changed_paths.outputs.pigweed-app == 'true' - timeout-minutes: 15 - run: | - scripts/examples/nrfconnect_example.sh pigweed-app nrf52840dk_nrf52840 - .environment/pigweed-venv/bin/python3 scripts/tools/memory/gh_sizes.py \ - nrfconnect nrf52840dk_nrf52840 pigweed-app \ - examples/pigweed-app/nrfconnect/build/zephyr/zephyr.elf \ - /tmp/bloat_reports/ - name: Build example nRF Connect SDK Pump App on nRF52840 DK if: github.event_name == 'push' || steps.changed_paths.outputs.nrfconnect == 'true' timeout-minutes: 15 diff --git a/.vscode/tasks.json b/.vscode/tasks.json index 2fb34adb0e8423..8516b5b12f2e5c 100644 --- a/.vscode/tasks.json +++ b/.vscode/tasks.json @@ -109,19 +109,6 @@ "command": "scripts/tests/esp32_qemu_tests.sh /tmp/test_logs", "problemMatcher": [] }, - { - "label": "Build nRF Connect Pigweed Example (nRF52840)", - "type": "shell", - "command": "source scripts/activate.sh && scripts/examples/nrfconnect_example.sh pigweed-app nrf52840dk_nrf52840", - "group": "build", - "problemMatcher": { - "base": "$gcc", - "fileLocation": [ - "relative", - "${workspaceFolder}/examples/pigweed-app/nrfconnect/build/nrf52840dk_nrf52840" - ] - } - }, { "label": "Build i.MX Linux examples", "type": "shell", diff --git a/examples/pigweed-app/nrfconnect/.gitignore b/examples/pigweed-app/nrfconnect/.gitignore deleted file mode 100644 index 84c048a73cc2e5..00000000000000 --- a/examples/pigweed-app/nrfconnect/.gitignore +++ /dev/null @@ -1 +0,0 @@ -/build/ diff --git a/examples/pigweed-app/nrfconnect/CMakeLists.txt b/examples/pigweed-app/nrfconnect/CMakeLists.txt deleted file mode 100644 index 183e929f2bdc80..00000000000000 --- a/examples/pigweed-app/nrfconnect/CMakeLists.txt +++ /dev/null @@ -1,102 +0,0 @@ -# -# Copyright (c) 2020 Project CHIP Authors -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. -# -cmake_minimum_required(VERSION 3.13.1) - -get_filename_component(CHIP_ROOT ${CMAKE_CURRENT_SOURCE_DIR}/third_party/connectedhomeip REALPATH) -get_filename_component(NRFCONNECT_COMMON ${CHIP_ROOT}/examples/platform/nrfconnect REALPATH) -set(PIGWEED_ROOT "${CHIP_ROOT}/third_party/pigweed/repo") - -include(${CHIP_ROOT}/config/nrfconnect/app/check-nrfconnect-version.cmake) - -# Load NCS/Zephyr build system -set(CONF_FILE prj.conf) - -if(${BOARD} STREQUAL "nrf52840dongle_nrf52840") - list(INSERT OVERLAY_CONFIG 0 ${CHIP_ROOT}/config/nrfconnect/app/overlay-usb_support.conf) -endif() -list(APPEND ZEPHYR_EXTRA_MODULES ${CHIP_ROOT}/config/nrfconnect/chip-module) -find_package(Zephyr HINTS $ENV{ZEPHYR_BASE}) - -if (EXISTS ${CMAKE_CURRENT_SOURCE_DIR}/boards/${BOARD}.conf) - list(APPEND CONF_FILE boards/${BOARD}.conf) -endif() - -project(chip-nrf52840-pigweed-example) - -include(${CHIP_ROOT}/config/nrfconnect/app/enable-gnu-std.cmake) - -# -Wmaybe-uninitialized has too many false positives, including on std::optional -# and chip::Optional. Make it nonfatal. -# -# See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635 -target_compile_options(app PRIVATE -Werror -Wno-error=maybe-uninitialized) - -# Make all targets created below depend on zephyr_interface to inherit MCU-related compilation flags -link_libraries($) - -include(${PIGWEED_ROOT}/pw_build/pigweed.cmake) -include(${PIGWEED_ROOT}/pw_protobuf_compiler/proto.cmake) - -pw_set_module_config(pw_rpc_CONFIG pw_rpc.disable_global_mutex_config) -pw_set_backend(pw_log pw_log_basic) -pw_set_backend(pw_assert.check pw_assert_log.check_backend) -pw_set_backend(pw_assert.assert pw_assert.assert_compatibility_backend) -pw_set_backend(pw_sys_io pw_sys_io.nrfconnect) -set(dir_pw_third_party_nanopb "${CHIP_ROOT}/third_party/nanopb/repo" CACHE STRING "" FORCE) - -add_subdirectory(third_party/connectedhomeip/examples/platform/nrfconnect/pw_sys_io) -add_subdirectory(third_party/connectedhomeip/third_party/nanopb/repo) -add_subdirectory(third_party/connectedhomeip/third_party/pigweed/repo) - -target_include_directories(app PRIVATE main/include - ${NRFCONNECT_COMMON}/util/include - ${CHIP_ROOT}/src/lib/support - ${PIGWEED_ROOT}/pw_sys_io/public - ${PIGWEED_ROOT}/pw_span/public_overrides - ${PIGWEED_ROOT}/pw_span/public - ${PIGWEED_ROOT}/pw_polyfill/public - ${PIGWEED_ROOT}/pw_polyfill/standard_library_public - ${PIGWEED_ROOT}/pw_polyfill/public_overrides - ${PIGWEED_ROOT}/pw_rpc/public - ${PIGWEED_ROOT}/pw_status/public - ${PIGWEED_ROOT}/pw_preprocessor/public - ../../common - ../../common/pigweed/nrfconnect - ${NRFCONNECT_COMMON}/pw_sys_io/public) - -target_sources(app PRIVATE main/main.cpp - ../../common/pigweed/RpcService.cpp - ../../common/pigweed/nrfconnect/PigweedLoggerMutex.cpp - ${NRFCONNECT_COMMON}/util/LEDWidget.cpp - ${NRFCONNECT_COMMON}/util/PigweedLogger.cpp -) - -target_link_libraries(app PUBLIC - pw_checksum - pw_hdlc - pw_hdlc.pw_rpc - pw_log - pw_rpc.nanopb.echo_service - pw_rpc.server - pw_sys_io -) - -# Workaround cyclic dependency between nrf_security libraries) -target_link_libraries(mbedcrypto_base PUBLIC - mbedcrypto -) - -include(${CHIP_ROOT}/config/nrfconnect/app/flashing.cmake) diff --git a/examples/pigweed-app/nrfconnect/Kconfig b/examples/pigweed-app/nrfconnect/Kconfig deleted file mode 100644 index 94a99f971ac195..00000000000000 --- a/examples/pigweed-app/nrfconnect/Kconfig +++ /dev/null @@ -1,20 +0,0 @@ -# -# Copyright (c) 2022 Project CHIP Authors -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. -# -mainmenu "Matter nRF Connect Lighting Example Application" - -rsource "../../../config/nrfconnect/chip-module/Kconfig.features" -rsource "../../../config/nrfconnect/chip-module/Kconfig.defaults" -source "Kconfig.zephyr" diff --git a/examples/pigweed-app/nrfconnect/README.md b/examples/pigweed-app/nrfconnect/README.md deleted file mode 100644 index 8e24da6b73e2ba..00000000000000 --- a/examples/pigweed-app/nrfconnect/README.md +++ /dev/null @@ -1,296 +0,0 @@ -# Matter nRF Connect Pigweed Example Application - -The nRF Connect Pigweed Example demonstrates the usage of Pigweed module -functionalities in an application. - -Nordic Semiconductor logo -nRF52840 DK - -The example is based on -[Matter](https://github.com/project-chip/connectedhomeip), the -[Pigweed](https://pigweed.googlesource.com/pigweed/pigweed) module, which is a -collection of libraries that provide different functionalities for embedded -systems, and Nordic Semiconductor's nRF Connect SDK. - -You can use this example as a training ground for making experiments, testing -Pigweed module features and checking what actions are necessary to fully -integrate Pigweed in a Matter project. - -Pigweed functionalities are being gradually integrated into Matter. Currently, -the following features are available: - -- **Echo RPC** - Creates a Remote Procedure Call server and allows sending - commands through the serial port to the device, which makes echo and sends - the received commands back. - -
- -## Overview - -This example is running on the nRF Connect platform, which is based on the -[nRF Connect SDK](https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/index.html) -and [Zephyr RTOS](https://zephyrproject.org/). Visit Matter's -[nRF Connect platform overview](../../../docs/guides/nrfconnect_platform_overview.md) -to read more about the platform structure and dependencies. - -Pigweed libraries are built and organized in a way that enables faster and more -reliable development. In the Matter project, the Pigweed module is planned to be -used to create system infrastructures, for example for performing on-device -tests, but considering its general functionalities, it can be useful also in -other cases. - -
- -## Requirements - -The application requires a specific revision of the nRF Connect SDK to work -correctly. See [Setting up the environment](#setting-up-the-environment) for -more information. - -### Supported devices - -The example supports building and running on the following devices: - -| Hardware platform | Build target | Platform image | -| ------------------------------------------------------------------------------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | -| [nRF52840 Dongle](https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52840-Dongle) | `nrf52840dongle_nrf52840` |
nRF52840 DonglenRF52840 Dongle
| -| [nRF52840 DK](https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF52840-DK) | `nrf52840dk_nrf52840` |
nRF52840 DKnRF52840 DK
| - -
- -## Device UI - -This section lists the User Interface elements that you can use to control and -monitor the state of the device. These correspond to PCB components on the -hardware platform. - -**LED 1** shows the overall state of the device. The following states are -possible: - -- _Solid On_ — The application was flashed and ran successfully. - -**Serial port** can be used to communicate with the device by sending commands -and receiving responses. - -> **Important**: -> -> Please note that supported hardware platforms are using different transport -> interfaces to perform serial communication, which leads to differences in -> configuration. By default, these interfaces are used: -> -> - `nrf52840dk_nrf52840` - UART interface routed to the SEGGER J-Link USB -> port. -> - `nrf52840dongle_nrf52840` - USB interface routed to the USB port. - -
- -## Setting up the environment - -Before building the example, check out the Matter repository and sync submodules -using the following command: - - $ git submodule update --init - -The example requires a specific revision of the nRF Connect SDK. You can either -install it along with the related tools directly on your system or use a Docker -image that has the tools pre-installed. - -If you are a macOS user, you won't be able to use the Docker container to flash -the application onto a Nordic development kit due to -[certain limitations of Docker for macOS](https://docs.docker.com/docker-for-mac/faqs/#can-i-pass-through-a-usb-device-to-a-container). -Use the [native shell](#using-native-shell-for-setup) for building instead. - -### Using Docker container for setup - -To use the Docker container for setup, complete the following steps: - -1. If you do not have the nRF Connect SDK installed yet, create a directory for - it by running the following command: - - $ mkdir ~/nrfconnect - -2. Download the latest version of the nRF Connect SDK Docker image by running - the following command: - - $ docker pull nordicsemi/nrfconnect-chip - -3. Start Docker with the downloaded image by running the following command, - customized to your needs as described below: - - $ docker run --rm -it -e RUNAS=$(id -u) -v ~/nrfconnect:/var/ncs -v ~/connectedhomeip:/var/chip \ - -v /dev/bus/usb:/dev/bus/usb --device-cgroup-rule "c 189:* rmw" nordicsemi/nrfconnect-chip - - In this command: - - - _~/nrfconnect_ can be replaced with an absolute path to the nRF Connect - SDK source directory. - - _~/connectedhomeip_ must be replaced with an absolute path to the Matter - source directory. - - _-v /dev/bus/usb:/dev/bus/usb --device-cgroup-rule "c 189:_ rmw"\* - parameters can be omitted if you are not planning to flash the example - onto hardware. These parameters give the container access to USB devices - connected to your computer such as the nRF52840 DK. - - _--rm_ can be omitted if you do not want the container to be - auto-removed when you exit the container shell session. - - _-e RUNAS=\$(id -u)_ is needed to start the container session as the - current user instead of root. - -4. Update the nRF Connect SDK to the most recent supported revision, by running - the following command: - - $ cd /var/chip - $ python3 scripts/setup/nrfconnect/update_ncs.py --update - -Now you can proceed with the [Building](#building) instruction. - -### Using native shell for setup - -To use the native shell for setup, complete the following steps: - -1. Download and install the following additional software: - - - [nRF Command Line Tools](https://www.nordicsemi.com/Software-and-Tools/Development-Tools/nRF-Command-Line-Tools) - - [GN meta-build system](https://gn.googlesource.com/gn/) - -2. If you do not have the nRF Connect SDK installed, follow the - [guide](https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_assistant.html#) - in the nRF Connect SDK documentation to install the latest stable nRF - Connect SDK version. Since command-line tools will be used for building the - example, installing SEGGER Embedded Studio is not required. - - If you have the SDK already installed, continue to the next step and update - the nRF Connect SDK after initializing environment variables. - -3. Initialize environment variables referred to by the Matter and the nRF - Connect SDK build scripts. Replace _nrfconnect-dir_ with the path to your - nRF Connect SDK installation directory, and _toolchain-dir_ with the path to - GNU Arm Embedded Toolchain. - - $ source nrfconnect-dir/zephyr/zephyr-env.sh - $ export ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb - $ export GNUARMEMB_TOOLCHAIN_PATH=toolchain-dir - -4. Update the nRF Connect SDK to the most recent supported revision by running - the following command (replace _matter-dir_ with the path to Matter - repository directory): - - $ cd matter-dir - $ python3 scripts/setup/nrfconnect/update_ncs.py --update - -Now you can proceed with the [Building](#building) instruction. - -
- -## Building - -Complete the following steps, regardless of the method used for setting up the -environment: - -1. Run the `activate.sh` script, regardless of the building strategy. The - script is required for building the Pigweed library. Use the following - command: - - $ source scripts/activate.sh - -2. Navigate to the example's directory: - - $ cd examples/pigweed-app/nrfconnect - -3. Run the following command to build the example, with _build-target_ replaced - with the build target name of the Nordic Semiconductor's kit you own, for - example `nrf52840dk_nrf52840`: - - $ west build -b build-target - - You only need to specify the build target on the first build. See - [Requirements](#requirements) for the build target names of compatible kits. - -The output `zephyr.hex` file will be available in the `build/zephyr/` directory. - -### Removing build artifacts - -If you're planning to build the example for a different kit or make changes to -the configuration, remove all build artifacts before building. To do so, use the -following command: - - $ rm -r build - -
- -## Configuring the example - -The Zephyr ecosystem is highly configurable and allows you to modify many -aspects of the application. The configuration system is based on Kconfig files -and the settings can be modified using the menuconfig utility. - -To open the menuconfig utility, complete the following steps: - -1. Go to the example directory by running the following command, with the - _example-dir_ directory name updated for your configuration: - - $ cd example-dir - -2. Choose one of the following options: - - - If you are running the build for the first time, run the following - command: - - $ west build -b nrf52840dk_nrf52840 -t menuconfig - - - If you are running a subsequent build, run the following command: - - $ west build -t menuconfig - - - If you are running menuconfig with ninja, run the following commands: - - $ cd example-dir/build - $ ninja menuconfig - -Changes done with menuconfig will be lost if the `build` directory is deleted. -To make them persistent, save the configuration options in the `prj.conf` file. - -For more information, see the -[Configuring nRF Connect SDK examples](../../../docs/guides/nrfconnect_examples_configuration.md) -page. - -
- -## Flashing and debugging - -The flashing and debugging procedure is different for the nRF52840 DK and the -nRF52840 Dongle. - -### Flashing on the nRF52840 DK - -To flash the application to the device, use the west tool and run the following -command from the example directory: - - $ west flash --erase - -If you have multiple nRF52840 development kits connected, west will prompt you -to pick the correct one. - -To debug the application on target, run the following command from the example -directory: - - $ west debug - -### Flashing on the nRF52840 Dongle - -Visit -[Programming and Debugging nRF52840 Dongle](https://docs.zephyrproject.org/latest/boards/arm/nrf52840dongle_nrf52840/doc/index.html#programming-and-debugging) -to read more about flashing on the nRF52840 Dongle. - -
- -## Testing the example - -Run the following command to start an interactive Python shell, where the Echo -RPC commands can be invoked: - - python -m pw_hdlc.rpc_console --device /dev/ttyACM0 -b 115200 --proto-globs $CHIP_ROOT/third_party/pigweed/repo/pw_rpc/echo.proto -o /tmp/pw_rpc.out - -To send an Echo RPC message, type the following command, where the actual -message is the text in quotation marks after the `msg=` phrase: - - rpcs.pw.rpc.EchoService.Echo(msg="hi") diff --git a/examples/pigweed-app/nrfconnect/boards/nrf52840dk_nrf52840.overlay b/examples/pigweed-app/nrfconnect/boards/nrf52840dk_nrf52840.overlay deleted file mode 100644 index e3716a4a9248e9..00000000000000 --- a/examples/pigweed-app/nrfconnect/boards/nrf52840dk_nrf52840.overlay +++ /dev/null @@ -1,27 +0,0 @@ -/* - * Copyright (c) 2020 Project CHIP Authors - * - * Licensed under the Apache License, Version 2.0 (the "License"); - * you may not use this file except in compliance with the License. - * You may obtain a copy of the License at - * - * http://www.apache.org/licenses/LICENSE-2.0 - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the License is distributed on an "AS IS" BASIS, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the License for the specific language governing permissions and - * limitations under the License. - */ - -/ { - /* - * In some default configurations within the nRF Connect SDK, - * e.g. on nRF52840, the chosen zephyr,entropy node is &cryptocell. - * This devicetree overlay ensures that default is overridden wherever it - * is set, as this application uses the RNG node for entropy exclusively. - */ - chosen { - zephyr,entropy = &rng; - }; -}; diff --git a/examples/pigweed-app/nrfconnect/boards/nrf5340dk_nrf5340_cpuapp.conf b/examples/pigweed-app/nrfconnect/boards/nrf5340dk_nrf5340_cpuapp.conf deleted file mode 100644 index b9f4ed7648da78..00000000000000 --- a/examples/pigweed-app/nrfconnect/boards/nrf5340dk_nrf5340_cpuapp.conf +++ /dev/null @@ -1,17 +0,0 @@ -# -# Copyright (c) 2021 Project CHIP Authors -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. -# - -CONFIG_XOROSHIRO_RANDOM_GENERATOR=y diff --git a/examples/pigweed-app/nrfconnect/main/include/AppConfig.h b/examples/pigweed-app/nrfconnect/main/include/AppConfig.h deleted file mode 100644 index a8a44f3f41108f..00000000000000 --- a/examples/pigweed-app/nrfconnect/main/include/AppConfig.h +++ /dev/null @@ -1,20 +0,0 @@ -/* - * - * Copyright (c) 2020 Project CHIP Authors - * - * Licensed under the Apache License, Version 2.0 (the "License"); - * you may not use this file except in compliance with the License. - * You may obtain a copy of the License at - * - * http://www.apache.org/licenses/LICENSE-2.0 - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the License is distributed on an "AS IS" BASIS, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the License for the specific language governing permissions and - * limitations under the License. - */ - -#pragma once - -#define SYSTEM_STATE_LED DK_LED1 diff --git a/examples/pigweed-app/nrfconnect/main/main.cpp b/examples/pigweed-app/nrfconnect/main/main.cpp deleted file mode 100644 index dd092668d4192f..00000000000000 --- a/examples/pigweed-app/nrfconnect/main/main.cpp +++ /dev/null @@ -1,65 +0,0 @@ -/* - * - * Copyright (c) 2020 Project CHIP Authors - * - * Licensed under the Apache License, Version 2.0 (the "License"); - * you may not use this file except in compliance with the License. - * You may obtain a copy of the License at - * - * http://www.apache.org/licenses/LICENSE-2.0 - * - * Unless required by applicable law or agreed to in writing, software - * distributed under the License is distributed on an "AS IS" BASIS, - * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. - * See the License for the specific language governing permissions and - * limitations under the License. - */ - -#include "AppConfig.h" -#include "LEDWidget.h" -#include "PigweedLoggerMutex.h" -#include "pigweed/RpcService.h" -#include - -#include "pw_rpc/echo_service_nanopb.h" -#include "pw_sys_io/sys_io.h" -#include "pw_sys_io_nrfconnect/init.h" - -#include -#include - -LOG_MODULE_REGISTER(app, CONFIG_CHIP_APP_LOG_LEVEL); - -namespace { -LEDWidget sStatusLED; -pw::rpc::EchoService sEchoService; - -void RegisterServices(pw::rpc::Server & server) -{ - server.RegisterService(sEchoService); -} - -} // namespace - -int main() -{ - pw_sys_io_Init(); - - LOG_INF("=================================================="); - LOG_INF("chip-nrf52840-pigweed-example starting"); -#if BUILD_RELEASE - LOG_INF("*** PSEUDO-RELEASE BUILD ***"); -#else - LOG_INF("*** DEVELOPMENT BUILD ***"); -#endif - LOG_INF("=================================================="); - - // Light up the LED as a visual feedback that the flash was - // successful. - LEDWidget::InitGpio(); - sStatusLED.Init(SYSTEM_STATE_LED); - sStatusLED.Set(true); - - Start(RegisterServices, &::chip::rpc::logger_mutex); - return 0; -} diff --git a/examples/pigweed-app/nrfconnect/prj.conf b/examples/pigweed-app/nrfconnect/prj.conf deleted file mode 100644 index fad377211225f9..00000000000000 --- a/examples/pigweed-app/nrfconnect/prj.conf +++ /dev/null @@ -1,64 +0,0 @@ -# -# Copyright (c) 2020 Project CHIP Authors -# -# Licensed under the Apache License, Version 2.0 (the "License"); -# you may not use this file except in compliance with the License. -# You may obtain a copy of the License at -# -# http://www.apache.org/licenses/LICENSE-2.0 -# -# Unless required by applicable law or agreed to in writing, software -# distributed under the License is distributed on an "AS IS" BASIS, -# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -# See the License for the specific language governing permissions and -# limitations under the License. -# - -CONFIG_CHIP=y - -# This sample uses Kconfig.defaults to set options common for all -# samples. This file should contain only options specific for this sample -# or overrides of default values. - -# Add support for LEDs and buttons on Nordic development kits -CONFIG_DK_LIBRARY=y - -# Additional configs for debbugging experience. -CONFIG_THREAD_NAME=y -CONFIG_MPU_STACK_GUARD=y - -# Enable Pigweed RPC -CONFIG_CHIP_PW_RPC=y - -# Disable OTA requestor -CONFIG_CHIP_OTA_REQUESTOR=n - -# Disable QSPI NOR -CONFIG_CHIP_QSPI_NOR=n - -# Add support for C++17 to build Pigweed components -CONFIG_STD_CPP14=n -CONFIG_STD_CPP17=y - -# Add support for Zephyr console component to use it for Pigweed console purposes -CONFIG_CONSOLE_SUBSYS=y -CONFIG_CONSOLE_GETCHAR=y -CONFIG_CONSOLE_PUTCHAR_BUFSIZE=256 - -# Disable features which may interfere with Pigweed HDLC transport -CONFIG_SHELL=n -CONFIG_OPENTHREAD_SHELL=n -CONFIG_BOOT_BANNER=n - -# Configure Zephyr logger with defaults backends disabled as the app provides its own, -# based on Pigweed HDLC. -CONFIG_LOG=y -CONFIG_LOG_MODE_MINIMAL=n -CONFIG_LOG_MODE_IMMEDIATE=y -CONFIG_LOG_BACKEND_UART=n -CONFIG_LOG_BACKEND_RTT=n -CONFIG_LOG_OUTPUT=y - -# Disable factory data support. -CONFIG_CHIP_FACTORY_DATA=n -CONFIG_CHIP_FACTORY_DATA_BUILD=n diff --git a/examples/pigweed-app/nrfconnect/third_party/connectedhomeip b/examples/pigweed-app/nrfconnect/third_party/connectedhomeip deleted file mode 120000 index c866b86874994d..00000000000000 --- a/examples/pigweed-app/nrfconnect/third_party/connectedhomeip +++ /dev/null @@ -1 +0,0 @@ -../../../.. \ No newline at end of file