I have been trying to get MIDI working on SAMs USB without any luck
for awhile now and finally gave up.

For the past week I've tried to get SAM/OS4.1 to recognize my SanDisk
Mini Cruzer 512Mb - - no luck again. I have tried several 16/32 bit formats,
plugging in at various ports/hubs at different times and nothing.

I have also moved routines around as suggested in another thread - - nothing.

It is a 667MHz model.

Any ideas, suggestions, , anything ?

It also seems very fussy about keyboards, I have tried 3.

If I do a USBCtrl restart I get a message - Bad function call to - uhh something,,
if I have a mem stick plugged in.

I have Debian on a seperate HD and that has no problems with mem sticks.
I cannot try MIDI however since I do not see a usbmidi dev and, because the
kernel is monolithic I have no idea if it was built in.

So it dosen't look like a hardware problem,, but what do I know

Last edited by Mechanic on 09-Feb-2009 at 10:17 PM.

@Mechanic

I run into the same probs with my keyboard. I tested 2 (both from MS) and none worked.

Well, keyboards and mice use usb 1.1 (OHCI) and that driver isn't yet perfect. Remember that OS 4.1 for SAM is still in BETA and not completed.

Anyway, do what I did. Go at a computer store and buy a cheap keboard that does NOT need any EXTRA drivers installed. Most propably, that keyboard will work with your system since it is "compatible" by default.

Oh, and I also cannot get my Sansa clip mp3 player work under OS 4.1 .

_________________

@Cool_amigaN

Quote:

Oh, and I also cannot get my Sansa clip mp3 player work under OS 4.1 .

Yeah, you know what I'm feeling.

Maybe soon.

Just not sure how much I should put on this thing until the basic stuff is
working.

@Mechanic

At the risk of being called an idiot, may I just point out that the keyboard must be plugged into the top USB socket on the board? I misread the instructions on this point, so others may have done also.

The USB problems are acknowledged and being worked on. Because the hardware is different from the A1s, the drivers are new and there were (at the time of release) only a few betatesters with Sam boards.

_________________
cheers
tony

Hyperion Support Forum: http://forum.hyperion-entertainment.biz/index.php

@tonyw

Thanks Tony.

For my needs this system is fairly unusable right now, but I'm willing
to wait.

@tonyw

How helping the OS developpers with USB big problems ???

No program to catch informations about usb device we all have to be injected on aos4.1 ???

How an user could help aos4 developpers by betatesting for AOS4 his USB hardware ??

_________________
BTW, what you have done for the amiga today ????

-A1200+Mediator+VooDoo3+060/50+96mo+SCSI-KIT
-SAM440EP-667mhz-on MapowerKC3000+AOS4.1

Amiga Docs Disks Preservation Project

@Mrodfr
Quote:

No program to catch informations about usb device we all have to be injected on aos4.1 ???

There are the logging options in Prefs/USB and the T:usb.log file.

@ZeroG

True.
But if the powers that be are aware of the problem then log output is not
necessary. Besides, where would it be sent ?

@Mechanic

Perhaps I can help a bit..
Have you installed CAMD.library ? What version?
Have you installed USBMidi.lha? What version?
What kind of USB MIDI device are you trying to connect with?
What happens when you plug it in?
With your device installed, what do you see with Sys:Utilities/USBInspector under the "Functionality, Audio" tab?
What are the "Class", "Subclass", and "Driver" entries for everything you find in that list?

we should be able to figure this out pretty quickly with this information.
I don't have a SAM, (yet) and I'm still running 4.0, but the details I have asked for above will answer a lot of questions.

LyleHaze

(edit: post 666.. wonder if that means anything?)

Last edited by lylehaze on 09-Feb-2009 at 01:22 AM.

_________________
question=(2b||!(2b))

@ZeroG

OK. I will tests my USB hardware on SAM and catch the logs and will try to found someone for sending to output to him.

Last edited by Mrodfr on 09-Feb-2009 at 12:41 PM.
Last edited by Mrodfr on 09-Feb-2009 at 11:49 AM.

_________________
BTW, what you have done for the amiga today ????

-A1200+Mediator+VooDoo3+060/50+96mo+SCSI-KIT
-SAM440EP-667mhz-on MapowerKC3000+AOS4.1

Amiga Docs Disks Preservation Project

@Mechanic

The Logitech Wireless Desktop Pro 2400 (wireless keyboard and mouse) works just fine on Sam boards !

Laurent aka Faranheit

_________________
ZORAWSKI Laurent
Amedia Computer France
Your Amigadventurer
Mobile : (+33) 7 71 10 72 22
Fax : (+33) 3 87 57 07 21
Mail : laurent@amedia-computer.com
Site : http://www.amedia-computer.com
Site : http://faranheit.dyndns.org:8080/FPGA%20Arcade/
MSN

@lylehaze

