• Locked Locked
  • Replies 4 replies
  • Subscribers 56 subscribers
  • Views 3435 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.

CCS 5.2.1: Load Program fail: ARM9: Trouble Setting Breakpoint with the Action "Process CIO

Harikrushna Sheth
Prodigy 210 points

Other Parts Discussed in Thread: TM4C129XNCZAD

Hi,

I am trying to burn UBL for Davinci DM368 based IP camera from Appro(DM368IPNC-MT5) using CCS 5.2.1. I am using gel file (gel_ ipnc_dm36x_1.0.0.gel), provided from Appro. (Userguide recommend CCS version 3.3 )

I have setup "target configuration" and successfully connected with target but when I load any program I found following error messages regarding breakpoints. I do not have single breakpoint in my code. Please help me to resolve this issue.

 -------------------------------------------

ARM9: Breakpoint Manager: Retrying with a AET breakpoint

ARM9: Trouble Setting Breakpoint with the Action "Process CIO" at 0x8e0097f0: Error 0x00000008/-1066 Error during: Break Point,  Cannot set/verify breakpoint at 0x8E0097F0  

ARM9: Breakpoint Manager: Retrying with a AET breakpoint

ARM9: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x8e009c18: Error 0x00000008/-1066 Error during: Break Point,  Cannot set/verify breakpoint at 0x8E009C18  

ARM9: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x8e004604: Error 0x00000008/-1066 Error during: Break Point,  Cannot set/verify breakpoint at 0x8E004604  

-------------------------------------------

following are the screenshots for the same.

Regards,

--HK

  • TI__Guru**** 171519 points

    Hi,

    I got a similar scenario when I tried to load code that had some memory regions misconfigured, which overran some configuration registers. If that is your case, can you try to load a simple hello world code for the DM365 using the project wizard? You can find details in the section Creating projects of the CCSv5 Getting Started Guide.

    Also, ARM9 platforms are known to require the use of adaptive clocking for reliable operation. In this case it is possible that you will need an emulator with this capability (XDS100, XDS560) or severely reduce the speed of the JTAG clock. Additional details about this can be found here.

    Hope this helps,

    Rafael

  • in reply to desouza
    Prodigy 80 points

     got a similar scenario ,I do not kenow how to fix it

  • in reply to zhou taiyun
    Prodigy 10 points

    Me, too. I have no idea what the problem is. My system was "working" for a while, then I started getting this issue suddenly. I'm stumped.

  • in reply to Brian Moon1
    Expert 1015 points

    I ran into this issue debugging on a TIVA launchpad.  I was playing around with locking flash sectors and changed a line in my gel file from:

    GEL_MapAddStr(0x00000000, 0, 0x00100000, "R", 0);  /* Flash */

    to

    GEL_MapAddStr(0x00000000, 0, 0x00100000, "R|W", 0);  /* Flash */.

    That caused the problem for me and when I changed back to the default tm4c129xnczad.gel, the problem went away.  

    Yan