Jump to content

armbian on A10 tablet


dee0987

Recommended Posts

Today i have tried to boot armbian on my old tablet. After i copied script.bin from tablet nanda partition and applied it on Armbian_5.20_Lime-a10_Debian_jessie_3.4.112_desktop image desktop has started.

The first thing i have checked is CPU temperature 65 - 67 'C - 1008MHz
300Mb of 512 free mem


Not working:
1) touch screen
2) wifi
3) accelerometer

Is it normal 65-57 'C for Allwinner A10 CPU ?
And how to add support for wifi and touch screen ?

 

 

hardware:



cpu		Allwinner A10 
wifi		Realtek RTL8188CUS
touchscreen	raysens rs10f160904 
			ssd2533qt6
ddr3	x4	h5tq1g83tfr-h9c
flash	x2	29f32g08
lition power system	axp209
Link to comment
Share on other sites

Here is some log files from Android system and Armbian:

dmesg-android.zip

dmesg.zip

 

lsmod Android:

8192cu 575431 0 - Live 0xbf0f6000
rtl8150 8910 0 - Live 0xbf0ef000
mcs7830 6557 0 - Live 0xbf0e9000
qf9700 8513 0 - Live 0xbf0e2000
asix 22500 0 - Live 0xbf0d7000
usbnet 23745 3 mcs7830,qf9700,asix, Live 0xbf0cb000
sun4i_csi0 27946 0 - Live 0xbf0c0000
gt2005 23058 0 - Live 0xbf0b5000
gc0308 17836 1 - Live 0xbf0ac000
videobuf_dma_contig 5659 1 sun4i_csi0, Live 0xbf0a7000
videobuf_core 18067 2 sun4i_csi0,videobuf_dma_contig, Live 0xbf09d000
bma250 7026 0 - Live 0xbf097000
mali 130193 18 - Live 0xbf06a000
ump 42190 21 mali, Live 0xbf059000
ssd253x_ts_1F 9742 0 - Live 0xbf031000
Novatek_TouchDriver 39335 0 - Live 0xbf023000
ft5x_ts 47181 2 ssd253x_ts_1F,Novatek_TouchDriver, Live 0xbf000000

lsmod Armbian:

Module                  Size  Used by
bnep                   14384  2 
disp_ump                 842  0 
mali_drm                2603  1 
drm                   215458  2 mali_drm
cpufreq_userspace       3463  0 
mali                  112077  0 
ump                    61801  4 mali,disp_ump
8192cu                631231  0 
a20_tp                  3238  0 
8021q                  18339  0 
garp                    6092  1 8021q
stp                     1992  1 garp
llc                     5332  2 stp,garp
hidp                   17852  0 
rfcomm                 59273  4 
hci_uart               25258  0 
bluetooth             268232  10 bnep,hidp,hci_uart,rfcomm

lsusb Android:

Bus 001 Device 001: ID 1d6b:0001
Bus 002 Device 001: ID 1d6b:0002
Bus 003 Device 001: ID 1d6b:0001
Bus 003 Device 002: ID 1a81:1006
Bus 004 Device 001: ID 1d6b:0002
Bus 005 Device 001: ID 1d6b:0001
Bus 004 Device 002: ID 0bda:8176

lsusb Armbian:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 1a81:1006 Holtek Semiconductor, Inc. 
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Link to comment
Share on other sites

It's a bit harder from here since you probably don't have any data sheet: by experimenting - trial and error, by using own and other experiences (reading stuff around), ...

 

There is no straight answer on this question. Here the real hard work / fun usually begins  :P

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines