I am using DA1468x MESH SDK 1.6.1.
When I tried to start periodic broadcasting I got the following messages.
Device seems to work for a while, stopped eventually with SAR Context messages.
How can I fix this?
[NET Tx] Pkt. SRC:0x010D, DST:0xFFFF, IVI:0x00, SEQ:0x0000144B, CTL:0x00, TTL:0x7F, Len: 16, is_relay:0x00
[NET Tx] Pkt. SRC:0x010D, DST:0xFFFF, IVI:0x00, SEQ:0x0000144C, CTL:0x00, TTL:0x7F, Len: 6, is_relay:0x00
[NET Tx] Pkt. SRC:0x010D, DST:0xFFFF, IVI:0x00, SEQ:0x0000144D, CTL:0x00, TTL:0x7F, Len: 16, is_relay:0x00
[NET Tx] Pkt. SRC:0x010D, DST:0xFFFF, IVI:0x00, SEQ:0x0000144E, CTL:0x00, TTL:0x7F, Len: 6, is_relay:0x00
[** ERR **]:[ltrn_replay_cache.c]:[689]: [LTRN] Ack Rtx timer start failed
[NET Rx] Pkt. SRC:0xFFFF, DST:0x010D, IVI:0x00, SEQ:0x00002C66, CTL:0x01, TTL:0x7F, NID:0x72
[** ERR **]:[net_init.c]:[234]: [NET Rx] SRC ADDR 0xFFFF not a Unicast Address. Dropping...
[NET Rx] Pkt. SRC:0xFFFF, DST:0x010D, IVI:0x00, SEQ:0x00002C66, CTL:0x01, TTL:0x7F, NID:0x72
[** ERR **]:[net_init.c]:[234]: [NET Rx] SRC ADDR 0xFFFF not a Unicast Address. Dropping...
[NET Rx] Pkt. SRC:0xFFFF, DST:0x010D, IVI:0x00, SEQ:0x00002C66, CTL:0x01, TTL:0x7F, NID:0x72
[** ERR **]:[net_init.c]:[234]: [NET Rx] SRC ADDR 0xFFFF not a Unicast Address. Dropping...
[NET Rx] Pkt. SRC:0xFFFF, DST:0x010D, IVI:0x00, SEQ:0x00002C66, CTL:0x01, TTL:0x7F, NID:0x72
[** ERR **]:[net_init.c]:[234]: [NET Rx] SRC ADDR 0xFFFF not a Unicast Address. Dropping...
[NET Rx] Looks like we are processing a relayed packet!
[NET Rx] Pkt. SRC:0x010D, DST:0xFFFF, IVI:0x00, SEQ:0x00001445, CTL:0x00, TTL:0x7E, NID:0x72
[LTRN Rx] Pkt originated from Local SRC. Some repeater probably send back our message.. Dropping...
[NET Rx] Pkt. SRC:0xFFFF, DST:0x010D, IVI:0x00, SEQ:0x00002C67, CTL:0x01, TTL:0x7F, NID:0x72
[** ERR **]:[net_init.c]:[234]: [NET Rx] SRC ADDR 0xFFFF not a Unicast Address. Dropping...
[NET Rx] Looks like we are processing a relayed packet!
[NET Rx] Pkt. SRC:0x010D, DST:0xFFFF, IVI:0x00, SEQ:0x0000144B, CTL:0x00, TTL:0x7E, NID:0x72
[LTRN Rx] Pkt originated from Local SRC. Some repeater probably send back our message.. Dropping...
[** ERR **]:[ltrn_replay_cache.c]:[489]: [LTRN] Failed to allocate SAR Context. Returning
[** ERR **]:[ltrn_api.c]:[312]: [LTRN Tx] SAR Context Allocation for Tx Failed.
Battery Check ...95%
[** ERR **]:[ltrn_replay_cache.c]:[489]: [LTRN] Failed to allocate SAR Context. Returning
[** ERR **]:[ltrn_api.c]:[312]: [LTRN Tx] SAR Context Allocation for Tx Failed.
[** ERR **]:[ltrn_replay_cache.c]:[489]: [LTRN] Failed to allocate SAR Context. Returning
[** ERR **]:[ltrn_api.c]:[312]: [LTRN Tx] SAR Context Allocation for Tx Failed.
[** ERR **]:[ltrn_replay_cache.c]:[489]: [LTRN] Failed to allocate SAR Context. Returning
Device:
Hi firebird,
I am working on both of your queries with our team internally. Will get back to you with a solution asap.
Best,
LC_Dialog
Hi firebird,
To help resolve this issue, we need more information regarding your implementation. Can you please provide the following details.,
What changes did you made to the application?
How many nodes are you using?
How often do you broadcast data?
What is the size of the packet sent?
Best regards,
LC_Dialog
Hi teams,
I made several changes to mesh example. Especially modified vendor server/client model.
It is too many to list in this post, so first I want to know the root cause of this error.
1. I have two nodes one is for vendor server and the other is for vendor client model, but when only one vendor server is running, the same error occurs. So, I think only one node which has vendor server model may have problem.
2. The bloadcast period is 10 seconds.
3. The data parts of each broadcast packet is 13 bytes.
Additional observations:
1. The broadcasting period is not related. When I changed period to 1 second, device show the same error after exactly 16 successful transmission.
Changing period and test several times, device always failed after 16th tx.
2. When I reduced packet size, 5 bytes is threshold. If packet size is below 5, packet fragmentation does not occur, and error also not occurs.
But if the packet size is over 5, errors are always happening.
3. BTW, the following messages also disappeared when non-fragment condition. Why?
Hi firebird,
Thanks for sharing the details. We are looking into it..
Best regards,
LC_Dialog
This issue is NOT completed.
Why this question is marked as "completed"?
I am still waiting for feedback.
Hi firebird,
I am not sure why it was set to completed. You are right, it is in progress. I will get the checked.
Also, we are working on your 2 pending questions and should be able to provide some update next week.
Best regards,
LC_Dialog
Reminding...
Awating update...