• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1372 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

backtrace after getting exception in C66x sysbios

Weichun Yuan
Expert 1210 points
Other Parts Discussed in Thread: SYSBIOS

we've run into an exception when we develop and debug on C6657 based system using jtag. We run SysBios 6.32.05.54 with CCS5.1.1. From the exception print out, we can find out the pc and sp at the time of crash. Even though we could find out the offending assembly instruction, we could not find out why we got there, because that particular function is called frequently.

We would like to have a way to either 1) do a backtrace, so that we can find out how the function call hierarchy cause the exception or 2) to find out the local variables in the function failed so that we can know why the function failed.

We tried several ways to get those information, but none of them work.

1. add ti.sysbios.family.c64p.Exception.enable_print in cfg file

2. use the following functions as exception hook, try to get back to the offending function. We could return from exception handler, but ccs does not generate backtrace of the calling hierarchy.

Could anyone give us some suggestions on how to debug this kind of problems?

thanks

Weichun

  • 0
    TI__Guru**** 450961 points

    Hello Weichun,

    C6657 supports various tracing capability, which can be a powerful feature to debug cases such as yours. Which JTAG emulator are you using with your target?

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1210 points

    Hi, Ki,

    we are using BH-USB-100v2 jtag. How can we use trace buffer to back trace? Is there a document or demo which we can follow?

    thanks

    Weichun

  • 0 in reply to Weichun Yuan
    TI__Guru**** 450961 points

    Weichun Yuan said:
    we are using BH-USB-100v2 jtag

    This emulator is pretty limited. But you should be able to use the ETB on the device. Check out the ETB wiki for more details:

    http://processors.wiki.ti.com/index.php/ETB

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1210 points

    Hi, Ki,

    thank you so much for the information, which is really useful.

    What is the best way for me to find the HWI vector? The closest I found is ti_sysbios_family_c64p_Hwi_dispatchC_I. Is this a good one?

    in our particular case, the exception happened before the sysbios started. That is probably why we could not catch it using the trace buffer after we stopped trace.

    any more suggestions?

    thanks

    Weichun

  • 0 in reply to Weichun Yuan
    TI__Guru**** 450961 points

    Weichun Yuan said:
    What is the best way for me to find the HWI vector? The closest I found is ti_sysbios_family_c64p_Hwi_dispatchC_I. Is this a good one?

    I suggest posting in the BIOS forum for this questions. The BIOS experts there can help you best.

    Thanks

    ki