CCSv4.1.1 on Vista: Debugger crash

Petrei,

These Microsoft dependedencies are supposed to come from the Microsoft redistributable installers. On the chance something wasn't installer correctly, could you re-run these installers by browsing to <Location of CCS Installer>\install_images\msvc and re-run both MSVC80_Runtime.msi and vcredist_x86.exe ?

Please let me know if that helps.

Hi Andy,

I checked but the behavior is the same. If this help, here is the message window after the crash:

Regards,

Pertei

I also get these crashes and worse on my new Windows 7 Home Premium 64-bit Core i7 Sony laptop. Worse being I get the Blue Screen of Death.

Seems to happen when using the emulator to flash and debug. So I had to go back to my old Windows XP laptop. I bought the new laptop because I was having trouble flashing and debugging on the old laptop but the BSODs made the situation worse so I am back on my old laptop where I have yet to get a BSOD. I had started with the Spectrum Digital XDS510LC emulator but switched to the Blackhawk USB2000 because of too many restarts flashing and debugging with the XDS510LC.

I am using CCS v4.1.x and developing for a F2808. The CCS installer would not install the Blackhawk drivers on the Win7 laptop so I had to install them manually. I would really like to use the new laptop since I think the USB ports on my old laptop are problematic and I have only one left that works consistently.

I would appreciate any thoughts on how to improve the reliability on my new laptop.

Thanks.

Siraj.

Thank you for trying this out. For the next step, could you refer to this page: http://processors.wiki.ti.com/index.php/Troubleshooting_CCS go about these steps:

• If you haven't already, please follow the steps under "Debugger" to delete the cache files.
• Then, please refer to the "JVM Error Logs" section, and provide the two sets of log files mentioned if they are present.
• Finally, refer to the "Debug Server Logging" section, and capture the DSS logs

Unfortunately, the error dialog you posted is a generic thing created by eclipse that does not help with this case.

Hi Andy,

I have accomplished all steps requested in the link provided - here are some more explicit informations:

CCS Version: 4.1.1.00014 

CCS Installation Directory: C:\TI

Setup Configuration.CCXML file in "<user name>\user\CCSTargetConfigurations": none 

ccBoard0.dat file - attached in archive

Target Board: TI EKS-LM3S8962 Rel-B Trace: 0015806ZAF LOT:BS9868CTU

Host Operating System: Vista Home Premium Service Pack2, 32 bits

Connection to board: USB 

Program to debug: Hello application in StelarisWare\boards\ek-lm3s8962, no changes

The necessary files are in the attached archive6038.CCSv4-Vista-YOAN-Bug.zip

Regards,

Petrei

Thank you Petrei.

The crash is occuring in an Acer module called "PSDProtect" which is part of an Acer product called eDataSecurity. I am not familiar with this product, but I see there are a number of posts about a compatibility issue with it on Vista and recommendations to upgrade to the latest version. Would  you be able to apply the latest patches for this component? The version of the DLL you are using is v2.0.

Please let us know if this helps.

Hi Andy,

I uninstalled the Acer module eDataSecurity which contained "PSDProtect" module - but the results are the same, I cannot debug. In the debugger view I can see the two messages "In Circuit Debugger Interface_0/CORTEX_M3_0/" and "In Circuit Debugger Interface_0/CORTEX_M3_0 CIO/"; in the console view is re-printed the second message. I expect the flash to be erased  and the .bin program to be downloaded, but after a while there is the crash. In one try I started a console program set to COM15 which is where the COM channel of FTDI driver is installed and noticed the Eclipse is sending a series of "FF" bytes, then stopped. 

Some questions in this situation:

a) I read in another forum post that the version 4.1.2 is available. Can you tell me a link where can be downloaded? my version came first with the CD from Luminary Micro(is EKS-LM3S8962-CD-535 with special license; also downloaded from Luminary site) ; I checked their site and seems to be there the same old one, based on version 4.1.0. Starting Eclipse I was invited to upgraded to 4.1.1; I can try a fresh installation with 4.1.2, maybe more luck...(but not with an Internet upgrade, it is too slow).

b) with the present installation I checked again the files packed and sent yesterday, the PSDProtect does not appear.

