s132 5.1.0 SD assert error

[Mike]

I'm trying to get a Bluetooth interface (Bluefruit) to the Nordic BLE softdevice under NuttX. Right now it's very unstable. It will work occasionally for 90 seconds and then hangs. Sometimes it'll hang during sd_softdevice_enable(). So pretty random. Sometimes it'll die "nicely' by calling the error callback. Here are two such calls to the error callback:

        nrf_error_cb: id = 1, pc = 0xdcc8, info = 0x00000000

        nrf_error_cb: id = 1, pc = 0x13ea4, info = 0x00000000

Any information on what these two assertion failures mean might help in understanding the underlying issue(s).

I have a Segger J-Trace module on order so hopefully that will give me some indication of what the interaction between the softdevice and NuttX is when things go wrong.

Mike

[acassis]

Hi Mike,

Recently NuttX is getting support for a native BLE stack. Please consider using it instead of messing with SoftDevice.

I think soon the Nordic guys will realize that NuttX is the great RTOS and will start supporting it. Until there we need to work together to improve it ourselves, then supporting the open-source BLE stack is the best alternative.

BR,

Alan

[Mike]

It was decided that we need a certified Bluetooth stack so we decided to use the Nordic BLE softdevice. We had looked at Zephyr and it's open source "Bluetooth like" stack. If we didn't have the requirement for a certified stack, we likely would have chosen Zephyr instead of NuttX. Although I'm not overly enthused about some of the directions coming out of the Zephyr camp these days.

I'm not "overly enthused" about each Nordic softdevice release having major API differences either. I'm not looking forward to moving to 6.0. Doesn't seem to be a good choice available for developers who just want to use BLE.