Path: chuka.playstation.co.uk!scea!greg_labrec@interactive.sony.com From: sumner@metrowerks.com (Joel Sumner) Newsgroups: scea.yaroze.programming.codewarrior Subject: Re: System memory Date: Wed, 23 Jul 1997 15:37:34 -0500 Organization: Metrowerks Lines: 28 Message-ID: References: <01bc957d$ffb78880$9fbf43ce@wkwerner> <01bc9580$b51472e0$9fbf43ce@wkwerner> <01bc96f0$7f4cfa80$9dbf43ce@wkwerner> <33d63d08.2134142@news.scea.sony.com> NNTP-Posting-Host: jsumner2.metrowerks.com X-Newsreader: Anawave Gravity v1.10 In article <33d63d08.2134142@news.scea.sony.com>, jamin1@psu.edu says... > That's what I thought as well. You may still use PSComUtil without > rebooting, but to use siocons, you need that "brick" screen. In addition to the "brick" screen, SIOCONS also requires the Net Yaroze to be in 'console mode' rather than in HSS mode (the packet-oriented debugging protocol that we use. It's the reason for the "Remote Debugger Startup" line on the TV screen when you activate PSComUtil or the Debugger). I'm not sure if there's a way to exit HSS mode without rebooting the console. (Anyone from Sony want to let me know on this one? ) > By the way, MAKE SURE you do not use PSComUtil if an MS-DOS prompt > is currently active. On my system if you do, you can't use PSComUtil > thereafter even if you close MS-DOS and reenter PSComUtil. It seems > like it refuses to reidentify the serial connection, since it didn't > work last time! My only resort is to reboot the computer. Can some > Metrowerks guys confirm me on this?? Hmm. I'll have to take a look at it. I assume this only happens after you have run SIOCONS in an MS-DOS window. MS-DOS windows that haven't touched the serial port that PSComUtil is trying to use should be fine. -- ------------------------- PlayStation Debugger Dude Metrowerks