Welcome, Guest

Author Topic: A10 on A20 Lime board  (Read 1045 times)

woj

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
A10 on A20 Lime board
« on: March 15, 2019, 11:32:33 AM »
Hi!

In my last part of Olimex board I ordered some A10 Lime boards. One of them is hybrid processor A10 on A20 lime board. I noticed it after some time, because at first this board start working with Android. The behavior was a little bit wayward. Sometimes it did not want to boot, sometimes boot faster than other. Finally it stop working at all. Then I check board preciselly and noticed, that the processor is placed on wrong board.
Is there any chance to put this board back to work?

Greetings!
Woj

LubOlimex

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1952
  • Karma: +50/-3
Re: A10 on A20 Lime board
« Reply #1 on: March 15, 2019, 02:58:39 PM »
> In my last part of Olimex board I ordered some A10 Lime boards. One of them is hybrid processor A10 on A20 lime board.

So all boards have A10 chip?

Consider that A10 and A20 chips are pin-to-pin compatible, drop-in replaceable. The A10-OLinuXino-LIME and A20-OLinuXino-LIME boards use the same board PCB just different processors are placed during manufacturing. Hardware-wise the PCB is the same.
Technical support and documentation manager at Olimex

woj

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: A10 on A20 Lime board
« Reply #2 on: March 18, 2019, 12:00:46 PM »
Thanks for answer.

> So all boards have A10 chip?

No. As I wrote only one of them is a hybrid.

I know that A10 and A20 are pin-to-pin and drop-in replaceable. Is there no difference on PCB like clock frequency?

I am asking, because at the begining this hybrid board work. It was booted faster than normal A10 Lime. After some time during starting it halted showing Android booting screen. I waited aruond 5 minutes, but the system did not start. So I turn off power and turn in on again. The Android did not boot at all, even if I use SD card with new image.
After one month it start working, but after some time situation repeated. From that time board is dead.
Could you give me any suggestion what to do with it?

Greetings,
Woj

LubOlimex

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1952
  • Karma: +50/-3
Re: A10 on A20 Lime board
« Reply #3 on: March 19, 2019, 08:29:03 AM »
Some software configurations might be different for the A10 and A20 chip. So if the board has A20 chip, use the Android for A20-OLinuXino-LIME, instead of the Android for the A10-OLinuXino-LIME. Images and links can be found here: https://www.olimex.com/wiki/A20-OLinuXino-LIME

The A20 chip is faster and more expensive, should be able to handle Android better.
Technical support and documentation manager at Olimex

woj

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: A10 on A20 Lime board
« Reply #4 on: March 19, 2019, 09:58:06 AM »
Repeating: I have A10 processor on A20 Lime board.
So for A10 chip I always used Android for A10, because I suspected different software configuration as you mentioned. The board is not working as I described already. How change configuration for A10 processor to work on A20 Lime board?

LubOlimex

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1952
  • Karma: +50/-3
Re: A10 on A20 Lime board
« Reply #5 on: March 19, 2019, 10:23:12 AM »
OK. Maybe I didn't explain it good enough.

This is not a mistake in assembly. In short: the white print on the PCB of product "A10-OLinuXino-LIME" is supposed to say "A20-OLinuXino-Lime".

This is because the PCB is the same for products "A10-OLinuXino-LIME" and "A20-OLinuXino-LIME". If you got A20-OLinuXino-LIME PCB with A10 chip, then this is product "A10-OLinuXino-LIME". I got one product "A10-OLinuXino-LIME" board from the shop and took a picture so you can compare. Product "A10-OLinuXino-LIME" looks like in this two pictures: https://imgur.com/a/03KFpSy

As you see the PCB says A20-OLinuXino-Lime...
Technical support and documentation manager at Olimex

woj

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: A10 on A20 Lime board
« Reply #6 on: March 19, 2019, 10:32:43 AM »
OK. I have it. It does not solve my problem, but at least I know that there is no hardware mistake.

Greetings,
Woj

LubOlimex

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1952
  • Karma: +50/-3
Re: A10 on A20 Lime board
« Reply #7 on: March 19, 2019, 11:31:29 AM »
Alright, so what are the hardware revisions of the rest of the boards and this board? Are all A10 boards the same hardware revision? The hardware revision should be printed below the name of the board.

