Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

Jørgen Holmefjord — Mon, 12 Jul 2021 15:36:21 GMT

Yes, that looks correct.

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

jar0d — Mon, 05 Jul 2021 11:36:54 GMT

Thank you Jørgen,

it definitely solves the issue. I noticed that the rows have actually seven columns and not six as you can see from the table header. I added the extra Max Count Column header. Is it correct?

Before

After

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

Jørgen Holmefjord — Mon, 05 Jul 2021 09:14:39 GMT

Try pushing the string as described in Deferred processing:

void foo(void)
{ 
    char string_on_stack[] = "stack";
    //nrf_log_push() copies the string into the logger buffer and returns address from the logger buffer
    NRF_LOG_INFO("%s",NRF_LOG_PUSH(string_on_stack));
}

Most likely, the string goes out of scope and is overwritten before the logs are processed.

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

jar0d — Fri, 02 Jul 2021 10:36:41 GMT

Hello Jørgen,

I attach my post to your answer because I feel it could be related to this old issue. Even if I set all the count blocks in sdk_config.h I get this (SDK 17.0.2)

It seems all the rows are not properly managed. Under debug print_buffer contained in the row

NRF_LOG_INFO("%s", print_buffer);

has the right value

"| XXSmall | 4 | 100 | 0 | 4 | 0 | 0 |"

But then the result is what you can see above.

What is my fault?

Thank you.

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

Jørgen Holmefjord — Mon, 26 Oct 2020 16:50:20 GMT

It looks like print_block_info() will only print info if the block category is included:

// No statistic provided in case block category is not included.
if (m_block_count[block_cat] != 0)

Have you set any of the MEMORY_MANAGER_{SIZE}_BLOCK_COUNT defines in your sdk_config.h file?

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

Rafalino — Tue, 20 Oct 2020 11:18:56 GMT

Hello,

Can someone explain what should we see when running nrf_mem_diagnose() ?

Thanks in advance ,

Rafalno

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

Rafalino — Thu, 15 Oct 2020 08:40:08 GMT

Hello Jørgen,

I have used this updated version of mem_manager.c and also enabled the memory manager log :

#define MEM_MANAGER_CONFIG_LOG_ENABLED 1

I call nrf_mem_diagnose_reset() , nrf_mem_diagnose() every two seconds.

This is what I see in my log

00> <info> mem_mngr: +------------+------------+------------+------------+------------+------------+
00>
00> <info> mem_mngr: | Block | Size | Total | In Use | Min Alloc | Max Alloc |
00>
00> <info> mem_mngr: +------------+------------+------------+------------+------------+------------+
00>
00> <info> mem_mngr:
00>
00> <info> mem_mngr:
00>
00> <info> mem_mngr:
00>
00> <info> mem_mngr: +------------+------------+------------+------------+------------+------------+
00>
00> <info> mem_mngr: | Total | 98432 | 526 | 64
00>
00> <info> mem_mngr: +------------+------------+------------+------------+------------+------------+
00>
00> <info> mem_mngr: 2: 0 -> 1

I have the feeling that it is not working as expected.

Can you please clarify?

Thanks in advance ,

Rafalino

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

Jørgen Holmefjord — Wed, 14 Oct 2020 12:21:49 GMT

Ok, sorry. I though the rest of the errors was caused by the first one, but I see some of them are separate errors (missing m_max_count and semicolon after NRF_MEM_MANAGER_DIAGNOSE/NRF_MEM_MANAGER_DIAGNOSE_RESET). I have attached a version of the file that compiles in the application, but I did not do any further testing: devzone.nordicsemi.com/.../8244.mem_5F00_manager.c

I will add the other errors to the internal report.

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

Rafalino — Tue, 13 Oct 2020 15:17:06 GMT

Hello Jørgen,

As you can see from the log above , the Typo on line 504 in mem_manager.c is not the only issue.

Please make sure that you guys handle all other issues as well.

Thanks in advance,

Rafalino

RE: Unable to use Memory Manager Diagnostics even on the latest SDK (SDK 17.0.2)

Jørgen Holmefjord — Tue, 13 Oct 2020 13:12:58 GMT

Hi,

There seems to be a typo on line 504 in mem_manager.c. This line:

static const uint32_t m_min_size_default[BLOC_CAT_COUNT] =

Should be changed to:

static const uint32_t m_min_size_default[BLOCK_CAT_COUNT] =

I will report this internally.

Best regards,
Jørgen