NRF52 RAM memory usage

[Felipe Ribas]

I have seen this topic:

devzone.nordicsemi.com/.../

and a few others, in an attempt to visualize the RAM usage of my project. I currently use GNU ARM Embedded (gcc) for compiling. I do have a .map file but it just doesn't load into this website library (nothing happens).

Can I get any estimation of my RAM usage somehow?

[bjorn-spockeli]

Hi Felipe,

I recommend using Segger Embedded Studio since you're using GCC, it has a memory usage window that shows you how much FLASH and RAM you're using, see the screenshot below.

You can find a tutorial on how to import the Keil Projects from our SDK in to SES [here] (devzone.nordicsemi.com/.../).

Best regards

Bjørn

[Felipe Ribas]

I'm currently using Eclipse as an IDE but with manual makefile. To migrate to Segger it should be done all manually or there's any specific good method? Would you give also an personal opinion regarding the use of eclipse vs segger for nrf52 + s132 development (with nRF52 DK)?

[bjorn-spockeli]

Hi Felipe, I have not used SES that much yet as we mostly use Keil at work, but I have SES setup at home and use it for my personal projects. As far as I know there is not an option to import a custom project, so I am afraid that you will have to do it manually, i.e. add .c and .h files, and setup the compiler options. However, if you just follow the guide and import one of the SDK examples, then you can use that as a reference for the settings.

My personal opinion is that SES is much easier to setup and use compared to Eclipse. SES has a Pre-built C/C++ Compiler so you do not need to fetch the GNU toolchain compiler in addition to the IDE and it also has a built-in debugger so you do not have to go through the hassel of setting up GDB.

[Felipe Ribas]

Understood. Nice. But by built in compiler you mean I would have to rewrite the makefile and configure the project for the segger studio specifically or they use a GNU ARM based built in compiler?

[bjorn-spockeli]

Quote from the Segger webpage, here is the link. "Embedded Studio comes with the pre-built, ready-to-run GCC and LLVM compiler toolchains." You do not have to rewrite the makefile, but you will have to transfer linker, compiler flags, include paths etc from the makefile into the project options in SES. See the second screenshot I added to my answer.