Is there something strange in the logs of the board that stops working or when it doesn't want to boot? Like error message or something that can be used to debug the issue? How are the LEDs behaving in case of failed boot or when it stops working?
Technical support and documentation manager at Olimex

woj

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: A10 on A20 Lime board
« Reply #8 on: March 19, 2019, 02:42:39 PM »
This board is Rev.H. I do not know revision of the rest of the boards, because I have sell them already. I suspect, that they shoud have the same revision, because I bought them in one parcel in July 2018.

The power LED is shining. Today during test also start shining green Status LED (LED1).
I checked the boot messages using UART0. It stops always at the moment:

[    2.950375] Waiting for root device /dev/mmcblk0p2...
[   11.922547] [AXP]init charger->rest_vol = 100

Beggining of the booting sequence:

Code: [Select]
U-Boot SPL 2013.10-rc2-08405-g1b1908c-dirty (Nov 19 2013 - 16:46:29)
Board: A10-OLinuXino-Lime
DRAM: 512 MiB
CPU: 1008000000Hz, AXI/AHB/APB: 3/2/2
spl: not an uImage at 1600


U-Boot 2013.10-rc2-08405-g1b1908c-dirty (Nov 19 2013 - 16:46:29) Allwinner Technology

CPU:   Allwinner A10 (SUN4I)
Board: A10-OLinuXino-Lime
I2C:   ready
DRAM:  512 MiB
MMC:   SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   emac
Hit any key to stop autoboot:  3 \0x08\0x08\0x08 2 \0x08\0x08\0x08 1 \0x08\0x08\0x08 0
reading uEnv.txt
225 bytes read in 3 ms (73.2 KiB/s)
Loaded environment from uEnv.txt
reading boot.scr
** Unable to read file boot.scr **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
reading script.bin
49868 bytes read in 6 ms (7.9 MiB/s)
reading uImage
4006424 bytes read in 192 ms (19.9 MiB/s)
## Booting kernel from Legacy Image at 48000000 ...
   Image Name:   Linux-3.0.8+
   Created:      2014-02-04  21:26:44 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4006360 Bytes = 3.8 MiB
   Load Address: 40008000
   Entry Point:  40008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

