Search Result

304 results found on Nordicsemi

Article 11 | News 257 | Product 36 | All results

22555 results found on DevZone

NordicSemi

Bluetooth LE wearable gives musicians intuitive control of their performance

Genki Instruments’ Wave uses Nordic’s nRF52832 SoC to turn hand gestures into low latency wireless instrument control

Tags: nRF52832, Bluetooth LE, Audio, Wearables, nRF52 Series

News

10/5/2020

Bluetooth LE wearable provides continuous Covid-19 temperature monitoring

CWD Innovations’ SmartTemp+ employs Nordic’s nRF52832 SoC to wirelessly send body temperature data to smartphone app or gateway

Tags: nRF52832, Bluetooth LE, Connected Health, nRF52 Series

News

10/8/2020

nRF Desktop

The ideal starting point for Bluetooth LE keyboard, mouse, and dongle applications

Product

Nordic-powered car seat safety solution alerts parents when child is unbuckled or unattended

Holmbergs DigitalSafety uses Nordic nRF52832 SoC to send safety alerts from child car seat to smartphone app via Bluetooth LE

Tags: nRF52832, Bluetooth LE, nRF52 Series

News

6/7/2022

Nut’s item tracker uses Nordic SoC for Bluetooth LE location finding with the Apple Find My app

Nutale Smart Finder uses nRF52832 SoC to help users locate valuables as part of the Apple Find My network

Tags: nRF52832, Bluetooth LE, Bluetooth 5.3, nRF52 Series

News

6/27/2022

Bluetooth LE smart fob allows user to directly control various home automation devices with the click of a button

Keyport’s OmniFob employs Nordic’s nRF52832 SoC to control smart home via Bluetooth LE connectivity without launching smartphone apps

Tags: Smart home, nRF52832, Bluetooth LE, nRF52 Series

News

7/30/2019

Wireless wearable beacon provides accurate contact tracing solution for crowded environments such as sports grounds

Omni-ID’s Sense Shield employs Nordic nRF52832 SoC with third party software for accurate personnel tracking using real time location system and mesh networking 

Tags: nRF52832, Bluetooth LE, Wearables, nRF52 Series

News

4/29/2021

Bluetooth LE beacon supports Industrial IoT asset tracking and condition monitoring

Nordic’s nRF52832 powers Confidex Viking Tough, a tamper-proof Bluetooth LE beacon enabling extended battery life in harsh environments

Tags: nRF52832, Bluetooth LE, NFC, Beacons, nRF52 Series

News

7/8/2021

Bluetooth LE wearable provides Covid-19 social distancing, contact tracing solution for events

Proximity Monitor developed by Forkbeard Technologies and deployed by EY, employs Nordic nRF52811 and nRF52832 SoCs to monitor proximity data

Tags: nRF52811, nRF52832, Bluetooth LE, Connected Health, Wearables, nRF52 Series

News

3/25/2021

Bluetooth LE module with PIR sensor enables wireless room occupancy detection

I-SYST’s BLUEPYRO-M3225 module employs Nordic nRF52832 SoC to deliver processing power for motion/proximity detection applications

Tags: nRF52832, Bluetooth 5, Bluetooth LE, Smart home

News

9/9/2021

DevZone - first 10 hits

What is the correct way to close the BLE connection?

