232 - serial - USART - UART - Nexus One Q&A, Help & Troubleshooting

anyone know if there is a serial port hidden anywhere.
The PSP has one in the earphone jack and the iphone has on pinned out in the connector.
I searched high and low for the Nexus One pinout/schematic cant find it.
(probably right in front of my face)
I did see /dev/console and /dev/ttyHS0 and console but I dont know what that is.
Any pointers would be appreciated.

d1mbu1b said:
anyone know if there is a serial port hidden anywhere.
The PSP has one in the earphone jack and the iphone has on pinned out in the connector.
I searched high and low for the Nexus One pinout/schematic cant find it.
(probably right in front of my face)
I did see /dev/console and /dev/ttyHS0 and console but I dont know what that is.
Any pointers would be appreciated.
Click to expand...
Click to collapse
TTL level (~3.3v?) serial is present on the D+/D- pins of the micro USB connector whenever VBUS (usb +5v power) is not present. This is physical UART1 (ttyMSM0). In standard builds the FIQ kernel debugger runs there. You'll have to disable the FIQ debugger and enable the serial device in your kernel config if you want to use it as a regular serial port.

http://www.instructables.com/id/Android_G1_Serial_Cable/
Obviously you need a micro usb cable instead of mini, but this should work I think. I'll let you know when my serial adapter shows up.

swetland said:
You'll have to disable the FIQ debugger and enable the serial device in your kernel config if you want to use it as a regular serial port.
Click to expand...
Click to collapse
Thank you for the info.
Is this a kernel compile time or run time configuration?
jairuncaloth said:
http://www.instructables.com/id/Android_G1_Serial_Cable/Obviously you need a micro usb cable instead of mini, but this should work I think. I'll let you know when my serial adapter shows up.
Click to expand...
Click to collapse
thanks for the link. If Im not mistaken you may be able to eliminate a lot of this by splicing an existing micro USB cable with a MAX232 cable, will need to verify D+/- can handle 0-5 volts instead of 0-3.3v
Motorola T 191 serial cable
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.yoreparo.com/foros/files/t191cable_817.jpg
I can't tell is thats a 5 or 3 volt zener in the schematic

One zener is marked 5V, the other two are 3V3 which means 3.3 volts.

rotohammer said:
One zener is marked 5V, the other two are 3V3 which means 3.3 volts.
Click to expand...
Click to collapse
So it seems that one can simply splice the existing T191 and micro-usb cables and have a working adapter. I will be trying this when I get a chance.
The open questions are:
1) are the D+/- actually 3.3v levels
2) how is the kernel configuration performed to get /dev/tty?S?0

measured AM601 T191
tx is generating a 0-1.9v waveform at 19200 and 115200 and it took about 1 ms to charge the cap and start clocking data.

d1mbu1b said:
The open questions are:
1) are the D+/- actually 3.3v levels
Click to expand...
Click to collapse
USB signals are typically 3.6v, but the phone hardware may have a circuit to switch from USB to TTL serial. Regardless, the 3.3v zeners will give the MAX232 a nice flat topped square wave signal to work with.
Typically, to get a console on a serial port, you just specify a kernel boot option, or edit an entry in /etc/initab file. I'm not familiar the specifics of the android kernel though.

I ended up with this one.
http://www.sparkfun.com/commerce/product_info.php?products_id=718
snipped a usb cable and soldered it together. Works well.

jairuncaloth said:
I ended up with this one.http://www.sparkfun.com/commerce/product_info.php?products_id=718snipped a usb cable and soldered it together. Works well.
Click to expand...
Click to collapse
This data sheet says it implements the enture USB protocol on the chip.
Does this implement a USB host for the nexus one device?
I am confused.
I see there is a fuse and 5v connected to the USB 5v.
This implies the N1 is emulating a UART over the USB interface
and not clocking UART 232 over these same pins.
So my question is this an emulated 232 serial interface on the N1 or a UART in the N1 clocking 232 over the microUSB pins 2 and 3?
Please let me know what SW configuration you did on the N1 and what was the resulting name of the serial port in /dev/tty*
Thank you

WARNING - dead battery
seems once I played with the serial port the battery stopped charging even after applying the stock usb cable/charger
still trying to figure out.
for now recommend rebooting, then making surge charge bolt is in battery

@ jairuncaloth
Is it necessary to have root access to the phone for your solution?
Are any special drivers needed or is it possible with the builtin ones?
Can I just use /dev/ttyS0 then via NDK or preferable via a function of the Android API ?
Thanks.

jairuncaloth said:
snipped a usb cable and soldered it together. Works well.
Click to expand...
Click to collapse
A quick question to those of you who have access to the serial port : is it alive at boot time ? More specifically, do you get the SPL log messages ?

swetland said:
TTL level (~3.3v?) serial is present on the D+/D- pins of the micro USB connector whenever VBUS (usb +5v power) is not present. This is physical UART1 (ttyMSM0). In standard builds the FIQ kernel debugger runs there. You'll have to disable the FIQ debugger and enable the serial device in your kernel config if you want to use it as a regular serial port.
Click to expand...
Click to collapse
Can you/someone confirm it is 3.3V? Not 1.8V?

Serial Port
What is the port on device to open (/dev/?) in order to communicate with host PC

swetland said:
TTL level (~3.3v?) serial is present on the D+/D- pins of the micro USB connector whenever VBUS (usb +5v power) is not present. This is physical UART1 (ttyMSM0). In standard builds the FIQ kernel debugger runs there. You'll have to disable the FIQ debugger and enable the serial device in your kernel config if you want to use it as a regular serial port.
Click to expand...
Click to collapse
Whats the mapping D+/D- <-> RXD/TXD ? e.g. green -> RXD white -> TXD or vice versa ? .

swetland said:
TTL level (~3.3v?) serial is present on the D+/D- pins of the micro USB connector whenever VBUS (usb +5v power) is not present. This is physical UART1 (ttyMSM0). In standard builds the FIQ kernel debugger runs there. You'll have to disable the FIQ debugger and enable the serial device in your kernel config if you want to use it as a regular serial port.
Click to expand...
Click to collapse
I don't see how you need any adaptor if this is correct. Can you not just connect the D+/D- and gnd wires from some off the shelf micro usb plug to db-9 plug ?
edit: ok got it it's all about shifting the voltage levels up

I was able to create a cable using the sparkfun ft232r cable. After turning off FIQ and SERIAL_CONSOLE_DEBUGGER in the kernel I now have a command prompt and a bunch of kernel printlns out. How do I mute these kernel outputs and the command prompt? I want to use the serial port to communicate with a micro-controller using cat and echo to /dev/ttyMSM0 but all the noise from the kernel prevents me from having the microcontroller read the serial port without filtering out junk. Below are a few of the lines that I receive on the port.
--------------------------------
[ 102.658782] batt: 60%, 3889 mV, -7 mA (-5 avg), 24.5 C, 808 mAh
[ 102.717681] suspend: enter suspend
[ 102.718658] PM: Syncing filesystems ... done.
[ 102.777770] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 102.798736] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) don
e.
[ 102.828948] PM: suspend of devices complete after 9.603 msecs