DRAM: 512[    0.000000] Linux version 3.0.8+ (root@bundie) (gcc version 4.5.1 (Sourcery G++ Lite 2010.09-50) ) #9 PREEMPT Tue Feb 4 23:26:30 EET 2014
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: sun4i
[    0.000000] Total Detected Memory: 512MB with 1 banks
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Memory Reserved(in bytes):
[    0.000000] \0x09LCD: 0x5a000000, 0x02000000
[    0.000000] \0x09SYS: 0x43000000, 0x00010000
[    0.000000] \0x09G2D: 0x58000000, 0x01000000
[    0.000000] \0x09VE : 0x44000000, 0x05000000
[    0.000000] \0x09VE : 0x49000000, 0x01000000
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 114688
[    0.000000] free_area_init_node: node 0, pgdat c07b5918, node_mem_map c097a000
[    0.000000]   Normal zone: 896 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 113792 pages, LIFO batch:31
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 113792
[    0.000000] Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p2 rootwait loglevel=8 panic=10 root=/dev/mmcblk0p2 loglevel=8 rootwait console=ttyS0,115200 rw init=/init mac_addr=00:AE:99:A3:E4:AF
[    0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 448MB = 448MB total
[    0.000000] Memory: 313884k/313884k available, 144868k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
[    0.000000]     vmalloc : 0xdc800000 - 0xf0000000   ( 312 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xdc000000   ( 448 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .init : 0xc0008000 - 0xc002f000   ( 156 kB)
[    0.000000]       .text : 0xc002f000 - 0xc076e664   (7422 kB)
[    0.000000]       .data : 0xc0770000 - 0xc07c0130   ( 321 kB)
[    0.000000]        .bss : 0xc07c0154 - 0xc0979cb8   (1767 kB)
[    0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:96 nr_irqs:96 96
[    0.000000] timer0: Periodic Mode
[    0.000000] sw_timer_init,line:397
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] aw_clksrc_init, line:338
[    0.000000] Console: colour dummy device 80x30
« Last Edit: March 19, 2019, 02:44:38 PM by woj »

woj

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: A10 on A20 Lime board
« Reply #9 on: March 19, 2019, 02:43:50 PM »
Rest of booting sequence:

Code: [Select]
[    0.000103] Calibrating delay loop... 1001.88 BogoMIPS (lpj=5009408)
[    0.040021] pid_max: default: 32768 minimum: 301
[    0.040151] Mount-cache hash table entries: 512
[    0.040458] CPU: Testing write buffer coherency: ok
[    0.040663] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
[    0.041143] devtmpfs: initialized
[    0.042481] print_constraints: dummy:
[    0.042625] NET: Registered protocol family 16
[    0.043214] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.043701] try to parse apb frequency from script faild!
[    0.043780] SOFTWINNER DMA Driver, (c) 2003-2004,2006 Simtec Electronics
[    0.043847] Initialize DMAC OK
[    0.048738] bio: create slab <bio-0> at 0
[    0.049342] SCSI subsystem initialized
[    0.049555] usbcore: registered new interface driver usbfs
[    0.049633] usbcore: registered new interface driver hub
[    0.049785] usbcore: registered new device driver usb
[    0.050000] Advanced Linux Sound Architecture Driver Version 1.0.24.
[    0.050000] Bluetooth: Core ver 2.16
[    0.050000] NET: Registered protocol family 31
[    0.050000] Bluetooth: HCI device and connection manager initialized
[    0.050000] Bluetooth: HCI socket layer initialized
[    0.050000] Bluetooth: L2CAP socket layer initialized
[    0.050000] Bluetooth: SCO socket layer initialized
[    0.050000] cfg80211: Calling CRDA to update world regulatory domain
[    0.050000] Init eGon pin module V2.0
[    0.050000] Switching to clocksource aw 64bits couter
[    0.050000] FS-Cache: Loaded
[    0.050000] CacheFiles: Loaded
[    0.050000] Switched to NOHz mode on CPU #0
[    0.050000] [usb_manager]: CONFIG_USB_SW_SUN4I_USB0_OTG
[    0.050000] [sw_hcd0]: usb host driver initialize........
[    0.050000] [sw_hcd0]: open_usb_clock
[    0.066712] [sw_hcd0]: host_init_state = 1
[    0.066721] [sw_hcd0]: platform is usb host
[    0.066792] [sw_hcd0]: sw_hcd_init_controller: sw_hcd_host0: USB Host mode controller at f1c13000 using PIO, IRQ 38
[    0.066820] sw_hcd_host0 sw_hcd_host0: sw_hcd host driver
[    0.066836] sw_hcd_host0 sw_hcd_host0: new USB bus registered, assigned bus number 1
[    0.067406] hub 1-0:1.0: USB hub found
[    0.067432] hub 1-0:1.0: 1 port detected
[    0.067459] wrn: hcd is not enable, need not start hcd
[    0.067719] [sw_hcd0]: sw_usb_host0_disable start
[    0.067732] -------sw_hcd0_soft_disconnect---------
[    0.067743] [sw_hcd_host0]: Set USB Power OFF
[    0.067753] wrn: hcd is not enable, need not stop hcd
[    0.067783] [sw_hcd0]: close_usb_clock
[    0.067825] [sw_hcd0]: sw_usb_host0_disable end
[    0.067867] [sw_udc]: udc_init: version 20080411
[    0.068258] NET: Registered protocol family 2
[    0.068379] IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.068657] TCP established hash table entries: 16384 (order: 5, 131072 bytes)
[    0.068934] TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
[    0.069114] TCP: Hash tables configured (established 16384 bind 16384)
[    0.069125] TCP reno registered
[    0.069137] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.069158] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.069328] NET: Registered protocol family 1
[    0.069655] RPC: Registered named UNIX socket transport module.
[    0.069673] RPC: Registered udp transport module.
[    0.069681] RPC: Registered tcp transport module.
[    0.069689] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.069915] PMU: registered new PMU device of type 0
[    0.069971] [pm]aw_pm_init!
[    0.078187] ashmem: initialized
[    0.084099] VFS: Disk quotas dquot_6.5.2
[    0.084288] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.087573] NTFS driver 2.1.30 [Flags: R/W].
[    0.088041] fuse init (API version 7.16)
[    0.088703] msgmni has been set to 613
[    0.089164] cryptomgr_test used greatest stack depth: 6712 bytes left
[    0.089594] cryptomgr_test used greatest stack depth: 6480 bytes left
[    0.091786] cryptomgr_test used greatest stack depth: 6388 bytes left
[    0.092801] cryptomgr_test used greatest stack depth: 6312 bytes left
[    0.093297] alg: No test for stdrng (krng)
[    0.093537] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[    0.093553] io scheduler noop registered
[    0.093564] io scheduler deadline registered
[    0.093647] io scheduler cfq registered (default)
[    0.094329] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[    0.095589] serial8250.0: ttyS0 at MMIO 0x1c28000 (irq = 1) is a U6_16550A
[    0.759076] console [ttyS0] enabled
[    0.763325] sunxi-uart.0: ttyS0 at MMIO 0x1c28000 (irq = 1) is a U6_16550A
[    0.770623] sunxi-uart.4: ttyS1 at MMIO 0x1c29000 (irq = 17) is a U6_16550A
[    0.778146] G2D: drv_g2d_init
[    0.781183] G2D: g2dmem: g2d_start=58000000, g2d_size=1000000
[    0.786926] G2D: head:d8000000,tail:d9000000
[    0.791258] G2D: Module initialized.major:251
[    0.796216] brd: module loaded
[    0.801426] loop: module loaded
[    0.804913] PPP generic driver version 2.4.2
[    0.809362] PPP Deflate Compression module registered
[    0.814460] PPP BSD Compression module registered
[    0.820396] PPP MPPE Compression module registered
[    0.825194] NET: Registered protocol family 24
[    0.829674] PPTP driver version 0.8.5
[    0.833705] tun: Universal TUN/TAP device driver, 1.6
[    0.838753] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    0.845284] usbcore: registered new interface driver cdc_ether
[    0.851277] usbcore: registered new interface driver cdc_eem
[    0.856980] usbcore: registered new interface driver cdc_subset
[    0.862964] wemac Ethernet Driver, V1.00 in file:drivers/net/sun4i/sun4i_wemac.c
[    0.870583] can't get information emac_power gpio
[    0.875308] [EMAC] ahb clk enable
[    0.878707] [EMAC] ahb gate clk: 0x24140
[    0.892808] wemac wemac.0: PHY SETUP, reg 0 value: 3000
[    0.899030] wemac wemac.0: resetting device
[    0.903965] release temp resource
[    0.907333] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.913936] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.920348] [sw-ehci1]: probe, pdev->name: sw-ehci, pdev->id: 1, sw_ehci: 0xc086f614
[    0.928091] [sw-ehci1]: open clock
[    0.951477] [sw-ehci1]: Set USB Power ON
[    0.955405] sw-ehci sw-ehci.1: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.962921] sw-ehci sw-ehci.1: new USB bus registered, assigned bus number 2
[    0.970077] sw-ehci sw-ehci.1: irq 39, io mem 0xf1c14000
[    0.990055] sw-ehci sw-ehci.1: USB 0.0 started, EHCI 1.00
[    0.996008] hub 2-0:1.0: USB hub found
[    0.999773] hub 2-0:1.0: 1 port detected
[    1.004097] [sw-ohci1]: probe, pdev->name: sw-ohci, pdev->id: 1, sw_ohci: 0xc086f72c
[    1.011871] [sw-ohci1]: open clock
[    1.035223] sw-ohci sw-ohci.1: SW USB2.0 'Open' Host Controller (OHCI) Driver
[    1.042390] sw-ohci sw-ohci.1: new USB bus registered, assigned bus number 3
[    1.049472] sw-ohci sw-ohci.1: irq 64, io mem 0xf1c14400
[    1.114464] hub 3-0:1.0: USB hub found
[    1.118233] hub 3-0:1.0: 1 port detected
[    1.122538] [sw-ehci2]: probe, pdev->name: sw-ehci, pdev->id: 2, sw_ehci: 0xc086f848
[    1.130310] [sw-ehci2]: open clock
[    1.153659] [sw-ehci2]: Set USB Power ON
[    1.157582] sw-ehci sw-ehci.2: SW USB2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.165093] sw-ehci sw-ehci.2: new USB bus registered, assigned bus number 4
[    1.172229] sw-ehci sw-ehci.2: irq 40, io mem 0xf1c1c000
[    1.190038] sw-ehci sw-ehci.2: USB 0.0 started, EHCI 1.00
[    1.195880] hub 4-0:1.0: USB hub found
[    1.199641] hub 4-0:1.0: 1 port detected
[    1.203935] [sw-ohci2]: probe, pdev->name: sw-ohci, pdev->id: 2, sw_ohci: 0xc086f960
[    1.211703] [sw-ohci2]: open clock
[    1.235136] sw-ohci sw-ohci.2: SW USB2.0 'Open' Host Controller (OHCI) Driver
[    1.242305] sw-ohci sw-ohci.2: new USB bus registered, assigned bus number 5
[    1.249374] sw-ohci sw-ohci.2: irq 65, io mem 0xf1c1c400
[    1.314467] hub 5-0:1.0: USB hub found
[    1.318227] hub 5-0:1.0: 1 port detected
[    1.322441] Initializing USB Mass Storage driver...
[    1.327501] usbcore: registered new interface driver usb-storage
[    1.333533] USB Mass Storage support registered.
[    1.338207] usbcore: registered new interface driver ums-alauda
[    1.344189] usbcore: registered new interface driver ums-cypress
[    1.350258] usbcore: registered new interface driver ums-datafab
[    1.356300] usbcore: registered new interface driver ums_eneub6250
[    1.362538] usbcore: registered new interface driver ums-freecom
[    1.368582] usbcore: registered new interface driver ums-isd200
[    1.374559] usbcore: registered new interface driver ums-jumpshot
[    1.380708] usbcore: registered new interface driver ums-karma
[    1.386578] usbcore: registered new interface driver ums-onetouch
[    1.392745] usbcore: registered new interface driver ums-realtek
[    1.398816] usbcore: registered new interface driver ums-sddr09
[    1.404801] usbcore: registered new interface driver ums-sddr55
[    1.410781] usbcore: registered new interface driver ums-usbat
[    1.416738] usbcore: registered new interface driver usbserial
[    1.422664] usbserial: USB Serial Driver core
[    1.427064] USB Serial support registered for GSM modem (1-port)
[    1.433313] usbcore: registered new interface driver option
[    1.438880] option: v0.7.2:USB Driver for GSM modems
[    1.443903] ------print_msc_config-----
[    1.447736] vendor_id             = 0x18d1
[    1.451846] mass_storage_id       = 0x1
[    1.455678] adb_id                = 0x2
[    1.459509] usb_manufacturer_name = USB Developer
[    1.464225] usb_product_name      = Android
[    1.468404] usb_serial_number     = 20080411
[    1.472684] msc_vendor_name       = USB 2.0
[    1.476863] msc_product_name      = USB Flash Driver
[    1.481838] msc_release           = 100
[    1.485670] luns                  = 2
[    1.489327] ---------------------------
[    1.493373] [sw_udc]: [sw_usb_udc]: binding gadget driver 'android_usb'
[    1.499999] [sw_udc]: alloc request: ep(0xc079cd60, ep0, 64), req(0xd9a07340)
[    1.507171] WRN:L2703(drivers/usb/sun4i_usb/udc/sw_udc.c):ERR: usb device is not active
[    1.515197] [sw_udc]: sw_udc_pullup, is_on = 0
[    1.519652] WRN:L2738(drivers/usb/sun4i_usb/udc/sw_udc.c):ERR: usb device is not active
[    1.528994] android_usb gadget: Mass Storage Function, version: 2009/09/11
[    1.535918] android_usb gadget: Number of LUNs=2
[    1.540569]  lun0: LUN: removable file: (no medium)
[    1.545443]  lun1: LUN: removable file: (no medium)
[    1.550351] lun name: lun
[    1.552975] lun name: lun1
[    1.555874] WRN:L2703(drivers/usb/sun4i_usb/udc/sw_udc.c):ERR: usb device is not active
[    1.563917] android_usb gadget: android_usb ready
[    1.568775] mousedev: PS/2 mouse device common for all mice
[    1.574668] input: sun4i-keyboard as /devices/virtual/input/input0
[    1.581038] ==register_early_suspend =
[    1.585365] sunxi RTC version 0.1
[    1.588904] sunxi-rtc sunxi-rtc: sunxi_rtc_probe tmp_data = 380239881
[    1.595456] sunxi-rtc sunxi-rtc: sunxi_rtc_gettime
[    1.600260] sunxi-rtc sunxi-rtc: read time 2010-1-1 0:0:21
[    1.605966] using rtc device, rtc, for alarms
[    1.610203] sunxi-rtc sunxi-rtc: rtc core: registered rtc as rtc0
[    1.616517] i2c /dev entries driver
[    1.620147] !!! base_Addr = 0xdc912c00
[    1.623992] config i2c gpio with gpio_config api
[    1.628733] twi0, apb clock = 24000000
[    1.633943] axp_mfd 0-0034: AXP (CHIP ID: 0x41) detected
[    1.640388] I2C: i2c-0: AW16XX I2C adapter
[    1.644482] **********start************
[    1.648314] 0x40
[    1.650262] 0xf8
[    1.652186] 0x28
[    1.654108] 0x0
[    1.655945] 0x0
[    1.657780] **********end************
[    1.661506] !!! base_Addr = 0xdc914000
[    1.665386] twi1, apb clock = 24000000
[    1.669443] I2C: i2c-1: AW16XX I2C adapter
[    1.673568] **********start************
[    1.677401] 0x40
[    1.679323] 0xf8
[    1.681264] 0x59
[    1.683187] 0x0
[    1.685023] 0x0
[    1.686859] **********end************
[    1.690576] !!! base_Addr = 0xdc916400
[    1.694444] twi2, apb clock = 24000000
[    1.698458] I2C: i2c-2: AW16XX I2C adapter
[    1.702575] **********start************
[    1.706408] 0x40
[    1.708330] 0xf8
[    1.710271] 0x59
[    1.712194] 0x0
[    1.714030] 0x0
[    1.715866] **********end************
[    1.719668] lirc_dev: IR Remote Control driver registered, major 249
[    1.726126] IR NEC protocol handler initialized
[    1.730670] IR RC5(x) protocol handler initialized
[    1.735457] IR RC6 protocol handler initialized
[    1.739983] IR JVC protocol handler initialized
[    1.744524] IR Sony protocol handler initialized
[    1.749138] IR RC5 (streamzap) protocol handler initialized
[    1.754720] IR LIRC bridge handler initialized
[    1.759159] Linux video capture interface: v2.00
[    1.763813] [ace_drv] start!!!
[    1.767192] [ace_drv] init end!!!
[    1.770537] [pa_drv] start!!!
[    1.773788] [pa_drv] init end!!!
[    1.777137] print_constraints: axp20_ldo1: 1300 mV
[    1.782996] print_constraints: axp20_ldo2: 1800 <--> 3300 mV at 3000 mV
[    1.790642] print_constraints: axp20_ldo3: 700 <--> 3500 mV at 2800 mV
[    1.798408] print_constraints: axp20_ldo4: 1250 <--> 3300 mV at 2800 mV
[    1.806065] print_constraints: axp20_buck2: 700 <--> 2275 mV at 1400 mV
[    1.813717] print_constraints: axp20_buck3: 700 <--> 3500 mV at 1250 mV
[    1.820846] print_constraints: axp20_ldoio0: 1800 <--> 3300 mV at 2800 mV
[    1.828046] input: axp20-supplyer as /devices/platform/sun4i-i2c.0/i2c-0/0-0034/axp20-supplyer.28/input/input1
[    1.844658] pmu_pekoff_time = 6000
[    1.848060] pmu_pekoff_en = 1
[    1.851049] pmu_peklong_time = 1000
[    1.854535] pmu_pekon_time = 1000
[    1.857845] pmu_pwrok_time = 64
[    1.861001] pmu_pwrnoe_time = 2000
[    1.864398] pmu_intotp_en = 1
[    1.867832] [AXP]POWER20_OFF_CTL:1908-->0x42
[    1.872584] POWER20_PEK_SET:1925-->0x9d
[    1.876886] POWER20_PEK_SET:1936-->0x8d
[    1.881203] POWER20_PEK_SET:1945-->0x8d
[    1.885502] POWER20_PEK_SET:1956-->0x8d
[    1.889800] POWER20_PEK_SET:1968-->0x8d
[    1.894118] POWER20_HOTOVER_CTL:1977-->0x25
[    1.902266] [AXP]last_rest_vol = 0, now_rest_vol\0x09= 100
[    1.908195] [AXP]charger->rest_vol = 100
[    1.915103] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com
[    1.924011] device-mapper: multipath: version 1.3.0 loaded
[    1.929501] device-mapper: multipath round-robin: version 1.0.0 loaded
[    1.936079] device-mapper: multipath queue-length: version 0.1.0 loaded
[    1.942708] device-mapper: multipath service-time: version 0.2.0 loaded
[    1.949587] Bluetooth: HCI UART driver ver 2.2
[    1.954059] Bluetooth: HCI H4 protocol initialized
[    1.958847] Bluetooth: HCI BCSP protocol initialized
[    1.963826] Bluetooth: HCILL protocol initialized
[    1.968744] [mmc_pm]: no sdio card used in configuration
[    1.974096] [mmc]: sunximmc_init
[    1.977538] [mmc]: sunxi mmc controller using config : 0x9
[    1.983118] [mmc]: sunxi-mmc.0: pdev->name: sunxi-mmc, pdev->id: 0
[    1.989588] [mmc]: mmc 0 power off !!
[    1.993385] [mmc]: mmc0 Probe: base:0xdc91a000 irq:32 dma:0 pdes:0xd9a64000, ret 0.
[    2.001085] [mmc]: sunxi-mmc.3: pdev->name: sunxi-mmc, pdev->id: 3
[    2.007479] [mmc]: mmc 3 power off !!
[    2.011240] [mmc]: mmc3 Probe: base:0xdc91c000 irq:35 dma:0 pdes:0xd9a68000, ret 0.
[    2.019576] usbcore: registered new interface driver usbhid
[    2.025181] usbhid: USB HID core driver
[    2.029460] logger: created 256K log 'log_main'
[    2.034149] logger: created 256K log 'log_events'
[    2.038944] logger: created 256K log 'log_radio'
[    2.043693] logger: created 256K log 'log_system'
[    2.049044] enter sun4i Audio codec!!!
[    2.053614] sun4i audio support initialized
[    2.058033] sun4i Audio codec successfully loaded..
[    2.063853] soc_new_pcm,line:2112
[    2.067398] asoc: sndhdmi <-> sun4i-hdmiaudio.0 mapping ok
[    2.073284] ALSA device list:
[    2.076256]   #0: sun4i-CODEC  Audio Codec
[    2.080376]   #1: sndhdmi
[    2.083314] Netfilter messages via NETLINK v0.30.
[    2.088092] nf_conntrack version 0.5.0 (4904 buckets, 19616 max)
[    2.094635] ctnetlink v0.93: registering with nfnetlink.
[    2.099951] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
[    2.106936] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
[    2.113064] IPv4 over IPv4 tunneling driver
[    2.117601] GRE over IPv4 demultiplexor driver
[    2.121913] GRE over IPv4 tunneling driver
[    2.126720] ip_tables: (C) 2000-2006 Netfilter Core Team
[    2.132229] TCP cubic registered
[    2.135457] Initializing XFRM netlink socket
[    2.140572] NET: Registered protocol family 10
[    2.145896] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    2.151490] IPv6 over IPv4 tunneling driver
[    2.156510] NET: Registered protocol family 17
[    2.161027] NET: Registered protocol family 15
[    2.165649] Bluetooth: RFCOMM TTY layer initialized
[    2.170626] Bluetooth: RFCOMM socket layer initialized
[    2.175762] Bluetooth: RFCOMM ver 1.11
[    2.179511] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.184839] Bluetooth: BNEP filters: protocol multicast
[    2.190080] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    2.196099] L2TP core driver, V2.0
[    2.199520] PPPoL2TP kernel driver, V2.0
[    2.203465] L2TP IP encapsulation support (L2TPv3)
[    2.208356] L2TP netlink interface
[    2.211806] L2TP ethernet pseudowire support (L2TPv3)
[    2.217254] [mmc_pm]: No sdio card, please check your config !!
[    2.223246] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    2.231302] dram_sysdev_init finished!
[    2.236097] [LCD] lcd_module_init
[    2.883474] regulator_init_complete: axp20_buck3: incomplete constraints, leaving on
[    2.891533] regulator_init_complete: axp20_buck2: incomplete constraints, leaving on
[    2.899536] regulator_init_complete: axp20_ldo4: incomplete constraints, leaving on
[    2.907481] regulator_init_complete: axp20_ldo3: incomplete constraints, leaving on
[    2.915418] regulator_init_complete: axp20_ldo2: incomplete constraints, leaving on
[    2.923349] regulator_init_complete: axp20_ldo1: incomplete constraints, leaving on
[    2.931078] sunxi-rtc sunxi-rtc: sunxi_rtc_gettime
[    2.935870] sunxi-rtc sunxi-rtc: read time 2010-1-1 0:0:22
[    2.941397] sunxi-rtc sunxi-rtc: setting system clock to 2010-01-01 00:00:22 UTC (1262304022)
[    2.950375] Waiting for root device /dev/mmcblk0p2...
[   11.922547] [AXP]init charger->rest_vol = 100

