topic Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme in MCUXpresso IDE

MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

minibix — Thu, 05 Apr 2018 12:57:52 GMT

Hi,

I'm using the MCUXpresso FreeRTOS SDK and switched over to the Heap 5 memory allocation scheme in order to use both memory regions on the MK22FN1M0VLK12 I'm using (64kB + 64kB).

However, I can no longer accurately analyse how the heap is being used as the Heap Usage table shows blocks that are not part of the heap and it is preventing the green/red bar visualisation from displaying properly.

I am getting a ~500MB block of memory being reported.

How can I fix this?

Thanks

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

lpcxpresso_supp — Mon, 09 Apr 2018 11:39:25 GMT

Thanks for your report. We'll investigate, but I suspect that the FreeRTSO TAD plugin doesn't currently support the use of FreeRTOS's heap5 option (span multiple non adjacent (non-contiguous) memory regions).

Regards,

MCUXpresso IDE Support

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

minibix — Thu, 12 Apr 2018 15:59:21 GMT

Thanks.

When do you think you'll get an answer on this please?

I think this feature is important as the MCUXpresso SDK supports all FreeRTOS memory schemes and you'd expect MCUXpresso IDE to do so too.

Otherwise, development slows down.

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

lpcxpresso_supp — Sat, 14 Apr 2018 08:06:16 GMT

As previously stated, we are investigating this issue with the FreeRTOS TAD view. Hopefully we can incorporate a fix in the next IDE release.

Regards,

MCUXpresso IDE Support

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

minibix — Sat, 14 Apr 2018 12:27:52 GMT

Great, when's the next IDE release.

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

lpcxpresso_supp — Mon, 16 Apr 2018 08:42:52 GMT

The public release of the next version is expected around late May.

Regards,

MCUXpresso IDE Support

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

BlackNight — Sun, 06 May 2018 07:03:28 GMT

Hi Mike,

what version of the FreeRTOS plugin are you using? It seems to me you are using V1.0.1 which indeed had this issue. There is a V1.0.2 availble (update site: http://freescale.com/lgfiles/updates/Eclipse/KDS) which shows correctly for me two heap regions with 64KByte (Setup in MCUXpresso IDE as in Using Multiple Memory Regions with the FreeRTOS Heap | MCU on Eclipse ).

Maybe you can give V1.0.2 a try? The public release mentioned to be expected end of May should come with this (and other fixes too), but until then you could try V1.0.2 plugin.

I hope this helps,

Erich

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

biafra — Mon, 07 May 2018 16:11:00 GMT

Hi Erich,

I'm trying the new pulgin version, but it still displays wrong informations:

In the higher pane the sum of free space is not correct and there is not the green bar showing it.

In the lower pane the block size include the non existing space between two different blocks.

Many thanks

Biafra

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

BlackNight — Tue, 08 May 2018 18:57:46 GMT

Hi Francesco,

would you be able to share that project or files so I can try it on my end? Or at least share your memory configuration so I potentially could replicate this?

Erich

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

biafra — Wed, 09 May 2018 07:33:59 GMT

Hi Erich,

Sorry, but I can't share the project.

The heap memory configuration is as follows:

Region 1: start address -> 0x14000000, size 0x1000 (K66 internal FLEXRAM)

Region 2: start address -> 0x1FFF0000, size 0xF000 (K66 internal RAM lower bank)

Region 3: start address -> 0x900006A8, size 0x4E000 (external SRAM) (this region size is modified compared to the image I posted)

Many thanks

Biafra

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

BlackNight — Thu, 10 May 2018 17:28:21 GMT

Hi Biafra,

I'm sorry: as I don't have have any K66 and no external SRAM boards, I cannot try your configuration :-(.

Erich

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

biafra — Fri, 11 May 2018 15:52:01 GMT

Hi Erich,

I think the external SRAM is not needed: in the previous image, in the lower pane, the error is across two different memory blocks that are both internal, one in the lower bank and the other in the upper one.

There is another error (not shown in the image) that is across the upper internal bank and the external SRAM bank.

I don't think the problem is related to the external SRAM, I think it's related simply to the dual banks (heap 5 memory scheme).

Many thanks

Biafra

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

biafra — Fri, 18 May 2018 16:10:38 GMT

Hi everyone,

I've just downloaded and installed the latest MCUXpresso 10.2.0 where there is the updated FreeRTOS aware plugin.

Using memory scheme 5, in the heap usage view I get this error:

I've just read the document https://www.nxp.com/docs/en/quick-reference-guide/MCUXpresso_IDE_FreeRTOS_Debug_Guide.pdf and all the steps are correctly done.

What can I do to display the correct informations?

Many thanks

Biafra

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

BlackNight — Fri, 18 May 2018 18:06:14 GMT

Hi Francesco,

could you share your FreeRTOSConfig.h and freertos_tasks_c_additions.h?

Erich

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

biafra — Fri, 18 May 2018 23:06:11 GMT

Hi Erich,

Just done.

Many thanks

Biafra

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

BlackNight — Sat, 19 May 2018 09:04:19 GMT

Hi Biafra,

your files look fine.

I believe it could be an include order problem on your side, as I'm not able to replicate this on my end.

Can you change that value below to 5 and give it a try?

Erich

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

biafra — Mon, 21 May 2018 08:15:38 GMT

Hi Erich,

I set configFRTOS_MEMORY_SCHEME to 3 in FreeRTOSConfig.h.

In my system in freertos_task_c_additions.h file the lines 75 to 77 are grayed (configFRTOS_MEMORY_SCHEME has already been defined in FreeRTOSConfig.h).

Now I get this error:

Many thanks

Biafra

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

BlackNight — Mon, 21 May 2018 13:31:40 GMT

Hi Biafra,

I was under the impression you are using scheme 5?

I think I would need to see the whole picture. It looks to me something is strang in your setup. Would it be possible that you could share a project to reproduce this? You don't have to include your custom code, just the project with the SDK and FreeRTOS and its configuration?

Erich

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

biafra — Tue, 22 May 2018 13:01:54 GMT

Hi Erich,

I'm trying to prepare what you asked for.

Isn't this problem related to the fact that one of the regions is in external RAM?

My configuration is:

static __NOINIT(FLEX_RAM) uint8_t HeapReagion1[ HEAP_REGION1_SIZE ];
static __NOINIT(SRAM_LOWER) uint8_t HeapReagion2[ HEAP_REGION2_SIZE ];
static __NOINIT(EXTRAM) uint8_t HeapReagion3[ HEAP_REGION3_SIZE ];

static const HeapRegion_t xHeapRegions[] =
{
   { HeapReagion1, HEAP_REGION1_SIZE },
   { HeapReagion2, HEAP_REGION2_SIZE },
   { HeapReagion3, HEAP_REGION3_SIZE },
   { NULL, 0 } //Terminates the array
};

EXTRAM is at address 0x90000000

Many thanks

Biafra

Re: MCUXpresso Heap Usage (FreeRTOS) reporting problem when using Heap 5 memory scheme

biafra — Wed, 23 May 2018 10:28:59 GMT

Hi Erich,

This is the project without custom code.

Is that what you asked me?

Many thanks

Biafra