Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Kobo Reader

Notices

Reply
 
Thread Tools Search this Thread
Old 05-07-2012, 09:34 AM   #1
meskusala
Junior Member
meskusala began at the beginning.
 
Posts: 4
Karma: 10
Join Date: May 2012
Device: none
USB Host Mode on Kobo?

Hi all!

Does anyone know if it is possible to get USB host mode on Kobo? I don't own the device so I can not investigate this myself, but if someone with a terminal could find out what USB controller is used, that would be awesome!

Now, I am not sure what commands would give the most relevant info, but imagine that dmesg would give something useful. It is in busybox, so running
Code:
busybox dmesg
should work . Depending on how the kernel is configured
Code:
lsmod
might be interesting as well.

I have no idea what bus the Kobo uses, but
Code:
lspci -vv
could be worth a try as well .

Thanks!
meskusala is offline   Reply With Quote
Old 05-08-2012, 05:20 PM   #2
frankieGom
Interested
frankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcoverfrankieGom exercises by bench pressing the entire Harry Potter series in hardcover
 
frankieGom's Avatar
 
Posts: 131
Karma: 16358
Join Date: Aug 2011
Location: Paris suburb, France
Device: Kobo Touch & Glo, Sony PRS-T1
Here goes... good luck

François

[root@Kobo1 /]# lspci -vv
-sh: lspci: not found
[root@Kobo1 /]# lsmod
ar6000 308622 0 - Live 0x7f000000

[root@Kobo1 /]# busybox dmesg
me of devices complete after 0.154 msecs
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.535 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.368 msecs
PM: late suspend of devices complete after 0.214 msecs
PM: early resume of devices complete after 0.154 msecs
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.500 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.249 msecs
PM: late suspend of devices complete after 0.221 msecs
PM: early resume of devices complete after 0.155 msecs
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.597 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.305 msecs
PM: late suspend of devices complete after 0.216 msecs
PM: early resume of devices complete after 0.155 msecs
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.339 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.338 msecs
PM: late suspend of devices complete after 0.219 msecs
PM: early resume of devices complete after 0.154 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.299 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.332 msecs
PM: late suspend of devices complete after 0.215 msecs
PM: early resume of devices complete after 0.153 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.180 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.348 msecs
PM: late suspend of devices complete after 0.220 msecs
PM: early resume of devices complete after 0.153 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.130 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.321 msecs
PM: late suspend of devices complete after 0.217 msecs
PM: early resume of devices complete after 0.154 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.326 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.300 msecs
PM: late suspend of devices complete after 0.215 msecs
PM: early resume of devices complete after 0.154 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.312 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.313 msecs
PM: late suspend of devices complete after 0.214 msecs
PM: early resume of devices complete after 0.153 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.227 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.306 msecs
PM: late suspend of devices complete after 0.215 msecs
PM: early resume of devices complete after 0.154 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.377 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.313 msecs
PM: late suspend of devices complete after 0.211 msecs
PM: early resume of devices complete after 0.154 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.274 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.339 msecs
PM: late suspend of devices complete after 0.220 msecs
PM: early resume of devices complete after 0.154 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.150 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.353 msecs
PM: late suspend of devices complete after 0.217 msecs
PM: early resume of devices complete after 0.154 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.160 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.356 msecs
PM: late suspend of devices complete after 0.215 msecs
PM: early resume of devices complete after 0.154 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.171 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.324 msecs
PM: late suspend of devices complete after 0.218 msecs
PM: early resume of devices complete after 0.153 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.166 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.329 msecs
PM: late suspend of devices complete after 0.218 msecs
PM: early resume of devices complete after 0.153 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.156 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.355 msecs
PM: late suspend of devices complete after 0.217 msecs
PM: early resume of devices complete after 0.153 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.353 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.342 msecs
PM: late suspend of devices complete after 0.215 msecs
PM: early resume of devices complete after 0.154 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.245 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
PM: Preparing system for mem sleep
Freezing user space processes ... (elapsed 0.01 seconds) done.
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
pmic_battery_suspend
DVFS is stopped
PM: suspend of devices complete after 1.370 msecs
PM: late suspend of devices complete after 0.215 msecs
PM: early resume of devices complete after 0.153 msecs
power_supply mc13892_bat: Battery above 3.4V
DVFS is started
pmic_battery_resume
PM: resume of devices complete after 544.268 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
[semco] ar6000_pm_probe
[semco] call plat_setup_power_stub!
mmc1: queuing unknown CIS tuple 0x01 (3 bytes)
mmc1: queuing unknown CIS tuple 0x1a (5 bytes)
mmc1: queuing unknown CIS tuple 0x1b (8 bytes)
mmc1: queuing unknown CIS tuple 0x14 (0 bytes)
mmc1: queuing unknown CIS tuple 0x80 (1 bytes)
mmc1: queuing unknown CIS tuple 0x81 (1 bytes)
mmc1: queuing unknown CIS tuple 0x82 (1 bytes)
mmc1: new high speed SDIO card at address 0001
[semco] Host Rev: 0x3000016c(3.0.0.364)-r57
AR6000: configuration opcode 3 is not used for Linux SDIO stack
[semco] Target Rev: 0x30000384(3.0.0.900)
AR6000: configuration opcode 3 is not used for Linux SDIO stack
HIF Interrupt processing is SYNC ONLY
AR6000: configuration opcode 7 is only used for RTOS systems, not Linux systems
AR6000: configuration opcode 5 is not used for Linux SDIO stack
In aggr_init..
going out of aggr_init..status OK
[semco] ath6k/AR6003/hw2.0/A30H_Generic_20101118.bin
[semco] ath6k/AR6003/hw2.0/otp.bin.z77
[semco] ath6k/AR6003/hw2.0/athwlan.bin.z77
[semco] ath6k/AR6003/hw2.0/data.patch.bin
ar6000_init() Got WMI @ 0x8f93ae60.
Target Ready: credits: 25 credit size: 1664
AR6K: ** HIF layer does not support scatter requests (17)
AR6K: virtual scatter transfers enabled (max scatter items:16: maxlen:16384)
AR6K: max recv: 16384 max send: 12288
ar6000_init() WMI is ready
wmi_control_rx() : Unknown id 0x101e
AR6000 Reg Code = 0x61
Add Filter 0 = 5e:00:00:01
channel hint set to 2452
AR6000 scan complete: 16
Keep Filter 0 = 5e:00:00:01
WMM params
AC 0, ACM 0, AIFSN 3, CWmin 4, CWmax 10, TXOPlimit 0
AC 1, ACM 0, AIFSN 7, CWmin 4, CWmax 10, TXOPlimit 0
AC 2, ACM 0, AIFSN 2, CWmin 3, CWmax 4, TXOPlimit 94
AC 3, ACM 0, AIFSN 2, CWmin 2, CWmax 3, TXOPlimit 47
AR6000 connected event on freq 2452
with bssid 00:24:d4:e5:8d:a8 listenInterval=4, beaconInterval = 96, beaconIeLen = 22 assocReqLen=61 assocRespLen =48
Network: Infrastructure
AR6000 Neighbor Report Event
bssid 00:24:d4:e5:8d:a8

