Path: chuka.playstation.co.uk!foo.mel.cybec.com.au!nobody From: Toby Hutton Newsgroups: scee.yaroze.programming.gnu_compiler Subject: Re: Toby's question (not an answer). Date: 24 Aug 1999 18:22:30 +1000 Organization: PlayStation Net Yaroze (SCEE) Lines: 44 Sender: toby@foo.mel.cybec.com.au Message-ID: <86wvuld1vd.fsf@foo.mel.cybec.com.au> References: <86n1vj5c6o.fsf@foo.mel.cybec.com.au> NNTP-Posting-Host: 203.103.154.60 X-Newsreader: Gnus v5.6.45/XEmacs 21.1 - "20 Minutes to Nikko" tjs@cs.monash.edu.au (Toby Sargeant) writes: > 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 Psxfer has a stack of parameters for loading files into PSX memory, so I gather is wasn't intended to *only* put it into rdb mode. But it always does... > 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. You're actually using gdb to do file transfers? Have you set up some macros to handle AUTO files that DOS Yarozers create? I noticed when building a cross compiled gdb there are about half a dozen remote targets, mainly for embedded systems work I suppose. Is your AR stub based on any of these? They're all serial targets I think, where the AR is parallel? -- Toby.