Pi Isochronous ROM

Would anyone like to try this ROM (PiIsocRom.zip) on their raspberry pi – please read the ReadMe file). I’ve added isochronous support but would be interested if anyone had any problems with it in general ie any mouseclick or keypress problems.

If you are inclined to try a usb audio device this is my findings.

My cheap non asynchronous device seem to work ok – it only works up to 44.1/16. However using it on the same hub as the mouse or keyboard (ie some other USB1 device) causes one or other USB1 device not to work properly – looks like a problem with split transactions.

My usb asynchronous device has the odd crackle at any speed but being USB2 doesn’t cause problems when plugged into the same hub as USB1 devices.

I’ll try that when I get back from vacation. Monday or Tuesday, I promise ;-)

I have try your ROM with my SchlepPi. It is a Modell A on a Lapdock.
It was a short try with the old IsocRecorder and -Player from my xM and Panda. The recorded sound crackles very loud, a old wav-file is played without crackle. I hope I have a little bit more time next few days and I can try any more with different settings.

A very good side-effect… this Problem https://www.riscosopen.org/forum/forums/11/topics/1893#posts-22533 is fixed with your “Pi Isochronous ROM”. The upload speed to my NAS is now comparable with my xM and Panda. No crash with bigger files…

Well it’s good to see I’ve fixed one problem.

Can you record if the USB device is on a hub on it’s own?

Are there restrictions on the use of the ROM? Another German user wrote to me yesterday that his RPi freezes during boot up. He wanted to test the ROM in its network. I mean he has an old Model B (256MB). Not sure witch distro, possible RC8 Until now I have no answer yet.

Are there restrictions on the use of the ROM?

No I think it should work on any RPi.

Does the module initialisation complete ie does the RPi backdrop appear?

If so did he alter the boot file as noted in the !Readme File?

!Readme – yes.
It looks like a “keyboard/mouse” or “USB” – problem. It boots to the desktop but Mouse and keyboard not working, network also not. The LEDs are red normally any of them are green or off.

Sounds like USB not working at all. Does the latest beta pi rom from ROOL (here) work?

Sorry, it was a old Debug-DWCDriver in Predesk. The new ROM is working now but it looks like not with the same results in his network

:-(

has he tried a RC12a img with my ROM – that’s what I am using.

The RC12a image has updated firmware which might be important.

Maybe the “FIQ fix” that Jeffrey did recently is playing a part here, too, Raik?

Colin, I can’t try your ROM (no hardware) but great work!

I can confirm that writing from a Pi to our Iyonix is now almost as quick as PandaRO to Iyonix.
Writing from the Pi to a NAS or a Windows PC with LanMan98 remains slow i.e. about 2% of the speed of to an Iyonix.

I’ll do some tests transferring to the Pi when I can find the time.

I once tried something besides my work … Everything with LapDock, model A and LindyEther; 100MB file, and min. 3 runs

RC12, original ROM
Access to FAT USB stick and HD works
FTPc → NAS, RISC OS hangs after about 2 minutes and 30MB (varies slightly)
ShareFS → ARMini >30min

RC 12, Colins ROM
Access to FAT USB stick and HD does not work, system freezes
(I noticed yesterday as I should sort holiday pictures.)
FTPc → NAS approx 35s
ShareFS → ARMini >20min

RC12a, original ROM
Access to FAT USB stick and HD works
FTPc → NAS system hangs after about 2 minutes and 30MB (varies slightly)
ShareFS → ARMini >30min

RC 12a, Colins ROM
Access to FAT USB stick and HD now works
FTPc → NAS approx 35s
ShareFS → ARMini >20min

If the transfer of 100MB with the normal RCs worked in the past, which was not often, then it takes min. 15 minutes (usually more).

If I find time I’ll try the same things on my network also again with Model B or B+ with the “build in” LAN.

Would you like to try PiIsocRomTest/zip. I’ve just disabled the FORCE_SHORT_TRANSFER flag. It should show if that is causing the problem.

I hope this evening if I back at home. I am a bit busy with non-RISC OS work.
FORCE_SHORT_TRANSFER – I have read in the past (for Linux) and think (not sure) that Thomas play around with this in one of his debug-attempt as he try to find the reason for the “upload-problem”. One of his Debug_DWCDriver are working better in my Network as the original.

Sorry, it was a long working day, yesterday.
I the morning I try any thinks.
Summarized: copy one 100MB file
FTPc: xM —> NAS 35s
Pi (A, new ROM) —> NAS 35s
NAS —> Pi (A,B RC12a) 1 minute
RPi(B, RC12a) —> NAS 15 minutes
ShareFS: Panda —> xM 4 minutes
xM —> Pi(B, RC12a) 1 minute
RPi(B, RC12a) —> xM 27 minutes

I wouldt try your new ROM with my Keyboardcomputer. Is a old RPi Rev. B inside. But your ROM is not working (RC12a works) the init fails after
*init mod UnSqueezeAIF
*modinit error: Not enough memory, stack overflow (Error Number &80000021)

Ok so no change then. Thanks for testing it.

Thanks for your work. It is more as I can do.
I will try also with a new B or a B+ and with the audiostuff I’m also not ready yet. Time is missing
Note to the last Audio try: Normally I record to SDFS. Maybe the results are better if I record to the RAMDisc…

Don’t worry about the audio you appear to be getting similar results to me.

Anyone know how to use !omni with windows 8 (windows 7 should be the same) if I can test slow transfer speeds from here it may help. Never used omni before.

Colin: If a copy of LanMan98 would be of help please drop me an email at chris@cjemicros.co.uk

I eventually got lanman working connecting to my laptop – I needed to disable passwords. Unfortunately it didn’t help as upload speed from the pi was identical to the upload speed from my Iyonix (very slow at about 100KB/s)

I can’t recall anyone reporting having problems with the speed of LanMan or LanMan98 on an Iyonix before. Has anyone else seen this?

Anyone know how to use !omni

I have problems with Omni. Shows up the shares after a while, then fails dismally to connect. LanMan98 is more effective, IMHO, but at £40 odd, is not everyone’s ideal solution.

The data below is writing to a wireless laptop.

Using the normal Iyonix interface Lanman98 is fast (around 15 secs to read and write a 15MB file)

Using a Pluggable USB Ethernet adaptor on an Iyonix its slow (around 11 mins to read and write the same file).

On a pi using the internal usb ethernet it reads the file in about 20secs but writes it in about 13 min.

On the pi using the plugable adapter it reads and writes in about 13min

To me this shows that the backend of EtherUSB for the plugable adapter is slow for reading and writing and the backend for the pi’s internal adapter is only slow writing. It doesn’t seem to be a pi specific problem.

I should point out that everything appears fine using the internet with any combination. Pi networking is slightly slower.

Anyone disagree with the above findings or anything to add?