• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 83 subscribers
  • Views 288 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/TMS320F28388D: CCS Version: 10.1.0.00010

NAGESH RK
Expert 2260 points
Part Number: TMS320F28388D


Tool/software: Code Composer Studio

hello,

I am using CCS  Version: 10.1.0.00010 .

I finding a strange behavior when i use breakpoints for debugging purpose, and after clearing the breakpoints i do not see the previous breakpoints clearing up, my software when executed for continuous execution the old break points still exists

how to remove the previous breakpoints.

thanks,

Nagesh  

  • 0
    TI__Guru** 115521 points

    Hi Nagesh,

    Are you clearing these breakpoint from breakpoint window or clearing them individually? Also are these hardware breakpoint or software breakpoint ? Do you see this issue only in CCS10 and it works fine in CCS9 ?

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2260 points

    hi Vivek, 

    i tried clearing by both ways, clearing by breakpoint  induvidually and from window.

    Yes it was fine in CCS Ver 9 as i did not face this situation.

    I have set Hardware Breakpoint.

    thanks,

    Nagesh

  • 0 in reply to NAGESH RK
    TI__Guru**** 468021 points

    Hi Nagesh,

    Can you make sure the Breakpoints view is clear and then run the following command from the Scripting Console:

    eval("DEBUG_DumpBreakpoints()")

    And then copy and paste the output in the Debug Console to a text file and attach the file to this thread.

    Thanks

    ki

  • 0 in reply to Ki
    Expert 2260 points

    hi Ki,

    I did as per your instructions, everytime i execute the output of above command is '0' either i select the breakpoints or not. below is the screen shot what i observed.

    thanks,

    Nagesh

  • 0 in reply to NAGESH RK
    TI__Guru**** 468021 points

    NAGESH RK said:
    I did as per your instructions, everytime i execute the output of above command is '0'

    That would be the output of the Scripting Console. What I am interested in is the output in the Debug Console.

  • 0 in reply to Ki
    Expert 2260 points

    Hi Ki, 

    I have attached the data of debug console with 2 files names with the command executed .

    1. Breakpoint enabled - debug console data

    Fullscreen breakpoints_Enabled_F28388D.txt Download 
    C28xx_CPU1: GEL Output: 
Memory Map Initialization Complete
C28xx_CPU1: GEL Output: 
... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: 
... DCSM Initialization Done ...
C28xx_CPU1: GEL Output: 
 CPU2 is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CPU2 to reach wait boot loop.)
C28xx_CPU1: GEL Output: 
 CM is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CM to reach wait boot loop.)
C28xx_CPU1: GEL Output: 
... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: 
... DCSM Initialization Done ...
C28xx_CPU1: GEL Output: 
 CPU2 is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CPU2 to reach wait boot loop.)
C28xx_CPU1: GEL Output: 
 CM is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CM to reach wait boot loop.)
C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. User code execution from SR could commence after both flash banks are programmed.
C28xx_CPU1: Only CPU1 on-chip Flash Plugin can configure clock for CPU1, CPU2 and CM Flash operations. Plugin automatically configures PLL when CPU1 Flash operations are invoked. However, if users want to do only CPU2 or CM Flash operations without doing a prior CPU1 operation in the current session, they should click on 'Configure Clock' button in CPU1's on-chip Flash Plugin before invoking CPU2 and CM Flash operations. When this button is used, Flash Plugin will configure the clock for CPU1/CPU2 at 190MHz and CM at 95MHz using INTOSC2 as the clock source. Plugin will leave PLL config like this and user application should configure the PLL as required by application.
C28xx_CPU1: GEL Output: 
... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: 
... DCSM Initialization Done ...
C28xx_CPU1: GEL Output: 
 CPU2 is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CPU2 to reach wait boot loop.)
C28xx_CPU1: GEL Output: 
 CM is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CM to reach wait boot loop.)