c) On an XP computer the same installation version/upgrade works OK; I cannot understand what could be  wrong on Vista; my office system is Vista, I need to be mobile. 

d) I think it would be more useful to have a separate command to erase the flash first and then to debug; the console view can be used to print some steps/messages about these processes, instead of a separate window.

e) Do you have any idea how to catch the wrong, crashing location/routine?

Regards,

Petrei. 

Hi Petrei,

I will be looking into this issue while Andy is away.

a. CCS4.1.2 can be downloaded here: http://processors.wiki.ti.com/index.php/Download_CCS

b. If it is available, can you send the dmp file that was generated from the CCS crash after you uninstalled PSDProtect?

c. I'm not sure why this is only happening on Vista; maybe there's a permission issue?

d. Are you using the 'Debug Active Project' feature? If you are, you can alternatively separate the steps of the features manually. This way you can isolate where the crash occurs.

  1. Right click on the CCXML configuration file in your project, and choose 'Debug As' -> 'Debug Session'. This will open a debug session for your Stellaris device.

  2. Connect to the Target using shortcut keys 'Alt+c' or going to top menu 'Target' -> 'Connect Target'

  3. After connecting to the target, try erasing the Flash via 'Tools' -> 'On-Chip Flash'. In the new view that opens, click on the 'Erase Flash' button.

  4. Try loading your program by going to 'Target' -> 'Load Program...'. Choose 'Browse project...' and pick the program you want to load.

Let me know which of these steps are causing the crash, and include the log and dmp files if they are available.

Thanks.

Ricky

Hi Ricky,

Thanks for the info above - I didn't knew about these steps in debugging.

I have tried and the debugger stops in the first phase - connecting to target. I  have also a debug log of this step, it is attached.

The second attached file is a debug log after I removed PSDprotect.dll by uninstalling the Acer's eDataSecurity feature.

Looking a little in the debug log - it seems each flash sector is somewhat protected - or at least I don't know how to interpret the message"Protect"....

Thanks and regards,

Petrei2816.CCS-Bug2.zip 

Petrei,

Unfortunately, the log files do not tell me where the crash is occuring. Were there any dmp files generated on the crash, like the DebugServer.dll20100420150159.dmp file you sent on the previous package you sent?

1. Turn off logging (ie; do not set TI_DS_ENABLE_LOGGING=1), and make sure it is still crashing on connect.

2. Install CCS 4.1.2 and see if it fixes the issue or not.

3. Rename the file located at C:\TI\ccsv4\DebugServer\bin\win32\FlashStellaris.dll to something like FlashStellaris.dll.bak; and try to connect to the device again. This will temporarily remove the Flash Programming functionality for Stellaris devices. This will help me determine if the Flash component is the cause of the crash.

I will continue to look into this issue on my end. Let me know if you have any questions.

Thanks.

Ricky

Hi Ricky,

I followed your instructions and installed version 4.1.2, but the problem still persist. After the first run and crash of the new version, Windows told me he setup a compatibility flag for Eclipse, the snip of the message window is included in the attached files. I included the .dmp files without and with FlashStellaris.dll renamed.

Regards,

Petrei0218.CCS-Bug3.zip 

Petrei,