keener2u said:
I was able to create a cable using the sparkfun ft232r cable. After turning off FIQ and SERIAL_CONSOLE_DEBUGGER in the kernel I now have a command prompt and a bunch of kernel printlns out. How do I mute these kernel outputs and the command prompt? I want to use the serial port to communicate with a micro-controller using cat and echo to /dev/ttyMSM0 but all the noise from the kernel prevents me from having the microcontroller read the serial port without filtering out junk. Below are a few of the lines that I receive on the port.
--------------------------------
[ 102.658782] batt: 60%, 3889 mV, -7 mA (-5 avg), 24.5 C, 808 mAh
[ 102.717681] suspend: enter suspend
[ 102.718658] PM: Syncing filesystems ... done.
[ 102.777770] Freezing user space processes ... (elapsed 0.01 seconds) done.
[ 102.798736] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) don
e.
[ 102.828948] PM: suspend of devices complete after 9.603 msecs
Click to expand...
Click to collapse
Hi
Take a loot at your kernel cmdline. I don't know where it is set in android. It should have something like 'console=/dev/ttyMSM0' Try removing it
Can somebody detail on the nexus pinout when in serial mode? I need to know which of the data pins is TXD, which is RXD ?
RED=+5V WHITE=??? GREEN=??? BLACK=GND
tia

Using this diagram as a reference
kineteka.com/microusb-b.aspx
2 Data − is hooked up to tx-0
3 Data + is hooked up to rx-i
Unfortunately I tore apart a best cell list cable and reused the micro-plug. It looks like they don't follow standards for wire color so i can't give you the correct color out to each wire but if you use a meter and check continuity you should be able to figure out the wire color from the above pin out.

Related

Optimus One support USB host mode? (update: working now!)

