You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by Jernej Turnsek <je...@gmail.com> on 2022/09/27 10:57:15 UTC

Interesting problem with mm_heap_s and mm_semaphore

Hi,

I am using mm_heap region from address space which starts with 0x00000000.
ITCM memory on NXP i.MX RT10xx processors has this address. in mm_heap_s
structure, mm_semaphore is the first element and when initialized, it is
compared to NULL, thus initialization fails. To get around this problem I
switched places with the next element, which is mm_heapsize. But I am
afraid that this is only a temporary solution. Looking for a permanent one?

Thanks,
Jernej

Re: Interesting problem with mm_heap_s and mm_semaphore

Posted by Jernej Turnsek <je...@gmail.com>.
I guess I could move the whole region a few bytes forward.

On Tue, Sep 27, 2022 at 12:57 PM Jernej Turnsek <je...@gmail.com>
wrote:

> Hi,
>
> I am using mm_heap region from address space which starts with 0x00000000.
> ITCM memory on NXP i.MX RT10xx processors has this address. in mm_heap_s
> structure, mm_semaphore is the first element and when initialized, it is
> compared to NULL, thus initialization fails. To get around this problem I
> switched places with the next element, which is mm_heapsize. But I am
> afraid that this is only a temporary solution. Looking for a permanent one?
>
> Thanks,
> Jernej
>