Path: chuka.playstation.co.uk!tjs From: tjs@cs.monash.edu.au (Toby Sargeant) Newsgroups: scee.yaroze.programming.gnu_compiler Subject: Re: Toby's question (not an answer). Date: 23 Aug 1999 23:02:48 GMT Organization: PlayStation Net Yaroze (SCEE) Lines: 29 Message-ID: References: <86n1vj5c6o.fsf@foo.mel.cybec.com.au> NNTP-Posting-Host: longford.cs.monash.edu.au X-Newsreader: slrn (0.9.4.3 UNIX) On 23 Aug 1999 14:54:39 +1000, Toby Hutton wrote: >Attention fellow unix users. What are you guy(s) using for comms to >the Yaroze? I've been using a crap (buggy) version of siocons which >is barely adequate. > >There's the HSS utils, but when I build them (after patching for >compile errors) and run psxfer (or whatever it's called, can't >remember) it *always* puts the Yaroze into rdb mode. Are other people >seeing this? > >It may be because I'm running FreeBSD and all of these tools are >geared towards Linux..? > >Not that I have the time, but a better comms tool needs to be done. >If anything, I need to put readline(3) into the siocons I use. Would >improve it tremendously. Could even put a customer completor in there. I've never had any luck with siocons. Psxfer is designed to stick the yaroze into rdb mode. it's useful for remote debugging that it does. You don't really lose anything, because (almost) everything you can do talking to CIP you can do with gdb. Personally, though, I use a homegrown MIPS gdb stub talking to an action replay cart talking to linux running a bunch of tools that I wrote as well as a modified gdb. Works like a charm. When I next find myself inspired, I'm going to try and turn the gdb stub into a flashable rom image, and then I'll be able to get rid of the memory overhead. Toby.