• Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 414 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.

Analyzing a crash on my C6424 EVM

Harikrishna Vuppaladhadiam
Expert 1855 points

Other Parts Discussed in Thread: SYSBIOS

Hi,

  I am using CCS 5.1 tools working on c6424 EVM. I get the following crash. but have no clue from the backtrace. Pl. advise how to enable any features? I get the following screen with little information. 

8473.Doc1.doc

Regards,

Hari

  • TI__Guru**** 171449 points

    Hari,

    The issue you are getting is a CPU Exception that is being reported by SYSBIOS.

    In this case, I strongly suggest you take a look at chapter 6 of the C64x/C64x+ CPU Instruction Set Guide (SPRU732).

    Specifically for your case, the IERR=0x1 indicates an Instruction Fetch Exception that seems to have occurred at the reserved address 0x0 (the line Exception at 0x0)

    Maybe a pointer is being reset or used before being properly initialized - this sometimes happens with untested malloc() calls, for example.

    In any case, this is highly related to either SYSBIOS or the device itself, therefore you may want to follow up this discussion at these forums and get the advice from the experts there.

    Hope this helps,

    Rafael

  • in reply to desouza
    Expert 1855 points

    This problem is reproducible on my setup. Is there anyway I can get more backtrace information so that it points me around the problematic code? I am not sure what else to enable on CCS project settings/debug settings? Pl. advise. 

  • in reply to Harikrishna Vuppaladhadiam
    TI__Guru**** 171449 points

    Hi,

    From a pure CCS standpoint, the screenshot you sent does not give much hope to reconstruct the previous history; as you can see in the Debug view, the only callstack information shown is the abort() function, as the CPU exception erased all previous information. In this case I would check with the device experts on the C6000 forum if the exception handling mechanism gives any additional information.

    Also, since you are using SYSBIOS I would imagine it could have some information through the ROV (menu Tools --> ROV) but again, I would check with the BIOS experts to see if they have additional ideas.

    Regards,

    Rafael