Thanks Adam, I have disabled BT and Shell, Only UART is there. Now, when i run the command with debug mode --> mcumgr -ldebug --conntype=serial --connstring='dev=/dev/ttymxc0,baud=115200' echo hello I

#ble #bluetoothmesh #nrf52840 #uart

Hi, I have nrf52840 on my custom board (Based on IMX6, Running Yocto linux) which is connected over UART. I want to do an OTA of zephyr OS on that chip over serial/ble and for that i had already tried

#ble #bluetoothmesh #nrf52840 #uart

Hi Mayank, If you are sure the partition layout of flash memory is correct and you flashed MCUboot and SMP_SVR sample respectively, then please check if the CONFIG_UART_MCUMGR_ON_DEV_NAME is set corre

#ble #bluetoothmesh #nrf52840 #uart

Hi Adam, Thanks for the quick reply.I have flashed MCUBOOT (0x0 to 0x8000) and smp_svr (0xC000 to 0x27000). The flag CONFIG_UART_MCUMGR_ON_DEV_NAME is defaults to 'UART_0'. My DTS file has following c

#ble #bluetoothmesh #nrf52840 #uart

Hi all, I have found that Zephyr;s code base Echo client & server Example application can be built either on third paty lwip stack or else on OpenThread stack based on config file. Do the Echo client

#nrf52840 #lwip #openthread

Hello fellow mailinglist members, I'm currently trying to get the samples "hci_uart" and "hci_usb" working on a laird654 module / Laird DVK-BL654-1.0 (nrf52480) Both samples work on the nrf52480DK (pc

#nrf52840 #defines

Hello Matthias, By default the BL654 DVK does not connect the external 32 kHz clock. In zephyr, the NRF52840 board files are setup to use the external 32 kHz clock. You have 2 options: Follow the inst

#nrf52840 #defines

Hi all, For reference, Can you please share an lwip example application built on top of Zephyrt's OpenThread integration code base? Do you support all the features of OT stack in Zephyrt's OpenThread

#nrf52840 #lwip #openthread

Hi, I'm currently using the i2c_nrfx_twi driver to process i2c transfers with some peripherals. I have several slave units on the same i2c bus and use multi-threading to deal with all of them. I have

#nrf52840

I would suggest you to use the mutex or even a semaphore to deal with the concurrent access to the driver. It seems to be the simple way in my point of view. Indeed I guess the first "workaround" you

#nrf52840

Hi community, I'm using nrf52840 on our own development board, I met one problem about abnormal disconnect. environment: [Central] use BLE nRF connect run on nRF52840_PCA10056 (Windows) [Peripheral 1]

#nrf52840 #ble

Hello Deepa, deepa.gopinath@... wrote: Where did you find it? Do you have any links/etc.?

#nrf52840 #lwip #openthread

Hi Vinayak, I enable HCI_CORE_DEBUG to got some logs in the link. 1. UART log. 2. air log. Thanks, Randy

#nrf52840 #ble

Hi Vinayak, I did some test today by using the latest master, there is no connection parameter update that means the CI keeps in 7.5ms, the connection keeps alive. I try to update the CI to 30ms manua

#nrf52840 #ble

Your config file looks ok. I will check if errata 201 will solve your issues. I will try to send you a patch by this weekend. As I will need to reproduce the issue, you will need to help me if it is t

#nrf52840 #ble

Hi Vinayak, Thanks for your reply. If you have any idea about this issue I can do the tests from my site. Regards, Randy Chettimada, Vinayak Kariappa <vinayak.kariappa.chettimada@...> 於 2018

#nrf52840 #ble

https://github.com/zephyrproject-rtos/zephyr/pull/11231 Could you please test the PR on your board and let me know if its better. Find attach the patch file as alternative to the diff in PR. Use "git

#nrf52840 #ble

Hi Paul, I have found it in this link - https://github.com/zephyrproject-rtos/zephyr/issues/10561 By referring the config file also we can able to find Echo client and server example can be built for

#nrf52840 #lwip #openthread

Hi Vinayak, I merge the patch, host (nRF Connect) get update connection parameter request. After CI change to 30ms, it can keep connection a bit longer but it still disconnect after few minutes (dista

#nrf52840 #ble

Hello Deepa, deepa.gopinath@... wrote: None of the links you mention has occurrence of "lwip" (case insensitive) in any material it points to. Zephyr doesn't work with lwIP, it has own

#nrf52840 #lwip #openthread