Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 18 replies
  • Answers 4 answers
  • Subscribers 101 subscribers
  • Views 2770 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BEAGLEBOARD-X15: Android Automotive

Dean Rumen
Prodigy 80 points
Part Number: BEAGLEBOARD-X15

Hi,

is Android Automotive 10 or master branch supported on BeagleBoard X15 boards?

Android Automotive 9 (Pie) is working (booting and loading). I have followed the instructions from:

https://wiki.linaro.org/AOSP/Boards/BeagleboardX15

Similar instruction are on:

http://software-dl.ti.com/processor-sdk-android/esd/docs/latest/android/How_To_Guides_Enable_Android_Auto.html

On the same Linaro page I found instructions to build Android on master branch:

https://wiki.linaro.org/AOSP/Boards/BeagleboardX15#AOSP_master_on_X15

I have tried to build both, Android and Android Automotive on master branch. The builds were successful but after flashing them on BeagleBoard X15 they both get stuck on boot animation. I can provide logs if needed. So the second question is whether the Android Automotive is working on AOSP master branch? And if not, is it working on any branch above Android 9 (Pie)?

I have found:

https://android.googlesource.com/device/ti/beagle-x15/+/refs/heads/master/auto/beagle_x15.mk

PRODUCT_NAME := beagle_x15_auto

PRODUCT_DEVICE := beagle_x15

PRODUCT_BRAND := Android

PRODUCT_MODEL := AOSP Auto on BeagleBoard X15

PRODUCT_MANUFACTURER := Texas Instruments Inc

My third question is if the above make file is work in progress or it should work? That is, should Android Automotive on AOSP master branch boot and load on BeagleBoard X15? And if it should, can you please provide step by step instructions how to build it and flash it?

Regards,

Dean

