| View previous topic :: View next topic |
| Author |
Message |
ljbeng
Joined: 10 Feb 2004
Posts: 205
|
| 3.249 locks up |
 Posted: Wed Mar 14, 2007 9:13 am |
 |
|
| I have a windows xp computer. I am running 3.249. I will be debugging and I will have just downloaded a newly compiled program. The debugger screen does it's thing and says 100% loaded Ready and the green button is GO. I will then press go and get a popup menu something like "Cannot execute, still reading ram...." and at this point, it never gives me a green GO and I cannot close the debugger screen. Sometimes if I unplug the ICDS40, the debugger screen will finally shut down and give a "list index" popup error. MOST OF THE TIME, the entire CCS program locks up and task manager can't even shut it down. I cannot shut the computer off and I have to pull the plug (of the pc) to reboot. CCS is stumped. Our IS dept is stumped. Is the computer junk? What could be causing this? |
|
 |
PCM programmer
Joined: 06 Sep 2003
Posts: 21708
|
|
|
ljbeng
Joined: 10 Feb 2004
Posts: 205
|
|
| Posted: Wed Mar 14, 2007 12:48 pm |
|
|
| I use the ICD-S40, serial port, not USB. |
|
|
PCM programmer
Joined: 06 Sep 2003
Posts: 21708
|
|
| Posted: Wed Mar 14, 2007 12:54 pm |
|
|
Sorry, I didn't see that. Heck, in that case, change to the USB ICD. 
I've never heard of a program dying because of a serial port issue.
Usually, programs that use the serial port are more reliable, in my
experience. We were using an Ethernet-based debugger from Zilog
and it wasn't 100% reliable. Then we switched to their serial port
version and it worked all the time.
All I can say is, try a different computer or maybe get a serial port
card and install it. Try using the ports on that card instead of the
built-in ones on your PC. Try re-installing all CCS software. |
|
|
Guest
|
|
| Posted: Wed Mar 14, 2007 1:06 pm |
|
|
| A lockup that bad sounds like it gets stuck in the driver. As far as your computer goes, Windows does a good job of ignoring or hiding memory errors. Find the program memtest86 on the Web and run it. (It's also on most Linux try-out CD's). Your IS department should know about this. They should also know that you don't have to unplug your computer to shut it off. Holding the so-called "power" switch for five seconds should do that. |
|
|
newguy
Joined: 24 Jun 2004
Posts: 1909
|
|
| Posted: Wed Mar 14, 2007 2:03 pm |
|
|
| PCM programmer wrote: | I've never heard of a program dying because of a serial port issue.
Usually, programs that use the serial port are more reliable, in my
experience. We were using an Ethernet-based debugger from Zilog
and it wasn't 100% reliable. Then we switched to their serial port
version and it worked all the time. |
Some time ago I asked about the ICD.exe program locking up my computer over on the ICD forum and got no replies. I finally sorted out what was wrong, but the issue had to do with ANY program attempting to access the serial port (RS232) on my PC. It would lock up every time, and only cycling the power would bring it out of lockup. The lockup was so severe that windows wouldn't even come up with the "your PC didn't shut down correctly" error upon reboot.
Anyway, CCS eventually emailed me a special version of ICD.exe which did not attempt to access the COM ports upon initialization (only USB). That fixed that particular issue.
However, if I attempted to use CCS's serial port monitor program or even hyperterminal, the PC would lock. After much head scratching and support calls/emails to Lava, I found that the problem was a defective Lava serial add-on PCI card. When I replaced the card, all my problems with locking up windows went away. |
|
|
ljbeng
Joined: 10 Feb 2004
Posts: 205
|
|
| Posted: Wed Mar 14, 2007 2:08 pm |
|
|
| "Pulling the plug" was just for drama.... I just hold in the power button to reset. |
|
|
|
FAQ 
Search
Register
Profile 
Log in to check your private messages 
Log in