woj

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: A10 on A20 Lime board
« Reply #10 on: March 19, 2019, 03:55:17 PM »
I forgot to mention, that I have checked all power test pads. All power supply: 3.3V, 2.5V, 1.5V and 1.2V are correct.

Greetings!
Woj

LubOlimex

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1952
  • Karma: +50/-3
Re: A10 on A20 Lime board
« Reply #11 on: March 19, 2019, 04:47:33 PM »
Which image exactly you used for this test? Or a at least can you point me to the base image before editing the script files?

From this log it appears that some partition can't be found since after that stoppage point the following should appear:

mmc0: new high speed SDHC card at address 0007                   
mmcblk0: mmc0:0007 SD4GB 3.70 GiB                               
mmcblk0: p1 p2

Not sure why, maybe try preparing another card.

Best regards,
Lub/OLIMEX
« Last Edit: March 19, 2019, 04:53:46 PM by LubOlimex »
Technical support and documentation manager at Olimex

woj

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: A10 on A20 Lime board
« Reply #12 on: March 20, 2019, 10:44:19 AM »
I use three images for tests. First is official Olimex Android release 1 for SD card:
https://www.olimex.com/wiki/images/1/19/A10_lime_android_SD_Olimex_release_1.torrent
Second is the same image edited and adjusted by me.
Third is the official Olimex Debian 3.4.90 release 3:
https://www.olimex.com/wiki/images/4/46/A10_Lime_debian_3.4.90_release_3.torrent

All of them finish boot at the same moment:
    Waiting for root device /dev/mmcblk0p2...

I used four or five SD cards from three manufactors. All of them give the same results.

I have also A10 Lime rev.E board send back to me by my contractor as broken one.
It also stop booting in the same moment.

Do you have any idea?

Greetings,
Woj
« Last Edit: March 20, 2019, 10:48:53 AM by woj »

LubOlimex

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1952
  • Karma: +50/-3
Re: A10 on A20 Lime board
« Reply #13 on: March 20, 2019, 11:24:48 AM »
Wait, the board in questions doesn't boot with Linux Debian either?

Well, this lowers the chances of software or configuration problem, maybe this board has a hardware problem of some kind. It might be hard to determine what exactly broke and why over the forums. I recommend you to send me an e-mail over support@olimex.com so we can give you further instructions, make sure to include a link this forum thread so we can skip initial instructions.
Technical support and documentation manager at Olimex

woj

  • Newbie
  • *
  • Posts: 14
  • Karma: +0/-0
Re: A10 on A20 Lime board
« Reply #14 on: March 21, 2019, 10:15:49 AM »
Thank you!
I wrote email to support@olimex.com and waiting for an answer.

Greetings!
Woj