AR6000 scan complete: 0
AR6000 Neighbor Report Event
bssid 00:24:d4:e5:8d:a8

AR6000 scan complete: 0
Keep Filter 0 = 5e:00:00:01
channel hint set to 2452
AR6000 disconnected
from 00:24:d4:e5:8d:a8
Disconnect Reason is 3, Status Code is 3
WMM params
AC 0, ACM 0, AIFSN 2, CWmin 4, CWmax 10, TXOPlimit 0
AC 1, ACM 0, AIFSN 7, CWmin 4, CWmax 10, TXOPlimit 0
AC 2, ACM 0, AIFSN 2, CWmin 3, CWmax 4, TXOPlimit 94
AC 3, ACM 0, AIFSN 2, CWmin 2, CWmax 3, TXOPlimit 47
WMM params
AC 0, ACM 0, AIFSN 3, CWmin 4, CWmax 10, TXOPlimit 0
AC 1, ACM 0, AIFSN 7, CWmin 4, CWmax 10, TXOPlimit 0
AC 2, ACM 0, AIFSN 2, CWmin 3, CWmax 4, TXOPlimit 94
AC 3, ACM 0, AIFSN 2, CWmin 2, CWmax 3, TXOPlimit 47
AR6000 connected event on freq 2452
with bssid 00:24:d4:e5:8d:a8 listenInterval=4, beaconInterval = 96, beaconIeLen = 22 assocReqLen=61 assocRespLen =48
Network: Infrastructure
Keep Filter 0 = 5e:00:00:01
Keep Filter 0 = 5e:00:00:01
AR6000 Neighbor Report Event
bssid 00:24:d4:e5:8d:a8

