Path: chuka.playstation.co.uk!scea!greg_labrec@interactive.sony.com
From: Kirk Bender <kbender@znet.com>
Newsgroups: scea.yaroze.programming.codewarrior
Subject: Re: Debugger problems
Date: Sat, 24 May 1997 15:01:33 -0700
Organization: SCEA Net Yaroze News
Lines: 30
Message-ID: <3387653D.5B9A@znet.com>
References: <3368DC25.5500@vicon.net>
NNTP-Posting-Host: capts-33.znet.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0Gold (Win95; I)
To: lobo@vicon.net
CC: support@metrowerks.com

Manifered H. Wolfe, II wrote:
> 
> I've been having problems with the debugger in Windows.  I thought it
> might be that I was using COM2, so I moved my mouse to the PS/2 port and
> tried it on COM1.  Same deal.  PSComUtil works fine, but when I try to
> use the debugger, it seems to connect (reflected on the PSX screen), but
> then I get an error message.  Any suggestions?  Thanks!
> 
> --
Wish I'd read this group sooner.
suggestion: wait for the new version of codewarrior. 
I have the same problem (W95, 486/133).  comutil and siocons work fine
on
 the check program.  In the debugger with the same com settings, it
 connects, then says "remote debugger startup" on my PSX, then the
 debugger says, "transferring check.pse" then it says, "A fatal
 Communications error has occurred.  Please close the symbol and task
 windows and reset your target."

Another thing I've noticed is that in siocons, you run the check
program,
 then hit the select button on the pad and you're back in the brick wall
 ready to try again.  In PScomutil, the psx freezes and you must wait
 30sec to reboot.  Not much, but it adds up.

regards,
kirk

kbender@znet.com
http://www.scea.sony.com/net/yaroze/pages/kbender.html