I'm looking for an Android phone that supports USB host mode. The Optimus One looks like a great phone but I can't seem to find anywhere whether USB host mode can be enabled for this phone. I'll have a separate power source for the USB devices, so the phone doesn't need to supply power in USB host mode, similar to Nexus One.
Has anyone tried to make USB host mode work with this phone? Thanks,
i read the p500 datasheet ..apparently the underlying chipset msm7227 supports it ..Its just been unutilised..So no i dont think we can have USB OTG here
sarfaraz1989 said:
i read the p500 datasheet ..apparently the underlying chipset msm7227 supports it ..Its just been unutilised..So no i dont think we can have USB OTG here
Click to expand...
Click to collapse
Thanks! By being unutilised do you mean it's hardware related or it's "just" a software issue? I'll probably give it a try if can be enabled with a proper driver.
USB host mode
I built a usb adapter just like here (but not the mini dongle, yet) but I see no output in dmesg.
I have tried it with my camera which should not be USB powered (olympus dslr - that would be the primary use, if we could get it working) and with a wireless mouse (it's dongle is surely USB powered). No output in dmesg whatsoever.
I will also try a keyboard, and also test it with a USB hub with separate power input. I will also try to make that mini dongle mentioned in the link, but have to find a cheap micro usb charger first.
Another thing is that I have no idea what drivers are included in the kernel, if any, for USB devices. still trying to figure out a way to do that. If anyone knows how, please tell me how.
my kernel version is 2.6.32.9 lg-electronics (at) android3g-buildserver #1 Sat Oct 9 20:54:44 KST 2010
Build number FRF91
Software version LG-P500-V10b
EDIT:
Found this site, with the same thing done to a ZTE Blade, which is similar (same chipset - MSM7227 and same problem with powering usb devices), but has eclair (different kernel version and of course different build).
Could any of the senior or more experienced members of XDA do something similar? It would be a very nice thing to have on our little phones...
Thanks, so it looks like it doesn't "just work".
I can't be of much help just yet since I don't have the phone, but I think if you see nothing in dmesg, then first you have to rebuild the kernel with USB host support, using maybe the driver in ehci-msm7201_Blade.tbz in your second link.
It could "just" work, haven't bought a proper usb otg cable yet, mine is hacked and might not be the right one,because the micro part of it is from a normal micro usb cable, and i think that the fifth pin on the micro usb must be wired through some kind of resistor to gnd or vcc of a certain value in order to activate the host mode in proper otg manner.
Also, i do not know if the port would provide (enough) power for unpowered devices (usb memory sticks).
Anyway, i am only interested in self powered devices, such as cameras (in mass storage mode).
Sent from my LG-P500 using XDA App
Some updates here! I took the plunge and got the Optimus One anyway
The good news is that the LG v10r kernel source seems to have the USB host driver for msm7x27; it is just not compiled into the official kernels. I compiled a kernel with usbcore, ehci-hcd, usb-storage and usbhid built in.
Extract boot.img and flash it with:
flash_image boot /sdcard/boot.img
If it works, then you should be able to attach a self-powered usb mass storage device or keyboard with it. I haven't actually connected the phone with any USB device yet; the phone still charges when connected to my computer, which might not be a good sign. I'll do more testing on it myself in a few days when I get the right cables. Be warned though that I take no responsibility for any potential damage
Oh, and note that usb client mode is nonexistent with the attached kernel because host and client drivers don't play nice with each other. Because of this you'll probably see some error message that some setting application crashed, but it's not a big deal.
EDIT: this one doesn't work; please see my next post
Could some one please explain, what is this "host mode" ?
I am new to android
@haoto
Done it, no luck (no output in dmesg whatsoever)... maybe some insmod should be in order?
My cable is a hacked one, with the sense pin "floating"
I used a external usb hub, and a Y cable (with a second usb for PC-style plug) to provide the power to the hub.
Could you please post a version of the kernel that is flashable via recovery (maybe more people - including me - would find it easier to do)?
I tried to connect the camera both directly and with the usb hub in between. Not even the usb hub was detected.
Maybe the sense pin in the micro plug, that in my hacked adapter is floating...
And also, do these drivers look at the sense pin on the usb cable? I haven't found a "proper" USB OTG adapter (using a pathed one, made fom am micro data cable and a usb extender), and in the cable that I have, pin 4 (the sense pin) is floating, it's not grounded.
I think that the conflict between host and client is solved in the ZTE Blade (with an official froyo update), and, if I remember correctly, the sources for the kernel are released (I think I have seen them here on XDA). And I think that it is solved by the means of the sense pin in the usb connector. Even in the Optimus the sense pin is connected, as far as I remember from the schematics in the service manual (also found here on XDA), and it could be watched/read... but then it would not work with hacked cables.
As for the charging, I'm not sure how the charging circuit works, but, if what I'm saying about the sense pin in the USB port (I'm obsessed with that pin, it seems...) being floating (not strapped to GND) in the charger cable, it might trigger the charging circuit to start charging.
And now to explain my "obssesion" with the sense pin:
I bought a Nokia CA-157 cable (USB OTG adapter) and, not being very careful, I did not notice that it is micro USB A, not B and it does not fit (same size, but it has squared ends, so it is a bit too big...). So I tried to "bend" it i order to fit, but I destroyed it. But then I read a bit more about the pins in the usb port, and measured it (very carefully, cause the pins are so small) and found that pins 4 an 5 are strapped together (zero ohms). Then I tried to measure the pins on the normal micro usb cable, and found out that they are not strapped. So I figured that, in order to have a OTG adapter working correctly (charging, usb host and usb gadget) you need to have that 4 pin strapped to pin 5 in order to get the chipset in host mode.
@DJoptimus-One:
USB host (or rather USB OTG) is the posibility to connect devices to your android just like connecting them to a PC, eg. connecting a photo camera to the phone directly (no PC) for copying photos, or connecting a PC keyboard directly to the phone, or connecting... a USB memory stick directly to your phone for file copy... etc.
@moderators:
Maybe this thread should be moved to the development section, as it has a bit of recompiling and testing, and maybe it could get more people involved in the development of this?
More updates. I'm using the LG kernel source LGP500(Thunder)_Android_Froyo_v10r.zip which is based on linux 2.6.32.9, with stock 2.2.2 system. Attached are the boot image, kernel zImage, and kernel config I used. You should be able to at least see some dmesg output this time. Sorry if it's not easy for you to flash it; I'm completely new to android phones and will learn the proper ways when I get the time. For now it looks like everyone wishing to take this further needs to hack and compile the kernel source anyway Also, I didn't compile the USB device code (Android gadget) in because it seems to crash my phone when combined with USB host driver. Maybe the LG driver engineers didn't expect us to use it this way yet.
A Micro-AB plug (our a hacked Micro-B one like yours by soldering ID and GND) is required to produce any response when a USB device is connected. According to OTG spec you should also connect a 36.5 kΩ resistor between ID and GND when using a charger. I didn't test this, but I don't think it's a problem for now.
However, there are some complications I cannot figure out.
First, the hardware doesn't produce an ID-changed IRQ (OTGSC_IDIS) when the Micro-AB plug is plugged-in, nor does OTGSC_ID ever becomes "A". I simply hacked the is_host() macro in drivers/usb/otg/msm72k_otg.c to always return true so that the driver believes it is a host. But for some unknown reason, you still need to use a Micro-AB plug.
I did manage to get the phone run in USB host mode, using a Y-cable to power the devices. But I can't get it to recognize any device. Below is a sample dmesg output when a USB keyboard is connected:
Code:
<7>[ 153.284488] usb usb1: usb resume
<7>[ 153.284513] msm_hsusb_host msm_hsusb_host.0: resume root hub
<7>[ 153.321383] hub 1-0:1.0: hub_resume
<7>[ 153.321453] msm_hsusb_host msm_hsusb_host.0: GetStatus port 1 status 84001403 POWER sig=k CSC CONNECT
<7>[ 153.321486] hub 1-0:1.0: port 1: status 0301 change 0001
<7>[ 153.431414] hub 1-0:1.0: state 7 ports 1 chg 0002 evt 0000
<7>[ 153.431471] hub 1-0:1.0: port 1, status 0301, change 0000, 1.5 Mb/s
<6>[ 153.551378] usb 1-1: new low speed USB device using msm_hsusb_host and address 2
<7>[ 153.553388] msm_hsusb_host msm_hsusb_host.0: detected XactErr len 0/8 retry 1
<7>[ 153.554364] msm_hsusb_host msm_hsusb_host.0: detected XactErr len 0/8 retry 2
...
<7>[ 155.943383] msm_hsusb_host msm_hsusb_host.0: detected XactErr len 0/8 retry 31
<7>[ 155.944376] msm_hsusb_host msm_hsusb_host.0: devpath 1 ep0out 3strikes
<7>[ 155.944399] usb usb1: clear tt buffer port 1, a0 ep0 t00080248
<3>[ 156.151369] usb 1-1: device not accepting address 5, error -71
<3>[ 156.151451] hub 1-0:1.0: unable to enumerate USB device on port 1
<7>[ 156.151478] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 000
Notably, connecting a high-speed device such as a USB stick produces a different, and shorter message:
Code:
<7>[ 4333.870061] usb usb1: usb resume
<7>[ 4333.870088] msm_hsusb_host msm_hsusb_host.0: resume root hub
<7>[ 4333.901361] hub 1-0:1.0: hub_resume
<7>[ 4333.901438] msm_hsusb_host msm_hsusb_host.0: GetStatus port 1 status 8c001002 POWER sig=se0 CSC
<7>[ 4334.011429] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
So, it seems that the hardware has difficulty recognizing USB "j states". I'm not really sure about this because I didn't do these experiments very carefully, and I do remember seeing "sig=j" once, but can never reproduce it anymore. (Hint: I guess it might be related to control of the pull-up resistor on the phone side. It's also possible that my cable is bad and it'll just work for you, fat chance )
As a side note, I also tried reversing the D+ and D- pins on one of the devices I tested as per:http://android.modaco.com/content-page/334222/an-experimental-cm7-kernel/page/200/#entry1667619 But (apparently) it doesn't help except making the device useless.
Hope someone can pick this up from here as I'm out of spare time at least for some weeks
Tried the latest kernel, but still does not work...
I will try to hack the cable a bit more, see if I can get any change in behavior.
I hope someone else reads this thread and and comes with some more input...
My only input so far is testing... (I do lack some knowledge about kernel building...)
Maybe looking into the ZTE Blade kernel and apps would help... (it's here)
Oops, I just noticed the build I uploaded doesn't work for me either; I changed some configuration and assumed it was harmless. They are updated now, sorry for the blunder
Will try it again (I assume it is in the older post).
Also, maybe a "software switch" (either app or simply a touch or something) could be made to switch from host to gadget mode like here? (Better after we get it working, though...)
Oh no, it's in the newer post
If you have the time, could you also try to measure the following with that kernel installed:
1) voltage between VCC and GND when nothing is connected
2) voltage between D- and GND and the voltage between D+ and GND when only a charger is connected
3) resistance between D- and GND, and resistance between D+ and GND when nothing is connected
I'm not sure I know what to do next, but this might help us clear up a couple things.
I'll try to have a look at the ZTE Blade kernel source later, thanks.
Update: it's suddenly working!!!
I successfully mounted a USB stick! So either the driver is unstable, or there indeed is something wrong with my hacked cable!
(And then I burned my USB charger! Thankfully my phone is alright. Looks like there is definitely something wrong with my cabling )
With my cable did not work, so I managed to completely destroy the micro part of my cable trying to find a way to short pins 4 and 5.
As I understand it, you have your cable with pins 4 and 5 shorted (sense - gnd).
I am still trying to find a proper adapter, but all I can find is the CA157 from nokia, which is A and does not fit...
And I could not find another standard otg cable (at least the part number, in order to find it faster) from a big manufacturer (htc, noika, samsung, whatever...).
I will get another micro and hack it once more, though, and try to measure the voltage on the pins. Maybe a noname cable is easier to mod...
As for the burnt charger... I don't think that there should be any problem... Here are some prints from the service manual.
Did you use the charger for powering the USB bus? Or did you just plug in the power?
I don't have issues with the charger connected just for charging the phone (I'm using a nokia micro USB charger, and it's working perfectly... even with the modded kernel)
I actually got a micro-B to mini-B adapter with all 5 lines connected, so I can cut the cable at any place to solder the ID and GND lines. Please do let me know when you get it working (or not... mine seems to work from time to time now)
The charger burned when I was using it to power the USB devices. I guess it's most likely caused by a short in my hacked OTG cable , it was a cheap USB charger which probably doesn't have any over-current protection.
sorry for this noobie question but did u meant we could attach usb devices directly to phone?
scorpionking674 said:
sorry for this noobie question but did u meant we could attach usb devices directly to phone?
Click to expand...
Click to collapse
Ya.
Sent from LG P500.
This seems very interesting! Can you guys write a short tutorial on the steps needed to get OTG working?
It is not fully working yet (at least not in a very friendly way).
Anyway, I'm still trying to hack a cable with the sense pin grounded, in order to do some testing at least...
Steps to be taken:
WARNING!
Rooting the phone and installing a new kernel and some other stuff presented here voids warranty, and MAY brick your phone!
Also, this requires connecting to your phone a cable that is HACKED and not supported by the manufacturer; it MAY (and is not very unlikely) FRY YOUR PHONE
We do not take ANY responsibility if you brick/fry your phone; this is only what we are doing or trying to do.
Also, the mod is not yet complete, as in the last version only the usb HOST is included (connect devices to Optimus), not the USB device is included (connecting the optimus to the PC does not work any more, not as sync nor mass storage, and there is no mode switching yet). Charging does work.
Also, after boot you get a message that some settings app does not work (we ignore that).
So, if you are willing to risk bricking or frying your phone at your own responsibilty, here is what we are trying to do...
0. Do a full backup. This is the firs step, no matter what you do to the phone (well, at least after rooting and installing custom recovery...), in order to have a WORKING restore point. (it will help if something that you have been warned might happen actually happens - except a fried phone)
1. a. Get a micro USB B male to USB A female OTG cable (that has pins 4 ans 5 straped together)
1. b. Alternatively, you can hack a cable like that, if you find the parts (one micro usb b male to mini usb male/female cable with all 5 wires inside and a normal usb a male to usb a female, and hack the cable)
2. root your phone (!! at your own risk !! only YOU are responsible for what you do to your phone)
3. install the latest kernel version posted here. Same warning as above.
4. make some hack on the cable (eg. get a y usb cable from an external hdd or something) in order to get +5V to the USB bus (at this time the phone does not supply +5V to the devices connected, maybe some state on the usb driver chip must be changed, or maybe the phone does not support providing power via the USB port). Connecting this cable to your phone may fry your phone, so double check, triple check and remember that YOU DO THIS AT YOUR OWN RISK...
5. connect a usb stick and... (from this point I could not test, as I do not have yet a cable with the sense pin grounded) make it work... (probably like in the steps below; NOTHING IS AUTOMATED YET, I GUESS)
6. open a terminal, type "su" (get root access), type "dmesg" (lots of lines will appear) and then identify the block device that the stick is (probably something like "sda").
7. make a folder somewhere where will mount the USB stick
8. mount the usb stick and see if it works properly.
From step 5 onward I did not test anything, so please correct me if I said something wrong.

