Mesh assert in core_tx.c

RE: Mesh assert in core_tx.c

bivay — Fri, 20 Sep 2019 10:34:46 GMT

I have same issue How you solved this

RE: Mesh assert in core_tx.c

Gerry — Wed, 04 Jul 2018 14:52:06 GMT

Hi,

The calls are made from the mainloop. The function read_uart() reads commands and then sends them to the mesh network.

while (true)
{
read_uart();
(void)sd_app_evt_wait();

}

I'm ignoring the NO_MEMORY cases at the moment so I don't retry at all. It seems to me, that in SDK 2.0.1 things are slower than before. With the same code in SDK 1.0.0 I was able to transmit 20-30 messages per second without an assert. With SDK 2.0.1 this NO_MEMORY status and the assert occurs regulary and I can only transmit 5-10 messages per second to a server.

Regards

Gerry

RE: Mesh assert in core_tx.c

tesc — Wed, 04 Jul 2018 13:38:37 GMT

Hi,

It would still be interesting to know what context those calls are made from. (For instance, are you using the app scheduler, does it come from an event handler, is it directly from the main loop, etc.)

How are you handling the NO_MEMORY cases, are you retrying the operation (with or without delay, if delay how?)

Regards,
Terje

RE: Mesh assert in core_tx.c

Gerry — Wed, 04 Jul 2018 11:55:56 GMT

Hi,

I don't use interrupts to send messages. The messages are sent by calling:

status = access_model_publish(m_clients[0].model_handle, &msg);

the function sometimes returns a status of 4 (NO_MEMORY). Is that maybe related to the problem?

Regards

Gery

RE: Mesh assert in core_tx.c

tesc — Wed, 04 Jul 2018 11:33:04 GMT

Hi,

This may happen if you call the mesh API from different interrupt contexts, so that one call may preempt another. Please make sure that you follow the directions in Interrupt priority levels.

Regards,
Terje