CCS5.1 Persistent Installation Warnings

Hi John,

I do not see the version you reference on our download site, however, assuming no typos, the first thing I would say is to please download the latest version of CCS v5.1 from the Wiki.  (5.1 M5 Version 5.1.0.05)

http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5

Please give this a try and keep me informed.   

Cheers,
LIsa

Hello again John,

I just wanted to do a double check that you have made better progress with the latest version.   Also note that (same link) there is now a newer version of CCS 5.1 - M6 you can check and try.

Best Regards,

Lisa

Hi John,

this is a bit odd.  There have been a few hickups with the 5.1 lite installer, not the dvd image version.

My only ideas at the moment are the following

- check if there is some resource/program type conflict.   Ie are you able to tell whether there is a certain program you have installed that is conflicting with/triggering the crashes with CCS use?

- uninstall CCS

- before and or after do a defragment and chkdsk to scan your harddrive.  It could be something is on a bad cluster?

- once you have done the above do the image install of 4.2.3 ... latest production release

Please keep me posted!

Regards,

Lisa

Hi Lisa,

CCS Crashes continue, it seems.  Here is what I did (project code has had no changes since it was (once) working):

1. Full (12 hour) chkdsk, defrag (both my disks)

2. deinstall V4.2.3

3. Reinstall into a new directory CCS v4.2.3 from the 1.1GB download image called "setup_CCS_4_Platinum.zip" whcih I received on July 3.

4. Import existing CCS Project (Copy project into new workspace)

5. Clean project - Build project.  no build errors reported except the ubiquitous error: (My config has a different file)

     CORTEX_M3_0: GEL: Error loading file 'D:\Data\Code Composer Data\Gel Files\CortexM3_util.gel': unable to open GEL file 'D:\Data\Code Composer Data\Gel Files\CortexM3_util.gel'

5a. Power up target, connect JTAG to USB on computer.  Note: Target can be seen to start running its program in Flash.

6. Debug target (3M2793) board using JTAG debugger, which stops target program running and loads the newly created .out file to target.

7. single-step, single-step (looks ok)

8. run

9. Pause debugger.   Program was hung at location fffffff8.

10. Terminate debug

11. Close CCS program

12. Open CCS program

13. Link up to target board as before, which loads the (same) program to target

14. Run debugger.

15. Pause debugger, Program was hung (same as above).

16. Press "Terminate debugger" button (same red square icon in UI)

17. Crash.  Windows says one minute to reboot...

---------

So ... Your suggestion?

Thanks and best regards,

jb

Hi John,

could you try creating a new project instead of importing?  Please let me know how that goes.  What is happening when your debug session 'hangs'?  Instruction, problem, etc .....

Best Regards,
Lisa

Lisa,

Following your instructions:

1. Created new project, copying all settings as well as I could, one by one, from the old to a new.

2. Project Clean, Build.  NO errors. 

3. Enter Debug.  .out loaded automatically.

4. Messages:

CORTEX_M3_0: GEL: Error loading file 'D:\Data\Code Composer Data\Gel Files\CortexM3_util.gel': unable to open GEL file 'D:\Data\Code Composer Data\Gel Files\CortexM3_util.gel'
CORTEX_M3_0: GEL Output:
Memory Map Initialization Complete
CORTEX_M3_0: GEL Output: Watchdog Timer Enabled
CORTEX_M3_0: GEL Output: UARTs Enabled

(note: I had to modify GEL file, see attached, to accomodate the 0x1000 start of the C3 version).

49a [Debug] - Stellaris In-Circuit Debug Interface_0/CORTEX_M3_0 [Project Debug Session]   
    Device   
        Thread [main] (Suspended)   
            0 main() at lights.c:1473 0x00003294   
            1 _args_main() at args_main.c:55 0x0000413a   
    Stellaris In-Circuit Debug Interface_0/CORTEX_M3_0 (2:17:17 PM)   
    Stellaris In-Circuit Debug Interface_0/CORTEX_M3_0: CIO (2:17:17 PM)   

5. Debug Run, 100mS, Debug Pause. 

6. Stack now reflects the Hang state:

/* lm3s2793a.gel
 *
 * Revisions:
 *  Jul-01-2009 1st revision
 *
 * This is part of revision 6738 of the Stellaris Peripheral Driver Library.
 *
 */

menuitem "StartUp"

hotmenu StartUp()
{
    /* Load the CortexM3_util.gel file */
    GEL_LoadGel("$(GEL_file_dir)/CortexM3_util.gel");

    GEL_MapOff();
    GEL_MapReset();
    GEL_MapOn();
    memorymap_init();
}

OnTargetConnect()
{
    watchdog_enable();
    uart_enable();
}