Flashable USB OTG Modules THAT WORK! (Now Including Ethernet Support)

I am not responsible for your bricked phone/SD. If blame me I will laugh at you.
You should know by now the disclaimer and blah blahs!
I have looked EVERYWHERE (google and fastboot is your friend) for these and tested multiple times
different modules and found the ones that work. They only program -should- be needed as it is the only
one I use is a program that is free on the Google Play Store is Paragan NTFS&HFS+ Program. *Root of course*
I have tested this on my phone itself and I am using my external mouse,
keyboard and external drive as we speak!
My personal set-up is a Targus PAEPRO090 so called "docking station" that has
5 USB HiSpeed Ports
LAN Adapter
Printer Port
Serial Port
3.5 mm Audio Jack (although I have yet to get it to work)
What this does
INSTALLS:
FUSE driver (Full NTFS Read Write support for ARM devices)
isofs (To allow mounting ISO and image files)
nls_utf8 (for mounting a CIFS windows share and allows extra features)
NTFS modules (to allow android to mount NTFS)
and a module that allows for NTFS USB mounting
Version 2 has Ethernet Drivers AND my OTG drivers all in one.
If things do not start up (ethernet) go to the terminal and enter
Code:
su
usb_ethernet
Thanks for sharing this!
One question: Can you actually take a regular USB OTG cable (with micro USB on one side and a female 'regular' USB A connector on the other side) like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And use it to connect e.g. a USB flash drive to your phone?
Because AFAIK the Droid 4 USB port doesn't provide power output, I once tested it with mine with a special splitted USB cable that get's the power elsewhere, which worked, but not with a regular USB OTG cable.
Thanks
You need a cable that is split and provides power externally.
Sent from my DROID4 using xda premium
I took the otg cable as shown striped a portion of the plastic back, took a standard charger (5.1v 850 mA) spliced in the red and black works fine with keyboard, mouse and flash drive(for me and my generic three). A powered USB hub works also just phone wont charge with the powered USB hub i have...
...would love to know how to get a dock type reaction when plugged into a powered otg cable without a third party app on a stock d4... ima take my dock apart see how they have it wired...
Sent from my DROID4 using xda app-developers app
dbreezy187 said:
I took the otg cable as shown striped a portion of the plastic back, took a standard charger (5.1v 850 mA) spliced in the red and black works fine with keyboard, mouse and flash drive(for me and my generic three). A powered USB hub works also just phone wont charge with the powered USB hub i have...
...would love to know how to get a dock type reaction when plugged into a powered otg cable without a third party app on a stock d4... ima take my dock apart see how they have it wired...
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
I believe it uses the 5th (pin 4) USB wire that "normally" isnt't used. But when you make the OTG Cable that requires external power make sure you connect up the power to the part you hook your external device and not the side you hook up to your phone... Get what im trying to say? lol
NORMAL
Pin 1: VCC
Pin 2: data-
Pin 3: data+
Pin 4 Not connected/unused/sense
Pin 5: ground
OTG Cable
Pin 1: VCC
Pin 2: data-
Pin 3: data+
Pin 4 ground (Pin 5)
Pin 5: ground
Yes this i understand i have made several otg cables for friends with quick connect power supply for use with a hub.. but a few would like a dock made rather then pay the 90$ i figured i could make one. When plugged into either of the two docks your prompted with a choice for a dock type office, bedside, charge only.. this is what I wish to achieve without any app installed or root as some of my moto friends don't wish to root... I can put a dock together for about 25$ with USB hub, hdmi and audio jack just no reaction from phone when plugged in... would even settle for landscape on home screen when plugged in...thank you kindly for any info... haven't yet had the time to take my two apart...
Sent from my DROID4 using xda app-developers app
I'm pretty sure the dock is detected by those 4 pins on the bottom right of the battery on the phone; a magnet is placed inside the dock in a spot that would line up with the phone's sensors.
II've never tried to do this but I'm sure it wouldn't be very difficult.
Sent from my XT894 using xda premium
Ok... so i took a look at the inside of the standard HD dock (no USB hub) it appears that a resistor on pin 4 prior to the ground triggers the dock mode... I was interrupted during the "examination" of the guts so the size of the resistance is not know yet and it appears pins 2, 3, and 5 are split off into the audio jack more details yet to come...
Sent from my DROID4 using xda app-developers app
Rick#2 said:
I'm pretty sure the dock is detected by those 4 pins on the bottom right of the battery on the phone; a magnet is placed inside the dock in a spot that would line up with the phone's sensors.
II've never tried to do this but I'm sure it wouldn't be very difficult.
Sent from my XT894 using xda premium
Click to expand...
Click to collapse
Actually I think those 4 pins are for the inductive charging battery cover option.
Cable needed
Can anyone point me to an exact place I can buy a cable? I'd prefer one that I can plug into a usb charger on one end, then my phone/usb otg device on the others. I'd appreciate it. I see so many places that say use this cable, then someone says no it doesn't work.
zeroktal said:
Can anyone point me to an exact place I can buy a cable? I'd prefer one that I can plug into a usb charger on one end, then my phone/usb otg device on the others. I'd appreciate it. I see so many places that say use this cable, then someone says no it doesn't work.
Click to expand...
Click to collapse
this is the one I bought
http://goo.gl/6hOAV
Awesome Thanks
I just ordered one, thanks a bunch.
Ok guys I want to share a guid with you on the same subject.
You can find all these modules, programs and instructions HERE.
I have tested the above and are working fine.
I was not able to make the wireless keyboard work though.
They say that you don't need a module for that but as far as I can see the wireless keyboard does not work on my phone.
It did work fine when I had the 2.3.4 with the older usb-hid and usb-keyb modules.
I use these on an Xperia Neon V with ultimate HD v.2.0 ROM and kernel .587
Can anyone test if wireless keyboards work on this setup and confirm?
Mouse works fine. Usb Storage as well.
As for the cable I ordered this one
It has a micro usb female port where you can suppry power using a standard USB charger cable.
Re: Installable ICS USB OTG Modules THAT WORKS!
Je2854: Cable works perfect, thanks a bunch.
zeroktal said:
Je2854: Cable works perfect, thanks a bunch.
Click to expand...
Click to collapse
your welcome, any time
je2854 said:
your welcome, any time
Click to expand...
Click to collapse
Hi! Does it work with Jelly Bean 4.1.2 stock rom? I've just got the cable (Y cable which can get external power from USB) from China, after more than 1 month, and I've just updated the phone.
Mr Wolf said:
Hi! Does it work with Jelly Bean 4.1.2 stock rom? I've just got the cable (Y cable which can get external power from USB) from China, after more than 1 month, and I've just updated the phone.
Click to expand...
Click to collapse
It should work with any version 4.x.x or higher
Ok... I'm ready to try!
A dumb question: should META-INF folder be copied in the root folder? And the modules in their path, right?
Mr Wolf said:
Ok... I'm ready to try!
A dumb question: should META-INF folder be copied in the root folder? And the modules in their path, right?
Click to expand...
Click to collapse
the only thing you should do it flash the zip...
everything goes to its proper folder in the OS
Many thanks!
Another dumb question: what I flash it with? RSD Lite o Flash recovery? :cyclops:

