How to differentiate between Kobo Touches: kobo_trilogy #421

Markismus · 2013-12-28T20:02:38Z

On the mobileread forum xping found a kobo touch that had ABS_X and ABS_Y swapped. This is to be expected from lines 365-366 of input.lua:

                -- FIXME some touch models should be treated as the other models,
                -- depending on board revision

After I asked him for more info, it is clear that function Device:getModel() and thus kobo_config.sh do not provide enough info to differentiate between versions.

kobo_config.sh:

#!/bin/sh
PCB=`ntx_hwconfig -s -p /dev/mmcblk0 PCB`
case $PCB in
        E60610D*) echo trilogy;;
        E606B*) echo kraken;;
        E5061*) echo pixie;;
        E606C*) echo dragon;;
        E606F*) echo phoenix;;
        *) echo trilogy;;
esac

Running the relevant command on Kobo Aura:

[root@(none) bin]# ntx_hwconfig -s -p /dev/mmcblk0
HW CONFIG v1.7 , size=39 bytes :
[0] PCB='E606F0B'
[1] KeyPad='FL_Key'
[2] AudioCodec='No'
[3] AudioAmp='No'
[4] Wifi='WC121A2'
[5] BT='No'
[6] Mobile='No'
[7] TouchCtrl='ektf2132'
[8] TouchType='C-Type'
[9] DisplayCtrl='MX508+TPS65185'
[10] DisplayPanel='6" Bottom EPD'
[11] RSensor='G Sensor'
[12] MicroP='MSP430'
[13] Customer='9'
[14] Battery='1500mA'
[15] Led='TYPE1'
[16] RamSize='256MB'
[17] IFlash='eMMC'
[18] ExternalMem='Micro SD'
[19] RootFsType='Ext4'
[20] SysPartType='TYPE3'
[21] ProgressXHiByte=0x01
[22] ProgressXLoByte=0x68
[23] ProgressYHiByte=0x02
[24] ProgressYLoByte=0xE4
[25] ProgressCnts=0x00
[26] ContentType=0x00
[27] CPU='mx50'
[28] UIStyle='Customer UI'
[29] RAMType='K4X2G323PC'
[30] UIConfig='Normal'
[31] DisplayResolution='1024x758'
[33] CPUFreq='1G'
[34] HallSensor='TLE4913'
[35] DisplayBusWidth='8Bits'
[36] FrontLight_Flags=BootON:OFF,TABLE1X:OFF
[37] PCB_Flags=NO_KeyMatrix:ON,FPC_Touch:OFF,LOGO_LED:OFF
[38] FrontLight_LEDrv='SY7201'

So the trilogy already uses all info available in field PCB

Has anybody an idea how to find the info xping gave:

Product no:N905-KBO-B
S/N: N905K342***** -B

The text was updated successfully, but these errors were encountered:

Markismus · 2013-12-28T20:09:15Z

Maybe we could differentiate based on displaycontroller.

Could people dump their ntx_hwconfig -s -p /dev/mmcblk0 output? Could especially those with a Kobo Touch also give their product and serial numbers?

Markismus · 2013-12-28T20:28:47Z

For my mother's Kobo Glo:

[root@(none) ~]# ntx_hwconfig -s -p /dev/mmcblk0
HW CONFIG v1.3 , size=35 bytes :
NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config file !!
[0] PCB='E606B0'
[1] KeyPad='FL_Key'
[2] AudioCodec='No'
[3] AudioAmp='No'
[4] Wifi='WC121A2'
[5] BT='No'
[6] Mobile='No'
[7] TouchCtrl='neonode_v2'
[8] TouchType='IR-Type'
[9] DisplayCtrl='MX508+TPS65185'
[10] DisplayPanel='6" Bottom EPD'
[11] RSensor='No'
[12] MicroP='MSP430'
[13] Customer='9'
[14] Battery='1000mA'
[15] Led='TYPE1'
[16] RamSize='256MB'
[17] IFlash='Micro SD'
[18] ExternalMem='Micro SD'
[19] RootFsType='Ext4'
[20] SysPartType='TYPE3'
[21] ProgressXHiByte=0x01
[22] ProgressXLoByte=0x68
[23] ProgressYHiByte=0x02
[24] ProgressYLoByte=0xE4
[25] ProgressCnts=0x00
[26] ContentType=0x00
[27] CPU='mx50'
[28] UIStyle='Customer UI'
[29] RAMType='K4X2G323PC'
[30] UIConfig='Normal'
[31] DisplayResolution='1024x758'
[32] FrontLight='TABLE0'
[33] CPUFreq='1G'
[34] HallSensor='TLE4913'
[35] DisplayBusWidth=[+]
[36] FrontLight_Flags=[+]
[37] PCB_Flags=[+]
[38] FrontLight_LEDrv=[+]

