• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 82 subscribers
  • Views 585 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 breakpoint issue

NAGESH RK
Expert 2260 points

Part Number: TMS320F28388D

Tool/software: Code Composer Studio

hello,

I am using CCS Version: 10.1.0.00010, but unfortunately, when I give for a continuous run from CCS on the TMS320F28388D controller it randomly halts at a random location (like a breakpoint)  without even me giving any breakpoint in the controller why is this only CCS issue?. This happens most of the times and not every time

I would like to know if I load the Debug executable on the controller and disconnect from CCS will the controller come to halt at any random location.

thanks,

Nagesh

  • 0
    TI__Genius 11645 points

    Can you pls help us with the opcode/instr available through disassembly window when the code halts ?

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    TI__Guru** 116261 points

    Hi Nagesh,

    Please refer this post and see if solution provided here solves issue you are facing.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2260 points

    Hi Vivek, 

    The post did not fix my issue, as it was something different.

    I am attaching the screenshots of the issue I have faced again while debugging where it abruptly halted at a location without having a breakpoint.

    Please see the screenshots 1st screenshot does not have a breakpoint, 2nd screenshot disassembly window.

    I have attached another log obtained  by executing the command in the scripting console "eval("DEBUG_DumpBreakpoints()")"Unexpected_Brekpoint.docx

    Fullscreen Console_Log_BreakPoint.txt Download 
    C28xx_CPU1: Breakpoint Manager Dump: Total Allocated Logical Breakpoints: 82

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

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: 4

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$$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: 		Type: Breakpoint

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

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

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

    thanks,

    Nagesh

  • 0 in reply to NAGESH RK
    TI__Genius 11645 points

    On reading through this a little more, I wanted to clarify a few items.

    1. You are executing code out of Flash right ?

    2. While the code is executing, you are seeing the execution getting halted randomly ?

    From your attachments I see its stopped in a location which its not intended to (Also I see core is suspended by a HW Breakpoint)

    These are more questions to you at this point, so that I can understand what you have mentioned better.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Expert 2260 points

    Hi Karthik, 

    1. You are executing code out of Flash right? Ans: Yes.

    2.  While the code is executing, you are seeing the execution getting halted randomly? Yes.

    The executable I used was a Debug configuration. is there a possibility for the controller to halt even when CCS is not connected?

    thanks,

    Nagesh

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

    Nagesh,

    On below -

     I would like to know if I load the Debug executable on the controller and disconnect from CCS will the controller come to halt at any random location.

     


    If you are not connected to CCS then there is no halt feature so CPU will not halt. Can you check if it is stopping in BOOTROM which as ESTOP instruction ?

    Regards,

    Vivek Singh

  • 0 in reply to NAGESH RK
    TI__Genius 11645 points

    Thanks for confirming the same.

    How did you identify that the CPU halted when CCS was disconnected (are you observing any outputs which stops to confirm) ?

    or

    You are attempting to connect the target which is already running out of flash via CCS and target gets halted at that moment ?

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    TI__Genius 11645 points

    We are closing this thread since there is no response.

    Please create a new thread if you still have any questions.