• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 54 subscribers
  • Views 3434 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CCS/CC2642R: Attach to running target (CC26XX) for debugging?

CCS/TMS320F28379S: View registers in Code Composer Studio

Steven Peters
Prodigy 90 points
Part Number: TMS320F28379S

Tool/software: Code Composer Studio

Hi,

I would like to read out the registers of a running target (TMS320F28379S) in CCSv7 using the Registers view. However, when I connect to the target many of the registers display the value 0x00000000. I know for sure that these values should be different. One of the registers that is not displayed as all zeros is the program counter. The value of the program counter is changing so I know the target is indeed running. The Dual Code Security Module is not set up at this stage, so the target is unlocked.

Whenever I load the program via CCS (using an XDS100 emulator), the right values are actually displayed in the Registers view. But this is not what I want. I would like to see the registers of a target that is already running without having to progam it again.

My guess is that I am overlooking something, so could someone point me in the right direction?

Kind regards,

Steven.

  • 0
    TI__Guru**** 450031 points
    Hi Steven,
    What is the exact version of CCSv7 you are using? Given your statements, it sounds like you are connecting (non-intrusively) to a running target while in real-time mode. Correct?

    Can you send a screenshot of the Core registers you see in the registers view?
    Thanks
    ki
  • 0 in reply to Ki
    Prodigy 90 points

    Hi Ki-Soo Lee,

    The version of CCS I’m using is: 7.4.0.00015.

    I tried connecting both in stop mode as in real-time mode. For real-time mode, I first cleared the DBGM bit of the ST1 register. I disabled the “halt the target on a connect” option and then enabled the Silicon Real-Time Mode (Polite). In the Registers view, I enabled the Continuous Refresh button. Is this the right approach?

    Also, for my application it is not necessary that time-critical interrupts are serviced during debugging. It also does not matter if the application is halted during debugging. I just would like to read out some registers (after initialization) without needing to load the application first. The value of the registers of interest does not change after initialization. This initialization is done in the beginning of the code, so if I halt the target after this I should read out the correct values. Should I use the real-time mode in this case?

    Attached you can find a screenshot of the Core Registers of the target which was already programmed and is simply connected to CCS. So the code was not loaded right before taking this screenshot.

    Kind regards,

    Steven.

  • 0 in reply to Steven Peters
    TI__Guru**** 450031 points

    Hi Steven,

    Sorry for the delay in response

    Steven Peters said:
    Also, for my application it is not necessary that time-critical interrupts are serviced during debugging. It also does not matter if the application is halted during debugging.

    Ah ok, then you are not trying to connect to a running target (and real-time mode is not needed).

    Steven Peters said:
    Attached you can find a screenshot of the Core Registers of the target which was already programmed and is simply connected to CCS. So the code was not loaded right before taking this screenshot.

    Thank you for the screenshot. I do not have enough knowledge on the device to confirm one way or another regarding the values of the registers. I will bring this thread to the attention of the C2000 device experts.

    Thanks

    ki

  • 0 in reply to Steven Peters
    TI__Guru 53135 points
    So you're saying that the values in the core registers (except PC) aren't changing even though you're executing code that is definitely writing to them? Even when you single step through code? Is this just affecting the core registers or do the peripheral registers display incorrectly as well?

    Can you go to Help->Installation Details in CCS and tell me what version of C2000 Device Support you have?

    Thanks,
    Whitney
  • 0 in reply to Whitney Dewey
    Prodigy 90 points

    Hi Whitney,

    I will give a little bit more context as I’m not sure that my previous post was clear.

    I have an application which uses TI-RTOS. One of the first things that is done in the code, is the initialization of the peripherals. This is done before the function ‘BIOS_start()’ is executed.

    For example, the EMIF is configured as follows (only three registers shown to illustrate):

    Emif1Regs_RCSR: 0x40000205
    Emif1Regs_ASYNC_WCCR: 0xF0000080
    Emif1Regs_SDRAM_CR: 0x00000620

     

    The value of these peripheral registers is not altered once the OS is started (this is BIOS_start() being executed).

    When I program the target and read out the registers using View->Registers, I correctly see the above values.

    However when I disconnect the target and re-connect it, then View-Registers shows:

    Emif1Regs_RCSR: 0x00000000
    Emif1Regs_ASYNC_WCCR: 0x00000000
    Emif1Regs_SDRAM_CR: 0x00000000

     

    So my question is, how can I read out the registers without having to program the target again?

    The version of C2000 Device Support I have is: 4.2.2.0

     

    Kind regards,

    Steven

  • 0 in reply to Steven Peters
    TI__Guru**** 450031 points

    Hi Steven,

    Steven Peters said:

    However when I disconnect the target and re-connect it, then View-Registers shows:

    Emif1Regs_RCSR: 0x00000000
    Emif1Regs_ASYNC_WCCR: 0x00000000
    Emif1Regs_SDRAM_CR: 0x00000000

    If you are using the default f28379s.gel startup GEL file, then this can be explained by the fact that the OnTargetConnect GEL callback function defined in the GEL function (which will get called when you connect to the target) has an action to reset the CPU (line 101). It is the CPU reset that is clearing the register values.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 90 points
    Hi Ki,

    Thanks for the help. I now commented out the call to GEL_Reset().

    Is it possible to see the internals (I mean the definition) of these GEL builtin functions, to see what is going on under the hood?


    Kind regards,
    Steven.
  • 0 in reply to Steven Peters
    TI__Guru**** 450031 points
    The documentation for all the build-in GEL functions are in the CCS Help.

    Regarding the GEL_Reset() in the GEL file, I'm sure the C2000 team added that call for a reason. Hence there may be other issues you run into if that call is simply removed. I will let the C2000 experts comment on that.

    Thanks
    ki