I am having problems with downloading the latest package you uploaded (I'm getting a '404 - File or directory not found.' error). If you still have the fiiles, can you try re-uploading it for me.

Thanks.

Ricky

Hi Ricky,

Here are the files.7002.CCS-Bug3.zip

Regards,

Petrei

Have you tried the windows xp virtualization that is part of Windows 7?  Unfortunately I don't know if it works with Home Premium but it starts working with some level of win 7.

You have virutalization hardware in your new processor where the Windows XP virtual operating system runs.

Hi,

My system is Vista Home Premium - Virtual PC 2007 does not install - it says "Wrong OS" and virtualization tools for Windows 7 requires "Genuine Windows 7" to install. No Vista support. I have tried also virtual tools from SUN but they does not work - I was not able to figure out why.

Petrei 

I doubt that missing dll's that depends is reporting are the source of the crash. I am running on win7 (which is different from Vista, but closer to vista than XP) without issues. I also get those dll's reported as missing when running depends. 

Do you get a crash only when trying to start debugger? 

martin

If you are running Windows Vista or Windows XP on your physical machine, you can still use Microsoft Virtual PC 2007 to run multiple operating systems at the same time on the same physical computer. Switch between virtual machines with the click of a button. Use virtual machines to run legacy applications, provide support, train users, and enhance quality assurance.

Virtual PC 2007 requires a 400 MHz Pentium-compatible processor (1.0 GHz or faster recommended), and requires approximately 35 MB of disk space. It runs on Windows Vista Business, Windows Vista Enterprise, Windows Vista Ultimate, Windows XP Professional, Windows XP Tablet PC Edition, Windows Vista Service Pack 1 (SP1) (Enterprise, Business, Ultimate), and Windows XP Service Pack 3 (SP3).

You need to be using at least Vista Business.

Petrei,

That's good to know. I have closed the CQ that was opened for you.

Regards.

Ricky

Hi,

I have excat the same problem. However, installing the version 4.1.2 (downloaded) after de-installing the updated version did not solve the problem. I use the C2000 as target and a Signum JTAG device. My OS is a WIN7 64bit. The previous ccs version worked fine. So please don't close the issue.

Any hints what else to try? Currently I have to use the ccsv3.3 in order to get my work done :-(

Regards,

Klaus

Klaus,

Can you refer to the post from Andy earlier in the thread and follow the Troubleshooting CCS page, providing any logging information that are available in your situation. This will greatly help with understand the problem you are facing.

Thank you.

Ricky

Ricky,

attached is a zip w/ all logs and dumps I found.

Regards,

Klaus

4087.CrashCCS.zip

Klaus,

Have you tried the following to determine which step is causing the crash?

"Are you using the 'Debug Active Project' feature? If you are, you can alternatively separate the steps of the features manually. This way you can isolate where the crash occurs.

  1. Right click on the CCXML configuration file in your project, and choose 'Debug As' -> 'Debug Session'. This will open a debug session for your Stellaris device.

  2. Connect to the Target using shortcut keys 'Alt+c' or going to top menu 'Target' -> 'Connect Target'

  3. After connecting to the target, try erasing the Flash via 'Tools' -> 'On-Chip Flash'. In the new view that opens, click on the 'Erase Flash' button.

  4. Try loading your program by going to 'Target' -> 'Load Program...'. Choose 'Browse project...' and pick the program you want to load.

Let me know which of these steps are causing the crash, and include the log and dmp files if they are available."

and can you also let me know if this is reproducible every single time?

Thanks.

Ricky

Ricky,

if I select the Debug As->Debug Session then it takes a while and I see the switch to the Debug perspective and then the app crash. Means that the IDE disappears and the Error dialog appears. This is for every single time. I can't use ccs for now :-(.

As you can see I'm even not able to do step 2.

All the dump and log files (and the screen shot) are attached to my last post.

Regards,

Klaus

Klaus,

Since CCS is crashing on the first step, can you send me your CCXML file as well for analysis?

Also, please confirmed that you have tried these steps in the Troubleshooting site.

- Cleaning the workspace

- Delete the target configuration cache

- Deleting target database cache (please note the 4.1.2 difference)

Thank you.

Ricky

Hi Ricky,

yes I did all the steps you mentioned.

Attached is the CCXML file: 4341.MF08.zip

Regards,

Klaus

Hi Klaus,

I have no experience with WIN7/64 bits but I can share with you my experience installing CCSv4.1.2 to work with Stellaris on my Vista system. If something does not apply in your case please don' t blame me.

1. First, make a folder in C:\  where you like to install. Do not install in C:\Program Files. Right click on the folder name and select Properties. Modify access rights, i.e, allow full control for the user.  

 2. Go and disable UAC, disconnect from Internet and restart the computer.

 3. Start installing CCSv4.1.2. Select for installation the folder previous created. Be careful when selecting the installation configuration: do not install (uncheck) any emulators XDS5xxx, since you have another one. Follow the installation to the finish. (This is the main difference in my previous installations). Install your Signum drivers - check the documentation, maybe it is necessary to be installed first.

4. Re-enable UAC and restart your computer.  

5. Start CCS and go to Help | licensing option and register your software.

Hope these help,

Regards,

Petrei

HI Petrei,

most of your suggestions are already complied. But in my case it doesn't help. The only thing I didn't tried so far is the UAC stuff, since I'm administrator on my machine and the UAC are changed so that installations are allowed and some other things ( I can't remember the details ).

Thanks,

Klaus

HI Ricky,

after some more investigation I figured out that the problem is the connect to the target. Now I'm able to start via the "Launch TI Debugger" w/o connecting to the target. If the target board isn't connected to the JTAG emulator then I get the expected error message. However, if I connect the board and then try to connect to the target (alt + c) it takes a few moments and then ccs crash w/ an error dialog. This is reproducible after a fresh installation and cleaning up every thing. I didn't checked the registry. Is there any information stored ?

Hope these information helps to localize the problem area.

Regards,

Klaus

Hi,

I read in an other thread http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/36438/165462.aspx#165462about a similar problem. As a test  the ctools.dll has to be disabled (by renaming). So I tried this one too, since the error message is so similar. And after renaming ctools.dll I can successfully connect to the target. So it looks like that the BUG sit in the ctools.dll. However, I don't know the consequence of it yet.

Is somebody at TI development working on this issue? What do I have to do in order that this BUG wents to development :-).