AR6000 Neighbor Report Event
bssid 00:24:d4:e5:8d:a8

AR6000 Neighbor Report Event
bssid 00:24:d4:e5:8d:a8

AR6000 Neighbor Report Event
bssid 00:24:d4:e5:8d:a8

AR6000 Neighbor Report Event
bssid 00:24:d4:e5:8d:a8

AR6000 Neighbor Report Event
bssid 00:24:d4:e5:8d:a8

AR6000 Neighbor Report Event
bssid 00:24:d4:e5:8d:a8

[root@Kobo1 /]#
frankieGom is offline   Reply With Quote
Old 05-08-2012, 08:15 PM   #3
meskusala
Junior Member
meskusala began at the beginning.
 
Posts: 4
Karma: 10
Join Date: May 2012
Device: none
Thank you, François!

Unfortunately, dmesg seems to not remember the last time the device rebooted and shows the suspend/wake up cycle. But the mention of SDIO got me digging .

Looking at the Freescale i.MX508 documentation (processor in Kobo Touch) tells us that the chip provides two ports: one OTG, the other host mode. Sounds good . The physical port on the device looks like a micro-B, but I could not find any decent pictures. Could anyone confirm this?

Another thing I liked in the docs was the mention of 5 (!) UART ports, I wonder if there are any that one could easily (with the help of soldering iron) connect to...
meskusala is offline   Reply With Quote
Old 05-10-2012, 04:04 AM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 6,073
Karma: 6108201
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo Touch, Kobo Glo
Quote:
Originally Posted by meskusala View Post
Looking at the Freescale i.MX508 documentation (processor in Kobo Touch) tells us that the chip provides two ports: one OTG, the other host mode. Sounds good . The physical port on the device looks like a micro-B, but I could not find any decent pictures. Could anyone confirm this?
Yes, it is a micro-B USB socket. But, I can't answer the other questions.

Last edited by davidfor; 05-10-2012 at 04:07 AM.
davidfor is offline   Reply With Quote
Old 05-10-2012, 04:16 PM   #5
ah-
Connoisseur
ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.ah- could sell banana peel slippers to a Deveel.
 
Posts: 64
Karma: 3062
Join Date: Jan 2012
Device: Kobo Touch
This might be useful: https://github.com/kobolabs/Kobo-Reader
ah- is offline   Reply With Quote
Old 05-10-2012, 10:45 PM   #6
meskusala
Junior Member
meskusala began at the beginning.
 
Posts: 4
Karma: 10
Join Date: May 2012
Device: none
Thanks, this definitely is useful . It is a bit sad that instead of using a microSD card for internal memory (which was the case for the original Kobo), Kobo Touch has a regular flash chip. At least with the microSD card you could recover even if you messed up the kernel. I'm not sure if there is a way to recover from that in Kobo Touch...
meskusala is offline   Reply With Quote
Old 05-16-2012, 04:51 PM   #7
stef70
Member
stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.
 
Posts: 24
Karma: 1302
Join Date: Jun 2011
Device: Kobo Touch
The 2GB of internal flash memory of the KT provides 3 partitions:

/dev/mmcblk0p1 is the root partition (about 256MB)
/dev/mmcblk0p2 is the rescue partition (about 256MB)
/dev/mmcblk0p3 is the user partition (about 1.4GB) and contains the books and other user files

So the system with all firmware upgrades is entirely contained in the root partition.
The rescue partition contains a copy of the root partition with the original firmware (mine has a 1.9.0)

If you make a mistake in the root partition, just perform a factory reset (keep the button pressed while booting) and the rescue partition will be copied to the root partition. The books in the user partition will also be removed.

So, as far as I know, it is not possible to put the KT in a non-recoverable state as long as the rescue partition is not modified.
stef70 is offline   Reply With Quote
Old 05-16-2012, 05:16 PM   #8
meskusala
Junior Member
meskusala began at the beginning.
 
Posts: 4
Karma: 10
Join Date: May 2012
Device: none
Hehe . Good news then... Anyway, the more I hear about Kobo the more I like it. I'll try to get my hands on one at about June and then... Well, open it up . Will post any useful results!
meskusala is offline   Reply With Quote
Old 05-17-2012, 06:05 AM   #9
dasjoe
Junior Member
dasjoe began at the beginning.
 
