CCS C Software and Maintenance Offers
FAQFAQ   FAQForum Help   FAQOfficial CCS Support   SearchSearch  RegisterRegister 

ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

CCS does not monitor this forum on a regular basis.

Please do not post bug reports on this forum. Send them to CCS Technical Support

ICD-U40 won't launch from PCW, Access Violation crashes PCW

 
Post new topic   Reply to topic    CCS Forum Index -> CCS ICD / Mach X / Load-n-Go
View previous topic :: View next topic  
Author Message
soundscu



Joined: 29 Jun 2007
Posts: 62
Location: Raleigh, NC

View user's profile Send private message Visit poster's website

ICD-U40 won't launch from PCW, Access Violation crashes PCW
PostPosted: Mon Mar 03, 2008 10:55 pm     Reply with quote

I am no longer able to launch the ICD-U40 debugger from PCW. It used to, before I enabled one of the mouse-over functions in the debugger config window.

In PCW I go to Debug -> Enable Debugger. The debugger screens open, followed by a separate ICD Start Connection box. When I click Connect the box disappears briefly then reappears. When I click Abort, one of two things happen: either PCW abruptly closes, or I get a PCWH error box that says: "Access violation at address 007D5484 in module 'Pcw.exe' Read of address 0000000C." When I click OK in this error box, PCW abruptly closes.

Since the debugger window never completely opens, I can't try turning off the mouse-over function that I turned on. I looked for an ini file that might contain the settings, but didn't find anything.

Last week I was having this problem, but I found that I could recover by using the ICD to program a part. This would launch the external ICD program, which works fine. After that, the debugger would work again for a while.

But today, that workaround has completely stopped working. Now I'm unable to debug my project at all.

I tried reinstalling PCW, no difference.

ARRGGGGG. :( I have a deadline looming, and I'm almost done the project... this is EXTREMELY annoying. Any suggestions on how to get my debugger working would be much appreciated. I really need break points and the watch window to get through this.

Thanks so much.

Jim
PCM programmer



Joined: 06 Sep 2003
Posts: 21708

View user's profile Send private message

PostPosted: Mon Mar 03, 2008 11:50 pm     Reply with quote

Quote:
It used to, before I enabled one of the mouse-over functions.

I tried reinstalling PCW, no difference.

Since the debugger window never completely opens, I can't try turning off the mouse-over function that I turned on. I looked for an ini file that might contain the settings, but didn't find anything.

The mouse-over setting might be in a file somewhere within the PCWH
directory, or it could be in the Registry.

You could save your license file (.CRG) in a safe place, un-install
PCWH, and then open a dos window and DelTree the compiler directory.
If the settings are in a file in that directory, this would clear them.

Then re-install PCWH, copy your .CRG file back into the directory,
and run PCWH. If the mouse-over is still active, then the settings are
likely in the Windows Registry. You could search the Registry for the
word 'CCS' or 'PCWH' or 'PCW'. Maybe look for a Debugger section.
Or just delete all the settings that you find, and then re-install PCWH.
(Possibly backup the registry first, if you're not familiar with editing it).
soundscu



Joined: 29 Jun 2007
Posts: 62
Location: Raleigh, NC

View user's profile Send private message Visit poster's website

PostPosted: Tue Mar 04, 2008 7:07 am     Reply with quote

Thank you!

I did a complete unininstall and reinstall, and have managed to recover. (Too bad working late last night resulted in f&*^&%$g with the debugger instead of getting the job done.)

Thanks again!
Jim
soundscu



Joined: 29 Jun 2007
Posts: 62
Location: Raleigh, NC

View user's profile Send private message Visit poster's website

It's a FTDI USB conflict...
PostPosted: Thu Mar 13, 2008 10:04 am     Reply with quote

I've finally realized that these problems arise whenever I am using any other USB device that has an FTDI chip in it, including DMX converters from Enttec, Maxstream RF Development boards, and more.

The current conflict arises with the Maxstream XBIB-U board. A real problem since I'm developing a wireless device and need this rf unit in place for testing.

Anybody else having this problem? Is there a workaround so PCW will connect to the ICD-U40 when other FTDI-based USB devices are online?

Jim
soundscu



Joined: 29 Jun 2007
Posts: 62
Location: Raleigh, NC

View user's profile Send private message Visit poster's website

PostPosted: Thu Mar 13, 2008 10:08 am     Reply with quote

P.S. The ICD program connects without a problem, it's only PCW that won't. I can program chips with ICD, but can't debug from PCW if other FDTI-based devices are online.

Jim
treitmey



Joined: 23 Jan 2004
Posts: 1094
Location: Appleton,WI USA

View user's profile Send private message Visit poster's website

PostPosted: Tue Apr 22, 2008 11:19 am     Reply with quote

This goes back to 2004. Others have seen this also.

http://www.ccsinfo.com/forum/viewtopic.php?t=19921&highlight=icdu40+ftdi

see my solution:

http://www.ccsinfo.com/forum/viewtopic.php?p=41123#41123
Display posts from previous:   
Post new topic   Reply to topic    CCS Forum Index -> CCS ICD / Mach X / Load-n-Go All times are GMT - 6 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group