CCS/CC1352R: TI RTOS Memory_alloc ends up in the spin loop

Hi Robert,

Seem to me, based on the trace, that you run into some error (or exception) during your malloc. Have you tried to use the ROV (Runtime object viewer) to see if there is a Hwi exception and/or decode the Error block (this would be the typical first step to debug these kind of issues).

Thanks for your reply M-W.

I have looked in the ROV. There is no Hwi exception. I have not looked at any Error block since I am using malloc. Is there any documentation on how to use Error blocks with Memory_alloc? I could switch to that I guess, but looking at the documentation here:

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/6_42_01_20/exports/bios_6_42_01_20/docs/cdoc/xdc/runtime/Memory.html

I see nothing about that Memory_alloc can end up in the spin loop. If an allocation failed, I would have expected it to simply return NULL. How can I learn about using Error blocks together with Memory_alloc. Honestly, I have not used the Error module at all before.

Thanks

Hi Robert, 

Could you maybe share your TI-RTOS configuration file with me? I would assume that there is something with the actual kernel configuration that puts you in this state. I also see you use the "Memory_alloc" call, you could also use the generic "malloc" and "free" if you want to also have some portability in the code.