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/TMS320F240: CCSv3.3 C Source Debug

Part Number: TMS320F240


Tool/software: Code Composer Studio

Hello,

because of the used dsp TMS320F2407A I have to use the CCSv3.3.

I just moved from an old Windows XP VM to a real Windows 7 64 bit PC.
In the old XP VM I use the Spectrum Digital XDS510PP, now I use the Blackhawk USB510L Emulator, because of the 64-bit-OS.

To use the possibility of a flash breakpoint, I use the symbols ANAENBL, HBPENBL, PGABRKP and PGAQUAL.
Today I only can find some information in the file SPU055B, but this document was written for the TMS320C5x.

These symbols work in my old XP VM in a GEL-File:
dialog EnableFlashBreakpoint( ProgAdr "ProgAdr")
{   
    ANAENBL = 0x0001;       /* #0 = 1: enable analysis Module            */
    HBPENBL = 0x0020;        /* #5 = 1: enable program adress            */
    PGABRKP = ProgAdr;        /* new program adress                        */
    PGAQUAL = 0x0002;        /* = 2: Program instruction acquisition    */
}

hotmenu DisableFlashBreakpoint()
{
    ANAENBL = 0x0000;       /* #0 = 0: disable analysis Module            */
    HBPENBL = 0x0000;        /* #5 = 0: disable program adress            */
    PGABRKP = 0x0000;        /* reset program adress                        */
    PGAQUAL = 0x0000;        /* = 0:                                    */
}

But this GEL-file doen't work on my Windows7-PC.
I can display these symbols in the watch window, but they have a fixed value and I cannot change them.

Do I have to install some Scripting tools?

What is wrong?

Gerd

  • Hi Gerd,
    GEL scripting is supported by default. You don't need to install anything else to run your GEL scripts.

    I tried this out on my environment:
    -Windows 7-64
    -CCS v3.3.82.13 (SR12)
    -Blackhawk Driver Release v3.3.300.8
    -Blackhawk USB510L

    I loaded the gel file and added the four registers to the watch window. When I call the GEL functions, I see the four values change. I can also change the values via the watch window.

    Is your issue that when you call the GEL functions, the values do not change and any modification you make to the vales in the watch window do not take?

    Thanks
    ki
  • Hi Ki,

    I have the same environment, but some more Blackhawk driver for the CCS7 for the bigger DSP F2812:
    - Blackhswk Emulation Device Drivers for Windows - v1.13.08.13
    - Blackhswk Emulation Device Drivers for Windows - v1.14.03.03

    I did a reboot of my PC and a power cycle of the Blackhawk hardware.
    After a "connect" and "Load symbol" I can see:
    ANAENBL = 0x0001, HBPENBL = 0x0020, PGABRKP = 0x3E72, PGAQUAL = 0x0002
    These values was perhaps the result from my very first try to set a "breakpoint" last week.
    It is not possible to change these values neither by a GEL call, nor by a manuel change in the watch window.
    Where could be the data storage of the displayed values?

    By the way: How long does it take to start the CCS3 in your configuration?
    On my PC it takes more than 100s.

    Gerd
  • Are you using the default f2407A.gel file in .\cc\gel\f2407A.gel?

    It takes be about 10-15s to start up CCSv3.3 on my Windows 7 PC
  • Hallo Ki,

    I hadn't used the f2407A.gel. But now I loaded this gel-File.

    Another avareness:
    After "Connect", I can see:
    ANAENBL = 0x0000, HBPENBL = 0x0000, PGABRKP = 0x7300, PGAQUAL = 0x0000.
    I am able to change these values. I am able to debug with these registers.
    By the way: How can the CCS display these values? Where is the definition of these addresses.

    After "Load symbols only", I can see:
    ANAENBL = 0x0001, HBPENBL = 0x0020, PGABRKP = 0x3E72, PGAQUAL = 0x0002.
    Now I am not able to change these values any more.

    Gerd

  • Gerd,
    I am not familiar with these registers so I can't provide much more comments on them. I am going to move this thread to the C2000 forum. The experts there are much more familiar with the hardware and can provide more insight.

    Thanks
    ki
  • No ideas?

  • Hi Gerd,

    I discussed this issue with some of the C2000 experts. They were able to point me to the correct document for C2000:

    /cfs-file/__key/communityserver-discussions-components-files/171/SPRU151A.pdf

    However your issue of why you are unable to access these analysis registers on your Windows 7-64 environment was unresolved. It is likely something specific to your environment since I was not able to reproduce it. If you can successfully launch CCS and connect to the target, you should be able to write to those registers like you were able to in your XP environment (assuming the target is not running). With that said, you are using an unsupported configuration as CCSv3 is not supported on Windows 7. I assume you need that functionality available by setting the registers vs just the standard HW/SW breakpoint support you get via the CCS IDE. If that is the case, it would be recommended to stick with your XP VM since that environment is working best for you.

    ki

  • Hello Ki,

    I installed the whole software into a 32-Bit VM Windows 7.

    But I get exactly the same behaviour than on my 64-Bit computer.
    If I start the CCS, I can change all the debug register.
    But after "Load Symbols Only", I cannot change these debug regsiter any more.

    What happens while "Load Synbols Only" or is the problem in the OUT-File, that is loaded?
    Where could be stored the address "0x3E72".
    Both computer (the real and the VM) display this not changable addess, even if I power cycle all hardware.
    Is there any possibiliy to set these registers to read only?

    To stay on the XP-computer is not an option, because I have to switch it off.
    This is an order from the IT department.

    Regards

    Gerd

  • Gerd Seher said:
    What happens while "Load Synbols Only" or is the problem in the OUT-File, that is loaded?

    "Load Symbols Only" would only load the debug symbols to the debugger. It should not affect the target itself. I don't see why it would impact the ability to write to the emulation analysis pseudo-registers that you are trying to use.

    Can you send me the out file? This is the one piece that I didn't try when trying to reproduce your issue.

    Note that I am out of the office next week but I can have some else to reproduce if I don't get the out file in time.

    Thanks

    ki

  • Here is the out file.
    Test.zip

  • Thank you. I can now reproduce the issue. I don't have an explanation as to why. I will see if the engineers here can take a look. However, please note that since this configuration is unsupported and the CCS version itself is completely unsupported, I can't make any promises on when any potential resolution (if possible) can occur.

    Thanks
    ki
  • Dear Ki,

    I send you the PRJ and the CMD file.
    Perhpas these files will help your engineers.

    Os.zip

    Thanks

    Gerd

  • Are there any new ideas?

    Thanks

    Gerd