HeapBuf Error: Cannot call HeapBuf_free when no blocks have been allocated

G T

Expert 1940 points

Other Parts Discussed in Thread: SYSBIOS

"[ 135.954] [t=0x00000015:52ce7b00] ti.sysbios.heaps.HeapBuf: ERROR: line 296: assertion failure: Cannot call HeapBuf_free when no blocks have been allocated"

I started getting this assert after modifying my DSP firmware to call MessageQ_put() function twice for two different messageQs after receiving a msg from host.

MessageQ_put() function description says that "the application loses ownership of the message once MessageQ_put() is called."

Is this asserting for the same reason? Or is this something else.

Any ideas on how I should handle a case where DSP need to respond via two different MessageQs for the same message received from the host?

Here are the packages I am using now on DRA7xx with DSP running on TI RTOS,

IPC - 3.36.01.11

SYSBIOS - 6.41.03.51

XDC - 3.30.06.67-core

CGT6x - 7.4.4

Let me know if any other info is required.

Thanks,

Girish

over 9 years ago

0 Aldabreu over 9 years ago

TI__Intellectual 2890 points

Hi Girish,

I could see the assert being hit if your application is calling MessageQ_free() on the message that doesn't exist anymore rather than calling Message_put() on the same message twice. Is this occurring within one of your threads?

Best,
Alexander

0 G T over 9 years ago in reply to Aldabreu

Expert 1940 points

Hi Alexander,
Yes, you are right. It is calling MessageQ_free() in an error case, as it failed Message_get() call.
I will look into this error more and see why Message_get() is returning status<0.

Thanks!

0 ToddMullanix over 9 years ago in reply to G T

TI__Guru* 96960 points

You cannot call Message_put twice with the same message. Once you send the message, you lose ownership of the message. You cannot resend it or delete it. Once you call Message_get and receive the message, you can send it again or delete it.

Todd

0 G T over 9 years ago in reply to ToddMullanix

Expert 1940 points

Hi Todd,
I figured that and modified my code accordingly.
But I am still seeing MessageQ_get failing even when I am not calling MessageQ_put twice.
I just posted in linux forum another related question.
e2e.ti.com/.../534807

Thanks.
Girish

0 ToddMullanix over 9 years ago in reply to G T

TI__Guru* 96960 points

Sounds good. The device forums are handling the IPC questions now.

Todd

Processors

Processors forum

HeapBuf Error: Cannot call HeapBuf_free when no blocks have been allocated