Search Result

Hi Devzone, On my nrf52840-based custom board, I am implementing the scanning of devices broadcasting the Heart Rate service while advertising a custom service and connecting to another Central device. In order to do this I based myself off of the Central and Peripheral HRS example: developer.nordicsemi.com/.../README.html I can advertise my custom service, connect to it, and send commands to start scanning, however, when I connect to my board (my board acting as a peripheral in that case), I get the following warning: [00:00:16.727,966] BLE_MANAGER: Connected 44:1C:A8:E2:B6:96 (public) [00:00:16.729,675] bt_hci_core: opcode 0x2039 status 0x0d Even though it works as expected for now, I would like to get rid of the error message. The status states BT_HCI_ERR_INSUFFICIENT_RESOURCES, and from what I've found, the opcode 0x2039 stands for BT_HCI_OP_LE_SET_EXT_ADV_ENABLE (I do have CONFIG_BT_EXT_ADV enabled in my prj.conf). Do you have an idea where this warning originates from ? Here is the ble_manager.c

Hi, I am working on a project where I perform location determination with GNSS and send data over NB-IoT. I have written working code where I am reading location by GNSS and I have working code where I am sending data over NB-IoT to an AWS cloud service. Both the projects work perfectly separately but once I merge these projects I get a Fatal error. lte_lc: Could not send AT command, error: 65536 [00:00:02,122,283] lte_lc: Could not set system mode, error: -14 [00:00:02,122,314] lte_connectivity: lte_lc_init, error: -14 [00:00:02,122,344] aws_iot_sample: conn_mgr_all_if_up, error: -14 *** Booting nRF Connect SDK v2.5.0 ***e: Fatal error! Rebooting the device. When I use the function lte_lc_func_mode_set(LTE_LC_FUNC_MODE_ACTIVATE_GNSS) in my initialization my controller goes rebooting. I get an error message that the AT command cannot be set and that I get errors with following functions. Could there be a problem if I use the function lte_lc_func_mode_set(LTE_LC_FUNC_MODE_ACTIVATE_GNSS) and then

While using Visual Code I have noticed that: First compile always generates errors, which is fine. The error notifications are persistent even after they have been fixed. The only thing that clears these errors is exiting Visual Code and restarting the program. Adding a second build within the same project consistently cause all builds to fail with missing file errors While creating custom applications, such as the Hello World App from the DevAcademy, the printk function does not output to any terminal. Also the DevAcademy still references the NRF Terminal, which has been removed Many of the sample applications or examples do not copy over correctly into target directories with several files having hard coded directory paths which are not valid due to the path move These are annoyances and can be worked around but having to close and reopen VC to clear errors is troublesome and not being able

Dear Support Team I cant build the application for nRF5340. Following all iinstallation prerequisites and examples i get stuck. I always get this error message: PS C:\ncs\v2.6.0\nrf\applications\nrf5340_audio\tools\buildprog> python3 buildprog.py -c app -b debug -d both +------------+----------+---------+--------------+---------------------+---------------------+ | snr | snr conn | device | only reboot | core app programmed | core net programmed | +------------+----------+---------+--------------+---------------------+---------------------+ | 1050162484 | True | headset | Not selected | Selected | Not selected | | 1050118947 | True | gateway | Not selected | Selected | Not selected | +------------+----------+---------+--------------+---------------------+---------------------+ Invoking build step Run: west build C:\ncs\v2.6.0\nrf\applications\nrf5340_audio -b nrf5340_audio_dk_nrf5340_cpuapp -d C:\ncs\v2.6.0\nrf\applications\nrf5340_audio\build\dev_headset\build_debug -DCONFIG_AUDIO_DEV=1 -DCONFIG_NCS_INCLUDE_RPMSG_CHILD_IMAGE=n Der Befehl "west" ist entweder falsch geschrieben oder konnte nicht gefunden werden. Traceback (most recent call last): File "C:\ncs\v2.6.0\nrf\applications\nrf5340_audio\tools\buildprog\buildprog.py", line 498, in __main() File "C:\ncs\v2.6.0\nrf\applications\nrf5340_audio\tools\buildprog\buildprog.py", line 480, in __main __build_module(build_cfg, options) File "C:\ncs\v2.6.0\nrf\applications\nrf5340_audio\tools\buildprog\buildprog.py", line 189, in __build_module raise Exception("cmake error: " + str(ret_val)) Exception: cmake error: 1 PS C:\ncs\v2.6.0\nrf\applications\nrf5340_audio\tools\buildprog> I

