index   prev   next RISC OS Notes


# USB fundamentals

Type A plugs and receptacles (socketS) are flat Type B are chunky - eg printer cables at device end

#USB charger

... a USB host can be connected to the USB interface on handset either for battery charging or data transmission purpose. How can the handset distinguish a USB port from a power adapter and be able to select the right input current limit? The regulation requires that the power adapter to have both D+ and D- line be shorted together inside the charger. When the data lines are not shorted, the handset will recognize that the source is a USB port and thus will limit the input current to maximum 500mA in order to conform to the USB standard.

# *help usb. -- gives lots of info

USB ambiguous disc name - cure:_ > *rmreinit scsifs (alias *jrkick) A9 look in IDEFS::HardDisc4.$.!Boot.Resources.!USB.bin for some * commands that give info:- *usbdevices *usbshowmod *usbobjects A9 look in IDEFS::HardDisc4.$.!Boot.Resources.! for some other * commands that give info:- *USB_Lib *Sup_Lib *ShowInfo2 - **similar info to usbdevices but better layout *ShowInfo *RestartLog *Overview *BootApp *Analyzer A9 the module USBHUB has *help usbhub => Help on keyword USBHub (Module) Module is: USBHub 2.15 (24 Feb 2006) (c) Simtec .. 2001-2005 Commands provided: USBHub_Install USBHub_DeviceReset USBHub_List USBHub_PortPower USBHub_Log USBHub_LogClear USBHub_Log - gives useful information A9 the module USBHID_Input has *help usb_hidinput => Help on keyword USB_HIDInput (Module) Module is: USB HIDInput 2.15 (24 Feb 2006) (c) Simtec .., 2002- 2005 Commands provided: USBHid_Devs USBHid_Log USBHid_LogClear *USBHid_Log - starts the log

# A9 stuff

Plug in the device and in a task window, type *usbdevices to see if it is listed (vendor and product id should match what your Iyonix says they are) to check that they are being detected. Assuming they are mass storage types then !MassFS should work with them, if they're not being added to the icon bar then try running !MassFS manually (in !Boot.Resources) If you still have no icons then you might have to add them and fiddle with some flags in the OtherDevs file inside MassFS, instructions for this and plenty of examples are included at the top of the file. Suggest that you set read only or copy your data off while experimenting! Let me know how you get on please. A9 MassFS compatible cards/pendrives: FAT16: -reading/writing is ok on the A9home and you can transfer files to and from a PC -transferring files to the Iyonix is possible but it usually corrupts the filenames. FAT32 reading/writing ok on the A9home but you can't transfer files to or from a PC (files written on the A9home won't appear on the PC - also files written on the PC won't appear on the A9home.) NEVER FORMAT a card under WIN XP !! (winXP can't format FAT16 and will initialise the card as a FAT32 device.) Filecore formatted disc: If you initialise a USB card/pendrive on the Iyonix with !SCSIformat you can read/write such a device on the A9home (but you have to use the flag 'F' in your OtherDevs file.) Clicking on a filecore formatted disc on the iconbar will then open MassFC::name.$ I have tested this with cards up to 8GB. IF you have problems reading or writing on a MassFS device most of the times the device has been formatted as FAT32. Use !USB-util or the 32bit compatible MkDosDisc utility to initialise the card as a FAT16 device. -- Kees Meijer A9Home user

# pinouts and voltage

look into FEMALE usb with white block on top pins are 1-4 left to right 1 +5v 2 data + 3 data - 4 gnd sample MALE plug from dead mouse lead with white underneath L-R lead 1 white 2 blue 3 green 4 red 4.0v iyonix 4.0v compaq 4.0v 4-port hub 5.1v freeloader (charging) 1.1v freeloader (not charging)

© JR 2013