PRODUCT_NAME := beagle_x15_auto
PRODUCT_DEVICE := beagle_x15
PRODUCT_BRAND := Android
PRODUCT_MODEL := AOSP Auto on BeagleBoard X15
PRODUCT_MANUFACTURER := Texas Instruments Inc
  • 0
    TI__Expert 6005 points

    Dean,

    X15 Android is a AOSP reference solution .

    The initial support is added on that platform for android auto configuration in Android 9 as a reference only and intended for community development only.

    With that background, let me answer your questions.

    1. is Android Automotive 10 or master branch supported on BeagleBoard X15 boards?

    AOSP master is a continuously evolving project. i checked X15 on auto configuration few months back and it was functional. 

    There is no published Android10 release on X15 , So didnot verify that combination, but i dont see a reason why it will not work, the changes in device project are straightforward.

    2. Stuck at bootanimation on master.

    Have you tried with the snapshot https://snapshots.linaro.org/android/android-lcr-reference-x15-master-auto/

    AOSP master is a continuous moving target so cannot comment the status of a given day (E2E is not the forum to comment on this)

    Also Check logcat on the failure and what service is crashing.

    3. All the instructions are at http://www.ti.com/lit/an/spraco0/spraco0.pdf 

    Simply saying; pretty much standard android building and flashing commands 

    https://source.android.com/setup/build/building ; choose beagle_x15_auto target 

    --

    Additional Information.

    We collaborate closely with google and linaro to support X15 as "reference" solution for Android opensource community. Android Auto is not a productive combination on current SDK of AM57x based on Pie.

  • 0 in reply to Praneeth Bajjuri
    Prodigy 80 points

    Hi Praneeth,

    1. AOSP master is a continuously evolving project. i checked X15 on auto configuration few months back and it was functional. 

    Can you remeber on which branch/tag have You tried that?

    2. Have you tried with the snapshot https://snapshots.linaro.org/android/android-lcr-reference-x15-master-auto/ 

    I have tried now You provided the link. Tried all snapshots (9, 9 auto, 10, master, master auto). Neither of them loaded. All stopped on bootanim.

    3. Simply saying; pretty much standard android building and flashing commands 

    Can you say what .img from build directory should be flashed to X15?

    4. All the instructions are at http://www.ti.com/lit/an/spraco0/spraco0.pdf 

    Inside this are instructions for Android Pie. Are there some instructions for Android 10 or/and master?

    Few more questions.

    Are there any necessary HW that needs to be connected to X15 in order for Android Automotive to finish loading (pass over boot anim)?

    Is there a way to connect http://www.ti.com/tool/TMDXIDK57X-LCD/ to BeagleBoard X15?

    Regards,

    Dean

  • 0 in reply to Dean Rumen
    Prodigy 80 points

    Hi Praneeth,

    just one more thing. In https://snapshots.linaro.org/android/android-lcr-reference-x15-master-auto/ build there is no recovery.img. Is it needed for flashing or not? On older version it was. And when I try flashing this images without recovery image it stucks right on load, without even coming to boot anim.

    Regards,

    Dean

  • 0 in reply to Dean Rumen
    TI__Expert 6005 points

    Atrach dmesg serial log and logcat

  • 0 in reply to Dean Rumen
    TI__Expert 6005 points

    1. Tried around end of last year on HEAD commit of "master" branch . 

    2./3.  Used the .img and flashing instructions from http://www.ti.com/lit/an/spraco0/spraco0.pdf . The linaro wiki page is not current will check with them to update it.

    4. The current TI Android SDK is Pie, We dont have SDK instructions based on 10/master. Linaro wiki is the right place to look for master reference instructions.

    Few more questions: X15 display out is HDMI. the LCD link you pointed out is for a different variant of AM57x platform but not for X15.

    Please send boot logs ,

    Also one more pointer, Android expects a input device to play with the homescreen/ui. Please connect a USB mouse at USB3_1 

  • 0 in reply to Praneeth Bajjuri
    Prodigy 80 points

    Hi,

    regarding serial and adb boot log, I'm building images on clean master and will flash them soon. I will collect and send the logs soon.

    One more question. Is this the correct flashing procedure/order for master:

    sudo fastboot oem format
    sudo fastboot flash xloader MLO
    sudo fastboot flash bootloader u-boot.img
    sudo fastboot flash boot boot_fit.img
    sudo fastboot flash recovery recovery.img
    sudo fastboot flash system system.img
    sudo fastboot flash userdata userdata.img
    sudo fastboot flash vendor vendor.img
    sudo fastboot reboot

    Regards,

    Dean

  • 0 in reply to Dean Rumen
    TI__Expert 6005 points

    Dean,

    That instructions will not work with current master, There are some recent changes merged to various projects 

    (device/ti/ , hardware/ti/, uboot and kernel) to add support to A/B support.

    More info at: https://e2e.ti.com/support/processors/f/791/p/891757/3297060 

    Current master boots to normal/tablet ui. But didnot try auto_target.

    Please buid/flash pie release and try to boot with a usb mouse connected.

    --

    By the way, what is your usecase that you need Auto UI instead of standard tablet UI ?

  • 0 in reply to Praneeth Bajjuri
    Prodigy 80 points

    Hi,

    Regarding Pie, I have built it and flash it and it works. Both versions, auto and android.

    Regarding auto on master, in attachment are serial and adb logs. There we 3 restarts done by me. In cat.log are some commands with which i manage to get boot anim to load and display (not now, i need to delete iSurfaceFlingerConfigs from manifest.xml in order to get boot anim, I didn't do it now).

    The only difference between this and master is an added line i board config specifing system image size to 1000 MB.

    Regards,

    Dean

    master-auto-logs.zip

  • 0 in reply to Dean Rumen
    Prodigy 80 points

    Hi Praneeth,

    Regarding "That instructions will not work with current master, There are some recent changes merged to various projects" and "Current master boots to normal/tablet ui.". Can you tell me which images should I flash and in which order.

    And one more thing. In snapshot link you provided (https://snapshots.linaro.org/android/android-lcr-reference-x15-master-auto/) there is no recovery image but there are some other images. So if you can please provide partition names and which images should be flashed on them?

    Regards,

    Dean 

  • 0 in reply to Dean Rumen
    TI__Expert 6005 points

    Dean,

    Thanks for confirming that Pie baseline works for you .Auto and normal UI. 

    Re-iterating, This is just a reference implementation as we stage some AOSP work. Android Auto on X15 is not a production feature for that platform.

  • 0 in reply to Dean Rumen
    TI__Expert 6005 points

    Regarding Master:

    I reviewed the logs and few things doesnt looks correct. 

    1. Bootloader is 2019.01. ( The correct current bootloader in aosp is 2020.04 tagged This includes A/B and some other features needed for master. you have to rebuiild bootloader images from aosp/external/u-boot and update partition table along with new bootloader. )

    2. Kernel is 4.14 , default AOSP takes prebuilt images from aosp/device/ti/beagle-x15-kernel , This needs to be updated.

    a. build  https://android.googlesource.com/kernel/omap/+/refs/heads/android-beagle-x15-4.19 

    b. go to aosp dir and provide KERNELDIR=<path_to_kernel_in_a>

    c. lunch; build

    ---

    Any reason why you are using Master instead of a Known and tested baseline(Pie?) for your product development.?

    Master is a continuously evolving baseline , i would not recommend to use this for product until a tagged release is available (with updated instructions in wiki.linaro or AOSP )

    Someone will update wiki.linaro updated instructions so watch out for updates there.

    --

  • 0 in reply to Praneeth Bajjuri
    Prodigy 80 points

    Hi Praneeth,

    thank you very much for answers. We did everything You wrote (builded uboot, kernel 4.19, provide KERNELDIR). We have all the images now but when we flash them we get cyclic restarts every 5 seconds. Logs are attached.

    Can you please say what partitions we should create and which images should we flash? If anyhow possible, the exact commands to do this.

    Regards,

    Dean

    cyclic_restart.log 
    U-Boot SPL 2020.04-rc5-00007-gdfd5321 (Apr 09 2020 - 14:12:40 +0200)
DRA752-GP ES2.0
Trying to boot from MMC2_2
no pinctrl state for default mode
Loading Environment from FAT... no pinctrl state for default mode
MMC: no card present
Loading Environment from MMC... OK


U-Boot 2020.04-rc5-00007-gdfd5321 (Apr 09 2020 - 14:12:40 +0200)

CPU  : DRA752-GP ES2.0
Model: TI AM5728 BeagleBoard-X15 rev C
Board: BeagleBoard X15 REV C.00
DRAM:  2 GiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... MMC: no card present
Loading Environment from MMC... OK
Net:   eth0: ethernet@48484000
Hit any key to stop autoboot:  0 
MMC: no card present
MMC: no card present
MMC: no card present
MMC: no card present
Trying to boot Linux from eMMC ...
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
** Unrecognized filesystem type **
CACHE: Misaligned operation at range [fffd37a8, fffd3fa8]
BCB: Normal boot requested...
Trying to boot Android from eMMC ...
switch to partitions #0, OK
mmc1(part 0) is current device

MMC read: dev # 1, block # 169472, count 40960 ... 40960 blocks read: OK
## Loading kernel from FIT Image at 90000000 ...
   Using 'am57xx-beagle-x15-revc.dtb' configuration
   Trying 'kernel@1' kernel subimage
     Description:  TI kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x900000b8
     Data Size:    5554688 Bytes = 5.3 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x82000000
     Entry Point:  0x82000000
   Verifying Hash Integrity ... OK
## Loading ramdisk from FIT Image at 90000000 ...
   Using 'am57xx-beagle-x15-revc.dtb' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  Android Ramdisk Image
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x9054c368
     Data Size:    782542 Bytes = 764.2 KiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x88080000
     Entry Point:  0x88080000
   Verifying Hash Integrity ... OK
   Loading ramdisk from 0x9054c368 to 0x88080000
## Loading fdt from FIT Image at 90000000 ...
   Using 'am57xx-beagle-x15-revc.dtb' configuration
   Trying 'fdt@1' fdt subimage
     Description:  AM57xx-beagle-x15-revc
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x9060b4e4
     Data Size:    131348 Bytes = 128.3 KiB
     Architecture: ARM
     Load Address: 0x83000000
   Verifying Hash Integrity ... OK
   Loading fdt from 0x9060b4e4 to 0x83000000
   Booting using the fdt blob at 0x83000000
   Loading Kernel Image
   Loading Ramdisk to 8ff40000, end 8ffff0ce ... OK
   Loading Device Tree to 8ff1c000, end 8ff3f113 ... OK
Using machid 0xfe6 from environment

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.102-g943e19f-dirty (deru272633@deulmts01) (gcc version 7.5.0 (Linaro GCC 7.5-2019.12)) #1 SMP PREEMPT Thu Apr 9 14:17:04 CEST 2020
[    0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=30c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] OF: fdt: Machine model: TI AM5728 BeagleBoard-X15 rev C
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000095800000, size 56 MiB
[    0.000000] OF: reserved mem: initialized node ipu2-memory@95800000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x0000000099000000, size 64 MiB
[    0.000000] OF: reserved mem: initialized node dsp1-memory@99000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009d000000, size 32 MiB
[    0.000000] OF: reserved mem: initialized node ipu1-memory@9d000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x000000009f000000, size 8 MiB
[    0.000000] OF: reserved mem: initialized node dsp2-memory@9f000000, compatible id shared-dma-pool
[    0.000000] cma: Reserved 256 MiB at 0x00000000efc00000
[    0.000000] OMAP4: Map 0x00000000ffd00000 to (ptrval) for dram barrier
[    0.000000] DRA752 ES2.0
[    0.000000] random: get_random_bytes called from start_kernel+0xb4/0x544 with crng_init=0
[    0.000000] percpu: Embedded 17 pages/cpu s38668 r8192 d22772 u69632
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 513686
[    0.000000] Kernel command line: androidboot.selinux=permissive printk.devkmsg=on cma=256m vmalloc=400m androidboot.serialno=0c0140051dac0802 console=ttyS2,115200 androidboot.console=ttyS2 androidboot.hardware=beagle_x15board
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 1626948K/2060288K available (12288K kernel code, 716K rwdata, 3564K rodata, 2048K init, 394K bss, 40124K reserved, 393216K cma-reserved, 1201152K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xe7000000 - 0xff800000   ( 392 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xe6800000   ( 616 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0x(ptrval) - 0x(ptrval)   (14304 kB)
[    0.000000]       .init : 0x(ptrval) - 0x(ptrval)   (2048 kB)
[    0.000000]       .data : 0x(ptrval) - 0x(ptrval)   ( 717 kB)
[    0.000000]        .bss : 0x(ptrval) - 0x(ptrval)   ( 395 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000]  Tasks RCU enabled.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] OMAP clockevent source: timer1 at 32786 Hz
[    0.000000] arch_timer: cp15 timer(s) running at 6.14MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x16af5adb9, max_idle_ns: 440795202250 ns
[    0.000005] sched_clock: 56 bits at 6MHz, resolution 162ns, wraps every 4398046511023ns
[    0.000017] Switching to timer-based delay loop, resolution 162ns
[    0.000294] clocksource: 32k_counter: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 58327039986419 ns
[    0.000303] OMAP clocksource: 32k_counter at 32768 Hz
[    0.000802] Calibrating delay loop (skipped), value calculated using timer frequency.. 12.29 BogoMIPS (lpj=61475)
[    0.000817] pid_max: default: 32768 minimum: 301
[    0.000921] Security Framework initialized
[    0.000934] SELinux:  Initializing.
[    0.001041] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001055] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001750] CPU: Testing write buffer coherency: ok
[    0.001786] CPU0: Spectre v2: using ICIALLU workaround
[    0.002031] /cpus/cpu@0 missing clock-frequency property
[    0.002050] /cpus/cpu@1 missing clock-frequency property
[    0.002062] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.059908] Setting up static identity map for 0x80200000 - 0x80200060
[    0.079920] rcu: Hierarchical SRCU implementation.
[    0.100151] EFI services will not be available.
[    0.119983] smp: Bringing up secondary CPUs ...
[    0.200346] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.200352] CPU1: Spectre v2: using ICIALLU workaround
[    0.200477] smp: Brought up 1 node, 2 CPUs
[    0.200489] SMP: Total of 2 processors activated (24.59 BogoMIPS).
[    0.200498] CPU: All CPU(s) started in HYP mode.
[    0.200505] CPU: Virtualization extensions available.
[    0.200559] CPU1: update max cpu_capacity 1024
[    0.210352] CPU1: update max cpu_capacity 1024
[    0.221657] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.222085] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.222101] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.229231] pinctrl core: initialized pinctrl subsystem
[    0.229773] DMI not present or invalid.
[    0.230064] NET: Registered protocol family 16
[    0.231331] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.232262] omap_hwmod: l3_main_2 using broken dt data from ocp
[    0.340088] wkupaon_cm:clk:0068:0: failed to disable
[    0.438409] schedtune: configured to support 5 boost groups
[    0.438847] audit: initializing netlink subsys (disabled)
[    0.439030] audit: type=2000 audit(0.420:1): state=initialized audit_enabled=0 res=1
[    0.439580] cpuidle: using governor ladder
[    0.439723] cpuidle: using governor menu
[    0.470690] OMAP GPIO hardware version 0.1
[    0.475931] platform 48020000.serial: Linked as a consumer to 4a002b78.dma-router
[    0.482732] platform 58820000.ipu: Linked as a consumer to 48840000.mailbox
[    0.483026] platform 55020000.ipu: Linked as a consumer to 48842000.mailbox
[    0.483397] platform 40800000.dsp: Linked as a consumer to 48840000.mailbox
[    0.485640] platform 4809c000.mmc: Linked as a consumer to 4a002e00.pbias_regulator
[    0.485675] platform 4809c000.mmc: Linked as a consumer to 4805d000.gpio
[    0.487716] platform 40800000.dsp: Linked as a consumer to 40d01000.mmu
[    0.488596] platform 40800000.dsp: Linked as a consumer to 40d02000.mmu
[    0.489353] platform 58820000.ipu: Linked as a consumer to 58882000.mmu
[    0.490128] platform 55020000.ipu: Linked as a consumer to 55082000.mmu
[    0.502310] platform 48468000.mcasp: Linked as a consumer to 4a002c78.dma-router
[    0.507723] platform 4b500000.aes: Linked as a consumer to 4a002c78.dma-router
[    0.508772] platform 4b700000.aes: Linked as a consumer to 4a002c78.dma-router
[    0.509814] platform 480a5000.des: Linked as a consumer to 4a002b78.dma-router
[    0.510866] platform 4b101000.sham: Linked as a consumer to 4a002c78.dma-router
[    0.517613] platform 41000000.dsp: Linked as a consumer to 41501000.mmu
[    0.517636] platform 41000000.dsp: Linked as a consumer to 41502000.mmu
[    0.517663] platform 41000000.dsp: Linked as a consumer to 48842000.mailbox
[    0.520273] platform fixedregulator-evm_5v0: Linked as a consumer to fixedregulator-main_12v0
[    0.520788] platform 4809c000.mmc: Linked as a consumer to fixedregulator-vdd_3v3
[    0.520843] platform 480b4000.mmc: Linked as a consumer to fixedregulator-vdd_3v3
[    0.521927] platform fixedregulator-aic_dvdd: Linked as a consumer to fixedregulator-vdd_3v3
[    0.525490] No ATAGs?
[    0.525562] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.525577] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.526874] OMAP DMA hardware revision 0.0
[    0.540749] edma 43300000.edma: memcpy is disabled
[    0.569579] edma 43300000.edma: TI EDMA DMA engine driver
[    0.627196] omap-dma-engine 4a056000.dma-controller: OMAP DMA engine driver (LinkedList1/2/3 supported)
[    0.628407] evm_5v0: supplied by main_12v0
[    0.631791] omap-iommu 40d01000.mmu: 40d01000.mmu registered
[    0.631977] omap-iommu 40d02000.mmu: 40d02000.mmu registered
[    0.632626] omap-iommu 58882000.mmu: 58882000.mmu registered
[    0.633288] omap-iommu 55082000.mmu: 55082000.mmu registered
[    0.634076] omap-iommu 41501000.mmu: 41501000.mmu registered
[    0.634259] omap-iommu 41502000.mmu: 41502000.mmu registered
[    0.634535] iommu: Adding device 58820000.ipu to group 1
[    0.634614] iommu: Adding device 55020000.ipu to group 2
[    0.634743] iommu: Adding device 40800000.dsp to group 0
[    0.634965] iommu: Adding device 41000000.dsp to group 3
[    0.636246] SCSI subsystem initialized
[    0.636432] usbcore: registered new interface driver usbfs
[    0.636481] usbcore: registered new interface driver hub
[    0.636578] usbcore: registered new device driver usb
[    0.638236] i2c 0-0058: Linked as a consumer to 4ae10000.gpio
[    0.638638] palmas 0-0058: Irq flag is 0x00000008
[    0.662532] palmas 0-0058: Muxing GPIO 2f, PWM 0, LED 0
[    0.662840] platform 4809c000.mmc: Linked as a consumer to 48070000.i2c:tps659038@58:tps659038_pmic
[    0.663052] platform 58000000.dss: Linked as a consumer to 48070000.i2c:tps659038@58:tps659038_pmic
[    0.663175] platform fixedregulator-vdd_3v3: Linked as a consumer to 48070000.i2c:tps659038@58:tps659038_pmic
[    0.663210] platform fixedregulator-vtt: Linked as a consumer to 48070000.i2c:tps659038@58:tps659038_pmic
[    0.664699] SMPS12: supplied by regulator-dummy
[    0.666298] SMPS3: supplied by regulator-dummy
[    0.667888] SMPS45: supplied by regulator-dummy
[    0.669621] SMPS6: supplied by regulator-dummy
[    0.670987] SMPS7: supplied by regulator-dummy
[    0.672313] SMPS8: supplied by regulator-dummy
[    0.673513] SMPS9: supplied by regulator-dummy
[    0.674145] LDO1: supplied by regulator-dummy
[    0.691428] LDO2: supplied by regulator-dummy
[    0.711171] random: fast init done
[    0.711324] LDO3: supplied by regulator-dummy
[    0.731335] LDO4: supplied by regulator-dummy
[    0.751345] LDO5: supplied by regulator-dummy
[    0.751987] LDO6: supplied by regulator-dummy
[    0.752637] LDO7: supplied by regulator-dummy
[    0.753289] LDO8: supplied by regulator-dummy
[    0.753930] LDO9: supplied by regulator-dummy
[    0.771382] LDOLN: supplied by regulator-dummy
[    0.791419] LDOUSB: supplied by regulator-dummy
[    0.812432] platform 48070000.i2c:tps659038@58:tps659038_rtc: Linked as a consumer to 0-0058
[    0.812694] platform 48070000.i2c:tps659038@58:tps659038_pwr_button: Linked as a consumer to 0-0058
[    0.813275] platform 48070000.i2c:tps659038@58:tps659038_usb: Linked as a consumer to 48059000.gpio
[    0.813460] i2c 0-0048: Linked as a consumer to 48051000.gpio
[    0.813628] i2c 0-0018: Linked as a consumer to fixedregulator-vdd_3v3
[    0.813669] i2c 0-0018: Linked as a consumer to fixedregulator-aic_dvdd
[    0.813856] omap_i2c 48070000.i2c: bus 0 rev0.12 at 400 kHz
[    0.814396] i2c 2-006f: Linked as a consumer to fixedregulator-vdd_3v3
[    0.814469] omap_i2c 48060000.i2c: bus 2 rev0.12 at 400 kHz
[    0.814678] media: Linux media interface: v0.10
[    0.814719] videodev: Linux video capture interface: v2.00
[    0.814796] pps_core: LinuxPPS API ver. 1 registered
[    0.814805] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.814826] PTP clock support registered
[    0.814860] EDAC MC: Ver: 3.0.0
[    0.815644] omap-mailbox 48840000.mailbox: omap mailbox rev 0x400
[    0.815901] omap-mailbox 48842000.mailbox: omap mailbox rev 0x400
[    0.816433] Advanced Linux Sound Architecture Driver Initialized.
[    0.817315] clocksource: Switched to clocksource arch_sys_counter
[    0.882286] VFS: Disk quotas dquot_6.6.0
[    0.882351] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.884202] NET: Registered protocol family 2
[    0.884811] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.884842] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.884904] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.885031] TCP: Hash tables configured (established 8192 bind 8192)
[    0.885105] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.885139] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.885266] NET: Registered protocol family 1
[    0.885767] Trying to unpack rootfs image as initramfs...
[    0.913849] Freeing initrd memory: 768K
[    0.914654] hw perfevents: no interrupt-affinity property for /pmu, guessing.
[    0.914867] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
[    0.916189] Initialise system trusted keyrings
[    0.916380] workingset: timestamp_bits=13 max_order=19 bucket_order=6
[    0.922206] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.922336] Registering sdcardfs 0.1
[    0.922553] ntfs: driver 2.1.32 [Flags: R/O].
[    0.927666] Key type asymmetric registered
[    0.927678] Asymmetric key parser 'x509' registered
[    0.927726] bounce: pool size: 64 pages
[    0.927769] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    0.927780] io scheduler noop registered
[    0.927789] io scheduler deadline registered
[    0.927898] io scheduler cfq registered (default)
[    0.927909] io scheduler mq-deadline registered
[    0.927918] io scheduler kyber registered
[    0.929279] platform 4a084000.phy: Linked as a consumer to 48070000.i2c:tps659038@58:tps659038_pmic
[    0.929547] platform 4a085000.phy: Linked as a consumer to 48070000.i2c:tps659038@58:tps659038_pmic
[    0.932423] phy phy-4a084000.phy.0: Linked as a consumer to regulator.20
[    0.932759] phy phy-4a085000.phy.1: Linked as a consumer to regulator.20
[    0.935080] pinctrl-single 4a003400.pinmux: 282 pins, size 1128
[    0.939058] dra7-pcie 51000000.pcie: Linked as a consumer to phy-4a094000.pciephy.3
[    0.939517] dra7-pcie 51000000.pcie: host bridge /ocp/axi@0/pcie@51000000 ranges:
[    0.939559] dra7-pcie 51000000.pcie:    IO 0x20003000..0x20012fff -> 0x00000000
[    0.939587] dra7-pcie 51000000.pcie:   MEM 0x20013000..0x2fffffff -> 0x20013000
[    1.939884] dra7-pcie 51000000.pcie: Phy link never came up
[    1.940029] dra7-pcie 51000000.pcie: PCI host bridge to bus 0000:00
[    1.940043] pci_bus 0000:00: root bus resource [bus 00-ff]
[    1.940056] pci_bus 0000:00: root bus resource [io  0x0000-0xffff]
[    1.940067] pci_bus 0000:00: root bus resource [mem 0x20013000-0x2fffffff]
[    1.946223] PCI: bus0: Fast back to back transfers disabled
[    1.952029] PCI: bus1: Fast back to back transfers enabled
[    1.952074] pci 0000:00:00.0: BAR 0: assigned [mem 0x20100000-0x201fffff 64bit]
[    1.952095] pci 0000:00:00.0: PCI bridge to [bus 01-ff]
[    1.952427] pcieport 0000:00:00.0: Signaling PME with IRQ 170
[    1.952563] pcieport 0000:00:00.0: AER enabled with IRQ 170
[    1.958550] Serial: 8250/16550 driver, 10 ports, IRQ sharing enabled
[    1.958779] serial serial0: tty port ttyS0 registered
[    1.958896] serial serial1: tty port ttyS1 registered
[    1.959122] serial serial2: tty port ttyS3 registered
[    1.959237] serial serial3: tty port ttyS4 registered
[    1.959349] serial serial4: tty port ttyS5 registered
[    1.959461] serial serial5: tty port ttyS6 registered
[    1.959573] serial serial6: tty port ttyS7 registered
[    1.959684] serial serial7: tty port ttyS8 registered
[    1.959791] serial serial8: tty port ttyS9 registered
[    1.960572] console [ttyS2] disabled
[    1.960628] 48020000.serial: ttyS2 at MMIO 0x48020000 (irq = 45, base_baud = 3000000) is a 8250
[    3.408098] console [ttyS2] enabled
[    3.413462] omap_rng 48090000.rng: Random Number Generator ver. 20
[    3.413999] random: crng init done
[    3.423187] omapdss_dss 58000000.dss: Linked as a consumer to regulator.19
[    3.430242] DSS: OMAP DSS rev 6.1
[    3.434640] platform 58040000.encoder: Linked as a consumer to 4a002b78.dma-router
[    3.442290] platform 58040000.encoder: Linked as a consumer to 48070000.i2c:tps659038@58:tps659038_pmic
[    3.453663] omapdss_hdmi5 58040000.encoder: Linked as a consumer to regulator.13
[    3.461202] omapdss_hdmi5 58040000.encoder: Dropping the link to regulator.13
[    3.480960] brd: module loaded
[    3.490475] loop: module loaded
[    3.497820] libphy: Fixed MDIO Bus: probed
[    3.502842] tun: Universal TUN/TAP device driver, 1.6
[    3.567349] davinci_mdio 48485000.mdio: davinci mdio revision 1.6, bus freq 1000000
[    3.575045] libphy: 48485000.mdio: probed
[    3.583692] davinci_mdio 48485000.mdio: phy[1]: device 48485000.mdio:01, driver Micrel KSZ9031 Gigabit PHY
[    3.593415] davinci_mdio 48485000.mdio: phy[2]: device 48485000.mdio:02, driver Micrel KSZ9031 Gigabit PHY
[    3.603697] cpsw 48484000.ethernet: Detected MACID = 90:9a:77:94:30:d0
[    3.610330] cpsw 48484000.ethernet: initialized cpsw ale version 1.4
[    3.616714] cpsw 48484000.ethernet: ALE Table size 1024
[    3.622028] cpsw 48484000.ethernet: cpts: overflow check period 500 (jiffies)
[    3.630070] cpsw 48484000.ethernet: cpsw: Detected MACID = 90:9a:77:94:30:d1
[    3.638200] PPP generic driver version 2.4.2
[    3.642570] PPP BSD Compression module registered
[    3.647298] PPP Deflate Compression module registered
[    3.652404] PPP MPPE Compression module registered
[    3.657218] NET: Registered protocol family 24
[    3.661704] PPTP driver version 0.8.5
[    3.666934] dwc3 48890000.usb: Failed to get clk 'ref': -2
[    3.674693] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    3.681447] ehci-pci: EHCI PCI platform driver
[    3.685949] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    3.692194] ohci-pci: OHCI PCI platform driver
[    3.697436] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    3.702965] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[    3.710907] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010
[    3.720398] xhci-hcd xhci-hcd.0.auto: irq 175, io mem 0x48890000
[    3.726836] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    3.735161] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.742433] usb usb1: Product: xHCI Host Controller
[    3.747348] usb usb1: Manufacturer: Linux 4.19.102-g943e19f-dirty xhci-hcd
[    3.754253] usb usb1: SerialNumber: xhci-hcd.0.auto
[    3.759513] hub 1-0:1.0: USB hub found
[    3.763313] hub 1-0:1.0: 1 port detected
[    3.767618] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    3.773140] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[    3.780859] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
[    3.787513] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.795793] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[    3.804116] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.811392] usb usb2: Product: xHCI Host Controller
[    3.816292] usb usb2: Manufacturer: Linux 4.19.102-g943e19f-dirty xhci-hcd
[    3.823212] usb usb2: SerialNumber: xhci-hcd.0.auto
[    3.828464] hub 2-0:1.0: USB hub found
[    3.832262] hub 2-0:1.0: 1 port detected
[    3.836640] usbcore: registered new interface driver usb-storage
[    3.843197] usbcore: registered new interface driver xpad
[    3.848679] usbcore: registered new interface driver usb_acecad
[    3.854659] usbcore: registered new interface driver aiptek
[    3.860309] usbcore: registered new interface driver gtco
[    3.865768] usbcore: registered new interface driver hanwang
[    3.871504] usbcore: registered new interface driver kbtab
[    3.877073] i2c /dev entries driver
[    3.883723] gpio-fan gpio_fan: GPIO fan initialized
[    3.889880] tmp102 0-0048: initialized
[    3.895674] device-mapper: uevent: version 1.0.3
[    3.900507] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
[    3.910375] cpu cpu0: Linked as a consumer to regulator.3
[    3.915888] cpu cpu0: Linked as a consumer to regulator.26
[    3.922187] energy_model: pd0: invalid cap. state: -22
[    3.927450] cpu_cooling: cpu0 is not running as cooling device: -22
[    3.934296] sdhci: Secure Digital Host Controller Interface driver
[    3.940607] sdhci: Copyright(c) Pierre Ossman
[    3.946265] sdhci-pltfm: SDHCI platform and OF driver helper
[    3.953312] ledtrig-cpu: registered to indicate activity on CPUs
[    3.960865] hidraw: raw HID events driver (C) Jiri Kosina
[    3.968356] usbcore: registered new interface driver usbhid
[    3.973952] usbhid: USB HID core driver
[    3.978351] ashmem: initialized
[    3.984904] u32 classifier
[    3.987833]     input device check on
[    3.991510]     Actions configured
[    3.995448] xt_time: kernel timezone is -0000
[    3.999946] gre: GRE over IPv4 demultiplexor driver
[    4.004844] IPv4 over IPsec tunneling driver
[    4.009760] Initializing XFRM netlink socket
[    4.014345] NET: Registered protocol family 10
[    4.029812] Segment Routing with IPv6
[    4.033562] mip6: Mobile IPv6
[    4.037426] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    4.044247] NET: Registered protocol family 17
[    4.049053] NET: Registered protocol family 15
[    4.053578] l2tp_core: L2TP core driver, V2.0
[    4.058022] l2tp_ppp: PPPoL2TP kernel driver, V2.0
[    4.063165] Registering SWP/SWPB emulation handler
[    4.068081] omap_voltage_late_init: Voltage driver support not added
[    4.074480] Power Management for TI OMAP4+ devices.
[    4.080056] registered taskstats version 1
[    4.084171] Loading compiled-in X.509 certificates
[    4.109969] dmm 4e000000.dmm: workaround for errata i878 in use
[    4.117210] dmm 4e000000.dmm: initialized all PAT entries
[    4.123085] vdd_3v3: supplied by regen1
[    4.127386] aic_dvdd_fixed: supplied by vdd_3v3
[    4.132191] vtt_fixed: supplied by smps3
[    4.137047] omapdss_hdmi5 58040000.encoder: Linked as a consumer to regulator.13
[    4.144523] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    4.151180] omapdss_hdmi5 58040000.encoder: Dropping the link to regulator.13
[    4.159730] dwc3 488d0000.usb: Failed to get clk 'ref': -2
[    4.168115] omap_gpio 4805d000.gpio: Could not set line 27 debounce to 200000 microseconds (-22)
[    4.176939] sdhci-omap 4809c000.mmc: Got CD GPIO
[    4.181777] sdhci-omap 4809c000.mmc: Linked as a consumer to regulator.25
[    4.188831] sdhci-omap 4809c000.mmc: Linked as a consumer to regulator.10
[    4.195697] sdhci-omap 4809c000.mmc: Dropping the link to regulator.10
[    4.202335] sdhci-omap 4809c000.mmc: Linked as a consumer to regulator.30
[    4.209347] sdhci-omap 4809c000.mmc: Linked as a consumer to regulator.10
[    4.216214] sdhci-omap 4809c000.mmc: no pinctrl state for ddr_3_3v mode
[    4.249180] mmc0: SDHCI controller on 4809c000.mmc [4809c000.mmc] using ADMA
[    4.256946] sdhci-omap 480b4000.mmc: Linked as a consumer to regulator.30
[    4.263831] sdhci-omap 480b4000.mmc: Dropping the link to regulator.30
[    4.270498] sdhci-omap 480b4000.mmc: Linked as a consumer to regulator.30
[    4.303071] mmc1: SDHCI controller on 480b4000.mmc [480b4000.mmc] using ADMA
[    4.311206] omapdss_hdmi5 58040000.encoder: Linked as a consumer to regulator.13
[    4.319144] omapdss_dss 58000000.dss: bound 58001000.dispc (ops dispc_component_ops)
[    4.327272] omapdss_dss 58000000.dss: bound 58040000.encoder (ops hdmi5_component_ops)
[    4.336127] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    4.342838] [drm] No driver support for vblank timestamp query.
[    4.349173] usb 1-1: New USB device found, idVendor=0451, idProduct=8142, bcdDevice= 1.00
[    4.357452] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=1
[    4.364658] usb 1-1: SerialNumber: D70D0859B562
[    4.405489] mmc1: new DDR MMC card at address 0001
[    4.411083] mmcblk1: mmc1:0001 M62704 3.53 GiB 
[    4.416104] mmcblk1boot0: mmc1:0001 M62704 partition 1 2.00 MiB
[    4.422530] mmcblk1boot1: mmc1:0001 M62704 partition 2 2.00 MiB
[    4.428780] hub 1-1:1.0: USB hub found
[    4.432754] hub 1-1:1.0: 4 ports detected
[    4.436866] mmcblk1rpmb: mmc1:0001 M62704 partition 3 512 KiB, chardev (243:0)
[    4.468376]  mmcblk1: p1 p2 p3 p4 p5 p6 p7 p8 p9
[    4.497383] usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[    4.527619] usb 2-1: New USB device found, idVendor=0451, idProduct=8140, bcdDevice= 1.00
[    4.535865] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    4.571645] hub 2-1:1.0: USB hub found
[    4.575491] hub 2-1:1.0: 4 ports detected
[    4.701981] [drm] Enabling DMM ywrap scrolling
[    4.706592] omapdrm omapdrm.0: fb0: omapdrm frame buffer device
[    4.713637] [drm] Initialized omapdrm 1.0.0 20110917 for omapdrm.0 on minor 0
[    4.721650] hctosys: unable to open rtc device (rtc0)
[    4.727608] ALSA device list:
[    4.730589]   No soundcards found.
[    4.735334] Freeing unused kernel memory: 2048K
[    4.740013] Run /init as init process
[    4.745971] init: init first stage started!
[    4.750696] init: [libfs_mgr]ReadFstabFromDt(): failed to read fstab from dt
[    4.758300] init: [libfs_mgr]Error updating for slotselect
[    4.763828] init: [libfs_mgr]ReadFstabFromFile(): failed to load fstab from : '/fstab.beagle_x15board'
[    4.773236] init: Failed to fstab for first stage mount
[    4.778564] init: Using Android DT directory /proc/device-tree/firmware/android/
[    4.786536] init: [libfs_mgr]Error updating for slotselect
[    4.792085] init: [libfs_mgr]ReadFstabFromFile(): failed to load fstab from : '/fstab.beagle_x15board'
[    4.801539] init: First stage mount skipped (missing/incompatible/empty fstab in device tree)
[    4.810204] init: Skipped setting INIT_AVB_VERSION (not in recovery mode)
[    4.817091] init: execv("/system/bin/init") failed: No such file or directory
[    4.824717] init: InitFatalReboot: signal 6
[    4.828953] usb 1-1.1: new low-speed USB device number 3 using xhci-hcd
[    4.871331] init: #00 pc 000c901c  /init (UnwindStackCurrent::UnwindFromContext(unsigned int, void*)+84)
[    4.880965] init: #01 pc 0005bfa5  /init (android::init::InitFatalReboot(int)+64)
[    4.888543] init: #02 pc 0005c1d3  /init (android::init::InstallRebootSignalHandlers()::$_18::__invoke(int)+14)
[    4.898707] init: #03 pc 001202cc  /init (__restore)
[    4.903707] init: #04 pc 0011d2ac  /init (abort+100)
[    4.909701] init: #05 pc 0005de5f  /init (android::init::InitAborter(char const*)+22)
[    4.917595] init: #06 pc 000975d3  /init (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_3::__invoke(char const*)+38)
[    4.930386] init: #07 pc 000980d7  /init (__android_log_call_aborter+22)
[    4.937130] init: #08 pc 000970f1  /init (android::base::LogMessage::~LogMessage()+420)
[    4.945203] init: #09 pc 0005656b  /init (android::init::FirstStageMain(int, char**)+3750)
[    4.953593] init: #10 pc 0011c7a3  /init (__real_libc_init(void*, void (*)(), int (*)(int, char**, char**), structors_array_t const*, bionic_tcb*)+410)
[    4.967276] init: Reboot ending, jumping to kernel
[    5.000977] usb 1-1.1: New USB device found, idVendor=046d, idProduct=c077, bcdDevice=72.00
[    5.009393] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    5.016738] usb 1-1.1: Product: USB Optical Mouse
[    5.021506] usb 1-1.1: Manufacturer: Logitech
[    5.045457] reboot: Restarting system with command 'bootloader'

