• Locked Locked
  • Replies 7 replies
  • Subscribers 54 subscribers
  • Views 854 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.

IS UBM supported in Code Composer Studio 5.3.0 and TMS320C6726B DSP?

Joshua Wu81
Intellectual 800 points
Other Parts Discussed in Thread: TMS320C6726B

I tried to use Unified Breakpoint Manager (UBM) features in CCS for AET on TMS320C6726B DSP but can not get it working. Just want to make sure UBM is supported in CCS Version: 5.3.0.00090 with TMS320C6726B DSP.

  • TI__Mastermind 35645 points
    Hi,

    Moving your post to right forum to be better answered.

    Thanks & regards,
    Sivaraj K
  • Guru 192875 points
    Hi Joshua,

    Check this thread: e2e.ti.com/.../135573

    Regards,
    Gautam
  • in reply to Gautam Iyer
    Intellectual 800 points

    Hi Gautam,

    Thanks for your reply. I read that thread before I posted my question. I didn't find the answer.

    When I add breakpoints under BreakPoints Tab in CCS Debug window I can select "skip count" under "Breakpoint Properties..."

    But the "skip count"  is not working when add breakpoint as "Hardware BreakPoint" under Breakpoints Tab. It doesn't show the counter value and never stops at where the breakpoint is set. 

    The reason I would like to use "Hardware BreakPoint" is that it provides "Condition" under Debugger Response in "Breakpoint Properties..."

    Is there any way I can use the features in "Hardware BreakPoint"?

  • in reply to Joshua Wu81
    TI__Guru**** 433871 points

    Hello

    Joshua Wu81 said:
    But the "skip count"  is not working when add breakpoint as "Hardware BreakPoint" under Breakpoints Tab. It doesn't show the counter value and never stops at where the breakpoint is set. 

    The skip count is supported with HW breakpoints. The reason why you do not see the counter value in the count column of the Breakpoints view is because that column only keeps track of skip counts from "Debugger Response", which is the case for SW breakpoints. HW breakpoints skip count actions are non-intrusive, handled by the driver and emulation logic on the chip so the "skips" are handled non-intrusively without debugger interaction. Hence the debugger does not keep track of these.


    As for never stopping at the HW breakpoint, I see some issues when using skip counts. Try disabling and re-enabling the breakpoint to see if that clears things up


    Joshua Wu81 said:

    The reason I would like to use "Hardware BreakPoint" is that it provides "Condition" under Debugger Response in "Breakpoint Properties..."

    Is there any way I can use the features in "Hardware BreakPoint"?

    SW breakpoints also support "Condition" under "Debugger Response". It should be there. If you don't see it, please provide a screenshot of the breakpoint properties.


    Thanks

    ki

  • in reply to Ki
    Intellectual 800 points

    The SW breakpoints does support "Condition" under "Debugger Response". I don't know why I missed that. Thanks.

    As for the skip counts issue, I tried disabling and re-enabling the breakpoint but still not working. My static variable  already show the count beyond the value I put in the Skip Count in HW breakpoints. Any thought? Thanks.

  • in reply to Joshua Wu81
    TI__Guru**** 433871 points

    Hi Joshua,

    Sorry for the delay. I didn't see your last question and just noticed it as I was going though some old posts.

    Joshua Wu81 said:
    As for the skip counts issue, I tried disabling and re-enabling the breakpoint but still not working. My static variable  already show the count beyond the value I put in the Skip Count in HW breakpoints. Any thought? Thanks.

    I cannot reproduce this (at least the disable/re-enabling the BP works for me). I would recommend you at least update your CCS version. If you cannot go to 6.1, at least update to 5.5. Your current CCS version of 5.3 is very old.

    ki