I have a nRF9160DK board that is used for development of a custom nRF9160 board. The hardware designers have assigned GPIO P0.27 to be a general purpose output pin. This pin is also used as uart0_cts. when I try to toggle this pin with a simple test it does not work with the code shown below. If I use another pin such as P0.23 the pin toggles fine. I am assuming there is a pin conflict by assigning 2 things to the same pin. The boards are already manufactured with P0.27 as a general purpose output control pin. How can I get this to work? Is there something in the overlay file I need to add or remove? int test = 0 ; while ( 1 ) { printf ( "test GPIO BAT_MON_EN %d \r\n " ,test & 0x01 ); /* toggle test */ /* set/clear test */ if (test

Today I am attempting to set up an MQTT connection from a Thread device to an MQTT server on the Internet (for better or for worse, if this is a terrible idea I'm open to suggestions). I've done some preliminary investigation using the Thread CLI example and am now starting to develop code using the Thread API in SDK 2.6.0. I have a border router running on an RPi with NAT64. At this point I can do a DNS lookup using otDnsClientResolveIp4Address, sending the request to fd34:e64f:ccd9:02:0:0:808:808 (i.e. 8.8.8.8) and I get back the address of the MQTT server as a synthesized IPv6 address. I can ping this address and get a response. The next step is to attempt an MQTT connection. I start by calling getaddrinfo() to resolve the IP address of the broker, this fails with -ENOENT, it's the same whether I use hints.ai_family = AF_INET or AF_INET6.

Hi Guys, I know this question, have been asked many times, but even with the different thread I was not able to solve it.. I'm using LIS2DH sensor with ncs 2.3.0 and have an error : "undefined reference to `__device_dts_ord_137' " Here is how I init the sensor in main.c void test_accelero(void){ const struct device *sensor = DEVICE_DT_GET(DT_ALIAS(accel0)); if (sensor == NULL || !device_is_ready(sensor)) { printf("Could not get accel0 device\n"); return -ENODEV; } return; } Here is the devicetree overlay where I manually set the status to "okay" // To get started, press Ctrl+Space to bring up the completion menu and view the available nodes. // You can also use the buttons in the sidebar to perform actions on nodes. // Actions currently available include: // * Enabling / disabling the node // * Adding the bus to a bus // * Removing the node // * Connecting ADC channels

CD Feather9160, Azure IoTHub using DPS. Last part of the console log: [00:00:06.667,419] azure_iot_hub: azure_iot_hub_connect: User name buffer size is 160, actual user name size is: 132 [00:00:06.679,016] nrf_modem: getaddrinfo() fam: 0x0, type 0x1, proto 0x6 [00:00:06.794,921] nrf_modem: RPC_IP_GETADDRINFO_RES, result RPC_IP_ERR_OK [00:00:06.802,886] nrf_modem: Resolved 13.69.230.66 [00:00:06.808,868] nrf_modem: socket() fam 0x1, type 0x1, proto 0x102 [00:00:06.816,650] nrf_modem: RPC_IP_OPEN_RES, result RPC_IP_ERR_OK [00:00:06.824,005] nrf_modem: connect() fd 0x0 [00:00:06.829,437] nrf_modem: sa_family 0x1, destaddr_len 0x4, destport 8883 [00:00:06.981,872] nrf_modem: RPC_IP_CONNECT_RES fd 0x0, result RPC_IP_ERR_OK [00:00:06.990,051] nrf_modem: Attaching sock fd 0x0 [00:00:07.017,974] nrf_modem: RPC_IP_TLS_ATTACH_RES fd 0x0, result RPC_IP_ERR_OK [00:00:08.615,570] nrf_modem: RPC_IP_TLS_HANDSHAKE_COMPLETE_NTF fd 0x0, result RPC_IP_ERR_OK [00:00:08.625,122] nrf_modem: send() fd 0x0, len 185, blocking [00:00:08.632,812] nrf_modem: RPC_IP_SEND_RES fd 0x0, result RPC_IP_ERR_OK [00:00:08.640,747] nrf_modem: send() fd 0x0, 185 bytes sent [00:00:08.647,338] centralstation: Connection request sent to IoT Hub [00:00:08.782,104] nrf_modem: RPC_IP_RECVFROM_NTF, fd 0x0 (4 bytes) [00:00:08.789,459] nrf_modem: recv() fd 0x0, buf 0x200106e8, len 2, flags 64 (non-block) [00:00:08.798,583]

Hi, Starting from the AWS IoT sample, I’m having a hard time configuring the connection before calling net_if_up() which abstracts a lot of stuff. I would like to configure the APN and authentication information. I have tried enabling the PDN library and calling pdn_ctx_configure() (and pdn_ctx_auth_set()), but whatever APN I give it (“ibasis.iot” in my case, with the SIM shipped with the nRF9160DK) stops the network connection. Here is the AT_HOST log I’m getting: [00:00:04.934,082] pdn: on_cfun: Subscribing to +CNEC=16 and +CGEREP=1 +CEREG: 2,"7F1A","08561906",7 +CSCON: 1 +CNEC_ESM: 33,0 (Requested service option not subscribed) +CEREG: 2,"7F1A","08561906",7,0,19 +CSCON: 0 +CEREG: 2,"BEB8","09743A06",7 +CSCON: 1 +CNEC_ESM: 27,0 +CEREG: 2,"BEB8","09743A06",7,0,19 +CSCON: 0 … When I’m not calling pdn_ctx_configure(), I’m getting this log instead: com [00:00:04.926,879] pdn: on_cfun: Subscribing to +CNEC=16 and +CGEREP=1 +CEREG: 2,"7F1A","08561906",7 +CSCON: 1 +CGEV: ME PDN ACT 0,0 +CNEC_ESM: 50,0 (PDN type IPv4 only allowed) +CEREG: 5,"7F1A","08561906",7,,,"11100000","11100000" [00:00:19.462,951] aerobox_network: Got an IP

Dear Nordic Support Recently I have the issue that the nrf-connect.toolchain.path, set in the VS-Code workspace file, doesn't correctly resolve if predefined VS-Code variables are used. Example For a project having the SDK locally (linked as git submodule) we set nrf-connect.toolchain.path to ${workspaceFolder}\sdk\NordicSemi\toolchains . This used to work just fine, but now nRF Connect falls back to the latest installed toolchain, installed via Toolchain manager (global space): If I use an absolute path instead, the local toolchain is correctly selected: What might be the reason for this behavior? I would also like to understand the toolchain management in general. Is there a comprehensive description that answers questions like: How does nRF Connect plugin manage the selectable toolchains and its paths? Where and how are the variables pointing to toolchains stored? (like ${nrf-connect.toolchain:2.0.2} How can I remove links to local toolchain paths, from the list of selectable toolchains? (command "Uninstall Toolchain"