• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 298 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.

MCU-PLUS-SDK-AM243X: Abort diagnostics

Dominik Ondra
Prodigy 150 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: AM2431

Hello TI expert, 
our team is experiencing Issue with unknow abort.

We are using FreeRTOS and AM2431 custom board. After a while the the application gets stuck here:

When I set the loop variable to 0 and jump out of the loop. I get into the HwiP_data_abort_handler assembly.
As mentioned in comment above the register R14ABT should contain address. This contained the the address in screenshot.

However this doesnt seem like a valid adress. 

Is there a way to get some diagnostics after abort ? E.g. which instruction has caused this abort etc. ?

Thank you for your help and have a great day.

Dominik

  • 0
    TI__Mastermind 26205 points

    Hi Dominik,

    Are you seeing issue in SDK application or your custom application. Looks like somewhere in application there is an access to invalid address.

    Regards,

    Ankur

  • 0 in reply to Ankur Baranwal
    Prodigy 150 points

    Hello Ankur, 
    thanks for you answer. I understand that somewhere there is an access to invalid memory. 
    We are having a lot of trouble finding this spot. We have managed to stop the app before it entered the abort,
    The register R14_ABT was containing the adress of HwiP_svc_handler():

    Is there any way of knowing where did this invalid memory access happened ?

    Any specific technique (Maybe some register containg some information ?) / debugging tip would be helpful.

    We have identified the thread that is causing this. However locating the part of the code that is causing this is still a problem.

    Thank you for your answer,

    BR

    Dominik

  • 0 in reply to Ankur Baranwal
    Prodigy 150 points

    Hello Ankur, 
    thanks for you answer. I understand that somewhere there is an access to invalid memory. 
    We are having a lot of trouble finding this spot. We have managed to stop the app before it entered the abort,
    The register R14_ABT was containing the adress of HwiP_svc_handler():

    Is there any way of knowing where did this invalid memory access happened ?

    Any specific technique (Maybe some register containg some information ?) / debugging tip would be helpful.

    We have identified the thread that is causing this. However locating the part of the code that is causing this is still a problem.

    Thank you for your answer,

    BR

    Dominik

  • 0 in reply to Dominik Ondra
    TI__Mastermind 26205 points

    Hi Dominik,

    You can try few things here

    • You can try to see if the behavior is consistent, you are running into abort after the fixed interval/loop and at same point in code.
    • You can try to use the trace using the XDS emulator you have. https://www.youtube.com/watch?v=PXMvAnzA7Vs

    Regards,

    Ankur