nRF52840 mesh SDK coexistence

RE: nRF52840 mesh SDK coexistence

Bjørn Kvaale — Fri, 18 Jan 2019 09:49:14 GMT

Great to hear that you figured it out! I will mention this internally & hopefully the documentation will be updated to mention the flash_placement.xml file.

RE: nRF52840 mesh SDK coexistence

Sefer — Thu, 17 Jan 2019 21:49:50 GMT

I found the issue, flash_placement.xml file is different in mesh SDK examples, it has an extra line:

<ProgramSection alignment="4" keep="Yes" load="Yes" name=".nrf_mesh_flash"  inputsections="*(SORT(.nrf_mesh_flash.*))" address_symbol="__start_nrf_mesh_flash" end_symbol="__stop_nrf_mesh_flash"/>

So when you use ble_peripheral example and add mesh functionality to it, flash_placement.xml file should be modified also.

This solved my issue, thanks for the help.

RE: nRF52840 mesh SDK coexistence

Sefer — Mon, 14 Jan 2019 13:27:18 GMT

Did not yet finish that, got stuck on something else. I'll do it in the next few days and report back.

I used:

FLASH_PH_START=0x0

FLASH_PH_SIZE=0x100000

RAM_PH_START=0x20000000

RAM_PH_SIZE=0x40000

FLASH_START=0x26000

FLASH_SIZE=0xda000

RAM_START=0x20002a98

RAM_SIZE=0x3d568

But I tried different settings also, didn't seem to change anything.

RE: nRF52840 mesh SDK coexistence

Bjørn Kvaale — Mon, 14 Jan 2019 13:12:27 GMT

Did it work to modify the 52832 coexistence example to work on the 52840? Which flash & ram settings did you use for the 52840 mesh + ble peripheral app template example?

RE: nRF52840 mesh SDK coexistence

Sefer — Tue, 08 Jan 2019 14:48:15 GMT

Optimization level None, debugging level 3

RE: nRF52840 mesh SDK coexistence

Bjørn Kvaale — Tue, 08 Jan 2019 14:44:56 GMT

Which optimization level are you currently running at?

Also, what debugging level are you using?

RE: nRF52840 mesh SDK coexistence

Sefer — Tue, 08 Jan 2019 14:15:51 GMT

I took ble_app_template example and added mesh functionality to that first, I got same error as I got when I added my custom code.

No other errors/warnings in log, just:
"<error> app: ASSERTION FAILED at :0"

I've tried changing both RAM and FLASH settings, no help. I'll try modifying the 52832 coexistence project to work on 52840 instead of adding mesh to 52840 ble peripheral example.

RE: nRF52840 mesh SDK coexistence

Bjørn Kvaale — Tue, 08 Jan 2019 13:37:11 GMT

As I mentioned in a previous comment, it seems that the mesh coexistence project has only been created for the 52832 for now.

Which ble peripheral example did you test with from sdk 15.2.0? Have you tested the coexistence with a ble peripheral example (nRF5 SDK v15.2.0 & mesh sdk v3.0.0) first & then with your custom FW (based on nRF5 SDK v15.2.0) & then added the mesh functionality to that (mesh sdk v3.0.0)?

Do you receive any warnings in your log such as "Insufficient RAM allocated for the softdevice. Change the RAM start location from ... to ..."? It may be that the RAM settings might need to be adjusted. Could you please upload your complete log to this case?

RE: nRF52840 mesh SDK coexistence

Sefer — Thu, 03 Jan 2019 10:23:18 GMT

Mesh SDK 3.0.0 + SDK 15.2.0 same issue, getting NULL pointer for "p_entries" in mesh_config_backend_init();. Has mesh coexistence been tested with nRF52840 or just 52832?

RE: nRF52840 mesh SDK coexistence

Sefer — Wed, 02 Jan 2019 20:35:31 GMT

Yes I've seen the documentation. Same code works on 52832 without issues.

I took 52840 ble peripheral example from SDK 15 and I added preprocessor symbols and included all mesh source files according to the doc mentioned above. Then I added my custom firmware code from working 52832 project. I'll try with mesh SDK 3.0.0

RE: nRF52840 mesh SDK coexistence

Bjørn Kvaale — Wed, 02 Jan 2019 14:03:01 GMT

Have you taken a look at the documentation provided here? There is similar documentation if you want to use mesh sdk v2.2.0 here. I do not believe there are any coexistance examples for the 52840 at the moment unfortunately. The documentation should provide enough info (theoretically) for you to achieve the same on the 52840.

Did the coexistence example work without any issues on the 52832 (i.e. I guess you did not receive the same assert on the coexist example, correct?). What changes did you make to port the 52832 to the 52840?