(The warning is between every line, but I erased it to increase readability.)

Only PCB, TouchCtrl, TouchType, Rsensor, Battery, IFlash have different values. Values [35-38] are not given on the Kobo Glo.

Markismus · 2013-12-29T21:33:40Z

For the Touch with the swapped X- Y- coordinate (Product no:N905-KBO-B, S/N: N905K342***** -B):

HW CONFIG v1.3 , size=35 bytes : 
NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config file !!
[0] PCB='E60610D' 
[1] KeyPad='1Key' 
[2] AudioCodec='No' 
[3] AudioAmp='No' 
[4] Wifi='WC121A2' 
[5] BT='No' 
[6] Mobile='No' 
[7] TouchCtrl='neonode_v2' 
[8] TouchType='IR-Type' 
[9] DisplayCtrl='MX508+TPS65185' 
[10] DisplayPanel='6" Bottom EPD' 
[11] RSensor='No' 
[12] MicroP='MSP430' 
[13] Customer='9' 
[14] Battery='1000mA' 
[15] Led='TYPE1' 
[16] RamSize='256MB' 
[17] IFlash='Micro SD' 
[18] ExternalMem='Micro SD' 
[19] RootFsType='Ext4' 
[20] SysPartType='TYPE3' 
[21] ProgressXHiByte=0x01 
[22] ProgressXLoByte=0x68 
[23] ProgressYHiByte=0x02 
[24] ProgressYLoByte=0xE4 
[25] ProgressCnts=0x00 
[26] ContentType=0x00 
[27] CPU='mx50' 
[28] UIStyle='Customer UI' 
[29] RAMType='K4X2G323PC' 
[30] UIConfig='Normal2' 
[31] DisplayResolution='800x600' 
[32] FrontLight='No' 
[33] CPUFreq='NC' 
[34] HallSensor='No' 
[35] DisplayBusWidth=[+] 
[36] FrontLight_Flags=[+] 
[37] PCB_Flags=[+] 
[38] FrontLight_LEDrv=[+]

The PCB value for this Touch is 7 digits! Maybe we can differentiate on PCB only. Hopefully, someone with a newer Touch will post.
There are supposed to be 3 versions of Kobo Touch: A, B, and C. The newest seems to be able to run the same firmware as the Kobo Glo. The older ones are types Mark 3, the newer one Mark 4.

Markismus · 2014-03-18T13:22:35Z

This was reported here

Here's the ntx_hwconfig as requested.

I should note that while my device's fcc id shows it as an n905c, when I did a factory reset and it auto-downloaded the 3.2.0 firmware, it downloaded the one that this thread associates with the n905b.

I don't know why it's getting the warnings.

