This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

S13x 2.0.0-8 alpha peripheral connection count and RAM formula

I just read the S13x migration guide .. have some work to do :(. I'll have to read it a few more times to get my head around the bandwidth configuration but it looks super useful.

Two questions.

Is the periph_conn_count parameter now working so you can specify more than one concurrent peripheral connection or is that documented for the future but the 0.8 alpha still only supports one connection in peripheral mode and more than one in central mode as per previous releases?

Is there a formula given number of connections, number of high, low and medium bandwidth and all the other options you can give to work out what the BLE stack RAM requirement, or is the best advice to just give it lots, then read the value returned from the call to sd_ble_enable() in app_ram_base and fix your linker map to that value? How confident should we be that minor revs to the softdevice won't need more RAM for the exact same config parameters? I'd always be tempted to round it up a little bit to save having to do a firmware release because a minor softdevice revision wanted 16 extra bytes or something.

.. actually make that 3 questions. Is the 0.8 alpha API documentation up somewhere, I can find 0.7-alpha but not 8 in the infocenter. There's some changes since 0.7-alpha, would be handy not to have to go through the headers for them.

Parents
  • Only one peripheral connection is supported. So you can set it to 0, or 1.

    The best advice is to read the app_ram_base value returned from sd_ble_enable() and use it.

    How confident should we be that minor revs to the softdevice won't need more RAM for the exact same config parameters? I'd always be tempted to round it up a little bit to save having to do a firmware release because a minor softdevice revision wanted 16 extra bytes or something.

    Good question. We need to look into this. Will update soon.

    Unfortunately, the documentation will not be available in the Infocenter until the next SDK release.

  • thank you - I did actually set the number of peripheral connection to 2 to see the delta memory and it dint' break, but I didn't try to use the second one, it was just a memory test. I'll keep at 0 or 1 until the release notes tell me we're good for more.

Reply
  • thank you - I did actually set the number of peripheral connection to 2 to see the delta memory and it dint' break, but I didn't try to use the second one, it was just a memory test. I'll keep at 0 or 1 until the release notes tell me we're good for more.

Children
No Data
Related