You can find all information about the issue and how to produce it on GitHub: github.com/.../ncs-2.6.0-connect-crash
You can find all information about the issue and how to produce it on GitHub: github.com/.../ncs-2.6.0-connect-crash
Hi Simon,
1) Moving uart_rx_enable to after bt_enable didn't fix the issue.
2) Which sample do you mean? nrf/samples/bluetooth/peripheral_uart calls uart_rx_enable before bt_enable, too.
3) Since we are heavily relying on zephyrs driver/device model, and initialization(and deinitialization) of Bluetooth and UART happen independently and based on external factors, changing the order is not an option for us.
Thanks
Michael
Hi Simon,
1) Moving uart_rx_enable to after bt_enable didn't fix the issue.
2) Which sample do you mean? nrf/samples/bluetooth/peripheral_uart calls uart_rx_enable before bt_enable, too.
3) Since we are heavily relying on zephyrs driver/device model, and initialization(and deinitialization) of Bluetooth and UART happen independently and based on external factors, changing the order is not an option for us.
Thanks
Michael