Search Result

Greetings. I have a question that I hope someone can help me with. Recently, I've been working with the HX711 sensor to weigh with a certain precision. I have a custom board that uses a module integrating an nrf5340 and an nrf7002 for WiFi connectivity. The issue is that using the sensor driver from the repository https://github.com/nobodyguy/HX711_zephyr_driver , I've noticed that it only works using clock and dout pins configured as analog input. Considering that the sensor datasheet doesn't specify anything about this, I'd like to know why this happens and if it's possible to use it on non-analog pins. Thanks in advance.

Hi, I am developing hid device using nrf5 SDK. Iphone virtual keyboard does not shown when my hid device connected. What should I do? Which command Ihave to send Iphone over HID? or How should I re-design my report map? Here is my hids_init function. static void hids_init(void) { ret_code_t err_code; ble_hids_init_t hids_init_obj; ble_hids_inp_rep_init_t * p_input_report; ble_hids_outp_rep_init_t * p_output_report; ble_hids_feature_rep_init_t * p_feature_report; uint8_t hid_info_flags; static ble_hids_inp_rep_init_t input_report_array[2]; static ble_hids_outp_rep_init_t output_report_array[2]; static ble_hids_feature_rep_init_t feature_report_array[1]; static uint8_t report_map_data[] = { 0x05, 0x01, // Usage Page (Generic Desktop) 0x09, 0x06, // Usage (Keyboard) 0xA1, 0x01, // Collection (Application) 0x85, 0x01, // Report Id (1) 0x05, 0x07, // Usage Page (Key Codes) 0x19, 0xe0, // Usage Minimum (224) 0x29, 0xe7, // Usage Maximum (231) 0x15, 0x00, // Logical Minimum (0) 0x25, 0x01, // Logical Maximum (1) 0x75, 0x01, // Report Size (1) 0x95, 0x08, // Report Count (8) 0x81, 0x02, // Input (Data, Variable,

Hi, We've been trying to implement a custom hardfault handler on Zephyr, for a custom board based on nRF52833. According to Zephyr, also according to one old post on this forum, the Zephyr HardFault handler void k_sys_fatal_error_handler(unsigned int reason, const z_arch_esf_t *esf)) should be defined as weak, and it is, but on NCS there's no weak implementation. The weak implementation is defined on "zephyr/kernel/fatal.c" /* * Copyright (c) 2019 Intel Corporation. * * SPDX-License-Identifier: Apache-2.0 */ #include #include #include #include #include #include #include #include #ifndef CONFIG_XTENSA #include #endif LOG_MODULE_DECLARE(os, CONFIG_KERNEL_LOG_LEVEL); /* LCOV_EXCL_START */ FUNC_NORETURN __weak void arch_system_halt(unsigned int reason) { ARG_UNUSED(reason); /* TODO: What's the best way to totally halt the system if SMP * is enabled? */ (void)arch_irq_lock(); for (;;) { /* Spin endlessly */ } } /* LCOV_EXCL_STOP */ /* LCOV_EXCL_START */ __weak void k_sys_fatal_error_handler(unsigned int reason, const z_arch_esf_t *esf) { ARG_UNUSED(esf); LOG_PANIC(); LOG_ERR("Halting system"); arch_system_halt(reason); CODE_UNREACHABLE; /*

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

Dear Support Team, Hardware : nRF5340 Custom board Software : nRF Connect SDK v2.2.0 I have implemented OTA FW update for nRF5340. I've used multi-image simultaneous update configuration for the same. I have been testing and noticed that even if the network core image is not valid, the app core was being updated. I then found out that you can add dependency on images using imgtool [ format_to_add_dependecy ] during the signing process. I couldn't find much resources or examples on the same. Is the dependency mentioned here https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/mcuboot/imgtool.html#signing-images concerning only the version number or does it also apply when the image is corrupt? With the given command format, I have created the binaries but I can still see that the app core updated even when network core fails during the bootloader checks. Your help is much appreciated. Thanks, Rosh

I want to know if I can use the dongle BLED112 with the bluetooth low energy app. If not, which one should I consider? I am trying to replicate the experience given by the phone to connect to a bluetooth device and be able to change some configuration of the device itself. Thank you for the support.

Hi all, NRF5340 NRF Connect 2.6.0 We would like to perform the following operations on the NRF5340: * Read FICR.DEVICEADDR (BLE random MAC is also fine). * Set the BLE address with type random. Seems the FICR.DEVICEADDR is only accessible by the network core, which AFAIK is not documented anywhere in the PS. So need to call bt_enable first to get the random MAC address either via bt_id_get or bt_read_static_addr. However, using bt_id_create after BLE has been started does not apply the new MAC address for BLE comms. There seems to be a workaround for setting the public address at runtime, but this doesn't work for random. The HCI command returns SUCCESS though. devzone.nordicsemi.com/.../setting-nrf5340-public-ble-address Is there a solution for this specific use case?

Hi, we are facing an issue of loading the application written with nRF Connect SDK to the nRF52840 which has nRF5 SDK's secure bootloader. Update process should be performed by another MCU via UART (so two files are used for a single update: init packet and the image itself). Based on my request posted previously , we decided to use the nRF5 SDK's bootloader. Now, as I can see the output of the nRF Connect SDK is a single binary, yet the bootloader expects two files. Since the bootloader and all application logic (of another MCU) is already implemented, is there some easy way to be able to send updates to the target Nordic chip?

Unable to use uart ,I2c,SPI together as shown in the error message. I am attaching the dts overlay file // 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 // For more help, browse the DeviceTree documentation at https://docs.zephyrproject.org/latest/guides/dts/index.html // You can also visit the nRF DeviceTree extension documentation at https://nrfconnect.github.io/vscode-nrf-connect/devicetree/nrfdevicetree.html &uart1 { status = "okay"; }; &pinctrl { uart2_default: uart2_default { group1 { psels = , ; bias-pull-up; }; }; uart2_sleep: uart2_sleep { group1 { psels = , ; low-power-enable; }; }; }; &uart2 { status = "okay"; current-speed = ; }; &i2c2_default { status = "okay";

Hi, we can't open docs.nordicsemi.com in chrome without setting it to: Sites can send pop-ups and use redirects We don't want to do that for all sites, so we tried adding docs.nordicsemi.com to our Customized behaviors / Allowed to send pop-ups and use redirects Buy that does not work. Please let me know what to do.