Hi everybody, it seems I found a bug in v1.14.0. I'm using Zephyr on my nrf52840 based custom board together with mcuboot v1.3.0. Everything worked fine with Zephyr v1.13.0, but after updating to the

#nrf52840

Hey there, I'm currently running Zephyr V1.13 (and waiting desperately for 1.14) on my custom board. We're using mcuboot to update our application OTA. I'm curious if it's possible to update mcuboot i

#nrf52840 #ble #customboard

Is there anything else I could check to make it work?

#ble #nrf52840 #uart #hci

There's a "Group Reply" button in the bottom right-corner. It took me while to find because you can see it only *after* clicking "Reply", that's an unusual interface.

#ble #nrf52840 #uart #hci

Hello Johan, Thank you for your response. Following your suggestion I've updated my kernel to 4.20 and there is a change in behavior though I don't see LE CODED scanning to be working + btmgmt behavio

#ble #nrf52840 #uart #hci

Hi, HCI_Read_Local_Extended_Features is a BR/EDR-only command, which is why you are getting this response from the LE-only controller. You’ll also see that it’s not listed in the supported commands re

#ble #nrf52840 #uart #hci

Hi, Notice that these are MGMT commands and events, i.e. just communication between BlueZ user space and the Linux kernel and not directly related to the controller. The Set PHY Configuration MGMT com

#ble #nrf52840 #uart #hci

Hi, I'm trying to force a nRF52840-pca10056 DK to scan for BLE advertisements with PHY set to CODED via HCI and BlueZ 5.50 but keep getting rejected by the hci_uart from Zephyr examples (master branch

#ble #nrf52840 #uart #hci

Hi Yorick, This TEMP sensor are defined within zephyr sensors pattern. You should use it by binding the device to a struct and using the default functions from sensor.h You should use this to bind: st

#nrf52840 #sensor

Hello, I have recently started to use Zephyr. Up to now, I have been able to set up some tasks and ESS (with Temperature characteristic (dummy value for the moment)) and BAS Bluetooth profiles. The BA

#nrf52840 #sensor

Hi Phil, It doesn't have to be TLV index 0. You need to use the "type" in each type/length/value (TLV) datum to find the hash TLV in the image binary. I don't use mcumgr very much, just mcuboot, so I

#nrf52840

Hey Marti, thanks for your reply. So in my understanding the value of TLV 0 is the hash that will be displayed using "Image list", isn't it? Best Philipp

#nrf52840

Hi Phil, If you mean the hash of the image header and body, that is available as the value for the IMAGE_TLV_SHA256 key type in your signed image's TLV area (see https://mcuboot.com/mcuboot/design.htm

#nrf52840

Hi, I want to write a script under Linux for automatic FOTA using mcumgr. I need the hash of the image file for the update step "image test", but I can't figure out how to calculate the correct hash n

#nrf52840

1. Overview 1.1. Hardware - nRF52840 DK (PC10056) - nRF52840 Module (u-blox NINA-B302) 1.2. Software 1.2.1. nRF52840 DK - zephyr 1.9.2 - HCI_UART Example - nrf5.conf: o +CONFIG_BT_CTLR_TX_BUFFER_SIZE=

#ble #hci #uart #nrf52840

Could you provide details on how to reproduce the issue you are facing? Which commit, boards and devices used etc.

#ble #nrf52840

I'm trying to change the connection parameters from peripheral side right after the connection has been established (in the connected callback handler) using bt_conn_le_param_update. But the system se

#ble #nrf52840

Hey, any ideas here?

#nrf52840

Hi there, I suspect that sample requires a specific .conf file for nRF52840, since it fails on an invalid GPIO Kconfig symbol. Adding Mieszko and and Andrzej from Nordic. Carles

#nrf52840 #i2c #sensor

Please find the logs in attachment.

#nrf52840 #i2c #sensor