# ntx_hwconfig -s -p /dev/mmcblk0
HW CONFIG v1.0 , size=32 bytes : 
[0] PCB='E60610' 
[1] KeyPad='1Key' 
[2] AudioCodec='ALC5623' 
[3] AudioAmp='No' 
[4] Wifi='WC121' 
[5] BT='No' 
[6] Mobile='No' 
[7] TouchCtrl='neonode' 
[8] TouchType='IR-Type' 
[9] DisplayCtrl='MX508' 
[10] DisplayPanel='6" Bottom EPD' 
[11] RSensor='No' 
[12] MicroP='MSP430' 
[13] Customer='9' 
[14] Battery='1000mA' 
[15] Led='TYPE1' 
[16] RamSize='256MB' 
[17] IFlash='Micro SD' 
[18] ExternalMem='SD' 
[19] RootFsType='Ext4' 
[20] SysPartType='TYPE3' 
[21] ProgressXHiByte=0x01 
[22] ProgressXLoByte=0x68 
[23] ProgressYHiByte=0x02 
[24] ProgressYLoByte=0xE4 
[25] ProgressCnts=0x00 
[26] ContentType=0x00 
[27] CPU='mx50' 
[28] UIStyle='Customer UI' 
[29] RAMType='MDDR' 
[30] UIConfig='Normal2' 
[31] DisplayResolution='800x600' 
[32] FrontLight=[+] 
[33] CPUFreq=[+] 
[34] HallSensor=[+] 
[35] DisplayBusWidth=[+] 
[36] FrontLight_Flags=[+] 
[37] PCB_Flags=[+] 
[38] FrontLight_LEDrv=[+] 
[39] VCOM_10mV_HiByte=[+] 
[40] VCOM_10mV_LoByte=[+] 
[41] PCB_REV=[+]

Markismus · 2014-03-18T13:35:34Z

Summarizing [0] PCB=

Aura    E606F0B
Glo     E606B0
Touch B E60610D
Touch C E60610

Comparing this to kobo_config.sh:

#!/bin/sh
PCB=`ntx_hwconfig -s -p /dev/mmcblk0 PCB`
case $PCB in
        E60610D*) echo trilogy;;
        E606B*) echo kraken;;
        E5061*) echo pixie;;
        E606C*) echo dragon;;
        E606F*) echo phoenix;;
        *) echo trilogy;;
esac

It is obvious wherein the mistake lies. They just heap them together at the end! We can run the command ourselves and differentiate between Touch B and C.

giorgio130 · 2014-03-29T09:51:29Z

I don't know if I'm missing anything, but:

For the Touch with the swapped X- Y- coordinate (Product no:N905-KBO-B, S/N: N905K342***** -B):

HW CONFIG v1.3 , size=35 bytes : 
NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config file !!
[0] PCB='E60610D'

and in issue #535:

# ntx_hwconfig -s -p /dev/mmcblk0
HW CONFIG v1.0 , size=32 bytes : 
NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config file !!
[0] PCB='E60610'

so both models appear to have X and Y switched??? Even if we can distinguish between models, it could not be useful at all...

Markismus · 2014-03-29T11:52:49Z

So should we query model and firmware version?

giorgio130 · 2014-03-29T11:57:47Z

I don't think the firmware version changes the coordinates.
This variable could come into play:

[30] UIConfig='Normal2'

in the case of Aura, AuraHD and Glo, it is set to "Normal".

Markismus · 2014-03-29T15:11:03Z

Interesting.

But how does it discriminate between Touches?

giorgio130 · 2014-03-29T15:17:13Z

My guess is that those with inverted coordinates would have 'Normal2' as a
value, while those who don't would have 'Normal'. We had reports of
inverted coordinates by both touch-b and touch-c owners it seems, so that
shouldn't be the key of the issue.
Il 29/mar/2014 16:11 "Markismus" notifications@github.com ha scritto:

Interesting.

But how does it discriminate between Touches?

Reply to this email directly or view it on GitHubhttps://github.com//issues/421#issuecomment-38998250
.

Markismus · 2014-03-29T16:27:17Z

It would indeed be nice to have a different check for coordinate inversion and model dependency.

What about hwhw's suggestion for a "touch upper right corner" if there is no configuration file yet?

giorgio130 · 2014-03-30T11:25:24Z

A touch calibration step would be perfect, but I think it should be shown only to kobo touch owners.
I don't think I'll have the time to implement it myself, I could give a try to implement the setting in configuration to swap coordinates though.

Markismus · 2014-05-23T21:36:03Z

I'll close this since all the data has been gathered.

