Code generated using MESH results in embedded file paths.

[CanuckAbroad]

For some reason when we build a MESH enabled app we are getting a resulting hex file that includes complete file paths names. This is not occurring in our builds that do not use MESH. Is this a known issue or is there a know culprit?

Thank you

[tesc]

Hi,

Enabling the ASSERT_NO_FILE_INFO option removes file names and file paths from assert error messages, which seems to be what you have found in your binaries.

I did a test with the mesh chat example, and after setting that option I no longer find any file paths in the resulting binaries.

Regards,
Terje

[CanuckAbroad]

Hello,

Thank you for the reply, 

I am unable to find the file prj.conf, and when I search for references to it here on this website I find it referred to in the nRF Connect SDK, and more specifically for Zephyr. 

also, this file does not seem to exist in the Segger directories, my project directories or the MESH SDK 5.0 directories.

Is there an alternate solution that will work for the situation I am using?

- Segger embedded studio

- BLE Mesh coexistence

Thank you

[tesc]

Hi,

nRF5 SDK for Mesh is very different from nRF Connect SDK, yes. For new products we recommend nRF Connect SDK, see our nRF Connect SDK and nRF5 SDK statement. The solution I provided earlier is for nRF Connect SDK.

In nRF5 SDK, file and line numbers are printed from the assert handler, but that should be solved by doing a Release build. Apart from that, you might have to change the mesh logging manually here:

https://github.com/NordicSemiconductor/nRF5-SDK-for-Mesh/blob/a165eece1b743bc68ef396bf03ba389a0bac6f11/mesh/core/include/log.h#L288

Regards,
Terje