• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 3096 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/AM5728: Debug Console "not working after System Reset.

Anders Viken
Intellectual 740 points
Part Number: AM5728

Tool/software: Code Composer Studio

Hello.

I have an issue when working in CCS 7.2.0.00013 with my AM572 Board.

When launching the target configuration, connecting to the board and loading my program, the console is printing and showing errors as it should. After a while, I perform a System Reset, connect to the board again, and reload my program. After reloading, the console is not working (it is not printing, nor is it showing error messages from my program).

When launching the target configuration again, the console seems to be working fine, but I was hoping to find an easier approach, as I sometimes forget to relaunch the target configuration and then miss important information during testing.

Thanks for your help and suggestions.

Anders.

  • 0
    Intellectual 740 points
    Further information:

    I am using the part Blackhawk USB560v2 System Trace for debugging.
  • 0 in reply to Anders Viken
    TI__Guru**** 171044 points
    Anders,

    Interesting; you are not the first to report this issue somewhat recently. At the second run (when CIO is not working), what do you see when you open the Scripting Console View (menu View --> Scripting Console) and issue the following command:

    eval("DEBUG_DumpBreakpoints()");

    This should output a lot of information on the console view. With code loaded properly and halted at main(), you should be able to see at least one breakpoint enabled: either C$$IO$$ (if your code uses the TI compiler) or SVC_Handler (if using GCC).

    If the breakpoint is activated but there is no output, I suspect a bug exists.

    In the meantime, I will try to reproduce the issue here.

    I apologize for the inconvenience,
    Rafael
  • 0 in reply to desouza
    Intellectual 740 points
    Hello Rafael,

    Thank you for your quick response.

    Here is the output from eval("DEBUG_DumpBreakpoints()"); at the first run.
    CortexA15_0: Breakpoint Manager Dump: Total Allocated Logical Breakpoints: 76
    CortexA15_0: Breakpoint Manager Dump: Total Allocated Software Physical Breakpoints: 90
    CortexA15_0: Breakpoint Manager Dump: Total Allocated Legacy Hardware Physical Breakpoints: 0
    CortexA15_0: Breakpoint Manager Dump: Total Allocated 55 Hardware Physical Breakpoints: 0
    CortexA15_0: Breakpoint Manager Dump: Total Allocated Thread Physical Breakpoints: 0
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Enabled: 2
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "C$$EXIT" (0x801a190c)
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Terminate Program Execution
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "SVC_Handler" (0x80168434)
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Semi hosting
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Disabled: 3
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "C$$EXITE"
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Terminate Program Execution
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "C$$IOE$$"
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Process CIO
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "C$$IO$$"
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Process CIO
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system



    Here is the output from eval("DEBUG_DumpBreakpoints()"); at the second run.
    CortexA15_0: Breakpoint Manager Dump: Total Allocated Logical Breakpoints: 76
    CortexA15_0: Breakpoint Manager Dump: Total Allocated Software Physical Breakpoints: 90
    CortexA15_0: Breakpoint Manager Dump: Total Allocated Legacy Hardware Physical Breakpoints: 0
    CortexA15_0: Breakpoint Manager Dump: Total Allocated 55 Hardware Physical Breakpoints: 0
    CortexA15_0: Breakpoint Manager Dump: Total Allocated Thread Physical Breakpoints: 0
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Enabled: 1
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "C$$EXIT" (0x801a190c)
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Terminate Program Execution
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Disabled: 4
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "C$$EXITE"
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Terminate Program Execution
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "SVC_Handler" (0x80168434)
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Semi hosting
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "C$$IOE$$"
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Process CIO
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system
    CortexA15_0: Breakpoint Manager Dump:
    CortexA15_0: Breakpoint Manager Dump: Hardware Configuration
    CortexA15_0: Breakpoint Manager Dump: Location: "C$$IO$$"
    CortexA15_0: Breakpoint Manager Dump: Debugger Response
    CortexA15_0: Breakpoint Manager Dump: Condition:
    CortexA15_0: Breakpoint Manager Dump: Skip Count: 0
    CortexA15_0: Breakpoint Manager Dump: Current Count: 0
    CortexA15_0: Breakpoint Manager Dump: Action: Process CIO
    CortexA15_0: Breakpoint Manager Dump: Miscellaneous
    CortexA15_0: Breakpoint Manager Dump: Group: Default Group
    CortexA15_0: Breakpoint Manager Dump: Name:
    CortexA15_0: Breakpoint Manager Dump: Breakpoint set by the system

    The difference between the two outputs seems to be that SVC_Handler breakpoint is disabled at the second run (correct me if i am wrong).

    I have ticked off "Enable Semihosting (requires setting a breakpoint at SVC_Handler )" in the Program/Memory Load Options (CortexA15).

    Anders.
  • 0 in reply to Anders Viken
    TI__Guru**** 171044 points
    Anders,

    I was able to reproduce this on GCC generated code - using the TI compiler does not seem to throw this issue.

    I will file a bug report later today, but unfortunately at this point there is no workaround that could get to the point of being able to make the Console I/O to properly operate after a core reset.

    I apologize for the inconvenience,
    Rafael
  • 0 in reply to desouza
    TI__Guru**** 171044 points

    Anders,

    I just tried CCSv7.3 but couldn't reproduce this on my AM571x board. I need to borrow a "real" AM572x board and retry - my AM572x board uses pre-release Silicon and it may influence the outcome. 

    Please check the procedure in the short clip below - perhaps you notice something different that I may not be doing exactly as you. 

    (apologize for the delays; my computer is acting up today)

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 740 points

    Rafael,

    Hello, and thanks for helping me out.

    I noticed from watching your video that after you click "System Reset", you click the pause button, and then get the message "Cortexa15_0: GEL Output: Core Reset has occured."

    However, when I click "System Reset", i get an error message in the console.
    This is the message: "CortexA15_0: JTAG Communication Error: (Error -1044@ 0x3458) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.48.0) ".
    (I just assumed that I was supposed to get a JTAG communication error message when performing a system reset).

    You can see my procedure in the video below.

    Thanks again for your support.

    Anders.

  • 0 in reply to Anders Viken
    Intellectual 740 points
    Do you have any more insight to what I could try to fix this issue?

    The other developers on my team are all getting the same error message "CortexA15_0: JTAG Communication Error: (Error -1044@ 0x3458) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 7.0.48.0) ".
    Thanks again for your assistance.
  • 0 in reply to Anders Viken
    TI__Guru**** 171044 points
    Anders,

    Please apologize for the delay; I was out in a travel.

    The Error message you are seeing is most probably due to the fact the System Reset actually resets the PMIC of the board, thus completely collapsing the JTAG communications (as the device and the entire board gets powered cycled). That should be expected for this board/device.

    Despite this, I can see the CIO issue between resets, which is not expected. I will file a bug number for this.

    Unfortunately at this time there are no workarounds other than restarting the debug session. Sorry.

    I apologize for the inconvenience,
    Rafael