Hi, I have a central, where I want to close the BLE connection and restart the device. I have a button interrupt that does this: static void button_changed(uint32_t button_state, uint32_t has_changed){ int _err; if (has_changed & DK_BTN1_MSK) { printk("resetting the device.\n"); _err = bt_conn_disconnect(central_conn, BT_HCI_ERR_REMOTE_USER_TERM_CONN); printk("bt_conn_disconnect error: %d,\n", _err); bt_conn_unref(central_conn); central_conn = NULL; k_sleep(K_MSEC(1)); // reset the system //NVIC_SystemReset(); sys_reboot(0); } } However, when the device reboots. I get this warning and the scanner does not connect to the peripheral: The connection information is probably saved in a non-volatile memory, right? How do you properly disconnection the Bluetooth connection? Thanks for the help!!!

forum

11/14/2024

Setting Up Filter Accept List and Bonding for BLE Central Devices

Hi, Might be possible to answer the question in bold. Thanks in advance! We have many BLE central NUS (Nordic UART Service) and many peripheral NUS communicating with each other. The BLE connection should always connect to the same pre-configured BLE device and it should be a one to one connection. In discovery/scanning it should connect to the first BLE device it finds and always connect to the same device. When a button is pressed, you can clear the configuration and select a different BLE device to connect to. So I thought using Filter accept list with a BLE address would be perfect for this, but I could not find any examples to help me. I found the devAcademy Filter Accept List example ( Lesson 5 Exercise 2 ) and the peripheral_accept_list example but only for the peripheral but I want to do this on the scanner site as the

forum

11/14/2024

When set ADVERTISING_DURATION 180 sec, project resetted from main after elapsed this time

I run project on SDK17 central example and added some code for advertising. But when elapsed 180 sec, my project starts from main again. I suppose, when called end of advertising, error appears and due to this error I got reset my project. Project from example with just advertising- works properly. After 180 sec advertisig disapears. I copied all functions from this project to my central project and got described problem. What settings should I check ? Thanks.

forum

11/14/2024

Clarification on SPI Transceive Timing in nRF Connect SDK for RHS2116 Integration

We are developing on the nRF52 Development Kit (nRF52 DK) for the nRF52832 SoC. Our application involves a 4-wire pipelined SPI communication with the Intan RHS2116 chip. According to the RHS2116 documentation (page 30, Picture 1), the SPI connection is configured such that the RHS2116 automatically outputs data two command cycles after a command is sent. This means that by the time we reach the 3rd command, there will be output data on MISO that we need to receive concurrently as the master (nRF52832) transmits the next command via MOSI. Our challenge is with the nRF Connect SDK and Zephyr OS: specifically, it’s unclear from Zephyr’s SPI library documentation if the spi_transceive function performs read and write operations within the same command cycle, which is required to meet the pipelined data flow of the RHS2116. Could you confirm if spi_transceive in the nRF Connect SDK supports simultaneous read/write operations in

forum

11/14/2024

unable to remove the boot banners with mcboot enabled

With the mcuboot enabled, I'm not being able to disable the boot banners even by doing the below settings in prj.conf file. CONFIG_NCS_BOOT_BANNER = n CONFIG_BOOT_BANNER = n *** Booting MCUboot v2.1.0-dev-daf2946a0f07 *** *** Using nRF Connect SDK v2.7.0-5cb85570ca43 *** *** Using Zephyr OS v3.6.99-100befc70c74 *** I: Starting bootloader I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3 I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3 I: Boot source: none I: Image index: 0, Swap type: none I: Bootloader chainload address offset: 0xc000 I: Jumping to the first image slot How do I disable this boot banner?

forum

11/14/2024

How I get the passkey value??

Hello. I would like to receive the passkey value that the user entered when pairing Bluetooth and modify it. Originally, it was said that if you enter "0000", you have to enter 6 digits according to the regulations to enable Bluetooth pairing. So if I type "0000" I want to add "00" and make it "000000". But I'm still a beginner, so I'd like to know where I can get the value and modify it. You want to modify passkey and use it in the function below that you want to compare with static_passkey.

forum

11/14/2024

How I changed the PASSKEY in NRF52832??

I want to change static_passkey from "000000" to "0000". But It doesn't work when I update changed code to board. I changed like below pictures.(000000 -> 0000) And this is the code of PASSKEY Please help me.

forum

11/14/2024

nRF52832 PC10040 Recommended Inductor is EOL

Hi Nordic Support, Reaching out as due diligence on this. We've been relying on the HK100515NJ-T for L3 (15 nH DCC inductor), the recommendation from PCA10040, in our design. The part has reached EOL and we're considering replacements for it beyond the ones suggested by Digikey. https://www.digikey.com/en/products/detail/taiyo-yuden/HK100515NJ-T/957881#product-details-substitutes I would just like to know if there are any concerns worth considering when selecting this part beyond the 15nH 10% inductance and 50mA maximum current specified for L2 in series with it. Is there a concern with switching from ceramic core to air since this is a filtering inductor? Is there a limit to the DC resistance of the part you recommend staying below? Is there a reason you chose a part with 6x the current rating specified on the datasheet? Are you considering other parts going forward for the PCA10040 series? We're also considering https://www.digikey.com/en/products/detail/w%C3%BCrth-elektronik/7847804150/14640529 as an alt. Thanks, -Carl

forum

11/14/2024

SPI does not generate SCL signal on nRF52832

Hi I want to run an epaper with the nRF52832 therefore is SPI needed. Board file was generated from scratch. In the devicetree I added the SPI modul and a epaper modul, which connects to the SPI modul. To send data to the epaper over SPI I use the spi_transceive_dt function. void EPaper_Spi_WriteByte(uint8_t txData) { uint8_t tx_buffer = 0x88; struct spi_buf tx_spi_buf = { .buf = (void *)&tx_buffer, .len = 1 }; struct spi_buf_set tx_spi_buf_set = { .buffers = &tx_spi_buf, .count = 1 }; struct spi_buf rx_spi_bufs = { .buf = &txData, .len = 1 }; struct spi_buf_set rx_spi_buf_set = { .buffers = &rx_spi_bufs, .count = 1 }; int err = spi_transceive_dt(&spiSpec, &tx_spi_buf_set, &rx_spi_buf_set); if (err < 0) { printk("SPI: spi_transceive_dt() failed, err: %d\n", err); return err; } } Chipselect and MOSI Signal ar working as requeried. But the SCL signal does nothing, it stays the whole time on low.

forum

11/13/2024

incorrect values via zcbor

hello Nordic i am working with ncs v2.5.0 with nrf52840 and nrf52832 i use cbor for some command i build over smp (user groups >64).. i have this code part { zcbor_state_t *zse = ctxt->writer->zs; bool ok = true; uint32_t uptime_sec = (uint32_t)(k_uptime_get() / 1000); float temperature = temp_read(); #ifdef ONE_BAORD double temperature = 0; get_temp(&temperature); #elif defined (BOARD_X) || defined(BOARD_Y) float temperature = 0.0; get_temp(&temperature); #endif int16_t temperature_int = (int16_t)temperature; LOG_INF("temp %d, uptime %d", temperature_int, uptime_sec); ok = augu_status_encode_battery_mv(zse) && zcbor_tstr_put_lit(zse, FIELD_UPTIME_SEC) && zcbor_uint32_encode(zse, &uptime_sec) && zcbor_tstr_put_lit(zse, FIELD_TEMPERATURE) && zcbor_int_encode(zse, &temperature_int, sizeof(int16_t)) && ... return (ok ? MGMT_ERR_EOK : MGMT_ERR_EMSGSIZE); i see in the print of LOG_INF that the values are the same, i have no idea why temp changes with uptime rise and remain equal .. any ideas ??? and off course when i decode the cbor i get, using https://cbor.me/, i get that the temperature value is

forum

11/13/2024