bbaixiner · 2014-06-21T04:30:19Z

I have original N905 and N905B
The N905 has a integration flash onboard , not a micro sd .
Other main ICs as below：
CPU MCIMX508CVM8B
Power Supply IC of E-link TPS65185
FLASH KLM2G1DEHE
RAM K4X2G323PC
And a MC13892AJVL is a Power Management and User Interface componentfor Freescale’s i.MX51, i.MX37, i.MX35, i.MX31 and i.MX27
and a TI MSP430 MCU (MircoP ?)

The N905B has a micro sd on board as rom.
Other main ICs as below:
CPU MCIMX507CVM8B ( some board are MCIMX508CVM8B )
A sensor Lm75a
A small battery charger ic marks cdu ti 16W
RAM K4X2G323PC
and a TI MSP430 MCU (MircoP ?) one MSP430G2333

Markismus · 2014-06-21T08:44:56Z

@bbaixiner Nice that you have both Touches! Would you be willing to run the command ntx_hwconfig -s -p /dev/mmcblk0 at the shell prompt?
(If you're willing, but don't know how to run a terminal on your Touch, I'll write you through it.)

Next to the output of the command for each model I am also quite interested what tweaks to input.lua are needed to make it run smoothly.

bbaixiner · 2014-06-23T15:36:52Z

@Markismus Very unexpectedly that the command ntx_hwconfig -s -p /dev/mmcblk0 is no use at N905.
[root@(none) onboard]# ntx_hwconfig -s -p /dev/mmcblk0
-sh: ntx_hwconfig: not found

And I copy the a ntx_hwconfig in sd card and run it ，but no use all the same.
[root@(none) /dev]# /mnt/onboard/ntx_hwconfig -s -p /dev/mmcblk0
ntx_hwconfig_ap.c(408):Hw config header check error (-2)!
, size=0 bytes :
command hwcfg fail !!

Markismus · 2014-06-23T20:09:42Z

This is new! What are your installed firmwares for the Touches?
What does the command /bin/kobo_config.sh generate as a result?
What does the command /bin/ntx_hwconfig generate as a result?

bbaixiner · 2014-06-24T02:29:29Z

@Markismus I upgraded the N905 to 3.3.1 . and ntx_hwconfig -s -p /dev/mmcblk0 reported error , yet.
[root@(none) ~]# ntx_hwconfig -s -p /dev/mmcblk0
ntx_hwconfig_ap.c(408):Hw config header check error (-2)!
, size=0 bytes :
command hwcfg fail !!

/bin/kobo_config.sh

[root@(none) ~]# /bin/kobo_config.sh
NtxHwCfg_GetCfgFldStrVal:[WARNING]Config header error !!
NtxHwCfg_GetCfgFldStrVal : error (-2)
trilogy

And the koreader can run in N905,but the touch action tap need a very quick tap speed to work normally.

bbaixiner · 2014-06-29T11:55:25Z

@Markismus The N905B' s hwconfig below , I do not know what diffrence with N905C

(none) login: root
[root@(none) ~]# ntx_hwconfig -s -p /dev/mmcblk0
HW CONFIG v0.7 , size=29 bytes :
NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config
 file !!
[0] PCB='E60610'
[1] KeyPad='1Key'
[2] AudioCodec='ALC5623'
[3] AudioAmp='No'
[4] Wifi='WC121'
[5] BT='No'
[6] Mobile='No'
[7] TouchCtrl='neonode'
[8] TouchType='IR-Type'
[9] DisplayCtrl='MX508'
[10] DisplayPanel='6" Bottom EPD'
[11] RSensor='No'
[12] MicroP='MSP430'
[13] Customer='9'
[14] Battery='1000mA'
[15] Led='TYPE1'
[16] RamSize='256MB'
[17] IFlash='Micro SD'
[18] ExternalMem='SD'
[19] RootFsType='Ext4'
[20] SysPartType='TYPE3'
[21] ProgressXHiByte=0x01
[22] ProgressXLoByte=0x68
[23] ProgressYHiByte=0x02
[24] ProgressYLoByte=0xE4
[25] ProgressCnts=0x00
[26] ContentType=0x00
[27] CPU='mx50'
[28] UIStyle='Customer UI'
[29] RAMType=[+]
[30] UIConfig=[+]
[31] DisplayResolution=[+]
[32] FrontLight=[+]
[33] CPUFreq=[+]
[34] HallSensor=[+]
[35] DisplayBusWidth=[+]
[36] FrontLight_Flags=[+]
[37] PCB_Flags=[+]
[38] FrontLight_LEDrv=[+]
[39] VCOM_10mV_HiByte=[+]
[40] VCOM_10mV_LoByte=[+]
[41] PCB_REV=[+]

Markismus · 2014-06-29T18:51:29Z

Nice!

Too bad you can't get your Touch-C to spit out the data. That would have cleared up the difference between B and C. For now it confirms that the previous data dump is indeed a Touch-B model.

pazos · 2014-07-06T21:13:04Z

@giorgio130 I'm on firmware 3.4.1 on a kobo mini and have UIConfig='Normal2' and no swapped coordinates.

bbaixiner · 2014-07-09T14:00:47Z

@Markismus Ok, I have got a N905C, It has one more Zforce NN1001A chip.and hwconfig below:

(none) login: root
[root@(none) ~]# ntx_hwconfig -s -p /dev/mmcblk0
HW CONFIG v1.3 , size=35 bytes :
NtxHwCfg_GetCfgFldStrVal:[WARNING]Config version too old !! Please update config
file !!
[0] PCB='E60610D'
[1] KeyPad='1Key'
[2] AudioCodec='No'
[3] AudioAmp='No'
[4] Wifi='WC121A2'
[5] BT='No'
[6] Mobile='No'
[7] TouchCtrl='neonode_v2'
[8] TouchType='IR-Type'
[9] DisplayCtrl='MX508+TPS65185'
[10] DisplayPanel='6" Bottom EPD'
[11] RSensor='No'
[12] MicroP='MSP430'
[13] Customer='9'
[14] Battery='1000mA'
[15] Led='TYPE1'
[16] RamSize='256MB'
[17] IFlash='Micro SD'
[18] ExternalMem='Micro SD'
[19] RootFsType='Ext4'
[20] SysPartType='TYPE3'
[21] ProgressXHiByte=0x01
[22] ProgressXLoByte=0x68
[23] ProgressYHiByte=0x02
[24] ProgressYLoByte=0xE4
[25] ProgressCnts=0x00
[26] ContentType=0x00
[27] CPU='mx50'
[28] UIStyle='Customer UI'
[29] RAMType='K4X2G323PC'
[30] UIConfig='Normal2'
[31] DisplayResolution='800x600'
[32] FrontLight='No'
[33] CPUFreq='NC'
[34] HallSensor='No'
[35] DisplayBusWidth=[+]
[36] FrontLight_Flags=[+]
[37] PCB_Flags=[+]
[38] FrontLight_LEDrv=[+]
[39] VCOM_10mV_HiByte=[+]
[40] VCOM_10mV_LoByte=[+]
[41] PCB_REV=[+]

bbaixiner · 2014-07-09T14:07:14Z

@Markismus
some txt documents can not be opened and crash in KOBO Touch,and the large txt files can not be opened too....and zoom the jpeg cause crash too.

Markismus · 2014-07-09T20:24:56Z

Thanks for the info!

Could you make a separate issue for the crashes? Please add

a description of the crash,
the file that crashes koreader,
the build version of koreader,
your device name and
the firmware running on your device.

Without this info we can't do much more than writing that we're sorry for you and that it does work for us...

bbaixiner · 2014-07-12T09:35:41Z

@Markismus

Markismus · 2014-07-12T13:05:08Z

Why? What's wrong with Github communication?

Never pull the GLIBC_2.22 version of fmemopen on Linux. None of our ARM targets run anything that new. Fix koreader#421 Note to mainteners: there's an updated patch for the upcoming leptonica version, because the code got easier to deal with ;).

Since that block of comments is concerned with that kind of stuff ;).

