Search Result

0 results found on Nordicsemi

All results

105403 results found on DevZone

NordicSemi

DevZone - first 10 hits

Does the Event Trigger API always require CONFIG_BT_CENTRAL? Significantly increases peripheral image size.

Hi, I'm using the new Event Trigger API in a BLE peripheral to set up a connection event trigger as demonstrated in this official sample . The trigger seems to work fine, but I've noticed that CONFIG_BT_CENTRAL=y is required, even though my device is a BLE peripheral. Otherwise, I'm getting this error [00:00:06.745,758] bt_hci_core: opcode 0xfd13 status 0x01 [00:00:06.745,788] my_app: Error for command SDC_HCI_OPCODE_CMD_VS_SET_CONN_EVENT_TRIGGER (-5) The problem is that setting CONFIG_BT_CENTRAL=y seems to increase the image size in an optimized build by about 60 kbytes, which is not ideal. Am I missing something here, or is CONFIG_BT_CENTRAL indeed required to set up a connection event trigger in a BLE peripheral using the Event Trigger API? If so, is there any way I can reduce the impact it has on the image size? I'm using the the nRF52840 DK and nRF Connect SDK v2.6.0. Thanks

forum

6/17/2024

Bluetooth Connection Management Between Smartphone and Device

Hello, I need assistance with managing the Bluetooth connection between a smartphone (both Android and iOS) and my device, which functions as a keyboard and mouse (via touchpad). Specifically, I need to know if it is possible to connect and then completely disconnect (dissociate) a smartphone from my device directly from the device itself, without having to do so from the smartphone. I have noticed that the only way to dissociate and prevent a previously paired device from reconnecting after a reset is to dissociate it from the smartphone. Despite my efforts, I have not been able to find a way to remove any possibility of pairing from my device. I believe this issue is related to the way smartphones handle Bluetooth connections, but I need confirmation to inform my client that it is indeed impossible to completely dissociate a smartphone from the product without going through the smartphone. What

forum

6/17/2024

[Questions]DAC private key length in factory data confusing

Dear sir: The DAC private key is generated using P256, and the key length is 256 bits, which is 32 bytes. As below link, why is 68 bytes planned in the factory data? developer.nordicsemi.com/.../nrfconnect_factory_data_configuration.html dac_key DAC private key 68 B byte string mandatory The private key associated with the Device Attestation Certificate (DAC). This key should be encrypted and maximum security should be guaranteed while generating and providing it to factory data.

forum

6/17/2024

What is the source for menuconfig/guiconfig/nRF Kconfig GUI?

Hey I'm trying to figure out what is the intetned way of using the tools for configuring a project. We have the following config files in the following structure: . ├── boards │ ├── arm │ │ ├── app_nrf5340 │ │ │ ├── Kconfig │ │ │ ├── Kconfig.board │ │ │ ├── Kconfig.defconfig │ │ │ ├── app_nrf5340_cpuapp_defconfig │ │ │ ├── app_nrf5340_cpunet_defconfig │ │ │ ├── app_nrf5340_partition_conf.dts │ │ │ └── app_nrf5340_shared_sram_planning_conf.dts │ │ └── nrf5340dk_nrf5340_cpuapp.overlay │ └── debug_tools.conf ├── Kconfig ├── Kconfig.sysbuild ├── netcore │ ├── prj.conf ├── prj.conf ├── sysbuild │ └── mcuboot.conf ├── sysbuild.conf ├── west.yml Depending on what i choose in the build configuration: Different things happen when i open any of the config tools. Can anyone tell me what is the intetned behavior, and even more is it correct that on not supposed to use the save minimal config? When i save minimal

forum

6/17/2024

interfacing MT29F4G01ABAFDWB nand flash.

i have to interface MT29F4G01ABAFDWB in zephyr rtos but i need help how create overlay file for it(i want to interface it using spi), i already have bare metal drivers for mt29f4g01abafdwb now those i have to move it to zephyr. i'm using zephyr 2.6 and my controller is nrf52840dk board

