• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 1145 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.

Debugging a imprecise data abort

Brendan Hanna
Prodigy 20 points
Other Parts Discussed in Thread: AM3359

I am currently working on an AM3359 processor - in the guise of a beaglebone processor.

The problem is that I have an application that continually generates an imprecise data abort. I know it is a data abort because the data abort ISR is firing. I know it is an imprecise data abort because the DFSR (data fault status register) (cp15, c5, 0, c0, 0)  reports 0xc06 via JTAG.

So the question is, how do I work out that is the cause of this imprecise abort?

Thanks,

  • 0
    TI__Guru**** 393215 points
    Hi Brendan,
     
    Is this a Linux application? Can you add some debug prinouts in it so you can trace where this is happening?
     
     
  • 0 in reply to Biser Gatchev-XID
    Prodigy 20 points

    Hello Biser,

    It is not for a Linux application - rather a Mentor Graphics Nucleus environment.

    I have since traced the problem to an incorrectly size memory allocation - that I have fixed. 

    I don't really think that adding printouts would have helped much. The address range where the processor was executing when the imprecise exception finally fired did not appear to have much to do with the cause. It would be like a needle in a hay stack trying to find the right place to put debug printouts.

    Is there any other way to try and trace which attempt to access memory is causing a problem?  The ARM manuals refer to an AXI decode error. Is there a way to find a potential cause for that?

    Brendan