0 results found on Nordicsemi
All results103048 results found on DevZone
A peripheral advertises to a central and a connection is established as the peripheral's callback function is executed with parameter struct bt_conn *conn. Will this particular connection object remain the same through disconnects and reconnections of the central? Can I save the address of this object as an identifier of this particular connection and compare it with the conn parameter passed to connect and disconnect callbacks? What impact does a call to bt_conn_ref() or bt_conn_unref() have on how this works? Thanks, Ken
forum
3/28/2024
Hi everyone, I'm new to building my own custom board. I'm trying to connect analog accelerometer, temperature sensor and uv sensors to nRF52820. I'm also want to be able to communicate to my computer through bluetooth. Since I'm new to this field, I have no idea where to even start.. I'm also trying to connect solar panel to power the chip. Can someone please help me? Thank you so much!!
forum
3/28/2024
There are two USB ports. IMCU and nrf5340. I had a lot of trouble with bad cables but i found one that works and I find that I have a jlink drive that pops up so I know there is a good connection. However, when I run the quickstart, it does not find the DK. vscode also does not find the DK. It tells me to provied the log. however there isn't much to the output. 2024-03-27T21:14:24.036Z INFO Initialising nrfutil module: device 2024-03-27T21:14:24.053Z DEBUG Started watching devices 2024-03-27T21:14:27.675Z INFO Using nrfutil-device core version: 7.7.1 2024-03-27T21:14:28.515Z INFO Using nrfutil-device version: 2.1.1 2024-03-27T21:14:28.515Z INFO Using nrf-device-lib version: 0.17.5 2024-03-27T21:14:28.515Z INFO Using nrfjprog DLL version: 10.24.0 2024-03-27T21:14:28.516Z INFO Using JLink version: JLink_V7.94e Any suggestions? I'm not sure what I've got wrong.
forum
3/27/2024
in zcl_power_config_commands.c battery alarms don't work properly due to a typo in #define ZB_ZCL_CHECK_THRESHOLD_EXISTENCE (ep, attr_set, is_percentage) (is_percentage) ? \ ( zb_uint16_t )(attr_set + ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_PERCENTAGE_MIN_THRESHOLD_ID ) : \ ( zb_uint16_t )(attr_set + ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_VOLTAGE_MIN_THRESHOLD_ID )); \ ... (is_percentage) ? \ ( zb_uint16_t )(attr_set + ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_VOLTAGE_THRESHOLD1_ID ) : \ ( zb_uint16_t )(attr_set + ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_PERCENTAGE_THRESHOLD1_ID )); \ ... (is_percentage) ? \ ( zb_uint16_t )(attr_set + ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_VOLTAGE_THRESHOLD2_ID ) : \ ( zb_uint16_t )(attr_set + ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_PERCENTAGE_THRESHOLD2_ID )); \ ... (is_percentage) ? \ ( zb_uint16_t )(attr_set + ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_VOLTAGE_THRESHOLD3_ID ) : \ ( zb_uint16_t )(attr_set + ZB_ZCL_ATTR_POWER_CONFIG_BATTERY_PERCENTAGE_THRESHOLD3_ID )); \ The macro won't set the alarm states for thresholds 1,2, and 3 because the is_percentage flag is being incorrectly used to set the comparison against the voltage. Its done correctly for alarm 0 but the others are swapped. This issue exists on ncs 2.6.0
forum
3/27/2024
Hi all, I've been trying to get the samples/sensor/lsm6dsl example working with the nrf52840-based Xiao BLE Sense and have had no luck. I guess that it's due to the power line for the sensor being connected to the P1.08 I dug into the xiao_ble_sense.dts and I can indeed see: lsm6ds3tr-c-en { compatible = "regulator-fixed-sync", "regulator-fixed"; enable-gpios = ; regulator-name = "LSM6DS3TR_C_EN"; regulator-boot-on; startup-delay-us = ; }; However no matter how I try and drive it from the code the sensor refuses to initialize with the console output: [00:00:00.794,647] LSM6DSL: lsm6dsl_init_chip: failed to reboot device [00:00:00.794,677] LSM6DSL: Failed to initialize chip *** Booting nRF Connect SDK d96769faceca *** Begin init of lsm6ds3tr and regulator sensor: device not ready. My code to run is based of the sample code for the sensor with the lsm6ds3tr_c_en modifications: /* * Copyright (c) 2018 STMicroelectronics * * SPDX-License-Identifier: Apache-2.0 */ #include #include #include #include #include
forum
3/27/2024
I am developing a custom nrf5340 board design, that is using the BL5340PA external antenna module to implement the nrf5340 chip in the design. The BL5340 module allows all of the base functionality in the nrf5340 module, but also adds an external FEM in increase the TX power. I am utilizing the Zephyr/nrf SDK version 2.4.1 (received from Laird for updated TX power setting rules: GitHub - LairdCP/bl5340pa_manifest: Manifest for the Laird Connectivity fork of the nRF Connect SDK with support for the BL5340PA ). I am attempting to utilize either the HCI_USB or HCI_UART firmware projects, that come with Zephyr, in order to make this custom board a reliable BLE adapter for Linux. My Linux device is running off of kernel version 5.4.0-174-generic and is connected to the custom board through the NRF USB interface on the nrf5340. My BlueZ is version 5.66. The below actions are what I
forum
3/27/2024
We're using nRF Connect with SDK v2.4.0 (Zephyr). Central and peripheral roles combined. Custom hardware, with Fanstels module BT840 All was working well, but after extensive testing, we encountered a problem connecting our hardware to the certain integrated BLE Intel chipset on some of the Laptops. The connection gets rejected, it looks like some security issue. We tried different sets of drivers and it looks like only new drivers have this issue. We cannot connect if the Intel driver version is 22.250.0 or newer. We can connect with a laptop if the Intel driver version is 22.240.0 or less. We tried to downgrade the driver on affected laptops and then we were able to establish a Bluetooth connection. Intel driver list and corresponding release notes can be found here: https://www.intel.com/content/www/us/en/download/18649/787935/intel-wireless-bluetooth-for-windows-10-and-windows-11.html We are about to release the product, but first, we need to solve this issue, any advice will be much
forum
3/27/2024
this is causing expected expression before '{' token /** @brief WDT driver default configuration. */ #define NRFX_WDT_DEAFULT_CONFIG \ { \ .behaviour = (nrf_wdt_behaviour_t)NRFX_WDT_CONFIG_BEHAVIOUR, \ .reload_value = NRFX_WDT_CONFIG_RELOAD_VALUE, \ NRFX_WDT_IRQ_CONFIG \ }
forum
3/27/2024
I'm using nRF Connect SDK/Zephyr. I'm setting up a watchdog timer, with a certain timeout. All goes well, except that there are certain specific operations (such as dumping logs) that take much longer than the timeout I'm using. I'm trying to think of what recourse I have. It looks like I can't stop the WDT temporarily: Method wdt_nrf_disable() (the nRF implementation of wdt_api_disable() ) has a comment that " Started watchdog cannot be stopped on nRF devices", and simply returns -EPERM . I tried calling wdt_api_install_timeout() with a new timeout value in the wdt_timeout_cfg struct passed to it, then calling wdt_setup() again. This crashes the system. Any suggestions? E.g., are there registers that I can program directly, bypassing the API? Thanks!
forum
3/27/2024
Hi, I am currently looking into setting up a Matter project (based on the template) and reached ZAP and the required files. As far as I understood, the ".zap" file is the only file that is actually needed, the corresponding ".matter" file is generated from the ".zap" file (as documented here: https://project-chip.github.io/connectedhomeip-doc/code_generation.html#ensure-you-have-a-matter-file ). My idea is to not even keep the generated files (e.g., not place them under version control) and instead generate all files from the ".zap" file. In the template, however, you're using "BYPASS_IDL" and as described in the example for adding a new cluster ( https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.0/nrf/protocols/matter/getting_started/adding_clusters.html ) you're relying on pre-generated files. My real question: Is it somehow possible to really generate all files during the build, or what is the reason why the samples use "BYPASS_IDL"? I'm a bit dumbstruck by the Matter CMake integration, which actually uses the "generate.py" generator, but instead of first passing
forum
3/27/2024