forum

6/17/2024

When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears

Hi: My environment is: nRF5_SDK_17.1.0_ddde560, keil, s113_nrf52_7.2.0_softdevice When using the ble_app_uart example, "Failed receiving NUS message. Error 0x04. " appears static void nus_data_handler(ble_nus_evt_t* p_evt) { if (p_evt->type == BLE_NUS_EVT_RX_DATA) { uint32_t err_code; // NRF_LOG_DEBUG("Received data from BLE NUS. Writing data on UART. %d", p_evt->params.rx_data.length); // NRF_LOG_HEXDUMP_DEBUG(p_evt->params.rx_data.p_data, p_evt->params.rx_data.length); for (uint32_t i = 0; i params.rx_data.length; i++) { do { err_code = app_uart_put(p_evt->params.rx_data.p_data[i]); if ((err_code != NRF_SUCCESS) && (err_code != NRF_ERROR_BUSY)) { NRF_LOG_ERROR("Failed receiving NUS message. Error 0x%x. ", err_code); APP_ERROR_CHECK(err_code); } } while (err_code == NRF_ERROR_BUSY); } } } After investigation, it was found that `NRF_ERROR_NO_MEM` appeared when `app_uart_put`. I tried the following, but still couldn't solve it. Even when the data is far below 115200, this error will occasionally appear. 1. Uarte is turned on, and debugging shows that data is indeed sent and received through uarte. 2. Modify the data sending method in the interrupt. case NRF_DRV_UART_EVT_TX_DONE: //@modify by

forum

6/17/2024

7002 power consumption

I'm using custom board of nrf5340 with nrf7002. Use helloworld sample and have set "config serial=n" and "config device pm =y". The current is 90 ma when I don't do anything in the code, so I must initialize wifi interface to let the current be much lower. There are two situations what I encounter. 1. The current is 1 ma when I use api, "interface down", to shutdown nrf7002. 2. The current is 0.5 ma when m odify hardware to let the line of iovdd of nrf7002 disconnect. The current difference of two situations is 0.5 ma, what causes the difference of current? How can I further reduce the current?

forum

6/17/2024

the Zero-distance calibration of ddfs

when i try to use the ddfs to calculate the distance, i can't understand the comments in the README file, "Zero-distance calibration ************************* The measured values of distance measurement include an offset. The offset value may depend on the design of the radio circuit, the antenna used, or the PCB layout. When using a library and a sample, you need to compensate the zero-distance offset and perform the calibration manually. To determine the offset value, place the devices at a reference distance of 60 cm from each other and collect a batch of measurement data. The difference between the average measurement value and the actual distance can be used as an estimate of the offset." Appreciate if you can provide your valuable comments Thanks

forum

6/17/2024

Getting CONFIG_HEAP_MEM_POOL_SIZE under control (minimising)

After discovering that MBEDTLS requires at least 48000 bytes of heap to function, I've had to desperately find some spare bytes to conduct a TLS session over WiFi using a nRF5340 (with nRF7002 for WiFi). The biggest single allocation is from CONFIG_HEAP_MEM_POOL_SIZE. By default it is 153000. Why? I can't figure out where this number comes from, or how to figure that out. Note I'm using ncs 2.5.2, so that's before all the HEAP_MEM_POOL_ADD_SIZE_* stuff. All I can find is defaults of about 4096 for Bluetooth, and dramatically, 98304 for WiFi on some non-Nordic boards. So can't see why I'd need 153000, yet if I reduce it to 100000 it fails. Is there any opportunity to shave some bytes off, or is the figure quite accurate?

forum

6/17/2024

Guiconfig can not open

I'm following Intermediate course lesson 1 exercise 2 to use guiconfig. When I try to open guiconfig,the output in terminal as follow: How can I fix it?

forum

6/17/2024