You devil, trade you my (shoe) sole for working MIDI.

Lylehaze, Mrodfr, Faranheit,

I have been screwing around with this so much that yesterday I had to
reload OS4.1 and it will take some time to get all of the MIDI stuff
downloaded/installed. I'll get to work on that today. Keep in mind that
memory sticks, 512Mb SanDisk Cruzer, also do not work under OS4.1, but
do under Debian Lenny. And, I cannot check USB MIDI under Deb because
it 'looks like' it was not built into the kernel.

Here is some info I have right now.
Equipment;
Sam440ep 667MHz
Edirol UM-1X / UM-1SX USB MIDI Interface

Software;
CAMD 50.8
CamdTools 1.1
USBMIDI 50.1
zlib.library 3.2
jpeg.library 6.2a
HD-rec 0.9z
DG MIDI Player
Horny

When I had the MIDI drivers and software installed the USBinspector showed
it was using the usbmidi.driver. This is the output, right now, without
CAMD or USBmidi.driver up and running.They did show when they were installed.

Functionality;
Audio
-----UM-1
Product UM-1
Vendor EDIROL
Serial no unspecified
Version 2.0
Class Audio
Subclass 3
Driver none ( Will reinstall later )
Topology
-----Product no 0x0052
Vendor no 0x0582
Serial no unspecified
Version 2.0
Class Multiclass
Subclass 0
Mode Available
Driver (again not loaded at this time)

All the players seem to be sending to the UM-1, but it is not getting thru, no activity on the 'out' LED.

The Edirol worked on my uA1c and still works on x86 boxes.
The SAM sees it, HD-rec, Horny, DGmidi, Showkeys and MidiWatch all see it, but - - nothing gets thru.

Also, when shutting down HD-rec it pops up a error about not finding SYS:Prefs:midi. ??

A couple of other strange things. Only in my current OS4 load.

I disabled 'USBCtrl start' in S:Startup-sequence(USB still works) and if I
then 'USBCtrl start' from a shell it produces a full log in RAM:T.

If I do a 'USBCtrl restart', with a memory stick plugged in, the computer
locks up. It's fine without the stick in. The MIDI device has no problem.

Keep in mind mem sticks work fine under Deb.... so I don't think it's a
hardware problem. And I don't think it's usbmidi/CAMD either.

I was reading the docs



about assigning functions to keys (no Ramiga on one keyboard) and they say the
new info gets stored in ENV: ... Why is there no ENV: on the system as loaded

Later got to

P.S. I'll try the wireless keyboard/mouse ASAP.

@Mrodfr
MY usb log.

I: [06:28:18] USB stack | | ==========
I: [06:28:18] USB stack | | USB System Software Task started
I: [06:28:18] USB stack | | Starting HCDs...
I: [06:28:18] USB stack | | ...HCDs started.
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FF8FC80 is {Vendor: 0x0000, Product: 0x0000, Class: 09.00}
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FF8FE60 is {Vendor: 0x0000, Product: 0x0000, Class: 09.00}
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FF8FC80 initialized
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FF8FE60 initialized
I: [06:28:18] hub.usbfd | HUB | Device found on hub port 1.
I: [06:28:18] hub.usbfd | HUB | Device found on hub port 1.
I: [06:28:18] hub.usbfd | Hub port | Device at port 1 is low-speed.
I: [06:28:18] hub.usbfd | Hub port | Device at port 1 is low-speed.
I: [06:28:18] hub.usbfd | HUB | Device on hub port 1 succesfully added.
I: [06:28:18] hub.usbfd | HUB | Device on hub port 1 succesfully added.
I: [06:28:18] hub.usbfd | HUB | Device found on hub port 2.
I: [06:28:18] hub.usbfd | HUB | Device found on hub port 2.
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FDF70B0 is {Vendor: 0x6D04, Product: 0x15C3, Class: 00.00}
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FDF7010 is {Vendor: 0x6D04, Product: 0x18C0, Class: 00.00}
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FDF7010 initialized
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FDF70B0 initialized
I: [06:28:18] hub.usbfd | Hub port | Device at port 2 is full-speed.
I: [06:28:18] hub.usbfd | Hub port | Device at port 2 is full-speed.
I: [06:28:18] hub.usbfd | HUB | Device on hub port 2 succesfully added.
I: [06:28:18] hub.usbfd | HUB | Device on hub port 2 succesfully added.
I: [06:28:18] hub.usbfd | HUB | Driver Running
I: [06:28:18] hub.usbfd | HUB | Driver Running
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FDF7330 is {Vendor: 0x8205, Product: 0x5200, Class: 00.00}
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FDF71F0 is {Vendor: 0x8107, Product: 0x5051, Class: 00.00}
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FDF7330 initialized
I: [06:28:18] USB Fkt Init | Init Fkt | Fkt 0x5FDF71F0 initialized
I: [06:28:18] USB stack Process | | USB System Software Process started.
I: [06:28:18] USB stack Process | | Info logging disabled