Posts: 1
Karma: 10
Join Date: May 2012
Device: Kobo Touch
It's likely you'll see a bunch of serial headers. You'll also notice how the "internal flash memory" resides on a MicroSD card, which is easily replaceable.

Didn't get the Kobo to recognize larger partitions than the ones on the original card, although I didn't really try.
Edit: Actually, growing the data partition with gparted worked like a charm. It now reports I have 7500 MB available.


Last edited by dasjoe; 05-17-2012 at 08:47 PM.
dasjoe is offline   Reply With Quote
Old 05-21-2012, 05:58 AM   #10
stef70
Member
stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.stef70 is no ebook tyro.
 
Posts: 24
Karma: 1302
Join Date: Jun 2011
Device: Kobo Touch
Internal MicroSD card?

Strange... I opened my KT a few month ago and I do not remember any internal MicroSD card. I bought it very early so they may have changed the design.
stef70 is offline   Reply With Quote
Old 01-13-2013, 03:34 PM   #11
maza
Junior Member
maza began at the beginning.
 
Posts: 2
Karma: 10
Join Date: Jan 2013
Device: Kobo touch
Here is output from my Kobo touch.


Code:
[root@(none) /etc]# dmesg
Linux version 2.6.35.3-850-gbc67621+ (gallen@gallen-desktop) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #325 PREEMPT Wed May 23 09:35:44 CST 2012
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Freescale MX50 Reference Design Platform
...
CPU is i.MX50 Revision 1.1
[check_hardware_name-233] PCBA ID is 1
Using SDMA I.API
MXC DMA API initialized
IMX usb wakeup probe
the wakeup pdata is 0x80383520
IMX usb wakeup probe
the wakeup pdata is 0x803835d4
bio: create slab <bio-0> at 0
regulator: DCDC_3V15: 3150 mV 
SCSI subsystem initialized
CSPI: mxc_spi-2 probed
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
...
Serial: MXC Internal UART driver
mxcintuart.0: ttymxc0 at MMIO 0x53fc0000 (irq = 32) is a Freescale i.MX
console [ttymxc0] enabled, bootconsole disabled
mxcintuart.1: ttymxc1 at MMIO 0x53fbc000 (irq = 31) is a Freescale i.MX
mxcintuart.2: ttymxc2 at MMIO 0x5000c000 (irq = 33) is a Freescale i.MX
loop: module loaded
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[msp_int-1142] MSP430 interrupt triggered !!!
[arch/arm/plat-mxc/usb_common.c-343] usbh1_set_utmi_xcvr() 
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.1: irq 14, io base 0x53f80200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
MXC keypad loaded
input: mxckpd as /devices/virtual/input/input0
input: zForce-ir-touch as /devices/virtual/input/input1
...
Waiting for root device /dev/mmcblk0p1...
mmc0: new high speed SD card at address aaaa
mmcblk0: mmc0:aaaa SU02G 1.84 GiB 
 mmcblk0: p1 p2 p3
EXT4-fs (mmcblk0p1): recovery complete
EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:1.
Freeing init memory: 112K
EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
S1D13522 regiseter 10(0xa) not support !

