Compiler/CC3220SF: cc3220sf

Asaf Tvito

Part Number: CC3220SF

Tool/software: TI C/C++ Compiler

Hi,

i use dynamic memory and i get WDT because in function HeapMem_freeUnprotected it stack on

while (nextHeader != NULL && nextHeader < newHeader) {
/* Make sure the addr is not in this free block */
Assert_isTrue(((UArg)newHeader >= (UArg)nextHeader + nextHeader->size),
HeapMem_A_invalidFree);
curHeader = nextHeader;
nextHeader = nextHeader->next;
}

the problem is:

nextHeader = nextHeader->next

advice

Thanks

over 5 years ago

0 ToddMullanix over 5 years ago

TI__Guru* 96960 points

Hi Asaf,

I expect the application corrupted something in the heap and causing an infinite loop. Can you use the debug kernel instead of the release one. Take a look in the SimpleLink SDK User Guide to see how to import the debug kernel and use it. The debug kernel includes HeapTrack. I'm hoping this will help identify the issue. You can take a look at https://training.ti.com/debugging-common-application-issues-ti-rtos for more details about HeapTrack (it's the last third of the video/presentation).

Todd

0 Asaf Tvito over 5 years ago in reply to ToddMullanix

Genius 4010 points

Hi,

i follow the instruction in the document and implement the suggestion, but I'm not see how i found my problem.

how can i debug the problem?

0 ToddMullanix over 5 years ago in reply to Asaf Tvito

TI__Guru* 96960 points

Asaf,

I'm not sure how to help you with this. I was hoping that HeapTrack might flag something. You'll need to isolate the application code that is causing the corrupt. You can try using the debug kernel (refer to the SimpleLink SDK User Guide). Along with enabling asserts, it enables logging which might be helpful.

Todd

0 Asaf Tvito over 5 years ago

Genius 4010 points

Part Number: CC3220SF

Tool/software: Code Composer Studio

Hi,

i open the option BIOS.assertsEnabled = true;

my softwre stack on function:

Void Error_policyMin(Error_Block *eb, Types_ModuleId mod, CString file,
Int line, Error_Id id, IArg arg1, IArg arg2)

how can i know the reason?

what is the parameters in the function?

0 ToddMullanix over 5 years ago in reply to Asaf Tvito

TI__Guru* 96960 points

Asaf,

The easiest thing it to just look at the callstack. I expect somewhere up the callstack, you'll find what caused the problem.

Todd

0 Asaf Tvito over 5 years ago in reply to ToddMullanix

Genius 4010 points

Hi,

i get assert because i call malloc from interrupt.

why i can call malloc from interrupt?

0 ToddMullanix over 5 years ago in reply to Asaf Tvito

TI__Guru* 96960 points

malloc eventually transverses a linked list (of free blocks.) Because, by default, it use a GateMutex instance. GateMutex_enter calls Semaphore_pend with a BIOS_WAIT_FOREVER...which is a no-no from an ISR.

Options

1. Change your logic to have the memory allocated somewhere else.

2. Use a different heap implementation (e.g. HeapBuf or HeapMultiBuf) which does not use a semaphore for blocking. You need to fully understand your allocation needs to size the block size and counts properly though.

3. Setup a different Gate for the HeapMem module. For example you can use a GateHwi instance which disables/restores interrupts. The downside of this is that potentially you could have interrupts disabled a relatively long time while the free list of blocks is traversed. Fyi...HeapMem is a variable size heap allocation that uses a first-fit algorithm (instead of best-fit).

4. If the memory is being used for communication, use Mailbox instead. In the ISR use a zero timeout to Mailbox_post.

I'd highly recommend option 1. You could allocate some blocks in main a simply add them to linked list and then the ISR would just pop those off the linked list (and the consumer of the memory would push them back on).

Todd

0 Asaf Tvito over 5 years ago in reply to ToddMullanix

Genius 4010 points

Hi,

i cant use option 1, so i try to use option 2.

how can i change to HeapBuf api?

0 ToddMullanix over 5 years ago in reply to Asaf Tvito

TI__Guru* 96960 points

Create the HeapBuf instance and then use that as the IHeap_Handle in a Memory_alloc call (instead of using malloc) in the ISR.

0 Asaf Tvito over 5 years ago in reply to ToddMullanix

Genius 4010 points

i found that option 3 is the best for me.

how do i change to GateHwi?

0 Asaf Tvito over 5 years ago in reply to ToddMullanix

Genius 4010 points

i found that option 3 is the best for me.

how do i change to GateHwi?

0 ToddMullanix over 5 years ago in reply to Asaf Tvito

TI__Guru* 96960 points

Take the HeapMem Gate section of the HeapMem API Reference in SYS/BIOS. Here's a link you can use (this area has not changed for a long time).

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/sysbios/6_53_02_00/exports/bios_6_53_02_00/docs/cdoc/ti/sysbios/heaps/HeapMem.html

Todd

Wi-Fi

Wi-Fi forum

Compiler/CC3220SF: cc3220sf