• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 81 subscribers
  • Views 684 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.

CCS/TMS320F28375S: CLA debug: crazy disassembly window

fmdhr
Expert 1450 points
Part Number: TMS320F28375S

Tool/software: Code Composer Studio

Hi,

I have a problem to view my CLA code: as soon as I connect with the CLA, the contents of the disassamly window (and the source code window, and the expressions window) starts to refresh and jump around, so it is impossible to use it.

CCS version is 7.2.0, connection is via a Spectrum Digital XDS560V2 STM TRAVELER Emulator.

Any idea why this happens?

Regards,

Frank

  • 0
    TI__Mastermind 30255 points
    Frank

    Does it happen every time? Do you have auto refresh enabled on those windows? If so, disable it.
    See this behavior when using different emulator?

    Best regards
    Chris
  • 0 in reply to Christopher Chiarella
    Expert 1450 points

    Hi Chris,

    it happens as soon as I once started the CPU. Unfortunately this is necessary to get the CLA code copied to CLA RAM... It happens with the F28377S launchpad / XDS 100v2 too.

    I have no idea how to switch auto refresh off, and I did not found help in CCS, but I found a GEL_RefreshWindows(); function, it seems that it exactly does what I do _not_want (see below). May be it is called from a wrong place in GEL?

    Where is the knob to turn "auto refresh off"?

    Thanks & regards,

    Frank

    CCS Help:

    Forces a refresh of all IDE windows

    Format

    GEL_RefreshWindows();

    Parameters

    None

    Description

    This function causes the Disassembly window, Mixed Mode window, Register window, Memory window and the Watch window to refresh their contents with what is on the target. This can be useful if target memory is changing while the target is halted, such as due to a DMA transfer.

    Synchronous

    Synchronous from GEL: No

    Completely synchronous: No

    Example

    GEL_RefreshWindows

  • 0 in reply to fmdhr
    TI__Mastermind 30255 points

    Frank

    The GELs we setup for the devices from our end don't make use of that GEL function. You have the autorefresh turned off on the individual windows (memory browser, dissassembly, etc? The circled button below is what you should select on each window to turn it off and on for that particular window.

    I don't think it is a GEL issue, but you can also try connecting without a GEL. Open up the target configuration file, go to the advanced tab, and select the C28xx_CPU1, then delete the path to the "initialization script". Save and reconnect.

    Best regards

    Chris

  • 0 in reply to Christopher Chiarella
    Expert 1450 points

    Hi Chris,

    the "continuously refresh" button in the Memory Browser window works as expected. But there's no such button in the Disassembly window...

    Meanwhile I found a way: The windows behave normally if I halt the CLA using a __mdebugstop(); statement. Now I can inspect the generated code (and step through) without any "random" refreshs by the CCS. (I also tried to read the generated .asm files, but they are made to be read by machines.)

    The behaviour when the CLA is connected is different to that when only the CPU is connected: Here, the Disassembly window is static even while the CPU is running. May be the CCS developers want to check and review this in one of the next versions...

    Thanks and regards,

    Frank

  • 0 in reply to fmdhr
    TI__Mastermind 30255 points
    Frank

    Alright great that you found a way to resolve it! Yeah, I'll make note regarding what you observed.

    Best regards
    Chris
  • 0 in reply to Christopher Chiarella
    Expert 1450 points
    Chris,

    it would be great if the disassembly window would work without putting __mdebugstop() into the code, recompile & reload it, and - most difficult - not to forget to remove it again.

    Thanks & Regards
    Frank
  • 0 in reply to fmdhr
    TI__Mastermind 30255 points
    Frank

    Yes, definitely. Unfortunately, we haven't observed such behavior from our end. It is very strange you are seeing it.

    Best regards
    Chris