This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

app_error_weak.c, 105, Mesh assert at 0x0002C05A (:0)

Hi guys,

I am using nRF5 SDK for Mesh v4.2.0 and I implemented this simple message model which can enable the communication between LPN and server node. After my nodes are provisioned, I am able to send the data from LPN to the server node, but every time when I try that I got this assert: 

<t: 352737>, application.c, 245, Sending Simple msg: 25 of size: 2
<t: 352747>, app_error_weak.c, 105, Mesh assert at 0x0002C05A (:0)

Can you please help me to fix this issue, because before it worked without problems, but when I edited my code a little bit I started receiving this assert?

Also, is it possible to define a sleep time for a specific period of time in Mesh SDK. For now, I am using sd_app_evt_wait() function where I am not able to specific lets say 10 seconds of sleeping time. 

I look forward to hearing your answers soon.

Best regards, 

Adnan.

Parents
  • Hi.

    Do you have any more information to where this assert is originating from?

    You mention that you only see the assert after you modify the code. What part of the code did you change? I assume the assert is related to the modifications you made.

    Br,
    Joakim

  • Hi,

    The assert is related to app_error_weak.c file and line with the case NRF_FAULT_ID_SDK_ASSERT. I created the application where I measure a temperature and send the data via BLE to my server node using a simple message model. What I changed is that I added a new C file where I defined a scheduling logic that I want to use and just include the application.c file into it. In this new main C file, I defined the main function where I call tasks and that is the only change.

    I hope that this small description can help you with my issue.

    Br,

    Adnan.

  • Thanks!

    I was more interested in the exact function that causes the assert.

    Without more information about the modifications you made or where the assert is coming from, it's hard to say what is causing this.

    Maybe the scheduling logic that you've implemented is disrupting the timing of the Mesh somehow. You'll have to go through the code you added and see if you can find where it crashes.

    Br,
    Joakim

  • Hi Joakim,

    The problem is in sending function. I just tested the code and every time when I use a timer (single shot or repeated mode) this function works without problems, but the issue occurs when I want to call sending function without a timer, just by its name, then every time I get this type of assert. Do you maybe know what can cause a problem here? 

    Br,

    Adnan.

Reply Children
Related