... Turns out the old default fmemopen symbol name used a different version than the one used by the compat symbol... Yay. Meaning we can only apply the patch when building against glibc >= 2.22, so, do that. Fix koreader#421

Really fix koreader#421

ghost assigned giorgio130 Jan 7, 2014

This was referenced Mar 17, 2014

Touch response appears mirrored on Kobo Touch #535

Closed

Crash on launch for Kobo Touch #534

Closed

Markismus mentioned this issue Apr 1, 2014

Crash if open .djvu with cyrillic characters in path or name of file #542

Closed

Markismus mentioned this issue May 11, 2014

Screen always freezes after opening 2-3 pages of pdf or epub file via koreader #576

Closed

Markismus closed this as completed May 23, 2014

Markismus mentioned this issue Jun 21, 2014

Kobo Touch Mark3 has trouble turning a page with tapping. #630

Closed

pazos mentioned this issue Sep 5, 2014

(Home) button behaviour on Kobo Touch #869

Closed

houqp pushed a commit to houqp/koreader that referenced this issue Apr 24, 2017

Add a ref. to the fmemopen thing from koreader#421

781a739

Since that block of comments is concerned with that kind of stuff ;).

houqp added a commit to houqp/koreader that referenced this issue Apr 24, 2017

Merge pull request koreader#423 from NiLuJe/master