MHL hdmi/vga with OTG & charging cable build

has anyone built an MHL with OTG & charging cable that works yet?
if not I have just received my fully pined 11pin to 6 pin adapter, a working mhl cable, and I'll go start and see how far I get, but if someone knows of one thats done to save the time etc..
what i'd like to know is the full pinout for all 11 pins?
not even found a diagram for this new connector yet showing pin number ordering!
Well I have the mhl/hdmi cable now, let the hacking commence...
https://www.youtube.com/watch?v=2fhBikVZXPg
well the build has stalled for a few days, somehow something went wrong with the tv (psu) and it seems to have 'zapped' my mhl/hdmi adapter....
the adapter communicates with the phone, but i get green garbage on screen.
So to pass the time i took the 11pin micro USB plug apart...
heres how they get 11 pins into a 5 pin hole...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey op thxs for info. Been wondering about that 11 pin setup myself.
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
Whats a cheap 11pin mhl/hdmi cable?
flez1966 said:
well the build has stalled for a few days, somehow something went wrong with the tv (psu) and it seems to have 'zapped' my mhl/hdmi adapter....
the adapter communicates with the phone, but i get green garbage on screen.
So to pass the time i took the 11pin micro USB plug apart...
heres how they get 11 pins into a 5 pin hole...
Click to expand...
Click to collapse
So, considering USB is engineered as a hub design from ground up in the first place, do you think it would be possible to solder an OTG adapter to the 5 pins?
Hopefully this may be of some help, I have also been trying to make one of these for the last few weeks.
So far, from purchasing this MHL - hdmi adapter, I have managed to map most of the pins, but am having difficulties getting USB OTG to work.
Charge, HDMI, and PC data connection work, but i still need to find the USB OTG pins for "smart dock" mode.
I assumed that this would work for USB OTG but it doesn't seem to work for me, it acts as USB Slave not Host (I.e. Connection to PC not HDD/Keyboard)
so far the pins i have identified:
(normal usb part)
Pin 1 - Vcc
Pin 2 - USB - (Slave)
Pin 3 - USB + (Slave)
Pin 4 - Sense (40.2K Ohm)
Pin 5 - Gnd
(extended USB Part)
Pin 6 - ? (Audio/USB host?)
Pin 7 - ? (Audio/USB host?)
Pin 8 - DP (MHL +)
Pin 9 - DN (MHL -)
Pin 10 - MHL ID (connected to ID Pin of MHL Adapter)
Pin 11 - Gnd
I will try and upload some images tomorrow, and a diagram of the plug.
My 11pin mhl cable has a y piece with a usb on one side and hdmi plug on the other. No box like yours.
Do these cables have any components in them?
Is it worth me doing any testing with my cable, what actually activates otg? My son had a low end android tab and there was a menu option to change the usb mode, so how is it triggered on note 2, is it a signal, resistor, or just the presence of a peripheral?
There must be a way of spicing in a otg cable onto an mhl cable.
Smart docks wont be available in uk until march, but I would rather do it by myself with cables anyway.
First of all, sorry i didnt get arount to uplading any images yesterday.
Im in the same boat as you, I didnt think I could get a smart dock, and didnt fancy paying £100 for something I should be able to make for £10. I have since found 2 uk shops that sell them for £60.
On my MHL adaper the socket is built into the body if the device, but it only supplies 5v to the device, no data pins are connected through it unfortunately.
Inside these adapters, there is a chip to convert MHL's 2 data cables into hdmi's ~11 data cables.
On the note2 the modes are activated by a resistor on the sense pin of the USB plug, (pin 4) For smartdock mode, 40.2k ohm resistor is used.
The main problem I am having is acessing the pins, as they are so small on the plug. Im waiting for some copper clad pcb so I can make a breakout board for the usb connector.
Sent from my GT-N7105
Sorry i tried linking to the UK sellers in-case you are interested, but my post count is too low to do so.
www(Dot)clove(Dot)co(Dot)uk/samsung-galaxy-note-ii-smart-dock
www(Dot)mobilefun(Dot)co(Dot)uk/samsung-galaxy-note-2-s3-smart-dock-edd-s20eweg-p36945.htm?referer=FR_PROD-PR3&utm_source=google%2Bproducts&utm_medium=comparison&utm_campaign=google%2Bproducts
OK I have now opened another 5 to 11pin connector, this is the moulded plastic variety...
This is an image of what mine looks like, but i did not use this supplier, i just bought on ebay...
..and inside
01jacksonb. said:
(extended USB Part)
Pin 6 - Gnd
Pin 7 - MHL ID (connected to ID Pin of MHL Adapter)
Pin 8 - DN (MHL -)
Pin 9 - DP (MHL +)
Pin 10 - ? (Audio/USB host?)
Pin 11 - ? (Audio/USB host?)
I will try and upload some images tomorrow, and a diagram of the plug.
Click to expand...
Click to collapse
How did you work out which is pin 6? Was it marked etc?
flez1966 said:
How did you work out which is pin 6? Was it marked etc?
Click to expand...
Click to collapse
No markings on mine, I just started numbering them as I noted them down (left to right), however i didn't follow standard pin mapping, and think i have noted them in reverse order
The following should be standard numbering. (if Samsung release a spec or diagram of the plug )
Here are the images as promised.
Smart dock pins:
Pin 1 - Vcc
Pin 2 - USB - (Slave)
Pin 3 - USB + (Slave)
Pin 4 - ID/Sense (40.2K Ohm)
Pin 5 - Gnd
Pin 6 - ? (Audio/USB host?)
Pin 7 - ? (Audio/USB host?)
Pin 8 - DP (MHL +)
Pin 9 - DN (MHL -)
Pin 10 - MHL ID (connected to ID Pin of MHL Adapter)
Pin 11 - Gnd
---------- Post added 6th February 2013 at 12:37 AM ---------- Previous post was 5th February 2013 at 11:42 PM ----------
After watching a review of the smart dock, in which the S3 is said that USB doesn't work in dock mode, and along with the Note 2 working with PC Docking. I can only assume that the data has to be on the pins 6 & 7.
The next step is identifying the polarity of them, luckily D+ & D- both can take 3.3v (used as ID for USB 1.0 or 1.1) nothing should be damaged if the polarity is incorrect.
The next issue is connecting all of the wires to the USB pins at once. I can't connect all of the wires to the 0.3mm pins, and expect them to not come loose or short. The only solution that i can think of is to etch a breakout PCB for it. Hopefully it will arrive soon, Unfortunately my first board was way too thick for the plug.
Your attempts look as elegant as mine..
I was trying with a single strand of bare wire, if it goes down fine then it can be insulated with coloured mail varnish.
That way each stand kind of ends if like the varnish covered wire used in transformers or some of those cheap $2 headphones
if you look at 'spare' plugs sold on ebay for the s3, they have the pins setout very odd, for single sided board mounting
Normally when i need to connect to small pins like these, I use Kynar wire, as it is so small and single core. However when usb host didnt work, i assumed that it was because the cable had to much noise, so i changed to normal USB cable (which also didn't work)
The socket is interesting, it looks like they surface mount it, unlike the plug that i have, which mounts on the side of the circuit.
Have you seen anybody selling the plugs cheap, and in low quantities? the only place i can find is alibaba, and i have to buy a few hundred
Excuse the rough edges, I through together a breakout board for the plug, so that i can easily access all of the pins, and secure the cable in place.
I made a quick sketch on a PCB and etched it. Not quite figured out how to print them yet.
---------- Post added 7th February 2013 at 12:36 AM ---------- Previous post was 6th February 2013 at 11:53 PM ----------
I just powered it up, and gave pins 6 & 7 a try with a memory stick connected, unfortunately there was no response from android, it also didn't see a mouse.
not sure why it doesn't detect, maybe there is too much interference, or the pins just aren't usb.
anyway, i will dig out my osciloscope, and start testing the pins to see what data they are trying to send.
I may end up having to purchase the smart dock to see what makes it tick.
i'd check for shorts.
doesnt usb otg need a pin shorted to ground? or 100 ohms etc.
subscribed to this thread and will chime in when I can offer some insight - my smart dock is due to arrive (tomorrow?)
I'll hopefully be taking it apart to test around for what wire is getting what resistance etc...
one thing I'll need to do is make a usb-micro-male end into a usb-a-male end so I can test the dock w/my lapdock (it's been the goal for me on this hdmi/otg/charging build)
Thats the exact same reason that I have been trying to make one.
I have the lapdock ready and waiting to be modified. If you need any info on the lapdock's USB and HDMI connections, have a quick look at "RaspberryPi Lapdock"
I hope that you get your smartdock soon. Im Looking forward to your input.
Sent from my GT-N7105.
flez1966 said:
i'd check for shorts.
Doesn't USB OTG need a pin shorted to ground? or 100 ohms etc.
Click to expand...
Click to collapse
USB OTG uses a short between pin 4 & 5. The resistance between these pins "informs" the phone about which accessory is connected.
USB OTG mode, will only activate the USB host function, charge and HDMI are disabled in this mode.
Desk Dock mode, enables HDMI, and Charge, but not USB OTG
Smart Dock mode, enables HDMI, charge, and USB OTG.
Here is a list of (Samsung Galaxy S) resistor values I saved on my computer, I believe I found them on this forum, by "TheBeano"
(list is edited to show more relevant items to the Note 2)
Code:
RID_USB_OTG_MODE, GND USB OTG Mode
RID_RESERVED_1, 28.7K Reserved Accessory #1
RID_RESERVED_2, 34K Reserved Accessory #2
RID_RESERVED_3, 40.2K Reserved Accessory #3 (Smart Dock Mode)
RID_RESERVED_4, 49.9K Reserved Accessory #4
RID_RESERVED_5, 64.9K Reserved Accessory #5
RID_AUD_DEV_TY_2, 80.07K Audio Device Type 2
RID_PHONE_PWD_DEV, 102K Phone Powered Device
RID_TTY_CONVERTER, 121K TTY Converter
RID_UART_CABLE, 150K UART Cable
RID_CEA936A_TY_1, 200K CEA936A Type-1 Charger(1)
RID_FM_BOOT_OFF_USB, 255K Factory Mode Boot OFF-USB
RID_FM_BOOT_ON_USB, 301K Factory Mode Boot ON-USB
RID_AUD_VDO_CABLE, 1K or 365K Audio/Video Cable (HDMI/Desk mode/MHL)
RID_CEA936A_TY_2, 442K CEA936A Type-2 Charger(1)
RID_FM_BOOT_OFF_UART, 523K Factory Mode Boot OFF-UART
Car mode, 619K Car mode
RID_AUD_DEV_TY_1_REMOTE, 1000.07K Audio Device Type 1 with Remote(1)
RID_AUD_DEV_TY_1_SEND, 1002K Audio Device Type 1 / Only Send-End(2)
RID_USB_MODE, Open USB Mode, Dedicated Charger or Accessory Detach

