Mesh Chat Model - Error Message = No free slots for new incoming segmented messages

We are getting this message on our RELAY - via PuTTY.

"No free slots for new incoming segmented messages"

uart:~$ [01:00:53.683,380] <wrn> bt_mesh_transport: trans_seg: No free slots for new incoming segmented messages

then >>>

ASSERTION FAIL @ WEST_TOPDIR/zephyr/lib/os/ring_buffer.c:73

We are getting this error - using CHAT MODEL in MESH.  The RELAY gives us this same error message - we have increased the CONFIG_BT_MESH_ADV_BUF_COUNT value from 13 to 50.

We read here >>>  "No free slots" error while sending message  that adding a timing delay may help. 

We have not added a timing delay yet but lets say we use 0.1s between receiving and transmitting on to the proxy or the next Relay. Is this because of timing issues between the next available Tx slot being ready and the device being ready - or mistiming i should say.

How do we add a small delay?

We put this into our VS Code build - yes?

Please help if you can give us some information - many thanks.

We have nRF52840 BLE > nRF21540 DK as RELAY > nRF21540 DK as proxy.  

Thanks - Richard 

  • The flashing issue is intermittent.

    If I install Programmer with a version > 4.0.1 then I get JLink DLL errors when flashing. It does not work.

    If I install Programmer v4.0.1 with JLink v7.88j then flashing our XM122 beacons is intermittent i.e sometimes it works, sometimes it doesn't. 

  • Hi Andreas, Another question, is there a way of checking the voltage/battery/power supply level on a nrf21540 board? I can't see anything in the SDK.

  • TimD said:
    The proxy crash issue doesn't seem to be happening anymore. I did a fix by calling my python script with nohup python .....

    Glad to hear that this were resolved

    TimD said:
    Another question, is there a way of checking the voltage/battery/power supply level on a nrf21540 board? I can't see anything in the SDK.

    I think I need to restate our need for you to create a new case when you have questions unrelated to the topic you have ongoing. Your original topic was related to ring buffers and now we're looking into nRF21540 boards. I know the questions are quick and easy to answer, so this is both to ensure that you get an engineer with the proper expertise assigned to your case and to ensure that you get an avaialble engineer assigned to your case. Currently I am not available as I am working on other projects for a few weeks so to ensure that you get proper follow up from us it would be best if you create new cases for new topics and to keep a clean case/topic separation

    AHaug said:
    If rolling back the version does not resolve the issue, we would like you to raise a new ticket for that issue for easier trackability. Please feel free to refer to this ticket in the new one if you believe anything there is relevant.

    The same goes with the question related to the programmer as well. It is not to push you away from this ticket, but it is to ensure that you get an available engineer that can answer your questions.

    I hope you understand and that it is not too inconvenient for you

    Kind regards,
    Andreas

Related