Hello!
The NRF52832 based Raytec Module, the Garmin NRF52 module and the Nordic Dev kits all handle the Mesh firmware I have developed without change or modification and are rock solid. There seems to be something different with the Fanstel BM832 part. FIrmware examples that do not use the Soft Device run fine on the BM832 target board. Those that use the SoftDevice do not run - including my mesh application. For example the blinky without use of the radio runs fine on the BM832 board but the Blinky BLE does not. The Nordic Dev kit is standard and the modules I mention are mounted on our pre-production board.
I have done side by side tests with both NRF Mesh SDK and NRF Connect Zephyr where solutions download and can be stepped through to the Nordic SDK, Garmin and Raytec. The same projects download and verify on the BM832 but breakpoints can not be set and single stepping in the debugger seems to show a loop.
Just in case it was a hardware anomaly on the part, I replaced the BM832 which downloaded and verified on the first go but hangs up immediately once the code starts to run.
I am using the PCA10040 / S132 based examples . They seem to use Soft Device S132 7.02 It is my understanding that NRF Connect / Zephyr does not use the Soft Device so that is what leads me to believe it must be something I am doing wrong other than the Soft Device.
Do you have a direct line to Fanstel support that I can use? The BM832 is an approved module on the Nordic Semi website so it must work. I hope a little guidance from Fanstel will get me going.
Regards,
David Carlin