U-Boot SPL 2020.04-rc5-00007-gdfd5321 (Apr 09 2020 - 14:12:40 +0200)
DRA752-GP ES2.0
Trying to boot from MMC2_2
no pinctrl state for default mode
Loading Environment from FAT... no pinctrl state for default mode
MMC: no card present
Loading Environment from MMC... OK


U-Boot 2020.04-rc5-00007-gdfd5321 (Apr 09 2020 - 14:12:40 +0200)

CPU  : DRA752-GP ES2.0
Model: TI AM5728 BeagleBoard-X15 rev C
Board: BeagleBoard X15 REV C.00
DRAM:  2 GiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... MMC: no card present
Loading Environment from MMC... OK
Net:   eth0: ethernet@48484000
Hit any key to stop autoboot:  0 
MMC: no card present
MMC: no card present
MMC: no card present
MMC: no card present
Trying to boot Linux from eMMC ...
switch to partitions #0, OK
mmc1(part 0) is current device
SD/MMC found on device 1
** Unrecognized filesystem type **
CACHE: Misaligned operation at range [fffd37a8, fffd3fa8]
BCB: Normal boot requested...
Trying to boot Android from eMMC ...
switch to partitions #0, OK
mmc1(part 0) is current device

MMC read: dev # 1, block # 169472, count 40960 ... 40960 blocks read: OK
## Loading kernel from FIT Image at 90000000 ...
   Using 'am57xx-beagle-x15-revc.dtb' configuration
   Trying 'kernel@1' kernel subimage
     Description:  TI kernel
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x900000b8
     Data Size:    5554688 Bytes = 5.3 MiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x82000000
     Entry Point:  0x82000000
   Verifying Hash Integrity ... OK