Important my research on OTG on kindle 8.9HD my fndings

Hi i've been doing some research on why OTG it's not working on this device,
I own a galaxy s4 i9500 and measured pin voltages, on the microusb to USB (OTB cable I got) these are my findings.
USB A pinouts
------------------------
1 VCC +5
2 D-
3 D+
4 GND
Galaxy s4 3.8volts 9.8Wh battery readings
USB female connector (galaxy s4 i9500)
---------------------------------------------
pins 1-4 5 volts VCC while on OTG
pins 1-2 5 volts
pins 1-3 5 volts
USB female connector (kindle fire 8.9hd)
----------------------------------------------
1-4 Nothing
1-2 outputting 1.5 millivolts, bear in mind this is pin 1 vcc and pin 2 D-
1-3 outputting 1.5 millivolts same here pin 1 vcc and pin 3 D+
So that's why we're not getting anything to work out of the kindle with OTG cable, there's no voltage coming out at all. But my doubt is as follows. Would it be possible to bridge the 3.8 volts coming from the battery to pin 1 which should be
5vcc where USB 5 volts should be coming out, in that way we would be having the usb port working fine.
Problem is I don't know if the microusb on this device is propietary and I might redirect the 3.8volts from the battert to pin 1 and when I charge the device everything blows up .. So I would like to hear from you , anyone savvy on in depth electronics or with more background on the matter.
This has been a known issue ever since OTG was introduced for the Original KF. The solution as of now is to either use a powered hub or rig up a powered OTG cable jig.
I'm not sure if it can be fixed at the kernel level, but I'm sure it's being looked at.
I'd be happy with keyboard support like they had with the original KF at this point. 32GB is more than enough for me, so I don't need the extra usb HD space.
soupmagnet said:
This has been a known issue ever since OTG was introduced for the Original KF. The solution as of now is to either use a powered hub or rig up a powered OTG cable jig.
I'm not sure if it can be fixed at the kernel level, but I'm sure it's being looked at.
Click to expand...
Click to collapse
So what do you mean I need to inject 5 volts with a usb Y cable and inject 5 volts towards the kindle , I honestly prefer avoid 5 volts from entering the kindle. I prefer to feed up 5 volts line to the device I'm plugging , would that way work? . cause I did download usb diagnostics and it didn't detect a usb host. I'm using 10.1 ROM on kindle 8.9 . Any feedback ?
OTG is disabled in the kernel currently.
Hashcode said:
OTG is disabled in the kernel currently.
Click to expand...
Click to collapse
Hi hash, thanks for answering, did you disable it ? I'm currently on CM 10.1 is there any chance of enabling it ?. I do really need to use an external storage on my hd kindle. I did those voltage measurements and no voltage is coming out from either pins. I did run a usb diagnostic and no usb host is detected. So again , can you add OTG functionality ? I would be really grateful. Thanks !
dssence said:
Hi hash, thanks for answering, did you disable it ? I'm currently on CM 10.1 is there any chance of enabling it ?. I do really need to use an external storage on my hd kindle. I did those voltage measurements and no voltage is coming out from either pins. I did run a usb diagnostic and no usb host is detected. So again , can you add OTG functionality ? I would be really grateful. Thanks !
Click to expand...
Click to collapse
It was disabled by Amazon, and I just haven't had the time to debug and re-enable it.
Hashcode said:
It was disabled by Amazon, and I just haven't had the time to debug and re-enable it.
Click to expand...
Click to collapse
I understand , just take your time . I do really need this functionality. Would we still need external voltage applied for external stoarge to be detected as well as keyboard or gamepads?.

