Path: chuka.playstation.co.uk!news From: "Chris Wallace" Newsgroups: scee.yaroze.freetalk.english Subject: Re: Siocons under Linux Date: Sat, 10 Dec 2005 03:02:28 -0800 Organization: PlayStation Net Yaroze (SCEE) Lines: 146 Message-ID: References: NNTP-Posting-Host: cpc3-with3-3-0-cust26.bagu.cable.ntl.com X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.2180 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 I dont have my Yaroze with me, but if you havent solved it by the time I get home I might have a look to see if i can get it working. I'm running Fedora Core 3 with a 2.6 kernel. Chris "Andrew Partington" wrote in message news:dnc98u$2e52@www.netyaroze-europe.com... > Philippe Lorin wrote: > >> >> I checked my exe and connection under Windows. I tried several programs, >> and each of my two serial ports. I can run a simple "hello world", as >> well as some small game, with PsComUtil under Wine (at 9600 bps). The >> halting problem seems to occur only after a certain amount of data has >> been uploaded (with Invs, at 9600 bps, it happens about at the same >> place as at 115200 bps). >> > > It's a strange problem, and I just can't think what might be going wrong > - for me, it pretty much just worked straight away at 115200 bps. What > Linux distribution are you using? (I use Slackware 9.0 with a 2.4 > series kernel). I know it must be a pain at this stage but have you > considered switching distributions? > > Is there anything in your XF86Config (or xorg.conf) file in /etc/X11 > that messes with the serial port, e.g. settings for serial mice or other > stuff? If you do: > > $ less /etc/X11/XF86Config (or /etc/X11/xorg.conf), then when the file > is displayed, type: > > /ttyS0 > > this will find anything with the string ttyS0. Enter / on its own again > to repeat the search (or just use your text editor of choice, I just > find that less can be quicker to do stuff like that if you aren't going > to edit anything) > > >> >>> 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 >> >> >> I checked that, and root owns the port. As some communication does >> happen, this is presumably not a problem. However, I notice that where >> you get "uucp" I get "dialout" -- I have no idea what this mean, but >> could it be a clue? >> > > Possibly... I don't have a dialout group on my distribution so I > couldn't say for certain. You could try changing it to uucp and see > what happens (you can change it back easily enough if it doesn't work) > > as root (for com1): > > # chgrp uucp /dev/ttyS0 > > As you say it shouldn't make any difference since you do get at least > some comms working, but try changing the owner to your user ID. > > # chown /dev/ttyS0 > > If you're using a modem, you could try checking that the modem settings > aren't interfering with things (but how, I don't know, sorry) > > Another thing to try (which may or may not make any difference, > clutching at straws here): You can use this command to set the speed of > your port to 115200 > > # stty -F /dev/ttyS0 115200 > > >> >>> 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 installed Dosemu and set the serial ports up. Siocons begins the >> transmission but ends immediately with a "sync error". >> >> Btw there's an option to speed up the communications, I think it goes >> something like this: >> $_ports = "device /dev/ttyS1 fast" >> (see http://dosemu.sourceforge.net/docs/HOWTO/x246.html, and dosemu.conf) >> > > Yeah, I saw that option, it doesn't seem to have an effect for me > though. I seem to remember reading somewhere that that "fast" option > might only work with 2.6 kernels, but I can't find where I read that > anywhere. Perhaps if I built it from source... > >> >>> 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. >> >> >> Do you mean that you got HSSUtils to work provided you used >> mipsel-ecoff-strip? >> > > > Yeah, I had to run mipsel-ecoff-strip over the file it produced for it > to work with HSSUtils. This was when I built the code in the sample > directory on the Yaroze PC CD (the fastsprite bouncy ball demo), which > is pretty small anyway, i've not tried HSSUtils with anything else > because I didn't figure out how to make it read auto files (and I was > too lazy to write a script). So whether it fails for me when trying > larger files, I couldn't say. > > >> Next I'm going to try Kenny Millar's PsxComm (there are a lot of Siocons >> replacements out there!); I'll post my results here... >> (http://www.netyaroze-europe.com/~kmillar/) > > PsxComm doesn't work for me either. > > The only thing I can think of for now is if you ask over at > www.linuxquestions.org. If I think of anything else i'll post it here. > > Hope you get it sorted (and if not, there's always SDL/OpenGL to play > with!) > > > > Andy P