Pi Isochronous ROM

Can either of you tell me what

*show USBScanner$path 

shows.

Chris. Did it give an error message?

After launching DPingScan, opening its window and hitting F10 to acquire the scanner, *show USBScanner$path gives the following:
USBScanner$Path : USB5#usbtimeout40000; size16384

I haven’t tried to use Preview or Scan options.

Error line reads:

mod init doneError: Not enough memory, stack overflow (Error number &80000021)
*

no flashing cursor, keyboard not working

Would any of you like to try this version PiIsocRom.zip

Sorry, Colin: *show USBScanner$path shows exactly the same timeout error as my earlier post, testing with the latest ROM. I tried Preview: it froze the machine, forcing a switch-off reboot.

Scanner$path isn’t an error it’s the file name that is opened to read and write to the device. It dawns on me that it may be frozen waiting for a time out. The timeout is 40 seconds. Do you get control back after 40 secs? If not it may be because you are getting a series of 40 sec waits. If you don’t get control back after 40 secs if you do

*set scanner$path USB5#usbtimeout40; size16384

Where USB5 is the same usb number as the existing scanner$path – this will give a shorter timeout.

This won’t fix anything but if if you can get control back after scanning I can post a version which will output diagnostic data so that I can see what it is doing.

Did a new test with scanner connected directly to the Pi rather than via a powered hub (hence the different USB address below). Without changing anything, control didn’t return after 40 (or 60) secs. I then did the *set scanner$path command for a shorter timeout, but the command didn’t affect the *show USBScanner result: see task window output below:
*show USBScanner$path
USBScanner$Path : USB3#usbtimeout40000;size16384:
*set scanner$path USB3#usbtimeout40; size16384
*show USBScanner$path
USBScanner$Path : USB3#usbtimeout40000;size16384:
*

Ok George 1 last try. I’ve reverted the USB front end to the ROOL version so it should work. I’ve made it output diagnostic info so I can see what is happening. So can you try PiIsocRomTest.zip, The readme file tells you what I want you to do.

Thanks.

Surely: -

*show USBScanner$path
USBScanner$Path : USB3#usbtimeout40000;size16384:
*set scanner$path USB3#usbtimeout40; size16384 <— should be USBScanner$Path
*show USBScanner$path
USBScanner$Path : USB3#usbtimeout40000;size16384:

Colin: ‘The readme file tells you what I want you to do.’ Done :-)

Unfortunately, my 24v scanner psu has been packed away and I dont know when I will find it, so I couldn’t add to the testing results.
I’m guessing scanning on the Iyonix will be faster, due to the better disc writing though.

The USB audio has not missed a beat (or added pops or crackles so far) using SDFS, a local usb stick, or sharefs as a source for the wav’s.
I have been using the cheapo ‘3D SOUND’ dongle at the
usual 44.1 rate.
Simultaneous file transfers are possible, all in all a good result and the Rpi will probably be my preferred player for sending music to my analog amplifier.
I have a USB-EthernetCable-USB extension that I have tested OK previously on the Iyonix to try out sometime.
Thank you

Colin: would it help to have the *dadprint logfile for a successful scanner acquisition (i.e. under a ‘standard’ non-isochronous ROM)?

Wasn’t the log file you sent me a result of a successful acquisition? Doesn’t the test rom work normally with the scanner?

Er, yes! You can blame me for being excessively literal-minded – the instructions accompanying the latest ROM said ‘acquire’ the scanner then run the logfile – not ‘acquire and use’…. So, sorry for the confusion. But congratulations for solving the problem!

But congratulations for solving the problem

:-) except I haven’t. I reverted to ROOL’s USBModule file which removes the Isochronous/OS_GBPB changes from that file. I did discover that timeout doesn’t work though which is why my version freezes your machine. I know where the problem lies (OS_GBPB) but can I see why my version doesn’t work – No.

Now I /am/ confused. Using your latest ROM, it takes 8 secs to write an 11MB PDF over LM98 to a shared PC drive. Reverting to the ROM as supplied with my copy of RO5.21 dated 25-Feb-14, it takes 12 minutes(!). If this is what you call ‘not working’, all I can say is, the ‘working’ version will be quite something :-).

:-) USB consists of a lot of parts. Most of the changes I’ve made were left in for the test rom so USB ethernet for example is unchanged and you have fast ethernet. The bit I changed for the test rom disabled USB audio so at the moment you can have the USB scanner or USB audio but not both.

Would anyone like to try PiIsocRom.zip

I’ve fixed George’s problem with the scanner not working so it should work with scanners.

I find it only plays properly on a cheap USB1 16 bit usb device. My high res device is prone to crackles.

Please read the readme file.

Latest PiIsocRom working fine here. I didn’t need to enable the ‘AddToRMA 256K’ line in !Boot.Utils.BootRun. The scanner works. Transfer speeds accessing a networked PC shared drive from the Pi’s USB card:
copying to PC drive = c.2MB/sec; copying from PC drive = 1.5MB/sec.

Colin

I can confirm the latest PilSocRom is working ok here as well and I can use my scanner and for the first time my UCA202.

Just in time for the next MUG meeting this Saturday for a demo or two.

Thanks

Doug

So far only Doug and myself seem to have sent back testing input to Colin on the latest ROM. It would be nice if some of the other posters to this thread gave some time to the testing of what is a very substantial and welcome upgrade to the Pi’s performance (which raises networking speed from ‘atrocious’ to ‘pretty good*’ in one step). Apologies to anyone communicating test results directly to Colin!
[*by RISC OS standards]

I test the ROMs but I not have a scanner. At the first view I don’t see any changes.
At the second one, today morning it looks like the USB- and UMTS Stick handling is better.
I must do any more special things, e.g. USB audio but I have not enough time:-(

I have any problems with fat32fs and USBSticks. A 512MB and a 32GB FAT formatted freeze the RPi. If I kill fat32fs before, the 512MB works.
With the original RC12 ROM no problems with the Sticks.

I think I experienced some more general problems until I made running !USBModule the first job. Colin may say wether this is necessary when using PilsocRom.
I noticed that Fat32fs that came with this setup is not the latest version, though this probably wont help your problem.

Further audio tests have shown that my 48000 cmedia dongle plays back with constant low volume crackling, as expected.
The USB RJ45 Extension adapter can not only work well over a distance,
but it very noticeably cuts out (psu?) hum from my 44100 cmedia device.
There are dedicated usb isolater dongles available that are aimed at this sort of thing,

http://www.ebay.com/itm/141158966479?ssPageName=STRK

I dont know wether they would be needed when using an external psu/dac but it is possible they would benefit too.
The $5 USB RJ45 extender seems to be doing this job for me.

Sorry, I forget, I use the latest version of fat32fs I know and the latest daily ROM version works without this problems… try ModellA with my Lapdock (SchlepPi)