C28xx_CPU1: GEL Output: 
... DCSM Initialization Start ... 
C28xx_CPU1: GEL Output: 
... DCSM Initialization Done ...
C28xx_CPU1: GEL Output: 
 CPU2 is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CPU2 to reach wait boot loop.)
C28xx_CPU1: GEL Output: 
 CM is out of reset and configured to wait boot.
 (If you connected previously, may have to resume CM to reach wait boot loop.)
C28xx_CPU1: Breakpoint Manager Dump: Total Allocated Logical Breakpoints: 65

C28xx_CPU1: Breakpoint Manager Dump: Total Allocated Software Physical Breakpoints: 58

C28xx_CPU1: Breakpoint Manager Dump: Total Allocated Legacy Hardware Physical Breakpoints: 0

C28xx_CPU1: Breakpoint Manager Dump: Total Allocated 55 Hardware Physical Breakpoints: 0

C28xx_CPU1: Breakpoint Manager Dump: Total Allocated Thread Physical Breakpoints: 0

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: Enabled: 2

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Type: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 			Location: C:\Users\E537053\F28388D\GBL_V2_F28388D\Debug/../main.c, line 126 ("C:\Users\E537053\F28388D\GBL_V2_F28388D\Debug\GBL_V2_F28388D.out") (0x80b1a)

C28xx_CPU1: Breakpoint Manager Dump: 			Location Mask: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Compare Mode: None

C28xx_CPU1: Breakpoint Manager Dump: 			Action Type: 

C28xx_CPU1: Breakpoint Manager Dump: 				Halt CPU: true

C28xx_CPU1: Breakpoint Manager Dump: 				Drive EMU Pin: false

C28xx_CPU1: Breakpoint Manager Dump: 				RTOS Interrupt: false

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Remain Halted

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the user

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Type: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 			Location: C:\Users\E537053\F28388D\GBL_V2_F28388D\Debug/../main.c, line 231 ("C:\Users\E537053\F28388D\GBL_V2_F28388D\Debug\GBL_V2_F28388D.out") (0x80b79)

C28xx_CPU1: Breakpoint Manager Dump: 			Location Mask: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Compare Mode: None

C28xx_CPU1: Breakpoint Manager Dump: 			Action Type: 

C28xx_CPU1: Breakpoint Manager Dump: 				Halt CPU: true

C28xx_CPU1: Breakpoint Manager Dump: 				Drive EMU Pin: false

C28xx_CPU1: Breakpoint Manager Dump: 				RTOS Interrupt: false

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Remain Halted

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the user

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: Disabled: 4

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Location: "C$$IO$$"

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Process CIO

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: 

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the system

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Location: "C$$IOE$$"

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Process CIO

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: 

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the system

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Location: "C$$EXITE"

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Terminate Program Execution

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: 

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the system

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Type: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 			Location: "C$$EXIT" (0x820d6)

C28xx_CPU1: Breakpoint Manager Dump: 			Location Mask: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Compare Mode: None

C28xx_CPU1: Breakpoint Manager Dump: 			Action Type: 

C28xx_CPU1: Breakpoint Manager Dump: 				Halt CPU: true

C28xx_CPU1: Breakpoint Manager Dump: 				Drive EMU Pin: false

C28xx_CPU1: Breakpoint Manager Dump: 				RTOS Interrupt: false

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Terminate Program Execution

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: 

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the system

    2. Breakpoint disabled - debug console data still the code halts at same old breakpoint which was disabled.

    Fullscreen breakpoints_disabled_F28388D.txt Download 
    C28xx_CPU1: Breakpoint Manager Dump: Total Allocated Logical Breakpoints: 65

C28xx_CPU1: Breakpoint Manager Dump: Total Allocated Software Physical Breakpoints: 58

C28xx_CPU1: Breakpoint Manager Dump: Total Allocated Legacy Hardware Physical Breakpoints: 0