@Mechanic
Quote:

Besides, where would it be sent ?

Good question.

For USB drivers that came with OS4.x you could send it to a OS4 betatester/developer, there are some in this forum.

For 3rd party USB drivers (midi for example) you have to contact the author of it.

This Apple Keyboard works with OS4.1 :
http://store.apple.com/uk/product/MB110Z/A

P.S. I don't know why this thread is labelled "Sam USB Problems", when it should be "OS4.1 USB Problems". AFAIK, OS4.1 supports same USB devices on different motherboards.

_________________
Author of the PortablE programming language.
It is pitch black. You are likely to be eaten by a grue...

@ChrisH

Quote:

ChrisH wrote: This Apple Keyboard works with OS4.1 : http://store.apple.com/uk/product/MB110Z/A P.S. I don't know why this thread is labelled "Sam USB Problems", when it should be "OS4.1 USB Problems". AFAIK, OS4.1 supports same USB devices on different motherboards.

It seems that the problem is only on the 667MHz Motherboard. AFAIK.

@Mechanic

I will do whatever I can to help you get MIDI working. You can even keep your shoes!

ZeroG is right, help for the MIDI stuff will have to come from the author.
I maintain CAMD now (with some help) and I wrote the USBMIDI driver, so you're stuck with me for MIDI help.

The UM1 has a driver select switch.. looks like you have it set properly already. Looks like your versions are up to date. (yes, it's basic, but I have to start there!)

Sys:Prefs/MIDI is not supported or needed by any OS4 version of CAMD. Be glad it's gone and DO NOT go looking for an old copy!

usbmidi and CAMD should be simple installs, I think I scripted them both... (it's been a long time). After getting them re-installed please run "showclusters" from the camdtools package. It's a shell command. It will respond with a list of all the clusters that are there. This will tell me if the system "sees" the MIDI interface.

Since usbmidi "autoloads" when the interface is plugged in... If you do NOT see the interface after booting. Try:
1> unplugging the interface
2> rebooting
then 3> plugging it back in after bootup is complete.

Then run "showclusters" again to see if it's been found.

Yes, it'a a bit of detective work, I'm just trying to determine what is working and what is not.

Thanks for helping me to check this out..

LyleHaze

_________________
question=(2b||!(2b))

@Mechanic

Quote:

I disabled 'USBCtrl start' in S:Startup-sequence(USB still works) and if I then 'USBCtrl start' from a shell it produces a full log in RAM:T.

If you require help with the system, it's an idea not to mess about with it. Firstly, do not disable the "USBCTRL Start" line in the startup sequence. This is required to unload the boot drivers for mouse and keyboard, and load the full driver sets for all supported devices. During boot, there are a minimal set of USB function drivers which are initialised, and these contain sufficient functionality to get the USB system running. USBCTRL informs the USB stack that the OS is now fully up and running, and the "proper" drivers can be loaded.

Without this, you are only running the minmal drivers, so it's hardly surprising that things are not working.

Secondly, in order to try to find out why your SanDisk is not recognised (apart from not complying fully with the USB specs), you would be required to supply an dump of what USBInspector sees with the device inserted, and also a USB.log dump of the attachment phase, so that the relevant information and debug info can be seen.

Simon

_________________
Simon

Comments made by me on any public fora are not representative of, or on behalf of, any company I may have, or assumed by the reader to have, any association with.

Any comments are a personal opinion, and should be accepted as such.

@rigo

Thanks for the method for checking USB hardware on SAM and make the outputs.

- Have you got some persons to be contacted for sending the outputs (aos team) ???

- All necessary informations are on the logs for having ,on the next AOS4 SAM version, our USB hardwares working ???

_________________
BTW, what you have done for the amiga today ????

-A1200+Mediator+VooDoo3+060/50+96mo+SCSI-KIT
-SAM440EP-667mhz-on MapowerKC3000+AOS4.1

Amiga Docs Disks Preservation Project

@Mechanic , @ lylehaze,

I have the same problem with my midi interface ESI M4U with my A One G4.

I had to appear for OS4 Final already the problem which the ESI M4U no longer detected, and to make contact with Lylehaze took.
We then everything CAMD concerns and found it most OS4 USB stack is located.

Under OS4 upd. # 4 the ESI M4U ran flawlessly with Camd.

My hope, with OS4.1 USB interface detects again, has unfortunately not been met.

I have currently contacted Cyborg, who offered me his help, my problem with USB Midi continue to lead because my English is lousy.

I will post if I find something new.

Gruß Peter

_________________
I write with a translator program, if something is not understandable, please ask me

A One XE G4 @ 1066 MHz - Wasserkühlung
SamFlex @ 800 MHz