memorymap_init()
{
    /*
     * Syntax for GEL_MapAddStr.
     * GEL_MapAddStr(address, page, length, "attribute", waitstate);

    Basic Attribute Types           Derived Attribute Types
    String      Description         String      Description
    R           Read                NONE        No memory/protected
    W           Write               RAM         Read and write
    P           Port                ROM         Read only
    EX          External            WOM         Write only
    EM          Emulator            INPORT      Port read only
    PR          Programmable        OUTPORT     Port write only
    ER          Erasable            IOPORT      Port read and write
    DA          Dual access         SARAM       Single access RAM
    ASn         Access size         DARAM       Dual access RAM
    SHnC        Shared              FLASH       Flash ROM
    CACHE       Cache               EXRAM       External RAM
    TX          Text                EXROM       External ROM
    MN          Monitor             EPROM       Erasable write-able EPROM
    SA          Single access       MONITOR     Monitor ROM
    FL          Flash               PRAM        Program RAM
    MR          Memory mapped       PROM        Program ROM
    NULL        NULL                NULL        NULL

    */

    

GEL_MapAddStr(0x00001000, 0, 0x0001f000, "R", 0); /* Flash */
    GEL_MapAddStr(0x00020000, 0, 0x1FFE0000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x20000000, 0, 0x00010000, "R|W", 0); /* SRAM */
    GEL_MapAddStr(0x20010000, 0, 0x1FFF0000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x40000000, 0, 0x00001000, "R|W", 0);  /* WATCHDOG0 */
    GEL_MapAddStr(0x40001000, 0, 0x00001000, "R|W", 0);  /* WATCHDOG1 */
    GEL_MapAddStr(0x40002000, 0, 0x00002000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x40004000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTA */
    GEL_MapAddStr(0x40005000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTB */
    GEL_MapAddStr(0x40006000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTC */
    GEL_MapAddStr(0x40007000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTD */
    GEL_MapAddStr(0x40008000, 0, 0x00001000, "R|W", 0);  /* SSI0 */
    GEL_MapAddStr(0x40009000, 0, 0x00001000, "R|W", 0);  /* SSI1 */
    GEL_MapAddStr(0x4000A000, 0, 0x00002000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x4000C000, 0, 0x00001000, "R|W", 0);  /* UART0 */
    GEL_MapAddStr(0x4000D000, 0, 0x00001000, "R|W", 0);  /* UART1 */
    GEL_MapAddStr(0x4000E000, 0, 0x00001000, "R|W", 0);  /* UART2 */
    GEL_MapAddStr(0x4000F000, 0, 0x00011000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x40020000, 0, 0x00000800, "R|W", 0);  /* I2C0 MASTER */
    GEL_MapAddStr(0x40020800, 0, 0x00000800, "R|W", 0);  /* I2C0 SLAVE */
    GEL_MapAddStr(0x40021000, 0, 0x00000800, "R|W", 0);  /* I2C1 MASTER */
    GEL_MapAddStr(0x40021800, 0, 0x00000800, "R|W", 0);  /* I2C1 SLAVE */
    GEL_MapAddStr(0x40022000, 0, 0x00002000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x40024000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTE */
    GEL_MapAddStr(0x40025000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTF */
    GEL_MapAddStr(0x40026000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTG */
    GEL_MapAddStr(0x40027000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTH */
    GEL_MapAddStr(0x40028000, 0, 0x00001000, "R|W", 0);  /* PWM */
    GEL_MapAddStr(0x40029000, 0, 0x00003000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x4002C000, 0, 0x00001000, "R|W", 0);  /* QEI0 */
    GEL_MapAddStr(0x4002D000, 0, 0x00001000, "R|W", 0);  /* QEI1 */
    GEL_MapAddStr(0x4002E000, 0, 0x00002000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x40030000, 0, 0x00001000, "R|W", 0);  /* TIMER0 */
    GEL_MapAddStr(0x40031000, 0, 0x00001000, "R|W", 0);  /* TIMER1 */
    GEL_MapAddStr(0x40032000, 0, 0x00001000, "R|W", 0);  /* TIMER2 */
    GEL_MapAddStr(0x40033000, 0, 0x00001000, "R|W", 0);  /* TIMER3 */
    GEL_MapAddStr(0x40034000, 0, 0x00004000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x40038000, 0, 0x00001000, "R|W", 0);  /* ADC0 */
    GEL_MapAddStr(0x40039000, 0, 0x00001000, "R|W", 0);  /* ADC1 */
    GEL_MapAddStr(0x4003A000, 0, 0x00002000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x4003C000, 0, 0x00001000, "R|W", 0);  /* COMP */
    GEL_MapAddStr(0x4003D000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTJ */
    GEL_MapAddStr(0x4003E000, 0, 0x00002000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x40040000, 0, 0x00001000, "R|W", 0);  /* CAN0 */
    GEL_MapAddStr(0x40041000, 0, 0x00001000, "R|W", 0);  /* CAN1 */
    GEL_MapAddStr(0x40042000, 0, 0x00012000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x40054000, 0, 0x00001000, "R|W", 0);  /* I2S0 */
    GEL_MapAddStr(0x40055000, 0, 0x00003000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x40058000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTA AHB */
    GEL_MapAddStr(0x40059000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTB AHB */
    GEL_MapAddStr(0x4005A000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTC AHB */
    GEL_MapAddStr(0x4005B000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTD AHB */
    GEL_MapAddStr(0x4005C000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTE AHB */
    GEL_MapAddStr(0x4005D000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTF AHB */
    GEL_MapAddStr(0x4005E000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTG AHB */
    GEL_MapAddStr(0x4005F000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTH AHB */
    GEL_MapAddStr(0x40060000, 0, 0x00001000, "R|W", 0);  /* GPIO PORTJ AHB */
    GEL_MapAddStr(0x40061000, 0, 0x0006F000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x400D0000, 0, 0x00001000, "R|W", 0);  /* EPI0 */
    GEL_MapAddStr(0x400D1000, 0, 0x0002B000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0x400FC000, 0, 0x00001000, "R|W", 0);  /* HIB */
    GEL_MapAddStr(0x400FD000, 0, 0x00001000, "R|W", 0);  /* FLASH CTRL */
    GEL_MapAddStr(0x400FE000, 0, 0x00001000, "R|W", 0);  /* SYSCTL */
    GEL_MapAddStr(0x400FF000, 0, 0x00001000, "R|W", 0);  /* UDMA */
    GEL_MapAddStr(0x40100000, 0, 0x9FF0E000, "NONE", 0); /* Reserved */
    GEL_MapAddStr(0xE000E000, 0, 0x00001000, "R|W", 0);  /* NVIC */

    GEL_TextOut("\nMemory Map Initialization Complete\n");

}

menuitem "Peripherals"
hotmenu watchdog_enable()
{
    *(unsigned long*)0x400FE100 |= 0x8;

    GEL_TextOut("Watchdog Timer Enabled\n");

}

hotmenu uart_enable()
{
    *(unsigned long*)0x400FE104 |= 0x3;

    GEL_TextOut("UARTs Enabled\n");
}

Hi John,

we would like to investigate whether this could point to a potential debug issue.

Would you possibly be able to send any .dmp files generated?   Also if you could enable logging that could also produce some interesting information for us to look at.

Please keep us informed,

Lisa

Hi John,

just another quick update for you.  One thing to check is whether renaming the ctools.dll file will solve the issue.  Please see this thread as you do not seem to be alone with that windows error message being generated.

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/75777/275947.aspx#275947

Once again please keep me posted.

Best Regards,

Lisa

Lisa,

How do I generate .dmp debug log files?   The help file does not seem to be very helpful ...

Thx.  jb

Hi John,

ok could you please do the following and keep us posted.

1) Rename ctools.dll to something else.  This disables hardware breakpoints, however, can indicate if this dll is the source of the issue as we have seem to have seen before in at lease some cases,   Give this a try,

If this does not fix the issue here are the instructions regarding the logs, with my appologies for not posting them in the previous post.

2) a) Search your <ccs install dir>/ccsv4 folder for any files that look like "hs_err_pid<some number>.log" (for example: hs_err_pid4044.log). These are created by the JVM and may have some further details about what happened.

b) Could you refer to this page: http://tiexpressdsp.com/index.php/Troubleshooting_CCS , and under "Debug Server Logging", follow the unstructions to capture the DS logging output for what happens just before the crash.

c) See if any .dmp files are generated.

Thanks and regards,

Lisa

John, can you let us know if any of the above suggestions resolved your problem. We trying to get to the bottom of this issue but are having difficulties reproducing.
Raj

Thank you Lisa and Raj.   I very much appreciate your following through on this CCS crash and burn saga.    I had not responded because my results have not been reproducible either.    First, I found the following recipe (in another thread) to produce log files, and followed it (OS=Win-7, 64-bit):

1. Quit CCS.
2. Right click on the “MyComputer” icon on your desktop.
3. Select “Properties”.
4. In XP select System Properties, in Win7 click on "Advanced System Settings"
5. In the System Properties dialog, click on the “Advanced” tab. (should already be selected in Win7)
6. Click on the “Environment Variables” button.
7. In the “Environment Variables” dialog, under the “User variables” group, verify that the “TI_TRACE_LOGGING” environment variable exists and has a value of 6. Create it if it is not there.
8. Click “OK” in all dialogs.
9. Restart CCS.
10. Reproduce the problem, noting what steps were performed in what order.
11. Zip up the log file and attach it to this thread.  The log file will be in /ccsv4/emulation/analysis/bin/Logs/ti_trace_log_MMDDYY_PID.txt file.

As soon as I did this, I have not been able to log a crash, but have only tried maybe 50 times, using the (not entirely reproducible method I had before).   I have not yet tried removing the logging to see what happens.    Cannot work on this today, but hope to get back to it tomorrow - and will let you know.

jb

John,

.dmp file generation is automatically enabled, so you might already have some from previous crashes. On windows 7 these files are output to C:\Users\<your user name>\AppData\Local\.TI. If you can scan this entire directory, zip up and attach any files you find there, we might be able to get to the bottom of this issue. 

Thanks,

Mandeep

Mandeep,

7750.TI.zipI could not find any .dmp files therein, but here is what I did find.  Does this help any?

jb

Mandeep,

You have done an absolutely brilliant job of getting to the bottom of this problem that has plagued me for longer than I want to admit.   

Thank you!   jb