## Loading ramdisk from FIT Image at 90000000 ...
   Using 'am57xx-beagle-x15-revc.dtb' configuration
   Trying 'ramdisk@1' ramdisk subimage
     Description:  Android Ramdisk Image
     Type:         RAMDisk Image
     Compression:  uncompressed
     Data Start:   0x9054c368
     Data Size:    782542 Bytes = 764.2 KiB
     Architecture: ARM
     OS:           Linux
     Load Address: 0x88080000
     Entry Point:  0x88080000
   Verifying Hash Integrity ... OK
   Loading ramdisk from 0x9054c368 to 0x88080000
## Loading fdt from FIT Image at 90000000 ...
   Using 'am57xx-beagle-x15-revc.dtb' configuration
   Trying 'fdt@1' fdt subimage
     Description:  AM57xx-beagle-x15-revc
     Type:         Flat Device Tree
     Compression:  uncompressed
     Data Start:   0x9060b4e4
     Data Size:    131348 Bytes = 128.3 KiB
     Architecture: ARM
     Load Address: 0x83000000
   Verifying Hash Integrity ... OK
   Loading fdt from 0x9060b4e4 to 0x83000000
   Booting using the fdt blob at 0x83000000
   Loading Kernel Image
   Loading Ramdisk to 8ff40000, end 8ffff0ce ... OK
   Loading Device Tree to 8ff1c000, end 8ff3f113 ... OK