Best regards,

Klaus

Klaus,

Thanks for posting the link to the other thread. I am currently checking to see if there was any action taken to resolve the other issue.

Can you search your CCS installation folder and see if any *.dmp files were generated from your connect crash? If so, please send it over as well.

It's interesting that Petrei had a similar issue with connecting, with the cTools DLL enabled; but he was able to avoid the problem after a fresh install.

Either way, there seems to be some issues with the cTools component, and we need to make sure it is being looked into.

Thanks.

Ricky

Ricky,

here is a zip containing a lot of dmp files and I think they are all related to the connect crash : 7563.DebugServer.dlldmp.zip

Yes, unfortunately a fresh install (I did it for 3 times) do not help on every machine. Tomorrow (here the day is almost done :-)) I'll try it on a different machine w/ a different OS just to see if it is related to the configuration of a machine, too.

Regards,

Klaus

Hi,

I tested it on a different machine w/ Windows Vista 32 bit version. I installed the ccsv4.1.2 and generated a small test project. I get still the same error.

Regards,

Klaus.

Klaus,

Can you confirm that you can work around this issue by renaming cTools.dll on the Vista machine as well?

If yes, can you search for any hs_err_pid*.log and *.dmp files that were generated in the <installDir>\ccsv4\emulation\ directory, and attache them as well.

Regards,

Ricky

Hi Ricky,

yes I can confirm. After renaming the ctools.dll to ctools.dll_ I'm able to connect to the device. Attached are the *.dmp and hp*.log files.

4152.ccs4_crash_vista_32.rar

Regards,

Klaus

Hi Ricky,

thanks for your support. How can I track the issue online?

Regards,

Klaus

Klaus,

Please go here: https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDo-Web&contextid=SDOWP&username=readonly&password=readonly

and enter your CQ to track this issue.

Regards,

Ricky

TI - this bug still exists - terrible.

I've renamed all files that have cTool*.dll to something else.

USB driver problems have also crept up again under Windows 7.

I am ready to abandon this toolset - this is really disappointing.

I also loaded the bug and it says it was rejected - what is the reasoning?  Do you want to lose customers?  This bug is very real, and very alive, and very aggravating.

Hi Johnw,

I'm having the same problem and it is very annoying. Have you found a solution or  TI's ppl have fixed?

Max,

According the the information in the CQ system, SDSCM00036157 is marked fixed and should be included in the latest CCS5.1 build. Can you let me know which version of CCS you are using? and if you are not on CCSv5 yet, can you give it a try?

Thanks.

Ricky

Hi Ricky,

I have checked today CCS v5.1.0 on my Vista computer. No problems encountered so far, the debugger works OK.

Thanks and regards,

Petrei 

Hi Ricky,

I was using CCSv4.2.4 (Windows 7P) with no problem until one day I coudln't debug anymore, not even the examples projects. Every time I tried to connect with the target I got the message below. I installed CCsv4.2.4 again in another PC with vista and I could debug the same program that I was using when CSS started crashing in my first PC, so I have no idea what caused the problems. Anyhow, I've installed CCSv5 too in Windos 7 and it's working so far (besides crashing windows once), let hope it keeps behaving like that. Thanks.