Handling of errors in access_model_publish()

[Gerry]

Hi,

like described in this post I sometimes get an error = 4 (NO_MEMORY) when calling:

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

How should this be handled? (Ignore, retry with delay, etc)

Is there a way to find out, wether the softdevice is still sending a message and therefore is not ready for the next one?

I'm using the mesh SDK 2.0.1 

Regards

Gerry

[Gerry]

Thanks for your answer Hung

I think we don't really need one client per server, so I will eliminate this first and then set CLIENT_MODEL_INSTANCE_COUNT = 1. I only have to change the address using access_model_publish_address_set() when talking to the servers right? Does this affect the callbacks when receiving messages on the client also? 

[Hung Bui]

No it shouldn't affect when you have the reply from the server. The server replies to the unicast address of the client, so should always receive it, doesn't matter which public address you currently pointing to. 

[Gerry]

I changed the code to one client now, thanks for pointing this out.

access_model_publish() still returns 4 (NO_MEM) when sending approx. 5-10 messages / Sek (8 Bytes).

Also the assert still happens in core_tx_complete_cb_set()

This didn't happen in SDK 1.0.0. What could be the reason for that?

[Hung Bui]

Hi, 

 

Are you publishing reliable or unreliable message ? If you have no mem , most likely it was reliable packet not getting ACKed and piled up the stack. 

Could you check what cause assert in core_tx_complete_cb_set() and which error code ? The mesh stack is not a black box, please try to debug when you see an error. 

[Gerry]

Hi Hung

I'm publishing unreliable. the following line causes the assert in core_tx_complete_cb_set() :

NRF_MESH_ASSERT(m_packet.bearer_bitmap == 0);

I didn't find a way to debug this any further, since it only happens during havy communication but I placed a Log-message in front of this line to get the actual m_packet.bearer_bitmap. This suddenly returns 1 instead of 0 when this happens. I'm not publishing in an interrupt. 

What could cause this?

What is the meaning of bearer_bitmap?