Hi Mayank, I am surprised to say this doesn't appear to be covered in the MCUboot documentation. David, did I miss it somewhere? Mayank: you need at least three pins connecting the i.MX and nRF chips:

#ble #hci #nrf52480 #uart

Hello, I have nrf52840_pca10056 chip connected to imx6ul processor via uart (Both are embedded on my custom board) as shown in attached image. I'm using mcuboot bootloader on nrf52840 chip, now i want

#ble #hci #nrf52480 #uart

Hi Mayank: I had a similar requirement, also without a button on the same Nordic chip. I simply copied this file into my project, and called smp_svr_init() from my main() after bluetooth was up and ru

#ble #hci #nrf52480 #uart

Hello All, Right now I'm exploring the best way to do DFU OTA. I would like to ask that how i can do the DFU by booting the mcuboot bootloader in serial recovery mode. I have one nrf52840_pca10056 chi

#ble #hci #nrf52480 #uart

Hi Q1 – no, this mens that higher part of BLE stack runs on HCI client which has no access to nRF52840 flash at all. Q2 – mcuboot serial recovery or your proprietary protocol which can share common ua

#hci #nrf52480 #ble #uart #samples

Hi, I want to do an DFU OTA in nRF52840 BLE chip. I have flashed mcuboot bootloader and also flashed hci_uart (To scan BLE beacons) application. This will be one time flash using JTAG. Now, I want to

#hci #nrf52480 #ble #uart #samples

Thanks Adam, I have upgraded zephyr to latest version (2.1.0) using west update. Now with the configuration of my application as well as mcuboot, i reached at the stage where i can upload the signed a

#ble #bluetoothmesh #nrf52840 #uart

Hi Mayank, could you please attach your 'zephyr/.config' file? Maybe I will find some inaccuracy there. Cheers, Adam

#ble #bluetoothmesh #nrf52840 #uart

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 Mayank, If you are using UART as a connection type, then please disable other communication channels like BT and shell - at least in my case with STM32 it helped. I assume that flash partition layo

#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 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, 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 Josef, There is no maximum, neither as a central nor as a peripheral, nor combined. Whatever you can fit in RAM and in multiplexed time (depending on connection intervals, use of slave latency, etc

#uart #ble #hci #nrf52480

Hi, I am evaluating the use of nRF52 (HCI with BlueZ/Linux) as BLE central device. Does anyone know the maximum number of concurrent connections which Zephyr supports? Many thanks, Jos

#uart #ble #hci #nrf52480

Hi Ryan, The UART driver itself uses the GPIO driver internally so I don’t think there should be any issues with your usecase. Regards, Carles From: <devel@lists.zephyrproject.org> on behalf of Ryan E

#uart #nrf52480

Hello, I am using the NRF52840, UART1 with hardware flow control turned on. I want to be able to detect transitions on the CTS pin (input). Currently I tried using the GPIO driver to configure interru

#uart #nrf52480

Hi guys, I met a problem here and hop anyone can help. Thanks. I enable hardware control in menuconfig, build a firmware of hci_uart sample and burn the firmware into nrf52_pca10040 (nrf52832), and th

#uart #nrf52832

Looks like UART flow control is not implemented on stm32f746g_disco. I am going to get that working. Hopefully that makes this setup work.

#uart #bluetoothmesh #hci

Hi, This is a valid and quite common set up. The most important thing you'll need to enable is the host-side UART HCI driver using CONFIG_BT_H4=y. Johan

#uart #bluetoothmesh #hci