PocketBook Touch Lux 2 (626)

This device has an eInk device, dmesg shows an EPDC driver is used. An almost identical device exists, the Touch Lux 3. Mother board has some subtle differences, both uses the same firmwares.

= Identification =

On the back of the device, the following is printed: Manufacturer Marketing Name ModelNumber

The PCB has the following silkscreened on it: E026 PB626V1.4 20140625

= Sunxi support =

BSP

 * http://www.pocketbook-int.com/parts-of-software
 * https://github.com/pocketbook/Platform_A13/tree/master/Kernel

Manual build
You can build things for yourself by following our Manual build howto and by choosing from the configurations available below.

Sunxi/Legacy U-Boot
Use the  build target.

Mainline U-Boot
I tried tweaking the A13-OLinuXino_defconfig. Added: CONFIG_MMC_SUNXI_SLOT_EXTRA=2 to get u-boot doing something.

There are obvious issues with MMC detection. MMC2 (internal slot) seems to work perfectly, whereas MMC0 (external slot) does not really work. It seems detected ("mmc list" command) but issuing "mmc dev 0" has no effect: command returns code 1 with no error message.

Even with this, it is still possible to boot a mainline linux kernel, but it has the same issue with external slot.

Sunxi/Legacy Kernel
Use the  file.

Mainline kernel
Please look at the "discussion" tab of this page, I added some notes.

I tried tweaking the "sun5i-a13-olinuxino" device-tree. But there is an issue at this point with at least the external mmc slot (0):

But that did not help since everything seems good in device tree (clock definition, bus width etc.).

= Tips, Tricks, Caveats =

Please look at the "discussion" tab of this page, I added some notes.

Manufacturer SD image boots the old boot0 / boot1 / boot.axf way, then starts an uImage Linux 3 kernel (as of firmware 5.14.1225). We can find source code for the kernel here, but I think it is incomplete, and while I built it successfully, I have not been able to boot it.

FEL mode
Entering FEL mode with default pocketbook software: device powered off, press right button (square symbol), power on while keeping the button pressed. There is not LED or indicator showing if the device is on. However plugging the device to a computer through USB will show there is something. lsusb: Bus 002 Device 008: ID 1f3a:efe8 Onda (unverified) V972 tablet in flashing mode

Serial console output will look like: dram size =256 0xffffffff,0xffffffff super_standby_flag = 0 HELLO! BOOT0 is starting! boot0 version : 1.5.0 The size of Boot1 is 0x00038000. Succeed in loading boot1 from sdmmc flash. Ready to disable icache. Succeed in loading Boot1. Jump to Boot1. [      0.240] boot1 version : 1.5.1 [      0.240] pmu type = 3 [      0.241] bat vol = 4139 [      0.243] core_para->vol_threshold=3600 [      0.248] bat_cou=0x00000000 [      0.249] dcin_exist [      0.252] power_step_level =0x00000002, bat_vol = 0x0000102b [      0.291] axi:ahb:apb=3:2:2 [      0.291] set dcdc2=1400, clock=1008 successed [      0.293] key [      2.560] you can unclench the key to update now [      2.560] key found, jump to fel Device will answer to sunxi-fel: AWUSBFEX soc=00001625(A13) 00000001 ver=0001 44 08 scratchpad=00007e00 00000000 00000000

To get out of FEL mode, press power button for 10s.

Pocketbook uses a strange partition layout on this device: 626.img1      1009664 7763967 6754304   3.2G  b W95 FAT32 626.img2 *      73728  139263   65536    32M  6 FAT16 626.img3            1 1009664 1009664   493M 85 Linux extended 626.img5       139264  172031   32768    16M 83 Linux 626.img6       172032  204799   32768    16M 83 Linux 626.img7       204800  275455   70656  34.5M 83 Linux 626.img8       275456  776191  500736 244.5M 83 Linux 626.img9       776192  976895  200704    98M 83 Linux 626.img10      976896 1009663   32768    16M 83 Linux

boot1 seems to check a MBR at 0x01400000. Feeding it to sunxi-nand gives the following output: check partition table copy 0: mbr: version 0x00000100, magic softw311 OK check partition table copy 1: mbr: version 0x00000100, magic softw311 OK check partition table copy 2: mbr: version 0x00000100, magic softw311 OK mbr: version 0x00000100, magic softw311 8 partitions partition 1: class =         DISK, name =   bootloader, partition start =    32768, partition size =    65536 user_type=0 partition 2: class =         DISK, name =          env, partition start =    98304, partition size =    32768 user_type=0 partition 3: class =         DISK, name =         boot, partition start =   131072, partition size =    32768 user_type=0 partition 4: class =         DISK, name =       rootfs, partition start =   163840, partition size =    70656 user_type=0 partition 5: class =         DISK, name =      ebrmain, partition start =   234496, partition size =   500736 user_type=0 partition 6: class =         DISK, name =       secure, partition start =   735232, partition size =   200704 user_type=0 partition 7: class =         DISK, name =     updatefs, partition start =   935936, partition size =    32768 user_type=0 partition 8: class =         DISK, name =        UDISK, partition start =   968704, partition size =  6754304 user_type=0

Which is consistent with fdisk output considering the 0x0140000 offset.

Altering primary partition #1 and adding primary partition #4 is fine even if the MBR at 0x01400000 is not modified. But removing the other partitions makes boot1 fail the fs check and enter FEL mode.

= Adding a serial port (voids warranty) =



Serial TTL signal pads are clearly labeled on the board. Soldering is required.

Device disassembly
Insert the Plastic_tool between the back cover and the front cover. You can look at this video https://www.youtube.com/watch?v=c7AUData0UA Personally, I am using Dunlop 1.14mm guitar picks, it is not the most convenient but does the job.

Locating the UART
= Pictures =

= Also known as =

= See also =