Using machid 0xfe6 from environment

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.102-g943e19f-dirty (deru272633@deulmts01) (gcc version 7.5.0 (Linaro GCC 7.5-2019.12)) #1 SMP PREEMPT Thu Apr 9 14:17:04 CEST 2020

  • 0 in reply to Dean Rumen
    TI__Expert 6005 points

    ok , i tried android auto lunch target for X15 and was able to get to that hmi.

    Apply this patch and rebuild: 

    https://android-review.googlesource.com/c/device/ti/beagle-x15/+/1284705

    able to boot to ui:

    screenshots

  • 0 in reply to Dean Rumen
    TI__Expert 6005 points

    Reviewed your log, though you might be building the right kernel it looks like you are not picking the correct device tree file.

    For your convienience , detailed steps.

    1. Build kernel with mentioned aosp 4.19 branch in previous comment.

    make ARCH=arm CROSS_COMPILE=<tc_path>/bin/arm-none-linux-gnueabihf- ti_sdk_am57x_android_release_defconfig

    make ARCH=arm CROSS_COMPILE=<tc_path>/bin/arm-none-linux-gnueabihf- zImage dtbs modules

    2. Build uboot from aosp/external/u-boot

    make ARCH=arm CROSS_COMPILE=<tc_path>/bin/arm-none-linux-gnueabihf- am57xx_evm_defconfig

    make ARCH=arm CROSS_COMPILE=<tc_path>/bin/arm-none-linux-gnueabihf-

    output: u-boot.img , MLO

    3. Build AOSP

    export KERNELDIR=<path of kernel in step-1>; . ./build/envsetup.sh; lunch beagle_x15_auto-userdebug;make

    4. Flash

    4.1 : Update partition table 

    Should look like this : https://pastebin.ubuntu.com/p/Bc2HfwVSvp/ , 

    4.2 Flash and reboot

       => env default -f -a

        => setenv partitions $partitions_android

        => env save

    Now do "oem format" and flash all images:

    sudo ./fastboot oem format

    sudo ./fastboot flash xloader MLO

    sudo ./fastboot flash bootloader u-boot.img

    sudo ./fastboot flash boot_a boot.img

    sudo ./fastboot flash boot_b boot.img

    sudo ./fastboot flash dtbo_a dtbo.img

    sudo ./fastboot flash dtbo_b dtbo.img

    sudo ./fastboot flash vbmeta_a vbmeta.img

    sudo ./fastboot flash vbmeta_b vbmeta.img

    sudo ./fastboot flash recovery recovery.img

    sudo ./fastboot flash super super.img

    sudo ./fastboot flash userdata userdata.img

    sudo ./fastboot reboot

  • 0 in reply to Praneeth Bajjuri
    TI__Expert 6005 points

    Dean,

    Instructions are updated now at : https://wiki.linaro.org/AOSP/Boards/BeagleboardX15 

    --

    Master is a active dev project , this cannot be supported . Highly recommend you to stay on a tagged release if you are building a product.

    But if developing a feature and upstreaming to AOSP master, and you find issues , feel free to try on your own and send fixes to google gerrit.

  • 0 in reply to Praneeth Bajjuri
    TI__Expert 6005 points

    Dean,

    Closing the ticket based on the comments and confirmation on Pie baseline and additional specific instructions for Master auto  builds for X15. 

  • 0 in reply to Praneeth Bajjuri
    Prodigy 80 points

    Hi Praneeth,

    thank you very, very much for your support and patience. Especially for the patch you made, without it the Automotive doesn't boot up.

    Once more to confirm, with above instructions and provided patch the Android Automotive master from 2020-04-03 boots up and loads to UI on Beagle Board X15. We'll select a tagged release for future builds...

    Just one question for the end, which are TI officially supported boards for Android Automotive infotainment?

    Regards,

    Dean

  • 0 in reply to Dean Rumen
    TI__Expert 6005 points

    The known release for android automotive is here

    https://processors.wiki.ti.com/index.php/6AO.1.1_Release_Notes

    And

    https://training.ti.com/processor-sdk-android-automotive-overview

    It is based on Jacinto platform.

    X15 is supposed to be community/aosp reference for development purpose only.

    Hope it clarifies

    Regards

    Praneeth