==== [pvi_ioctl_Reset] 0x0a=0x0000====
fake_s1d13522_parse_epd_cmdline : epd cmdline parse already done .
client0 ,addr=0x48,name=lm75-1
[PROGRESS_BAR-2654] No progess ...
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
DVFS is started
lm75 temprature data = 0x12c0,18
ARC USBOTG Device Controller driver (1 August 2005)
Waiting arm_podf enabled!
ehci_fsl_bus_suspend, Host 1
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
Waiting arm_podf enabled!
usb0: MAC 9e:3c:11:1b:19:ca
usb0: HOST MAC 32:11:69:6c:a5:2b
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
dr_controller_run: udc enter low power mode 
fsl-usb2-udc: bind to driver g_ether 
Waiting arm_podf enabled!
Waiting arm_podf enabled!
usb unplugged
...
Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)
USB Host suspend begins
ehci_fsl_drv_suspend, pm event 
udc suspend begins
USB Gadget suspend ends
[sdhci_suspend-1755] skip suspend for mmc1
DVFS is stopped
PM: suspend of devices complete after 3.296 msecs
suspend wp cpu=800000000
PM: late suspend of devices complete after 0.182 msecs
PM: early resume of devices complete after 0.115 msecs
DVFS is started
[sdhci_resume-1792] skip resume for mmc1
USB Gadget resume begins
fsl_udc_resume, Wait for wakeup thread finishes
dr_controller_run: udc enter low power mode 
USB Gadget resume ends
ehci fsl drv resume begins: Host 1
ehci_fsl_drv_resume,pm event, wait for wakeup irq if needed
ehci_fsl_bus_resume, Host 1
PM: resume of devices complete after 217.920 msecs
PM: Finishing wakeup.
Restarting tasks ... done.
[mxc_rtc_ioctl-106] Micro P MSP430 status 0x0808 ....
[ntx_get_battery_vol-1113] 100
Waiting arm_podf enabled!
Waiting arm_podf enabled!
pvi_io : do not get the command [242]
lm75 temprature data = 0x1360,19
Waiting arm_podf enabled!
Waiting arm_podf enabled!
ehci_fsl_bus_suspend, Host 1
usb wakeup is here
the otgsc is 0x82c2f20, usbsts is 0x80, portsc is 0x1c000004, wakeup_irq is 0x80000000
otg udc vbus rising wakeup
try_wake_up_udc: udc out low power mode
[msp_int-1142] MSP430 interrupt triggered !!!
g_ether gadget: high speed config #1: CDC Ethernet (ECM)
usb plugged 1-0
power_supply mc13892_charger: charger status: online
The last part is probably caused by that I put the device in sleep mode and then connected usb. Then device woke up from sleep mode.

Code:
[root@(none) /etc]# lsmod
g_ether 32325 0 - Live 0x7f00b000
arcotg_udc 16843 1 g_ether, Live 0x7f000000
I have enabled Telnet/FTP USB (http://wiki.mobileread.com/wiki/Kobo_Touch_Hacking ). These are the modules that loaded to make it work. No other modules seems to be loaded.

Code:
[root@(none) /etc]# busybox lspci -vv
lspci: /sys/bus/pci/devices: No such file or directory
maza is offline   Reply With Quote
Old 01-13-2013, 04:55 PM   #12
maza
Junior Member
maza began at the beginning.
 
Posts: 2
Karma: 10
Join Date: Jan 2013
Device: Kobo touch
maybe the visible USB plug supports USB OTG and just goes in the host mode when usb otg cabel is used.. I don't have such cable, but if someone has it would be nice to try and look what "dmesg" contains.
maza is offline   Reply With Quote
Old 08-17-2013, 08:34 AM   #13
kenoi
Member
kenoi began at the beginning.
 
Posts: 10
Karma: 10
Join Date: Aug 2013
Device: Kobo Glo
Verdict?

Has there been a verdict on OTG support with (non-Android) Kobo devices?
kenoi is offline   Reply With Quote
Old 08-19-2013, 01:15 AM   #14
kenoi
Member
kenoi began at the beginning.
 
Posts: 10
Karma: 10
Join Date: Aug 2013
Device: Kobo Glo
According to Kobo technical support there is no support for OTG in Kobo Glo/Touch/Aura. Has anyone succeeded in getting OTG support on their Kobo through a custom kernel?
kenoi is offline   Reply With Quote
Old 08-19-2013, 01:30 AM   #15
PeterT
Taking a break; Fed up
PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.PeterT ought to be getting tired of karma fortunes by now.
 
PeterT's Avatar
 
Posts: 7,354
Karma: 46281507
Join Date: Nov 2007
Location: Toronto
Device: Wife: Touch, Arc, Vox Me: Nexus 7, Glo
There is a project who's name escapes me right now that involves using a Kobo as a flight display for (possibly) a glider.

They have a custom kernel, and I believe have also done some hardware mods to add OTG support.
PeterT is online now   Reply With Quote
Reply

Tags
kobo ush host

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
USB Host Mode (Master Mode) on K3 ericepe Kindle Developer's Corner 1 01-24-2012 05:59 AM
USB host mode hacking scotsman iRex 22 08-04-2010 07:29 PM
302 USB host mode, or: WOW! Serif PocketBook 5 06-10-2010 06:35 AM
USB Host Mode? brecklundin PocketBook 2 11-19-2009 03:49 AM
Host USB? fargo iRex 6 05-05-2008 06:36 PM


All times are GMT -4. The time now is 11:37 PM.


MobileRead.com is a privately owned, operated and funded community.