I used STM32f767 as the BLE host to compile the central demo, and the execution program encountered a similar error.
cmd:west build -b nucleo_f767zi samples/bluetooth/centra
l
I used STM32f767 as the BLE host to compile the central demo, and the execution program encountered a similar error.
cmd:west build -b nucleo_f767zi samples/bluetooth/centra
l
Yes, I was asking if it was possible to debug or get debug logs from the controller chip. I would also need to know if you are using a Nordic nRF chip or another third-party IC for the controller.
I used third-party IC for the controller.I can't get debug log from controller. It is possible that the controller has enabled hardware flow control, resulting in the inability to receive the uart data of the host. But I don't think this should be the reason of the above code to crash.
Like I mentioned earlier, the assert indicates that there is a communication issue between the devices. If you can't debug the controller, then I suggest you probe the signals with a logic analyzer/scope to see what is being transmitted and received.
For reliable communication, HW flow control may be necessary depending on the controller implementation and the UART host driver.