slaeshjag
¯\_(ツ)_/¯
We can't have USB 2.0 OTG and a 3.0 host port. The 3.0 port is the only OTG port the SoC supports.
Last edited by a moderator:
I would amend that to say:My ideal backside ports would be: - charging jack - full-size USB 2.0 + eSATAp - miniDP - wide microUSB 3.0 OTG + SlimPort
Good. That will stop anyone implementing such a stupid idea :wacko:Binky: AFAIK, USB3 pins = USB2 pins + extra USB3-specific pins. So no.
My Nexus One is only just now starting to have issues with the microUSB port. I think if the device had a better battery, that I wouldn't be having any trouble at all with it. And even now, it appears that the port is going to outlive the device as I'm starting to have some weird issues with the digitizer and random lock ups.Most people who have problems with it are having problems with it in their cell phones, which are devices they are plugging in daily. The average person has only owned 3-4 cell phones w/ Micro USB, since the acceptance of it as a somewhat standard for cell phones is fairly new. So your sample size of phones you have not had issues with is likely to be rather small compared to the number of phones out there.Mini USB is an obsolete standard which had several design issues and was dropped by the USB standard organization (for good reasons).
I have never had issues with Micro-USBs myself, so I am not sure why you guys have had bad experience with them. Maybe you went for cheap shit ?
-God Ginrai
Exactly. USB 2.0 host is more than adequate for a handheld device like the Pyra.or just insert it directly to the USB 2.0+eSATAp port and get "only" 35MB/s.
Just because you would not plug in a device with a large battery life daily does not mean other users will not. A lot of people will plug their devices in whenever they are not using them so that when they use it, they will have 100% battery, allowing them to use it for however long they need to.My Nexus One is only just now starting to have issues with the microUSB port. I think if the device had a better battery, that I wouldn't be having any trouble at all with it. And even now, it appears that the port is going to outlive the device as I'm starting to have some weird issues with the digitizer and random lock ups.
As long as you're mindful to put the jack in the correct side up and not force it, it might well outlive the Pyra. At any rate, if they opt to have the dedicated power cable, I see no reason why it's even going to be an issue. I rarely plug my Pandy in via the miniUSB.
I don't agree. That would not give us a way to get USB 3.0 speed when using the Pyra as a host. Also I don't think we have room for both a full size USB-A and USB-B port. And I don't think that micro-USB 3.0 is that flimsy, after all it is physically significantly larger than micro-USB 2.0.Exactly. USB 2.0 host is more than adequate for a handheld device like the Pyra.or just insert it directly to the USB 2.0+eSATAp port and get "only" 35MB/s.
As such, we don't need to include a flimsy microUSB port for OTG. We should just make it a sturdy, stable USB-B 3.0 port.
We don't need USB 3.0 speed for host. USB 2.0 speed is reasonably enough as it is.I don't agree. That would not give us a way to get USB 3.0 speed when using the Pyra as a host. Also I don't think we have room for both a full size USB-A and USB-B port. And I don't think that micro-USB 3.0 is that flimsy, after all it is physically significantly larger than micro-USB 2.0.Exactly. USB 2.0 host is more than adequate for a handheld device like the Pyra.or just insert it directly to the USB 2.0+eSATAp port and get "only" 35MB/s.
As such, we don't need to include a flimsy microUSB port for OTG. We should just make it a sturdy, stable USB-B 3.0 port.
So you would sacrifice the ability to have a USB3 OTG host because you don't like the connector? That seems incredibly short-sighted, and self-centred.We don't need USB 3.0 speed for host. USB 2.0 speed is reasonably enough as it is.
Also, please do a little fact-checking next time before you make comments about what we have room for. The microUSB 3.0 port that you seem so adamant about is wider than both the width and the height of USB-B 3.0. If there wasn't enough room for USB-B 3.0, then there surely would not be enough room for the microUSB 3.0 port.
-God Ginrai
Yes, because USB 2.0 Host is already adequate. You say that makes me short-sighted, I say that a blind demand for the faster speeds that USB 3.0 allows even though the connector is more likely to break is even more short-sighted. You want something that provides little extra benefit at the cost of quality of the connector.So you would sacrifice the ability to have a USB3 OTG host because you don't like the connector? That seems incredibly short-sighted, and self-centred.We don't need USB 3.0 speed for host. USB 2.0 speed is reasonably enough as it is.
Also, please do a little fact-checking next time before you make comments about what we have room for. The microUSB 3.0 port that you seem so adamant about is wider than both the width and the height of USB-B 3.0. If there wasn't enough room for USB-B 3.0, then there surely would not be enough room for the microUSB 3.0 port.
-God Ginrai
Actually, you just proved my point. If the cable falls out, then the cable is not damaging the device. Because of that firm grip on the cable that microUSB has, it tugs the connector off the PCB, which is why these connections are prone to breaking.I also don't get what makes you think the USB-B connector is so much better. My MIDI keyboard uses USB-B connector and the damn thing keeps falling out. It may be nice and secure for stationary items, but if you are moving your device around, it quickly loses its grip. My phone on the other hand uses a micro-USB connector and that always requires a firm tug to unplug.
I'm afraid I am unclear on what you are suggesting. Is it the port or the cable falling out? If the port is falling out, especially that easily, then it is likely a manufacturing defect. If the cable is falling out that easily, then it is likely that one of the two pieces, the port or the cable, is non-standard and not the right size.*shakes head* The limited amount of movement I subject my keyboard to, is enough to loosen the connector so much that the USB-B connector on the keyboard tends to fall out while I'm transferring data, not just when I'm moving the keyboard.
I'm not saying that it doesn't come out, but the resistance shows that it is pulling at the connector, which will slowly cause it to disconnect from the PCB.Also the MicroUSB cable does in in fact come out cleanly as it should if I do something stupid like walk away from the charger while it's plugged in. (I should know, I've managed to do that once or twice too) In any case the answer to that is just to anchor the connector firmly to the PCB, as Binky says, with through-hole tabs.
I want eSATAp (USB 2.0 Host + eSATA), USB-B 3.0, and some mini-hdmi or mini-displayport. (although I need more information about displayport, I'm not sure I would hook that to my TV)What are the two alternatives you are discussing, and is it the actual connector that breaks, or the solder joints holding it onto the pcb?
It's been all but confirmed to be the OMAP5 in the Tegra K1 topic.That is 4 ports total, which is within reason. Without knowing for sure what the SoC will be, what bus-es route to what, and where.
This Dockport thing looks interesting. But that would not be able to provide USB 3.0 slave (or gadget) mode, right? If so, it doesn't solve our problem. If it can, I would like to hear more about it. Also, it seems that TI is providing free samples for their Dockport chip. (http://www.ti.com/product/hd3ss2521) This is probably to encourage manufacturers to use it.How about assembling a list of combo ports instead?
There are some power+ usb stuff
There is the usb esata combo | Full usb 2.0 (only?)
mhl which doesnt have a required port, usually 5 pin microusb, sometimes 11 (proprietary samsung)
MyDP/slimport | microusb
Lightning Bolt/Dock port Im assuming | FullUSB, since its taking on video, there is extra space, but if there is only one fullport I prefer it over the esata combo
The latter being one that is not so known, so let me introduce it. Video, audio, power, and usb in one interface, royalty free. Backed by vesa, developed by TI and AMD.
Costs only a few dollars to implement. Costs a little bit of pcb space for an extra mux, as opposed to straight routing for video, but it also saves the space of the ports for those.
http://www.vesa.org/featured-articles/displayport-adds-dockport-extension-to-royalty-free-vesa-standard/ I need to read more myself
I don't see why we would need no USB 3.0 for host mode but we would need it for gadget mode. What do people use gadget mode for? To read/write data to/from their SD cards? In that case USB 2.0 speeds suffice, unless you have really fast SD cards. Did I miss something?We don't need USB 3.0 speed for host. USB 2.0 speed is reasonably enough as it is.I don't agree. That would not give us a way to get USB 3.0 speed when using the Pyra as a host. Also I don't think we have room for both a full size USB-A and USB-B port. And I don't think that micro-USB 3.0 is that flimsy, after all it is physically significantly larger than micro-USB 2.0.
Also, please do a little fact-checking next time before you make comments about what we have room for. The microUSB 3.0 port that you seem so adamant about is wider than both the width and the height of USB-B 3.0. If there wasn't enough room for USB-B 3.0, then there surely would not be enough room for the microUSB 3.0 port.
Yes you did. As we've pointed out numerous times, the USB 2.0 provided by the OMAP5 is host only. The only way to get USB slave mode through the chip is from the USB 3.0 OTG. I will not argue that USB 2.0 speeds would not suffice for USB slave mode. However, it is something the SoC simply does not provide.I don't see why we would need no USB 3.0 for host mode but we would need it for gadget mode. What do people use gadget mode for? To read/write data to/from their SD cards? In that case USB 2.0 speeds suffice, unless you have really fast SD cards. Did I miss something?