• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 2776 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.

Trouble setting the Break Point Action - issue

karthick ph
Prodigy 190 points


I have working on F28335 micro quite some time.  CCS ver3.3 being used for the project development.

I have developed a project which consists of  ADC, SCI and CPU timer0 interrupts.  In this all interrupts

are triggered as per the configuration. 

Now, I have flashed the program, erase, programming and verification all successfully done.

But, finally it emulator shows following messages,

Trouble setting the Break Point Action: "Halt Target" at 0x33b34f: Error 0x/00000008/-2046 Error during: Break Point, Unable to set hardware breakpoint at 0x0033B34F. breakpoints are already in use. Some hardware breakpoints may be used by analysis.

Trouble setting the Break Point Action: "Halt Target" at 0x33b32d: Error 0x/00000008/-2046 Error during: Break Point, Unable to set hardware breakpoint at 0x0033B32d. breakpoints are already in use. Some hardware breakpoints may be used by analysis.

"Terminate Program Execution" at 0x33b60f: Error 0x00000008/-2046 Error during: Break Point, Unable to set hardware breakpoint at 0x0033B60f. breakpoints are already in use. Some hardware breakpoints may be used by analysis.

"Terminate GEL_Go()" at 0x33a8e9: Error 0x00000008/-2046 Error during: Break Point, Unable to set hardware breakpoint at 0x0033a8e9. breakpoints are already in use. Some hardware breakpoints may be used by analysis.

This time, SCI interrupt is not triggered.  However other ADC and CPUtimer0 interrupts is works fine.

I don't know the reason why the working code behaves, suddenly like this.

I have also attaching the linker and build options configured in my project.1030.build_linker.zip

Any suggestion will be appreciated.

  • 0
    TI__Guru**** 173310 points

    If you are programming and debugging your code in Flash, then you are limited to two hardware breakpoints when working with F28xx devices. Make sure there are no breakpoints enabled when you start the debug session and also disable the two breakpoints that CCS sets by default.

    Please see the following articles for more details:
    http://processors.wiki.ti.com/index.php/C2000_Flash_Common_Issues/FAQs#Using_Breakpoints_During_Debugging

     

  • 0 in reply to AartiG
    Prodigy 190 points

    Hi Aarti

    Thanks for the valuable suggestion, posted link is pretty helpful.

    I disabled the default "CIO and EOP break points" through Option tab ->Customize->Program/Project/CIO configuration.

    I don't have a clue that how this break point issue, stopping the SCI Rx interrupt from triggering?

    Do you ever come across this problem..

    Regards,

    Karthick Ph

  • 0 in reply to karthick ph
    TI__Guru**** 173310 points

    karthick ph said:

    I disabled the default "CIO and EOP break points" through Option tab ->Customize->Program/Project/CIO configuration.

    I don't have a clue that how this break point issue, stopping the SCI Rx interrupt from triggering?



    So did the "Trouble Setting breakpoint" messages go away after disabling the CIO and EOP breakpoints? Are you saying that the SCI interrupt is still not getting triggered though? If so, I don't think it is related to the breakpoint issue. If you are trying to set a breakpoint in the interrupt ISR that is something different, but I don't believe simply running out of breakpoints should have any effect on interrupt triggering.

  • 0 in reply to AartiG
    Prodigy 190 points

    Hi Aarti,

    Thanks for the update.  Yes, the breakpoint messages has gone away.

    Can I know how many software break points will be supported while debugging flash code?

    I have resolved the issue.  The problem is I have configured the GPIO11 pin for PWM6 module in the InitEPwm6Gpio() function.

    Also I have used the same GPIO11 pin for the SCIRXDB (SCI receive in B channel) interrupt. 

    In main.c file I have called InitSci() function prior to InitEPwm6Gpio() function.  Such that, PWM6 have been configured.

    So, after this I configured GPIO11 only for SCI receive; then interrupt got triggered.

    Once again, I appreciate your suggestions on this.

    Thanks

    Karthick PH

  • 0 in reply to karthick ph
    TI__Guru**** 173310 points

    karthick ph said:

    Can I know how many software break points will be supported while debugging flash code?



    If you set a breakpoint in code in Flash it will always be a hardware breakpoint, so will be limited in number. When debugging in RAM software breakpoints can be used and theoretically there is no limit to the number of software breakpoints as a SW breakpoint is implemented as an opcode replacement.

    Glad to hear you have resolved the interrupt related issues.

  • 0 in reply to AartiG
    Prodigy 190 points

    Hi Aarti,

    Thanks for the update.

    You're suggestions are really helpful for me.

    Thanks,

    Karthick

  • 0 in reply to karthick ph
    Prodigy 120 points 
    Hi,
    I am facing similar such issue. The CCS Version i am using is Version: 4.2.4.00033 and the processor is TMS320F28335.
    I have tried to check it by disabling "Enable CIO function use" in the "Target" Tab of CCS Debug properties.
    Any Guidance/Suggestion/ reference to some documentation is highly appreciated.
    Regards
    Sudheer.