DMESG output....
PM me if you think you can help out...
Think of this as an open 'team' invite, not looking for an answer to specific question.
musb_hdrc: hw_ep 7rx, max 512
musb_hdrc: hw_ep 8tx, max 512
musb_hdrc: hw_ep 8rx, max 512
musb_hdrc: hw_ep 9tx, max 512
musb_hdrc: hw_ep 9rx, max 512
musb_hdrc: hw_ep 10tx, max 512
musb_hdrc: hw_ep 10rx, max 512
musb_hdrc: hw_ep 11tx, max 512
musb_hdrc: hw_ep 11rx, max 512
musb_hdrc: hw_ep 12tx, max 512
musb_hdrc: hw_ep 12rx, max 512
musb_hdrc: hw_ep 13tx, max 512
musb_hdrc: hw_ep 13rx, max 512
musb_hdrc: hw_ep 14shared, max 1024
musb_hdrc: hw_ep 15shared, max 1024
musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
TCP established hash table entries: 65536 (order: 7, 524288 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 65536 bind 65536)
TCP reno registered
NET: Registered protocol family 1
checking if image is initramfs... it is
Freeing initrd memory: 176K
dspbridge_init: 600000 bytes @ 81200000
boxer_wifi_init: start
Enabling VAUX for wifi
omap-iommu omap-iommu.0: isp registered
NetWinder Floating Point Emulator V0.97 (double precision)
ashmem: initialized
msgmni has been set to 976
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
OMAP RFBI rev 1.0
OMAP DISPC rev 3.0
OMAP DSI rev 1.0
Enabling power for LCD
spi_probe mode : 0, per_word 16, chip_select 0, speed 375000, master_bus 4,master_cs 1
brd: module loaded
loop: module loaded
Linux video capture interface: v2.00
omap-previewer omap-previewer: omap-previewer: Registered preview wrapper
omap3isp omap3isp: Revision 15.0 found
omap-iommu omap-iommu.0: isp: version 1.1
Saving csi2 context
Restoring csi2 context
Saving csi2 context
i2c /dev entries driver
DSP Bridge driver loaded
Driver 'sd' needs updating - please use bus_type methods
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci_hcd: block sizes: qh 128 qtd 96 itd 160 sitd 96
android init
android_probe pdata: c04a77f0
android_bind
android_bind_config
mass_storage_function_add
fsg_probe pdata: c04a8244
android_usb gadget: Number of LUNs=2
adb_function_add
android_usb gadget: android_usb ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: default language 0x0409
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.29-omap1 musb-hcd
usb usb1: SerialNumber: musb_hdrc
usb usb1: uevent
usb usb1: usb_probe_device
usb usb1: configuration #1 chosen from 1 choice
usb usb1: adding 1-0:1.0 (config #1, interface 0)
usb 1-0:1.0: uevent
hub 1-0:1.0: usb_probe_interface
hub 1-0:1.0: usb_probe_interface - got id
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
hub 1-0:1.0: standalone hub
hub 1-0:1.0: individual port power switching
hub 1-0:1.0: no over-current protection
hub 1-0:1.0: power on to power good time: 10ms
hub 1-0:1.0: 100mA bus power budget for each child
hub 1-0:1.0: local power source is good
hub 1-0:1.0: enabling power on all ports
input: TWL4030 Keypad as /devices/platform/i2c_omap.1/i2c-adapter/i2c-1/1-004a/twl4030_keypad/input/input0
input: gpio-keys as /devices/platform/gpio-keys/input/input1
cyttsp_init:Cypress TrueTouch(R) Standard Product
cyttsp_init:I2C Touchscreen Driver (Built Mar 29 2011 @ 13:26:30)
cyttsp_probe:Reseting TMA340
cyttsp_probe:Start Probe 1.2
cyttsp::found BL, Overriding maxx & maxy
cyttsp_initialize:cyttsp-i2c: Register input device
input: cyttsp-i2c as /devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0022/input/input2
cyttsp_initialize:cyttsp_initialize: Create sysfs_group successfully!
cyttsp_probe:Start Probe PASS
cyttsp_power_on:BL101: f=00 s=11 err=00 bl=010B bld=010B R=16
cyttsp_power_on:BL102: tver=1100 a_id=AA1D aver=0006
cyttsp_power_on:BL103: c_id=C0C1C2
cyttsp_power_on:BL104: f=04 s=00 err=00 bl=0000 bld=0000
PM Sent.
If this is what I think it is, I am pretty excited
If you get this working, you get a cookie.
is this usb host?
If you mean you enabled OTG mode in the kernel config, it's not that easy.
I was not able to get vbus out of it for example.
Also forced host mode patches from N900 guys are a pain to apply to the newer driver in .29 kernel from B&N.
I am playing with it separately, but that project is on hold for now until I get microUSB-A cable. It's probably not strictly necessary, but seeing all the troubles N900 guys went through without it I better wait. Should arrive next week.
I suggest posting your changes on github and letting others help rather than posting dmesg and asking for PMs.
So here's where I'm at. My USB keyboard shows up in kernel messages. Doesn't actually do anything yet, but as soon as I saw it was enumerated I decided to call it a night.
No vbus, using a y cable to supply power from wall wart.
No kernel source as I made no changes to dal's kernel yet.
Just wanted people to know it was/ is/ will be possible.
Sent from my Desire HD using XDA App
Still lots of issues to solve but, USB keyboard works. Going to upload a YouTube video in a few.
Sent from my Desire HD using XDA App
dalingrin said:
I suggest posting your changes on github and letting others help rather than posting dmesg and asking for PMs.
Click to expand...
Click to collapse
Off topic, but what happens when your thanks meter fills up? I think it means you win at life, and get a free pony of your choice but what do I know...
hololight said:
Still lots of issues to solve but, USB keyboard works. Going to upload a YouTube video in a few.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Very nice, congrats on the accomplishment! Looking forward to what all this brings....
http://www.youtube.com/watch?v=DhNz5OFmSkw&sns=em
Nicely done.
Nicely done Hololight...
It will rock when Evergreen gets real OTG working. I'd love to have OTG up and working and also a displaylink framebuffer driver.
A Pico projector working on the Nook Color would be pretty sweet.
This is great news!
this plus the work on nookbuntu makes me happy =P
I am really looking forward to this working. I have a nice powered usb docking station I picked up at a yard sale today for 75 cents. A couple usb ports plus ps/2 ports, serial, parallel, ethernet, and usb transfer ports.
Could this be the way we finally get audio input? Add a usb webcam and you've got skype video calls.
technicalsquash said:
I am really looking forward to this working. I have a nice powered usb docking station I picked up at a yard sale today for 75 cents. A couple usb ports plus ps/2 ports, serial, parallel, ethernet, and usb transfer ports.
Could this be the way we finally get audio input? Add a usb webcam and you've got skype video calls.
Click to expand...
Click to collapse
Anything that has drivers should work at this point, but ihave only tested a keyboard. At the moment I am mostly concerned with getting vbus up (followed by 'otg'-like functionality) . There is little to no chance of automatic switching between host and device, but I'd be happy with an app to trigger state changes.
Also on a side note, no vbus could be viewed as a feature by some, as the nook will charge while using the y cable.
Wow, congratulations!
Sent from my NookColor using XDA App
Spoke a bit too soon I guess. Just tried a flash drive; while it was detected, it was not configured as the kernel thinks there is 'not enough power'.
Basically either vbus needs to be fixed, or there will need to be a work around so that the kernel believes it has current available.... average wall charger is 500ma, so i'd go with that. I think usb spec is 500ma anyway.
Chris
Careful with that Y-cable.
When I tried that approach, I got my nook usb port fried on about third try.
verygreen said:
Careful with that Y-cable.
When I tried that approach, I got my nook usb port fried on about third try.
Click to expand...
Click to collapse
How did that happen? Since V+ is being connected to the normal charge circuit, shy of shorting V+ to the data lines I can't see what you could have done.
hololight said:
How did that happen? Since V+ is being connected to the normal charge circuit, shy of shorting V+ to the data lines I can't see what you could have done.
Click to expand...
Click to collapse
I am not entirely sure what caused it either.
I had a patch to enable certain twl4030 properties that were more suitable for host mode (+ forced host mode via the sysfs mode setting + force ID pin in twl4030-otg link state detect).
then plugged in a keyboard into Y cable (from my usb harddisk), one side of the Y cable going into my usb hub (unpowered), another into a keyboard and third into the nook.
Since then I am a little bit worried about replicating this experiment.
Do I get it right that you just enabled usb host + OTG mode in the kernel config (.32 I assume?) + Y cable and it sort of works without any kernel changes?
I really don't want to go through nook replacement again
Related
Hi,
I know this may sound similar as I've seen a couple of posts about USB audio streaming with the Android-powered device under USB Host mode. However, my question is more specifically about audio streaming from USB device to host with USB Audio Class(UAC) under USB Open Accessory Mode.
I've heard that it is confirmed to be supported and I'm interested to know whether there is anybody who have heard of any news (or rumors?) about the release date of USB Audio class support when the Android-powered device is put into USB Accessory mode. By support I mean that the Android-powered device would respond to a request to open USB isochronous endpoints for UAC traffic.
Ken
Android does not support ISOC Endpoints yet. There has been no mention of Audio Class. I dont think streaming audio from device to host is not supported yet. But I would be happy to see that too.
Hello!
I want to develop a peripheral device to connect to an android phone via USB OTG. The OTG specs [1] says: "A Targeted Host shall provide sufficient power to each peripheral on its TPL in at least one supported configuration".
Where do I find those TPL ("Targeted Peripheral List") lists? I searched at Sony Ericsson (because I have a Xperia Mini) and Samsung (as a different manufacturer) but with no luck. Is this an android related list?
On github I found a code fragement [2] from DooMLoRD. It mentions a OTG whitelist. But it seems to be something like a skeleton.
I do this research because I want to use the peripheral device in high power mode with about 300 mA. I thought I could compare the TPL with devices that also need 300 mA.
Thanks in advance for any help,
Michael
[1] usb.org/developers/docs/usb_20_071012.zip
[2] github.com/DooMLoRD/Xperia-2011-Kernel-2.6.32.9/blob/master/kernel/drivers/usb/core/otg_whitelist.h
rhododendronbusch said:
Hello!
I want to develop a peripheral device to connect to an android phone via USB OTG. The OTG specs [1] says: "A Targeted Host shall provide sufficient power to each peripheral on its TPL in at least one supported configuration".
Where do I find those TPL ("Targeted Peripheral List") lists? I searched at Sony Ericsson (because I have a Xperia Mini) and Samsung (as a different manufacturer) but with no luck. Is this an android related list?
On github I found a code fragement [2] from DooMLoRD. It mentions a OTG whitelist. But it seems to be something like a skeleton.
I do this research because I want to use the peripheral device in high power mode with about 300 mA. I thought I could compare the TPL with devices that also need 300 mA.
Thanks in advance for any help,
Michael
[1] usb.org/developers/docs/usb_20_071012.zip
[2] github.com/DooMLoRD/Xperia-2011-Kernel-2.6.32.9/blob/master/kernel/drivers/usb/core/otg_whitelist.h
Click to expand...
Click to collapse
found this, don't know if it will help in reference to USB OTG Dual mode:
"• The USB port must be able to deliver a minimum of 8 mA for a configured or unconfigured
device, and optionally, up to 500 mA for a configured device."
http://ww1.microchip.com/downloads/en/DeviceDoc/39721b.pdf
this is just one mfg though... for whatever it's worth.
You have any sucess with this?
I've been using my usb otg to charge mini peripherals successfully like a bt headset, keyboard, mouse, sony liveview, bluetooth pen... and it seems to go relatively fast in each case surprisingly.
From the other threads I have read, other android devices have had USB ethernet working, but they didn't go into details, as it should 'just work'. My end goal is to allow my phone to access the internet at work using a wired connection to my windows workstation running internet connection sharing.
I have a working Monoprice 100mbit USB adapter (id = 6150) using the well known linux compatible asix AX88772 chip
I have tried connecting the adapter directly, and with a powered USB hub. Same result. USB thumbdrive with hub works, so the cables all work.
I get the following dmesg pastebin.com/mdttaDmq which looks hopeful, as it detects the ASIX chipset no problem.
I ran adb netcfg while adapter connected, but there is nothing new there... pastebin.com/7nN5MY08 (shouldn't an eth0 or usb0 show up?)
I have a Galaxy S3 i747M stock 4.0.4 ICS rooted, any help would be greatly appreciated
one of the articles mentioning it just working,
http://forum.xda-developers.com/showthread.php?t=1792245
Solved my own problem since I got no hits.
http://forum.xda-developers.com/showthread.php?p=37548841#post37548841
Just received my Nexus Player today, and I can confirm that there is some level of driver/hardware support for USB Ethernet adapters over OTG. Hardware-wise, I have an OTG cable attached to a D-Link USB 2.0 hub, and a Cisco 10/100 USB Ethernet adapter attached to the hub.
Some notes about the behavior:
The IP address configuration happens automatically if you're using DHCP on your network, but there are no options in the initial configuration to enter static IP addressing. If you're unboxing and setting up your Player for the first time, just make sure to have your USB Ethernet adapter plugged in before plugging in power.
Aside from lacking configuration options, everything appears to work flawlessly, and the Player automatically downloaded an update from Google on first boot.
Hope this helps.
Good to know... thanks!
I bet you can figure out the MAC address, and assign an IP address through the router. It's better that way anyway.
Sent from my Oneplus One with Tapatalk Pro.
Wondering if a USB 3.0 hub with gigabit Ethernet will work on Nexus player.
The specs of Nexus player is USB 2.0, by connecting a USB 3.0 hub with gigabit Ethernet, will it work by capping at 480mb/s USB 2.0 transfer rate?
I doubt you would get the full 480mbps but you should be able to do better than 100mbps.
Sent from my Nexus 5
dongdong said:
Wondering if a USB 3.0 hub with gigabit Ethernet will work on Nexus player.
The specs of Nexus player is USB 2.0, by connecting a USB 3.0 hub with gigabit Ethernet, will it work by capping at 480mb/s USB 2.0 transfer rate?
Click to expand...
Click to collapse
i dont think it would make a difference, besides 10/100 is way enough to stream even 4k media
please give a update for amkette evotv..
Details
Operating System:
Android 4.0.4 ICS
User Interface:
EvoView
Processor:
Arm Cortex A9 + ARM MALI 401/ XBMC enabled
RAM:
DDR III 1 GB
In built Memory:
4GB
Wifi Hotspot:
Yes
VPN:
Yes
3G Dongle Compatible:
Majority of dongle supports
Video Output:
HDMI 480p, 720p, 1080p (50/60Hz)
Audio Output:
Stereo L/R , 7.1 Digital Audio using HDMI, Digital SPDIF Coaxial output
USB Ports:
Four USB 2.0 ports
Card Reader:
SD/MMC Slot for storage expansion
Network Sharing:
Internal Wi fi - 802.11 b/g/n Ethernet 10/100 Base-T Ethernet
Networking:
uPnP (DLNA), Samba Share (Windows)
Graphics Processor:
Arm Mali 400
Power Input:
12V 1.5A -- 110-240VAC
Weight & Size:
277 gm, 26 mm(H) x 118 mm(W) x 118 mm(D)