mesh integration on existing firmware -- Program dwells on unknown function

[Juliusc]

Hi,

I just recently began implementing the mesh stack into an existing application, using mesh v3.2 and nrf sdk 15.2. 

Integration works well by using the integration guide provided in the infocenter, but the mesh doesn't start after initializiation.

in detail I basically tried implementing the mesh_main.c file from the sdk_coexist proximity example, initialization seems to work alright, my services are still visible on LightBlue but as soo as I start the mesh stack my programs will suspend on an unknown function 0x978. This doesn't happen in the SoftDevice but rather at the end of the nrf_mesh_enable function. Debugging doesn't give me an error either, the program basically just stops.

Any hints on what is going on here? I copied most of the configuration from the proximity coexist example as flash_placement specs and configurations from the app_config file, only some settings have to stay the same as before. 

Im using a nrf52840 and SD140 6.1.0

Would appreciate any kind of help!

[Hung Bui]

Hi Juliusc, 

It's important to be able to debug the application and see where the code crashed. You can use either breakpoint and step in the code or use logging to print out debug info. 

Please check at exact which line the code stopped working. 

 I would suggest to use the proximity coexisting example as the base and integrate your application into the example. 

[Juliusc]

Thank you for the quick reply, let me put it like this, after the ble/mesh inits/starts my application goes into its main loop, makes a few cycles and then crashes. I can't really pinpoint the moment where it crashes its not at runtime so maybe a bluetooth event?

I thought about that too but right now that'd be a lot of code tweaking since my application is quite large and customised

[Hung Bui]

Please enable logging and try to debug. Do you see any assert ? hardfault ? The call stack should give you some hint of what caused the assertion. 

[Juliusc]

I did try so, the call stack is empty as soon as the application hangs on ldd r3 address 0x00000978

From my understanding, this means that anything pauses the bluetooth activity and therefore crashes the program.

Its what happens when you press pause in debug mode on a bluetooth application. I can't really pinpoint where it happens though

[Hung Bui]

If you put a breakpoint when the softdevice is active and continue after that it will fail. The reason is that the softdevice uses some timer and when you break in a breakpoint the timers will not stop and they continue, this will confuse the softdevice and you won't be able to continue after you break in a breakpoint. 

Please try printing out logging or use GPIO toggling to debug. 

I would suggest to simplify down the code, turn off other functionality and try to get just the softdevice (BLE) and mesh running. It would be easier to spot what's wrong on a minimal firmware. 
You can send us the minimal firmware that can reproduce the issue on a nRF52 DK so we can test and debug here. 

[Juliusc]

Hey Hung, so Im playing around with this a lot but can't really get a stable version.

I tried disabling the timer in the sdk_config since that's what's up in the proximity example as well and it does seem to work but my static provisioner still can't find the node. There must be something with the times lots somehow, I disabled every other peripheral and function and only init able and mesh. Im 100% certain its not in my code, since I copy and pasted the prox examples main files into my solution and excluded my own application from the built and still can't provision it, it must be somewhere else but I literally copied all of the settings for the linker/flash/sdk_config/preprocessors so Im really puzzled here.