Home
last modified time | relevance | path

Searched +full:nrf21540 +full:- +full:fem (Results 1 – 11 of 11) sorted by relevance

/Zephyr-latest/dts/bindings/net/wireless/
Dnordic,nrf21540-fem.yaml2 # SPDX-License-Identifier: Apache-2.0
6 This is a representation of the nRF21540 Radio Front-End module.
8 See the "nordic,nrf21540-fem-spi" binding to configure the SPI
10 of the SPI bus you have connected to the FEM. Then you "connect"
11 the FEM and SPI configurations using the spi-if property.
13 Here is an example nRF21540 configuration with a SPI interface
17 compatible = "nordic,nrf-spim";
19 cs-gpios = <&gpio1 3 GPIO_ACTIVE_LOW>;
22 my_spi_if: nrf21540-spi@0 {
23 compatible = "nordic,nrf21540-fem-spi";
[all …]
Dnordic,nrf21540-fem-spi.yaml2 # SPDX-License-Identifier: Apache-2.0
6 This is a SPI device interface to the nRF21540 Radio Front-End module
8 compatible: "nordic,nrf21540-fem-spi"
10 include: spi-device.yaml
Dnordic,nrf-radio.yaml2 # SPDX-License-Identifier: Apache-2.0
15 Front-End Module (FEM) support
16 ------------------------------
18 External front-end modules are range extenders used for boosting
20 system includes an external FEM, set it up in the devicetree using
21 this binding's 'fem' property, like this example:
24 fem = <&nrf_radio_fem>;
27 nrf_radio_fem: my-fem {
32 Currently supported "compatible" properties for the FEM node are:
34 - generic-fem-two-ctrl-pins
[all …]
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/nordic/hal/nrf5/radio/
Dradio_nrf5_fem_nrf21540.h4 * SPDX-License-Identifier: Apache-2.0
9 * radio node's fem property, in the case that it has compatible
10 * "nordic,nrf21540-fem".
14 * For nRF21540 devices:
17 * --------- --------
18 * PA pin tx-en-gpios
19 * PA offset tx-en-settle-time-us
20 * LNA pin rx-en-gpios
21 * LNA offset rx-en-settle-time-us
22 * PDN pin pdn-gpios
[all …]
/Zephyr-latest/samples/bluetooth/hci_ipc/boards/
Dnrf5340_audio_dk_nrf5340_cpunet_nrf21540_ek.overlay3 compatible = "nordic,nrf21540-fem";
4 tx-en-gpios = <&arduino_header 11 GPIO_ACTIVE_HIGH>; /* D5 */
5 rx-en-gpios = <&arduino_header 9 GPIO_ACTIVE_HIGH>; /* D3 */
6 pdn-gpios = <&arduino_header 15 GPIO_ACTIVE_HIGH>; /* D9 */
7 ant-sel-gpios = <&arduino_header 10 GPIO_ACTIVE_HIGH>; /* D4 */
8 mode-gpios = <&arduino_header 8 GPIO_ACTIVE_HIGH>; /* D2 */
9 supply-voltage-mv = <3000>;
14 fem = <&nrf_radio_fem>;
/Zephyr-latest/dts/bindings/gpio/
Dnordic,nrf-gpio-forwarder.yaml2 # SPDX-License-Identifier: Apache-2.0
15 Here is an example of how a nrf-gpio-forwarder can be used with a nRF5340
16 combined with a nRF21540 Front-End module. Consider the following node
18 the details of the nRF21540 Front-End module's interface:
20 nrf_radio_fem: nrf21540 {
21 compatible = "nordic,nrf21540-fem";
22 tx-en-gpios = <&gpio0 30 GPIO_ACTIVE_HIGH>;
23 rx-en-gpios = <&gpio1 11 GPIO_ACTIVE_HIGH>;
24 pdn-gpios = <&gpio1 10 GPIO_ACTIVE_HIGH>;
25 mode-gpios = <&gpio1 12 GPIO_ACTIVE_HIGH>;
[all …]
/Zephyr-latest/boards/nordic/thingy53/
Dthingy53_nrf5340_cpunet.dts4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include "thingy53_nrf5340_cpunet-pinctrl.dtsi"
10 #include <zephyr/dt-bindings/input/input-event-codes.h>
14 compatible = "nordic,thingy53-nrf5340-cpunet";
18 zephyr,shell-uart = &uart0;
19 zephyr,uart-mcumgr = &uart0;
20 zephyr,bt-mon-uart = &uart0;
21 zephyr,bt-c2h-uart = &uart0;
22 zephyr,bt-hci-ipc = &ipc0;
[all …]
Dthingy53_nrf5340_common.dtsi4 * SPDX-License-Identifier: Apache-2.0
6 #include "thingy53_nrf5340_common-pinctrl.dtsi"
7 #include <zephyr/dt-bindings/input/input-event-codes.h>
8 #include <zephyr/dt-bindings/battery/battery.h>
12 zephyr,bt-hci-ipc = &ipc0;
13 zephyr,bt-hci = &bt_hci_ipc0;
14 nordic,802154-spinel-ipc = &ipc0;
19 compatible = "gpio-keys";
33 compatible = "gpio-leds";
49 compatible = "pwm-leds";
[all …]
/Zephyr-latest/boards/nordic/nrf21540dk/
Dnrf21540dk_nrf52840.dts5 * SPDX-License-Identifier: Apache-2.0
8 /dts-v1/;
10 #include "nrf21540dk_nrf52840-pinctrl.dtsi"
11 #include <zephyr/dt-bindings/input/input-event-codes.h>
14 model = "Nordic nRF21540 DK NRF52840";
15 compatible = "nordic,nrf21540-dk-nrf52840";
19 zephyr,shell-uart = &uart0;
20 zephyr,uart-mcumgr = &uart0;
21 zephyr,bt-mon-uart = &uart0;
22 zephyr,bt-c2h-uart = &uart0;
[all …]
/Zephyr-latest/doc/releases/
Drelease-notes-2.6.rst13 * Added support for 64-bit ARCv3
14 * Split ARM32 and ARM64, ARM64 is now a top-level architecture
15 * Added initial support for Arm v8.1-m and Cortex-M55
22 https://github.com/zephyrproject-rtos/example-application
34 * CVE-2021-3581: Under embargo until 2021-09-04
41 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
46 * Driver APIs now return ``-ENOSYS`` if optional functions are not implemented.
47 If the feature is not supported by the hardware ``-ENOTSUP`` will be returned.
48 Formerly ``-ENOTSUP`` was returned for both failure modes, meaning this change
194 * Added support for null pointer dereferencing detection in Cortex-M.
[all …]
Drelease-notes-3.3.rst14 * Introduced :ref:`USB-C <usbc_api>` device stack with PD (power delivery)
17 CMSIS-DSP as the default backend.
30 * CVE-2023-0359: Under embargo until 2023-04-20
32 * CVE-2023-0779: Under embargo until 2023-04-22
66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding.
71 * Starting from this release ``zephyr-`` prefixed tags won't be created
82 image states). Use of a truncated hash or non-sha256 hash will still work
88 registration function at boot-up. If applications register this then
93 application code, these will now automatically be registered at boot-up (this
129 This may cause out-of-tree scripts or commands to fail if they have relied
[all …]