C28xx_CPU1: Breakpoint Manager Dump: Total Allocated 55 Hardware Physical Breakpoints: 0

C28xx_CPU1: Breakpoint Manager Dump: Total Allocated Thread Physical Breakpoints: 0

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: Enabled: 0

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: Disabled: 6

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Type: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 			Location: C:\Users\E537053\F28388D\GBL_V2_F28388D\Debug/../main.c, line 126 ("C:\Users\E537053\F28388D\GBL_V2_F28388D\Debug\GBL_V2_F28388D.out") (0x80b1a)

C28xx_CPU1: Breakpoint Manager Dump: 			Location Mask: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Compare Mode: None

C28xx_CPU1: Breakpoint Manager Dump: 			Action Type: 

C28xx_CPU1: Breakpoint Manager Dump: 				Halt CPU: true

C28xx_CPU1: Breakpoint Manager Dump: 				Drive EMU Pin: false

C28xx_CPU1: Breakpoint Manager Dump: 				RTOS Interrupt: false

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Remain Halted

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the user

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Location: "C$$IO$$"

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Process CIO

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: 

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the system

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Location: "C$$IOE$$"

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Process CIO

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: 

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the system

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Location: "C$$EXITE"

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Terminate Program Execution

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: 

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the system

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Type: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 			Location: C:\Users\E537053\F28388D\GBL_V2_F28388D\Debug/../main.c, line 231 ("C:\Users\E537053\F28388D\GBL_V2_F28388D\Debug\GBL_V2_F28388D.out") (0x80b79)

C28xx_CPU1: Breakpoint Manager Dump: 			Location Mask: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Compare Mode: None

C28xx_CPU1: Breakpoint Manager Dump: 			Action Type: 

C28xx_CPU1: Breakpoint Manager Dump: 				Halt CPU: true

C28xx_CPU1: Breakpoint Manager Dump: 				Drive EMU Pin: false

C28xx_CPU1: Breakpoint Manager Dump: 				RTOS Interrupt: false

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Remain Halted

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the user

C28xx_CPU1: Breakpoint Manager Dump: 

C28xx_CPU1: Breakpoint Manager Dump: 	Hardware Configuration

C28xx_CPU1: Breakpoint Manager Dump: 		Type: Breakpoint

C28xx_CPU1: Breakpoint Manager Dump: 			Location: "C$$EXIT" (0x820d6)

C28xx_CPU1: Breakpoint Manager Dump: 			Location Mask: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Compare Mode: None

C28xx_CPU1: Breakpoint Manager Dump: 			Action Type: 

C28xx_CPU1: Breakpoint Manager Dump: 				Halt CPU: true

C28xx_CPU1: Breakpoint Manager Dump: 				Drive EMU Pin: false

C28xx_CPU1: Breakpoint Manager Dump: 				RTOS Interrupt: false

C28xx_CPU1: Breakpoint Manager Dump: 	Debugger Response

C28xx_CPU1: Breakpoint Manager Dump: 		Condition: 

C28xx_CPU1: Breakpoint Manager Dump: 		Skip Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 			Current Count: 0

C28xx_CPU1: Breakpoint Manager Dump: 		Action: Terminate Program Execution

C28xx_CPU1: Breakpoint Manager Dump: 	Miscellaneous

C28xx_CPU1: Breakpoint Manager Dump: 		Group: Default Group

C28xx_CPU1: Breakpoint Manager Dump: 		Name: 

C28xx_CPU1: Breakpoint Manager Dump: 	Breakpoint set by the system

  • 0 in reply to NAGESH RK
    TI__Guru**** 468021 points

    Thanks. 

    NAGESH RK said:

    2. Breakpoint disabled - debug console data still the code halts at same old breakpoint which was disabled.

    breakpoints_disabled_F28388D.txt

    I can see that the breakpoints are indeed disabled. Can you try completely removing the breakpoints instead of disabling them?