Migration from nRF52832 to nRF52810

RE: Migration from nRF52832 to nRF52810

Alex — Tue, 13 Mar 2018 14:44:58 GMT

Hi Kristin,

Finally I was successful :-)

Due to a problem in the build configuration the application contained some unnecessary modules (nrf-log, RTT, remains of the bootloader etc.). Now the application fits into the flash as expected.

After this I was able to read the actual RAM usage of the softdevice with the nrf_sdh_ble_enable() function (as you suggested).

So this problem is solved, thanks.

RE: Migration from nRF52832 to nRF52810

Turbo J — Fri, 09 Mar 2018 12:42:02 GMT

The "Call stack" section directly below your link specifies 0x600 bytes stack minimum, which is not too far off the 2KB that some older softdevices require (and I was referring to).

RE: Migration from nRF52832 to nRF52810

Alex — Thu, 08 Mar 2018 16:33:04 GMT

Hi J, I am not sure if I have understood your answer at all. According to the Memory resource requirements the S112 softdevice needs 0xd60 + X Bytes RAM. Besides this memory, do you mean that the softdevice needs 2kB additional RAM? On the stack?

RE: Migration from nRF52832 to nRF52810

Alex — Thu, 08 Mar 2018 16:23:16 GMT

With the following linker-file settings the build is successful:

FLASH (rx) : ORIGIN = 0x18000, LENGTH = 0x18500
RAM (rwx) : ORIGIN = 0x20000F10, LENGTH = 0x50F0

Note:

The stack and heap size in the gcc_startup_nrf52810.S are set as follows:

Stack_Size = 2048 (default value)

Heap_Size = 0

RE: Migration from nRF52832 to nRF52810

Turbo J — Thu, 08 Mar 2018 14:58:48 GMT

Careful: The RAM usage displayed does not include the softdevice memories. And the softdevice wants about 2KB of stack memory, which has to be free after linking your application. That is what the linker moans about here. Not exactly sure about flash - try to fix the ram issue first.

RE: Migration from nRF52832 to nRF52810

FormerMember — Thu, 08 Mar 2018 14:32:37 GMT

From the build information, the ~80 kB application should fit well into the remaining 96kB of flash.

Could you test how much you need to increase the flash setting when compiling to make the compile finish without space issues? (Just for testing purpose..)

RE: Migration from nRF52832 to nRF52810

Alex — Wed, 07 Mar 2018 15:10:08 GMT

Hi Kristin, thanks for your reply.

I have changed the RAM size in the linker file. Furthermore I have set the HEAP_SIZE in the gcc_startup_nrf52810.S to 0 because I do not use dynamic memory allocation. So regarding the "overflowed RAM region" problem the linker is satisfied.

But unfortunately I still have the Flash overflow problem and therefore no running application yet...

RE: Migration from nRF52832 to nRF52810

FormerMember — Wed, 07 Mar 2018 14:16:45 GMT

I will start with the last: When enabling the softdevice using the function nrf_sdh_ble_enable(), the actual RAM usage used by the application will be printed over UART/RTT when log is enabled and the severity level includes "warning (sdk_config.h).

As stated in the S112 release note, the minimum amount RAM used by the softdevice is 3.68 kB. Could you try to lower the setting for the amount of RAM used by the softdevice in your application, until it compiles? And then, check how much RAM the softdevice requires in you application?