Path: chuka.playstation.co.uk!news From: Andrew Partington Newsgroups: scee.yaroze.freetalk.english Subject: Re: Siocons under Linux Date: Tue, 29 Nov 2005 20:43:53 +0000 Organization: PlayStation Net Yaroze (SCEE) Lines: 84 Message-ID: References: NNTP-Posting-Host: spr1-ward1-6-0-cust65.bagu.broadband.ntl.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.11) Gecko/20050729 X-Accept-Language: en-us, en In-Reply-To: Philippe Lorin wrote: > Andrew Partington wrote: > >> PSComUtil and CodeWarrior work under Wine (http://www.winehq.com) if >> that's any help. Perhaps the Yaroze GCC will also work, but i've not >> tried it myself. TIMUtil/TIMTool also work. > > > Thanks for the hint. However, I had no luck with PSCommUtil either. It's > better, still: it only freezes while downloading the second part of the > executable -- or is it always after a fixed amount of time/data? I > haven't tried it with various programs though; I'll do that when I get > some more time. > I don't get any problems with PSComUtil under wine freezing when trying to send programs/data across - could your executable be corrupted somehow, or perhaps you have a damaged or loose serial cable/port? I remember when I had my Yaroze connected up to my old shed of a laptop, serial comms were a bit unreliable - I found out eventually that the serial port was not holding the cable in properly and I had to balance stuff underneath the plug to get it working. From what you've written it sounds like you can connect and PSComUtil can see the Yaroze. If you can connect then this shouldn't make any difference, but try checking the ownership of /dev/ttyS0 (if your Yaroze is connected to com1) - PSComUtil will only connect for me if I own the device, ie: $ ls -l /dev/ttyS0 crw-rw---- 1 aparting uucp 4, 64 Nov 29 18:35 /dev/ttyS0 works for me, but doesn't when root owns the port: crw-rw---- 1 root uucp 4, 64 Nov 29 18:35 /dev/ttyS0 Another thing you might want to check is if there are links to the serial port in your wine config directory (I can't remember if wine creates these for you): $ cd ~/.wine/dosdevices $ ls -l lrwxrwxrwx 1 aparting users 10 Feb 2 2005 com1 -> /dev/ttyS0 lrwxrwxrwx 1 aparting users 10 Feb 2 2005 com2 -> /dev/ttyS1 If they don't exist, you can create the link by doing this: $ ln -s /dev/ttyS0 com1 $ ln -s /dev/ttyS1 com2 > I also tried Siocons with Wine, but got nothing at all (this is the > first time I'm using Wine, so I may very well have missed something). > I've not managed to get it working under wine either - but I didn't try too hard since PSComUtil worked for me. I've just tried the binary version of dosemu (http://www.dosemu.org) and siocons works under that when you enable serial ports, but serial comms are *really* slow. If you want to try it then you'll need both dosemu-1.2.2-bin.tgz and dosemu-freedos-b9r5-bin.tgz, then modify dosemurc to enable serial support, then copy dosemurc to ~/.dosemurc - I think i'll stick with PSComUtil for now. > I also tried HSSUtils for Linux, which does a bit like PsCommUtil: it > seems to work, but it won't launch the program (using the switch meant > for that -- sorry, I don't have the details of what I tried at hand). I built HSSUtils to try it out (and also built the cross compiler) - I found that unless I ran mipsel-ecoff-strip on the .pxe produced by the compiler it wouldn't launch, just as you describe. Hope that helps - if not, I could give your file a shot at this end, then you could determine if its a config problem or not. That's about all I can think of at the moment. Andy P