nRF52811 w/ soft device s140

RE: nRF52811 w/ soft device s140

Hung Bui — Tue, 12 Dec 2023 10:31:49 GMT

Hi Kevin,

Torbjørn is away for a week, so I will just drop an answer here.

No there isn't an option to change the max number of peripheral the S112 can support. Unfortunately there will be no new development on the legacy Softdevices as we moved to nRF Connect SDK from 3 years ago.

RE: nRF52811 w/ soft device s140

kclamb2015@gmail.com — Mon, 11 Dec 2023 23:19:33 GMT

So played around with this a bit and s140 is quite a bit bigger. Don’t suppose there’s a way to expand s112 to support more peripheral connections?

Here’s a cool video of us connecting 4 phones to the device.

https://www.instagram.com/p/C0t6Lrlutb1/?igshid=MzRlODBiNWFlZA==

Btw, appreciate the support.

Thanks,

Kevin Lamb

RE: nRF52811 w/ soft device s140

ovrebekk — Wed, 22 Nov 2023 12:56:33 GMT

Hi Kevin

The RAM_SIZE parameter is surely not correct. The available RAM size equals the total ram size (RAM_PH_SIZE = 0x6000) - 0x4990, which only leaves 0x1670 for the application (or 5.7kB).

I went through the exercise of updating the ble_app_uart example with project files for the pca10056e board running on the S140 SoftDevice, and I have attached it below:

devzone.nordicsemi.com/.../317960_5F00_ble_5F00_app_5F00_uart.zip

Could you take a look at the project in the \317960_ble_app_uart\pca10056e\s140\ses folder and see if you can use it for reference?

I tried with both 8 and 6 peripherals, but in either case I was not left with enough RAM for the ble_app_uart application libraries. I left it at 4 which seemed to work fine, and I was able to run the application.

I guess you need to enable more than 4 links in order to justify the move to the S140, but I am not sure how much more is practically achievable.

Best regards
Torbjørn

RE: nRF52811 w/ soft device s140

kclamb2015@gmail.com — Tue, 21 Nov 2023 16:44:24 GMT

Tried the settings your terminal suggested;

And got this;

Hmm I take it's too big then?

by the way, I am not sure how to get that terminal logging. Is it because I have NRF_SDH_BLE_LOG_ENABLED 0

Correct we want more peripheral links. This device will be connected to (and "controlled") by several phones/tablets. It has low data throughput (no audio, no video). Mainly just notify's the client (central) that it is on/off and some other simple stuff.

As far as project complexity, I believe the MCU use is fairly basic; Just twi, ble, gpio and interrupts, timers.

Still also having it throw an error for FPU;
Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)

what file was this supposed to be defined in?

Thanks,

Kevin

RE: nRF52811 w/ soft device s140

ovrebekk — Tue, 21 Nov 2023 12:33:05 GMT

Hi Kevin

[quote user="kclamb2015@gmail.com"]Okay good to know about the 20 connections. Would it at least expand it from 4 (s112) to a few more? 6-8 connections? Your best guess?[/quote]

It's impossible to give an accurate answer to that without knowing how much memory you need for your application, but I expect anything above 4 is going to be a challenge.

To test this you can try to build one of the standard Bluetooth samples, and experiment with the SoftDevice configuration in sdk_config.h.

I tested this myself based on the ble_app_uart sample, building the one targeting the pca10056 and the S140 SoftDevice.

When increasing the number of peripheral and total links to 8 I can see in the debugger that the new RAM start location should be 0x20004990, which means the SoftDevice RAM consumption alone is 18.8kB (0x4990 converted to decimal):

I set the data length and max MTU to minimum values to reduce RAM consumption somewhat. You could also try to use smaller values for the GAP_EVENT_LENGTH parameter, such as 2 or 3.

For clarity, do you want 20 links in peripheral or central role?

The S112 to my knowledge only support 4 peripheral connections, but when you need multiple links it is typically central links that are required.

Best regards
Torbjørn

RE: nRF52811 w/ soft device s140

kclamb2015@gmail.com — Mon, 20 Nov 2023 14:40:29 GMT

Okay good to know about the 20 connections. Would it at least expand it from 4 (s112) to a few more? 6-8 connections? Your best guess?

As for the FPU, the project was using dependencies for the nrf52810 and I was attempting to switch over those at the same time.
I likely missed a few spots where this needed to be updated, here's a list of locations I did update it;

Project Options (Common)->Debugger->Target Device = nRF52811_xxAA

Project Options (Common)->Debugger->Register Definition File = modules/nrfx/mdk/nrf52811.svd

these .s/.c files were changes in the project files;

Project Options (Common)->Preprocessor->Preprocessor Definitions =

APP_TIMER_V2
APP_TIMER_V2_RTC1_ENABLED
BOARD_PCA10056
CONFIG_GPIO_AS_PINRESET
FLOAT_ABI_HARD
INITIALIZE_USER_SECTIONS
NO_VTOR_CONFIG
NRF52811_XXAA
NRF_SD_BLE_API_VERSION=7
S140
SOFTDEVICE_PRESENT
CUSTOM_BOARD

Thanks Torbjørn!

RE: nRF52811 w/ soft device s140

ovrebekk — Mon, 20 Nov 2023 13:56:54 GMT

There is some information here regarding setting the right memory settings when using a SoftDevice. Essentially you have to run the code with your desired configuration, and logging enabled, and you will get a message to the log with instructions what the RAM configuration should be.

Unfortunately I don't think you will be able to support 20 concurrent connections in the nRF52811. When running multiple connections the RAM usage of the SoftDevice will increase considerably, and the nRF52811 has quite limited RAM available compared to the larger devices in the nRF52 family. Typically you would need something like the nRF52832 or the nRF52833 in order to run applications where you need a large number of links.

[quote user=""]

Not sure if this is related but when I tried to build the project the following error was displayed;

#error "Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)"

[/quote]

It is odd that changing the SoftDevice alone would introduce this error. Are you sure that there aren't some other configuration changes in the project that could have caused this?

Best regards
Torbjørn