Search Result

I'm trying to build the DTM sample app on ncs 2.4.1 on nRF5340 dk, but I get the following errors c:/ncs/toolchains/31f4403e35/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe: app/libapp.a(main.c.obj): in function `main': C:\ncs\v2.4.1\nrf\samples\bluetooth\direct_test_mode\src\main.c:73: undefined reference to `__device_dts_ord_65' collect2.exe: error: ld returned 1 exit status ninja: build stopped: subcommand failed. FATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\31f4403e35\opt\bin\cmake.EXE' --build 'c:\ncs\v2.4.1\nrf\samples\bluetooth\direct_test_mode\build' * The terminal process terminated with exit code: 1. * Terminal will be reused by tasks, press any key to close it.

Hello, I would like to know if Zephyr I2c have some locking mechanisms to prevent simultaneous access from multiple threads. Three devices are connected to the same I2c, accessed by three threads. If not, what is the best way to implement a lock on the i2c? Thanks for your help. Giorgio

I want to dynamically update several nrf5340dk GPIO active level settings. However as soon as I write the new 'flags' setting using gpio_pin_configure() or gpio_pin_configure_dt(), the GPIO stops responding to input changes. In the device tree the GPIO is configured as follows: gpio1 _sw: gpio1 _sw { gpios = ; label = "GPIO 1 switch input" ; }; When the device first comes up it will respond correctly to switch input changes but, as soon as I update the 'flags' settings, even if the update changes nothing, the GPIO fails to respond to input changes. Are there other actions I need to take when updating GPIO's on the fly other than just updating the flags? In addition, attempts to read the GPIO 'flags' settings by calling gpio_pin_get_config() or gpio_pin_get_dt() fail. In my prj.conf I have added CONFIG_GPIO_GET_CONFIG =y, is there something else I need to add to get this to

Hello, I am comparing an old implemtation based on Zephyr 2.7.1 for nRF52832 with examples for nRF5340. On both devices there are more than 1 connection allowed. On the older Zephyr 2.7.1 based implentation I see the device is advertising even when someone connects to the device. I use two phones with nRF connect App. One is for showing the RSSI graph and the other one connects to the BLE device. When the one phone connects to the device, I see RSSI updates on the other phone. I am trying different samples for the nRF5340 DK board. For example multiple_adv_set sample. There is 'Nordic Beacon' (non-connectable) and 'Nordic multi-adv-sets' (connectable) advertised. When the one phone connects to the 'Nordic multi adv sets', the other phone stops updating RSSI values - as long as the connections stays active. When I disconnect, the RSSI values show up again. So I asssume that

We are seeing issue with concurrent GPS + modem operation (increased latency) in nrf thingy91 due to switching multiplexing. It was mentioned in the following repo that future modem firmware will allow both modes to be active simultaneously. Is the new modem firmware available with this feature? https://github.com/ExploratoryEngineering/nrf9160-gps/tree/master The nRF9160 shares a single radio for GPS and LTE, and the current modem firmware (0.7.0-29.alpha) only allows one to be active at a time. We therefore have to switch back and forth between these modes in order to collect GPS data and send it. This switching introduces a delay which we minimize by buffering position data and sending it in batches. A future modem firmware will allow both modes to be active simultaneously, which will enable streaming of location data .

Does anyone have some troubleshooting tips for how to test a custom board with nRF9160. It is a new design, the schematic is based on the DK, including the j-link/swd connector. We have a 3V3 supply. I have been wondering about the inversion of the SWD RESET signal on the DK board so we implemented the schematic with both inversion and direct connection just to be sure. I assume connection of SWD nRESET signal to pin 32 throuth a 1k resistor with a capacitor is how it should be. Is the a guide on checking the CPU bootup etc...? I have tested by J-Link on the DK by powering it through the external power connector and using the P18 connector. On the DK my J-Link interface connects.

Hello, I'm working through the Bluetooth Low Energy Fundamentals tutorial, Lesson 3 Exercise 2. In step 9, the training has an optional step to enable Coded PHY. I have made the changes to main.c and prj.conf as instructed but the PHY will not change to Coded PHY. I have attached three screen captures: 1. instructions_for_coded_phy -> instructions from exercise on how to enable Coded PHY 2. main_code_fragment-> shows the changes I made to main.c per instructions 3. prj_code_fragment-> shows the change I made per instructions - by hovering over CONFIG_BT_CTLR_PHY_CODED=y, the dependencies popped up indicated that additional variables need to be set to enable Coded PHY - please advise. Here is my development setup: 1. Ubuntu 20.04.6 LTS 2. Visual Studio Co de Version 1.8.4.2 3. nRF Connect SDK 2.5.0 4. nRF5340-DK 2.0.1 5. Testing with iPhone 13 mini - specs include support for Bluetooth 5.0 Thank you, Gerry

Hello, I would like to use sysbuild and mcuboot without the partition manager but the sdk does not let me disable it. I'm trying to disable the partition manager with the sysbuild/with-mcuboot sample for the nrf52840dk_nrf52840 board. # Sysbuild configuration file. # Enable MCUboot per default for this sample. SB_CONFIG_BOOTLOADER_MCUBOOT=y SB_CONFIG_PARTITION_MANAGER=n Is there a way to disable it ?

hello , We are working on nRF52832 module we are using BLE part right now. and we have one query that we want to advertise our own data. using this nRF52 Beacon. so can u guys help us in this matter. we want to advertise our company name and some specific data too. thanks & regards.

Since a long time I get MPSL asserts when debugging with an active BLE/Thread communication (e.g. in Matter). Those issues are appearently asserts because of strict timing. I now experienced that debugging with the nrf-plugin for VSCode does not exhibit this problem. Is there a option to get this also running without the VSCode-plugin? I prefer vanilla VSCode launch configurations. Or, if it is because of the used debugger type, would there be an option to release the nrfconnect debugger without installing the whole nrfconnect VSCode plugin? Best regards, Juliane