8aef720

Really fix koreader#421

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

How to differentiate between Kobo Touches: kobo_trilogy #421

How to differentiate between Kobo Touches: kobo_trilogy #421

Markismus commented Dec 28, 2013

Markismus commented Dec 28, 2013

Markismus commented Dec 28, 2013

Markismus commented Dec 29, 2013

Markismus commented Mar 18, 2014

Markismus commented Mar 18, 2014

giorgio130 commented Mar 29, 2014

Markismus commented Mar 29, 2014

giorgio130 commented Mar 29, 2014

Markismus commented Mar 29, 2014

giorgio130 commented Mar 29, 2014

Markismus commented Mar 29, 2014

giorgio130 commented Mar 30, 2014

Markismus commented May 23, 2014

bbaixiner commented Jun 21, 2014

Markismus commented Jun 21, 2014

bbaixiner commented Jun 23, 2014

Markismus commented Jun 23, 2014

bbaixiner commented Jun 24, 2014

bbaixiner commented Jun 29, 2014

Markismus commented Jun 29, 2014

pazos commented Jul 6, 2014

bbaixiner commented Jul 9, 2014

bbaixiner commented Jul 9, 2014

Markismus commented Jul 9, 2014

bbaixiner commented Jul 12, 2014

Markismus commented Jul 12, 2014

How to differentiate between Kobo Touches: kobo_trilogy #421

How to differentiate between Kobo Touches: kobo_trilogy #421

Comments

Markismus commented Dec 28, 2013

Markismus commented Dec 28, 2013

Markismus commented Dec 28, 2013

Markismus commented Dec 29, 2013

Markismus commented Mar 18, 2014

Markismus commented Mar 18, 2014

giorgio130 commented Mar 29, 2014

Markismus commented Mar 29, 2014

giorgio130 commented Mar 29, 2014

Markismus commented Mar 29, 2014

giorgio130 commented Mar 29, 2014

Markismus commented Mar 29, 2014

giorgio130 commented Mar 30, 2014

Markismus commented May 23, 2014

bbaixiner commented Jun 21, 2014

Markismus commented Jun 21, 2014

bbaixiner commented Jun 23, 2014

Markismus commented Jun 23, 2014

bbaixiner commented Jun 24, 2014

bbaixiner commented Jun 29, 2014

Markismus commented Jun 29, 2014

pazos commented Jul 6, 2014

bbaixiner commented Jul 9, 2014

bbaixiner commented Jul 9, 2014

Markismus commented Jul 9, 2014

bbaixiner commented Jul 12, 2014

Markismus commented Jul 12, 2014