gt-s5570 and pl2303.ko
Hello, I want to communicate my android gt-s5570 with microcontroller via usb to serial communication adapter (Prolific pl2303hxd chip uart to rs232). Kernel is 2.6.35.7 version (custom ROM jb 4.2.2) and I compiled pl2303.ko module and installed with insmod command without errors. Also I created 8 devices as: mknod /dev/ttyUSB0 c 188 0 mknod /dev/ttyUSB1 c 188 1 ... and so on. But when I connect converter with otg cable nothing happens. Simpletest apk finds no devices and dmesg shows nothing related to inserted pl2303 converter. What can be the reason why android doesn't detect connected adapter? Thank you in advance, Milutin Aksic. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: gt-s5570 and pl2303.ko
Hello Greg, I supose that serial communication should work with this older model gt-s5570. I found custom rom with that old kernel version but I don't know how to find newer version for this phone. When I plug the converter to phone I can't see anything in the log that is related to converter but I send you the log as attachment. It is log when I insmod pl2303.ko via adb and after that pluged the converter. Bye. Milutin. > Date: Thu, 19 Feb 2015 13:27:22 -0800 > From: g...@kroah.com > To: milutin.ak...@hotmail.com > CC: linux-usb@vger.kernel.org > Subject: Re: gt-s5570 and pl2303.ko > > On Thu, Feb 19, 2015 at 02:55:24PM +0100, Milutin Aksic wrote: > > Hello, > > I want to communicate my android gt-s5570 with microcontroller via usb to > > serial communication adapter (Prolific pl2303hxd chip uart to rs232). Kernel > > is 2.6.35.7 version (custom ROM jb 4.2.2) and I compiled pl2303.ko module > > Eeek, 2.6.35? That's just _so_ old it's not funny, and nothing that any > community member can ever support, sorry. If you ar stuck with that > kernel version due to a vendor, please work with that vendor to solve > your issue, as you are paying support from them. > > > and installed with insmod command without errors. Also I created 8 devices > > as: > > mknod /dev/ttyUSB0 c 188 0 > > mknod /dev/ttyUSB1 c 188 1 ... > > Why would you do this? devtmpfs should have created them automatically > when the device is plugged in and bound to the driver? > > > and so on. But when I connect converter with otg cable nothing happens. > > Simpletest apk finds no devices and dmesg shows nothing related to inserted > > pl2303 converter. > > What does the kernel log show when you plug the device in? > > thanks, > > greg k-h <3>[46758.228075] [Battery] msm_batt_check_event <4>[46758.228578] [Battery] vbatt_adc-BATT_CAL_CHG <3>[46768.248122] [Battery] msm_batt_check_event <4>[46768.248625] [Battery] vbatt_adc-BATT_CAL_CHG <3>[46778.268000] [Battery] msm_batt_check_event <4>[46778.268498] [Battery] vbatt_adc-BATT_CAL_CHG <3>[46788.287963] [Battery] msm_batt_check_event <4>[46788.288458] [Battery] vbatt_adc-BATT_CAL_CHG <3>[46798.308112] [Battery] msm_batt_check_event <4>[46798.308617] [Battery] vbatt_adc-BATT_CAL_CHG <3>[46806.083895] usbserial: version magic '2.6.35.7+-androidarmv6 preempt mod_unload ARMv6 ' should be '2.6.35.7-androidarmv6+ preempt mod_unload ARMv6 ' <6>[46806.219275] usbcore: registered new interface driver usbserial <6>[46806.220047] USB Serial support registered for generic <6>[46806.220783] usbcore: registered new interface driver usbserial_generic <6>[46806.220832] usbserial: USB Serial Driver core <3>[46808.328000] [Battery] msm_batt_check_event <4>[46808.328490] [Battery] vbatt_adc-BATT_CAL_CHG <3>[46811.989677] pl2303: version magic '2.6.35.7+-androidarmv6 preempt mod_unload ARMv6 ' should be '2.6.35.7-androidarmv6+ preempt mod_unload ARMv6 ' <6>[46812.029715] USB Serial support registered for pl2303 <6>[46812.030512] usbcore: registered new interface driver pl2303 <6>[46812.030557] pl2303: Prolific PL2303 USB to serial adaptor driver <1>[46813.901103] AR6000 Neighbor Report Event <1>[46813.901165] <3>[46818.348133] [Battery] msm_batt_check_event <4>[46818.348632] [Battery] chg_en & prevVal <3>[46828.368093] [Battery] msm_batt_check_event <4>[46828.368595] [Battery] vbatt_adc-BATT_CAL_CHG <3>[46838.388367] [Battery] msm_batt_check_event <4>[46838.388863] [Battery] chg_en & prevVal <3>[46848.408025] [Battery] msm_batt_check_event <4>[46848.408530] [Battery] chg_en & prevVal <3>[46858.428022] [Battery] msm_batt_check_event <4>[46858.428510] [Battery] vbatt_adc-BATT_CAL_CHG <3>[46868.448060] [Battery] msm_batt_check_event <4>[46868.448555] [Battery] vbatt_adc-BATT_CAL_CHG <1>[46875.441727] AR6000 Neighbor Report Event <1>[46875.441797] <3>[46878.468012] [Battery] msm_batt_check_event <4>[46878.468515] [Battery] chg_en & prevVal <3>[46888.487987] [Battery] msm_batt_check_event <4>[46888.488480] [Battery] vbatt_adc-BATT_CAL_CHG <3>[46898.508057] [Battery] msm_batt_check_event <4>[46898.508558] [Battery] chg_en & prevVal <6>[46903.596590] [FSA9280]: irq active <3>[46903.596680] [Battery] battery_restart <6>[46903.596757] [FSA9280]: irq release <3>[46903.596858] [Battery] msm_fsa9280_check_event <6>[46903.597533] [FSA9280]: irq active <3>[46903.597563] [Battery] battery_restart <6>[46903.597600] [FSA9280]: irq release <6>[46903.597852] [FSA9280]: ir
Re: gt-s5570 and pl2303.ko
On 02/20/2015 04:31 PM, Greg KH wrote: On Fri, Feb 20, 2015 at 11:22:54AM +0100, Milutin Aksic wrote: Hello Greg, I supose that serial communication should work with this older model gt-s5570. I found custom rom with that old kernel version but I don't know how to find newer version for this phone. When I plug the converter to phone I can't see anything in the log that is related to converter but I send you the log as attachment. It is log when I insmod pl2303.ko via adb and after that pluged the converter. Looks like you haven't loaded a usb host controller driver for your hardware. Are you sure you have such a thing loaded and working? Does other types of USB devices work when plugged into this machine? You really are on your own here, sorry. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html I found host controller drivers in menuconfig and compiled them and inserted with insmod and again nothing happened.I tried with usb flash but nothing happened. I send you log for this. You will see in the log those drivers that I loaded (there is compliant about kernel version but insmod command passed and the modules are in /sys/module directory) and I didn't see anything related to usb converter and mass storage. The host controller drivers I loaded are : isp116x-hcd.ko, isp1760.ko, oxu210hp-hcd.ko, sl811-hcd.ko. That's it. Milutin. isp1362_hcd: version magic '2.6.35.7+-androidarmv6 preempt mod_unload ARMv6 ' should be '2.6.35.7-androidarmv6+ preempt mod_unload ARMv6 ' <4>[66113.287000] isp1362_hcd: Unknown symbol bitmap_find_next_zero_area (err 0) <3>[66115.188056] [Battery] msm_batt_check_event <1>[66119.274070] AR6000 Neighbor Report Event <1>[66119.274128] <3>[66125.207986] [Battery] msm_batt_check_event <4>[66128.358273] [BACLKIGHT] : 100 <4>[66128.358315] [LCD] BACKLIGHT SET <4>[66128.358350] Platform V:100, Find V:9 <4>[66128.374586] [BACLKIGHT] : 97 <4>[66128.374620] [LCD] BACKLIGHT SET <4>[66128.374653] Platform V:97, Find V:9 <4>[66128.391071] [BACLKIGHT] : 93 <4>[66128.391103] [LCD] BACKLIGHT SET <4>[66128.391136] Platform V:93, Find V:9 <4>[66128.407720] [BACLKIGHT] : 90 <4>[66128.407751] [LCD] BACKLIGHT SET <4>[66128.407783] Platform V:90, Find V:8 <4>[66128.425515] [BACLKIGHT] : 87 <4>[66128.425553] [LCD] BACKLIGHT SET <4>[66128.425585] Platform V:87, Find V:8 <4>[66128.443371] [BACLKIGHT] : 83 <4>[66128.443406] [LCD] BACKLIGHT SET <4>[66128.443440] Platform V:83, Find V:8 <4>[66128.458020] [BACLKIGHT] : 80 <4>[66128.458051] [LCD] BACKLIGHT SET <4>[66128.458085] Platform V:80, Find V:8 <4>[66128.474355] [BACLKIGHT] : 77 <4>[66128.474386] [LCD] BACKLIGHT SET <4>[66128.474420] Platform V:77, Find V:7 <4>[66128.491251] [BACLKIGHT] : 73 <4>[66128.491285] [LCD] BACKLIGHT SET <4>[66128.491316] Platform V:73, Find V:7 <4>[66128.507813] [BACLKIGHT] : 70 <4>[66128.507948] [LCD] BACKLIGHT SET <4>[66128.507983] Platform V:70, Find V:7 <4>[66128.524431] [BACLKIGHT] : 67 <4>[66128.524463] [LCD] BACKLIGHT SET <4>[66128.524495] Platform V:67, Find V:6 <4>[66128.541023] [BACLKIGHT] : 63 <4>[66128.541056] [LCD] BACKLIGHT SET <4>[66128.541088] Platform V:63, Find V:6 <4>[66128.557966] [BACLKIGHT] : 60 <4>[66128.558000] [LCD] BACKLIGHT SET <4>[66128.558031] Platform V:60, Find V:6 <4>[66128.574505] [BACLKIGHT] : 57 <4>[66128.574538] [LCD] BACKLIGHT SET <4>[66128.574570] Platform V:57, Find V:5 <4>[66128.591053] [BACLKIGHT] : 53 <4>[66128.591085] [LCD] BACKLIGHT SET <4>[66128.591118] Platform V:53, Find V:5 <4>[66128.607671] [BACLKIGHT] : 50 <4>[66128.607703] [LCD] BACKLIGHT SET <4>[66128.607735] Platform V:50, Find V:5 <4>[66128.624683] [BACLKIGHT] : 47 <4>[66128.624718] [LCD] BACKLIGHT SET <4>[66128.624751] Platform V:47, Find V:4 <4>[66128.642130] [BACLKIGHT] : 43 <4>[66128.642163] [LCD] BACKLIGHT SET <4>[66128.642196] Platform V:43, Find V:4 <4>[66128.657991] [BACLKIGHT] : 40 <4>[66128.658023] [LCD] BACKLIGHT SET <4>[66128.658055] Platform V:40, Find V:3 <4>[66128.674553] [BACLKIGHT] : 37 <4>[66128.674588] [LCD] BACKLIGHT SET <4>[66128.674620] Platform V:37, Find V:2 <4>[66128.691283] [BACLKIGHT] : 33 <4>[66128.691316] [LCD] BACKLIGHT SET <4>[66128.691348] Platform V:33, Find V:2 <4>[66128.734820] [BACLKIGHT] : 30 <4>[66128.734861] [LCD] BACKLIGHT SET <4>[66128.734893] Platform V:30, Find V:1 <4>[66128.737988] [BACLKIGHT] : 27 <4>[66128.738020] [LCD] BACKLIGHT SE
Re: gt-s5570 and pl2303.ko
On 02/20/2015 09:22 PM, Greg KH wrote: On Fri, Feb 20, 2015 at 05:37:37PM +0100, Milutin Aksic wrote: On 02/20/2015 04:31 PM, Greg KH wrote: On Fri, Feb 20, 2015 at 11:22:54AM +0100, Milutin Aksic wrote: Hello Greg, I supose that serial communication should work with this older model gt-s5570. I found custom rom with that old kernel version but I don't know how to find newer version for this phone. When I plug the converter to phone I can't see anything in the log that is related to converter but I send you the log as attachment. It is log when I insmod pl2303.ko via adb and after that pluged the converter. Looks like you haven't loaded a usb host controller driver for your hardware. Are you sure you have such a thing loaded and working? Does other types of USB devices work when plugged into this machine? You really are on your own here, sorry. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html I found host controller drivers in menuconfig and compiled them and inserted with insmod and again nothing happened.I tried with usb flash but nothing happened. I send you log for this. You will see in the log those drivers that I loaded (there is compliant about kernel version but insmod command passed and the modules are in /sys/module directory) and I didn't see anything related to usb converter and mass storage. The host controller drivers I loaded are : isp116x-hcd.ko, isp1760.ko, oxu210hp-hcd.ko, sl811-hcd.ko. That's it. Milutin. isp1362_hcd: version magic '2.6.35.7+-androidarmv6 preempt mod_unload ARMv6 ' should be '2.6.35.7-androidarmv6+ preempt mod_unload ARMv6 ' <4>[66113.287000] isp1362_hcd: Unknown symbol bitmap_find_next_zero_area (err 0) This means that the driver really didn't get loaded, so there's no way any USB devices could work on your system. Try fixing that up first... I fixed it and pl2303.ko and isp1362-hcd.ko loaded and registered without any errors and then pluged the converter and I think nothing happened sending you a log. Best regards, Milutin Aksic. <3>[ 1158.691813] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1158.691929] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1158.746828] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1158.747068] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.576239] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.576361] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.661988] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.662111] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.679193] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.679314] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.818993] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.819121] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.935216] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1159.935349] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.054038] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.054158] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.131698] [Battery] msm_batt_check_event <3>[ 1160.263098] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.263221] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.384104] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.384229] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.501316] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.501436] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.620126] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.620248] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.739431] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.739549] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.854791] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.854909] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.971298] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1160.971418] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1161.087951] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1161.088071] kgsl kgsl: |kgsl_yamato_ioctl| invalid ioctl code 40140931 <3>[ 1161.206566] kgsl
Re: gt-s5570 and pl2303.ko
On 02/20/2015 11:48 PM, Greg KH wrote: On Fri, Feb 20, 2015 at 11:37:17PM +0100, Milutin Aksic wrote: On 02/20/2015 09:22 PM, Greg KH wrote: On Fri, Feb 20, 2015 at 05:37:37PM +0100, Milutin Aksic wrote: On 02/20/2015 04:31 PM, Greg KH wrote: On Fri, Feb 20, 2015 at 11:22:54AM +0100, Milutin Aksic wrote: Hello Greg, I supose that serial communication should work with this older model gt-s5570. I found custom rom with that old kernel version but I don't know how to find newer version for this phone. When I plug the converter to phone I can't see anything in the log that is related to converter but I send you the log as attachment. It is log when I insmod pl2303.ko via adb and after that pluged the converter. Looks like you haven't loaded a usb host controller driver for your hardware. Are you sure you have such a thing loaded and working? Does other types of USB devices work when plugged into this machine? You really are on your own here, sorry. greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html I found host controller drivers in menuconfig and compiled them and inserted with insmod and again nothing happened.I tried with usb flash but nothing happened. I send you log for this. You will see in the log those drivers that I loaded (there is compliant about kernel version but insmod command passed and the modules are in /sys/module directory) and I didn't see anything related to usb converter and mass storage. The host controller drivers I loaded are : isp116x-hcd.ko, isp1760.ko, oxu210hp-hcd.ko, sl811-hcd.ko. That's it. Milutin. isp1362_hcd: version magic '2.6.35.7+-androidarmv6 preempt mod_unload ARMv6 ' should be '2.6.35.7-androidarmv6+ preempt mod_unload ARMv6 ' <4>[66113.287000] isp1362_hcd: Unknown symbol bitmap_find_next_zero_area (err 0) This means that the driver really didn't get loaded, so there's no way any USB devices could work on your system. Try fixing that up first... I fixed it and pl2303.ko and isp1362-hcd.ko loaded and registered without any errors and then pluged the converter and I think nothing happened sending you a log. Best regards, Milutin Aksic. If the host driver doesn't bind to the device and start up (you should see some log messages about finding a root hub) then no device will ever be found. sorry, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Ok, then what I should try else what can be the problem why host driver doesn't bind to the device? Maybe the phone gt-s5570 doesn't have any hardware (but I doubt it is the truth) or something else. Thanks Greg anyway, Milutin. -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