[Q] Nook HD/HD+ connector pinout and serial?

I see there was excellent work done by others to determine pinout for Nook Color/Tablet connector.
Now it would be great if we can get somebody to do the same for Nook HDs.
Additionally I really-really need a serial port out of the new Nooks for my kernel experiments (hopefully there's a serial in the big connector, but even if not, and somebody can help me to just solder wires somewhere on the pcb to gain serial, that would be great).
Please hit your hardware techie friends for me if you have any
If there is a serious person interested in this with no Nook to play, please contact me and I'll arrange for something.
(I already researched the Nook Color way of getting serial via twl on usb connector, but the newer twl in the newer Nooks does not have this car kit mode).
verygreen said:
I see there was excellent work done by others to determine pinout for Nook Color/Tablet connector.
Now it would be great if we can get somebody to do the same for Nook HDs.
Additionally I really-really need a serial port out of the new Nooks for my kernel experiments (hopefully there's a serial in the big connector, but even if not, and somebody can help me to just solder wires somewhere on the pcb to gain serial, that would be great).
Please hit your hardware techie friends for me if you have any
If there is a serious person interested in this with no Nook to play, please contact me and I'll arrange for something.
(I already researched the Nook Color way of getting serial via twl on usb connector, but the newer twl in the newer Nooks does not have this car kit mode).
Click to expand...
Click to collapse
I'm surprised no one has done this yet. I read somewhere that b&n simply modified an iPod connector and often times I've found that means they simply changed the order of the wires in order to gain propriety and therefore extra revenue. I have Two hd+ sitting on my desk with no charge because I'm too cheap to pay 30 bucks for a cable from b&n. I also have one charging cable cut in half so maybe I'll get on this myself, not that I can really take on another project at the moment.
The standard USB cable that came with the Nook only has 4 pins inside (going to the nook), so even if you cut your cable I don't think you will find anything useful.
I'm not sure about the HDMI one, it should have some extra pins inside to enable the video output, but I think that, without finding a compatible male plug with all the pins intact, it will be quite hard to find out the purpose of each pin.
Someone brave can do it on the nook side but I haven't open mine yet
Linux can use usb serial as console.
But I don't know is it possible to switch Nook usb subsystem to usb host early at boot.
lostnick said:
Linux can use usb serial as console.
But I don't know is it possible to switch Nook usb subsystem to usb host early at boot.
Click to expand...
Click to collapse
No, and by the time usb is up it's way too late in the booting game.
The big benefit of a real serial out is you get the output from bootloader and then transitioning into kernel including very early booting.
The nook end of the cable has only six pins. Two top and bottom on one side and one top and bottom on the other side. It would be easy to see what they connect to on the USB side. I'm definitely not an electronics engineer so I'm wondering if that is what is being discussed here and how that would do us any good? I would like to diy a car charger if I can.
pinout
I opened my Nook HD+, and there is a test point near the dock connector labeled usb-id. If this TP is shorted to GND with a slave USB device attached thru a USB-A to A gender bender, the Nook acts as host as expected per USB-OTG standard. This TP maps to pin 24. Unfortunately, this isn't one of the pins to a Nook HD+ USB cable.
The Nook HD+'s motherboard is labeled EXCELLENTLY. I've gotten most of the pins I can get easily. I think the remaining pins are for HDMI (which makes sense seeing B&N makes an HDMI adapter cable...). The HDMI adapter cable will probably get the remaining pins.
Here's the pinout I've got so far:
Pin - Signal
--------------------------------------
1 - USB VBUS (+5VDC)
2 - USB VBUS (+5VDC)
3 - HDMI 5V
4 - LINEOUT-DTC
5 - USB D-
6 - USB D+
7 -
8 -
9 -
10- GND
11-
12-
13- GND
14-
15-
16- GND
17-
18-
19- GND
20-
21-
22-
23-
24- USB-ID
25- LINE-L (Audio)
26- GND
27- LINE-R (Audio)
28- GND
29- GND
30- GND
---------- Post added at 06:27 AM ---------- Previous post was at 06:04 AM ----------
Also, there are two test points, SDA2-TX and SCL2-RX. These are I2C test points but I can't tell if they are the HDMI side or the system side. The HDMI chip is the TI TPD12s015, datasheet can be googled. Just a hunch that these are the HDMI side, since the datasheet says SDA_B and SCL_B are HDMI side, and they're labeled as SDA2 and SCL2.
connector type
Also, the Nook HD+ connector is NOT the same design as an Apple Dock Connector. The Apple connector has all the pins on one side of the internal fitting, while the Nook's connector has the pins on both sides.
So anyone attempting to mod their own connector should use a Nook connector.
Crud, i just bought one of those Samsung 30 pin to micro SD adapters hoping I could pull it apart and mod it, maybe I can't after all.
#edit# Is this our connector?
http://en.m.wikipedia.org/wiki/PDMI
Nope, not a PDMI...
myjess said:
Crud, i just bought one of those Samsung 30 pin to micro SD adapters hoping I could pull it apart and mod it, maybe I can't after all.
#edit# Is this our connector?
(link deleted, I'm too much of a noob to post links, I guess!)
Click to expand...
Click to collapse
No, from what I can tell, a PDMI connector is very similar to a Apple Dock Connector, with different pinouts assigned. The Nook HD+ has a unique connector layout from what I can tell.
It's similar to this:
...1...3...5...
...|...|...|...|...|...|...|...|...|...|...|...|..|...|...|
.+-v---v---v---v---v---v---v---v---v---v---v---v---v---v---v---+
.|
.+---^---^---^---^---^---^---^---^---^---^---^---^---^---^---^-+
.....|...|...|...|...|...|...|...|...|...|...|...|..|...|...|
.....2...4...6...
The Apple and Samsung have all pins on one side only, at double the density.
octachoron said:
Here's the pinout I've got so far:
Pin - Signal
--------------------------------------
...
Click to expand...
Click to collapse
Thanks!
Also, there are two test points, SDA2-TX and SCL2-RX. These are I2C test points but I can't tell if they are the HDMI side or the system side. The HDMI chip is the TI TPD12s015, datasheet can be googled. Just a hunch that these are the HDMI side, since the datasheet says SDA_B and SCL_B are HDMI side, and they're labeled as SDA2 and SCL2.
Click to expand...
Click to collapse
the TX one is the serial out, I got Adam Outler here at ABBQ to solder into it and I got the console out. Sadly it's not mapped anywhere in the connector, but at least I got my serial out now. We are less sure about the RX one, but I'll try it out once I get back home on Sunday.
Big thanks to Adam too!
TX & RX
verygreen said:
ThankDCCs!
the TX one is the serial out, I got Adam Outler here at ABBQ to solder into it and I got the console out. Sadly it's not mapped anywhere in the connector, but at least I got my serial out now. We are less sure about the RX one, but I'll try it out once I get back home on Sunday.
Big thanks to Adam too!
Click to expand...
Click to collapse
This is just a guess, but would not TX = transmit & RX = Recieve ?
Jimcisme said:
This is just a guess, but would not TX = transmit & RX = Recieve ?
Click to expand...
Click to collapse
Yes.
So TX definitely transmits the console output, we see it.
But tryign to input stuff onto RX pin does not result in anything visible, so that's why we are less sure if that's the input into the serial console.
But even if not, the console output is the more important one anyway for my kernel debugging plans.
Host Mode?
Does this imply that using the app to change USB to host mode will not work? I have seen several articles on using app with gender changer to get external keyboard or storage to HD+
I opened my Nook HD+, too. And I took some photos.
i40.tinypic.com/6yljxx.jpg
i40.tinypic.com/2yyrspi.jpg
Sorry, new user prevented from posting outside links in their messages.
Now I wonder if 5 test points of USB VBUS (+5VDC)、USB D-、USB D+、GND and USB-ID are connected to a MicroUSB Female adapter (5 pin) like most of Android smartphones and pads, will a MHL MicroUSB to HDMI cable work with the Nook HD+ ?
Has anyone ever opened up the HDMI adapter?
I would like to see whats inside before I rip mine open.
emottau said:
I'm surprised no one has done this yet. I read somewhere that b&n simply modified an iPod connector and often times I've found that means they simply changed the order of the wires in order to gain propriety and therefore extra revenue. I have Two hd+ sitting on my desk with no charge because I'm too cheap to pay 30 bucks for a cable from b&n. I also have one charging cable cut in half so maybe I'll get on this myself, not that I can really take on another project at the moment.
Click to expand...
Click to collapse
octachoron said:
I opened my Nook HD+, and there is a test point near the dock connector labeled usb-id. If this TP is shorted to GND with a slave USB device attached thru a USB-A to A gender bender, the Nook acts as host as expected per USB-OTG standard. This TP maps to pin 24. Unfortunately, this isn't one of the pins to a Nook HD+ USB cable.
The Nook HD+'s motherboard is labeled EXCELLENTLY. I've gotten most of the pins I can get easily. I think the remaining pins are for HDMI (which makes sense seeing B&N makes an HDMI adapter cable...). The HDMI adapter cable will probably get the remaining pins.
Here's the pinout I've got so far:
Pin - Signal
--------------------------------------
1 - USB VBUS (+5VDC)
2 - USB VBUS (+5VDC)
3 - HDMI 5V
4 - LINEOUT-DTC
5 - USB D-
6 - USB D+
7 -
8 -
9 -
10- GND
11-
12-
13- GND
14-
15-
16- GND
17-
18-
19- GND
20-
21-
22-
23-
24- USB-ID
25- LINE-L (Audio)
26- GND
27- LINE-R (Audio)
28- GND
29- GND
30- GND
---------- Post added at 06:27 AM ---------- Previous post was at 06:04 AM ----------
Also, there are two test points, SDA2-TX and SCL2-RX. These are I2C test points but I can't tell if they are the HDMI side or the system side. The HDMI chip is the TI TPD12s015, datasheet can be googled. Just a hunch that these are the HDMI side, since the datasheet says SDA_B and SCL_B are HDMI side, and they're labeled as SDA2 and SCL2.
Click to expand...
Click to collapse
Here is an updated pinout + PCB fragment with connector
Pin - Signal
--------------------------------------
1 - USB VBUS (+5VDC)
2 - USB VBUS (+5VDC)
3 - HDMI 5V
4 - LINEOUT-DTC
5 - USB D-
6 - USB D+
7 - GND
8 - GND
9 - HDMI CLK-
10- GND
11- HDMI CLK+
12- HDMI D0-
13- GND
14- HDMI D0+
15- HDMI D1-
16- GND
17- HDMI D1+
18- HDMI D2-
19- GND
20- HDMI D2+
21- GND
22- SDA2-TX(SCL2-RX?) - To be checked. Tx/Rx contact order according to HDMI connector pinout
23- SCL2-RX(SDA2-TX?)
24- USB-ID
25- LINE-L (Audio)
26- AGND
27- LINE-R (Audio)
28- AGND
29- GND
30- GND
As you can see, there is full HDMI signals set, so adaptor is just pass-through connection, no external chip needed in adaptor.
Regarding RX, it goes through TI TPD12s015. The PCB pad sits on chip output (system side), which is open-drain and can suppress this signal when HDMI 5V is not activated (reflecting connector's side not powered from HDMI 5V pullup). To activate it TPD12s015 input LS_OE and CT_CP_HPD must be set high (OMAP GPIOs) - VDAC-HDMI pad near processor?
But maybe CONS_2700_UART1 connector near processor will be more suitable for console?
the becalab
onlycash said:
Has anyone ever opened up the HDMI adapter?
I would like to see whats inside before I rip mine open.
Click to expand...
Click to collapse
Yes, that.
Have you done any ripping? I don't really have a use for the HDMI cable, but would buy and rip if I could get my mitts on the line level outputs. Can't imagine they'd plumb those, but I can dream.
Here is photos of my hdmi adapter(remove spaces from urls):
Code:
dropbox .com/s/f0tymbsva3cwwcb/hdmi1.JPG
dropbox .com/s/lpvubhb8at7lc8q/hdmi2.JPG
dropbox .com/s/pdw6ibn2zema04n/hdmi3.JPG
It is not so simple as i thought.
This is all very interesting, and some nice pics. I wonder, has anyone attempted (or even considered) to replace the annoying proprietary connector by soldering a replacement micro-USB onto the PCB? Is it even viable?
I can't understand why they would be so daft as to introduce a non-standard connection. Apple can just about get away with it because, well, they're Apple.

Categories

Resources