• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 628 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

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

Robert Rehammar
Intellectual 300 points
Part Number: CC1352R


Tool/software: Code Composer Studio

I end up in the spin-loop from a Memory_alloc according to this trace:

I cannot see anything in the documentation about that Memory_alloc can end up in the spin loop. I am calling it from an ordinary malloc.

Thanks for advice.

  • 0
    TI__Guru 58425 points

    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).

  • 0 in reply to IUsedToBeARealPerson (M-W)
    Intellectual 300 points

    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:

    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

  • 0 in reply to Robert Rehammar
    TI__Guru 58425 points

    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.