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.

memory address watchpoint

I have been setting various watchpoints.  As far as I can tell the app should break when it hits one of those points.  But it never breaks.  This despite messages from the simulator that the address in the watchpoint has been read or written. Any idea why this is not working for me?

  • Kurt,

    Which simulator are you using? Can you provide more information on where/how you are setting the watchpoints? Are they on local or global variables?

    If they are on local variables, double-check the address of the variable in the CCS locals view to make sure it matches up with the address where the watchpoint is set.  I tried some tests with a couple of different simulators and it did halt at the expected points, so any additional details you can provide will be appreciated.

  • c6747

    while running my program I am getting messages I am is accessing memory outside the linked range.  in one case my program was reading memory at address 0x0, 0x4, 0x8, etc. so I set a watchpoint at address 0x0, 0x20, 0x40, etc and made sure it was set to break.  On running the program again, I again see messages saying my program is reading 0x0, 0x4, 0x8, etc. but the watchpoint is never triggered.

    right now the only way I can find the problem is to break on some code then step lines and functions until I get a message

  • any more ideas out there?  I have had this question on E2E more or less for a month with no solution.  found nothing on the wiki.  found nothing searching the web. found nothiung searching E2E.  found nothing reading help.

    for whatever reason I cannot get a watchpoint to break either by accident or on purpose.

  • Are you able to share your project or at least the .out file so we can try to reproduce the issue? If so, also let us know at which addresses you are trying to set watchpoints.

  • yes, I can share the .out file But...when I try to attach the file I get a message saying "File Type Not Valid.  This type of file is not allowed. "

    lately I have getting messages about read access at address 0xe387bb00

     

  • Kurt Jensen said:

    yes, I can share the .out file But...when I try to attach the file I get a message saying "File Type Not Valid.  This type of file is not allowed. "

    Can you try zipping up the .out file and attaching the .zip file?

  • ok.  back again. sorry this took so long, I do not always see this problem but when I do I am completelyt blocked.

    when I ruun this program I get 3 READ access messages at address 0xe3a95bf0.  if i set a watch point the program never breaks.

    4578.UnitTests.zip

  • Kurt,

    Thanks for providing the requested .out file. I loaded the file on to a C6747 Device Cycle Accurate Simulator in CCS 4.2.4 and when I ran the code, I saw the message:

    TMS320C64X+_0: Warning: C674x_or_EDMA: READ access - 0xe3a1f7e0

    I then restarted the program (menu Target->Restart), set a watchpoint at this address, and set it to halt for all accesses. This time when I run the program, I halt at the instruction shown in the screenshot, which appears correct. The instruction LDW.D2T2  *B5[0], B6 is accessing this memory as B5 contains 0xE3A1F7E0 at this point.

    Do you not see similar behavior?

  • that is my problem...

    after I set a watchpoint at this address, and set it to halt for all accesses, it does not halt

  • Are you using the same version of CCS and simulator configuration as I - (ie) CCS 4.2.4 and C6747 Device Cycle Accurate Simulator?

  • I'm not sure how to proceed with this since I am able to get the simulator to halt at the set watchpoint properly. I'll check with the simulation team to see if they've seen such issues or have additional comments.

  • Yes, we know it works for you.  And not for me.  That is exactly why I wrote this post.

  • Kurt,

    Can you provide the following information.

    1. Which CCS version are you using? Information from Help-->about in CCS.

    2. Which platform? Windows Xp, Linux etc.

    3. Which exact simulator configuration? The name as displayed in Target configuration pane.

    Just wanted to be sure we are on the same page while trying to reproduce the problem locally. This also helps in identifying the exact simulator version.

    regards,
    Sheshadri

     

     

  • 1) v4.2.4.0003

    2) XP

    3) sim6748.ccxml