• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 1613 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

PROCESSOR-SDK-AM62X: Android AOSP - How to boot android AOSP from SD card

Ken Lin
Prodigy 170 points

Part Number: PROCESSOR-SDK-AM62X

Hello,


The TI website only introduced the steps for creating bootable sd card to flashing eMMC.

https://software-dl.ti.com/processor-sdk-android/esd/AM62X/08_03_00/docs/devices/AM62X/android/Overview_Flashing.html#sd-card-creation

Is it possible to make a bootable sd card contain all android partition and boot from it ?

Please teach me if it works.

Thanks,

Ken

  • 0
    TI__Intellectual 2835 points

    Hi Ken,

    It's not possible to boot from SDcard, nothing done actually to support it.
    it's probably possible with some changes but not plan to add it for now

    SDcard is just needed first time then you can update and flash all part with fastboot command

  • +1 in reply to Guillaume La Roque
    Prodigy 170 points

    Hi Guillaume,

    Thanks for your reply.

    I got blow error log after I compiling the bootloader source code (am62x android sdk) and booting from sd card.

    Do you have any idea for this problem?

    Fullscreen am62x_uboot_errorlog.txt Download 
    U-Boot SPL 2021.01-dirty (Sep 19 2022 - 09:52:16 +0800)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.3.2--v08.03.02 (Jolly Jellyfi')
Trying to boot from MMC2
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE:  BL31: v2.6(release):08.04.00.002
NOTICE:  BL31: Built : 20:32:07, Sep  7 2022

U-Boot SPL 2021.01-dirty (Sep 19 2022 - 09:53:06 +0800)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.3.2--v08.03.02 (Jolly Jellyfi')
Trying to boot from MMC2


U-Boot 2021.01-dirty (Sep 19 2022 - 09:53:06 +0800)

SoC:   AM62X SR1.0
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62-SKEVM rev E3
DRAM:  2 GiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
Verify GPT: success!
Loading Android boot partition...
switch to partitions #0, OK
mmc0(part 0) is current device
misc partition number:0x4
ANDROID: Booting slot: a
A/B cmdline addition: androidboot.slot_suffix=_a
Running without AVB...

MMC read: dev # 0, block # 28672, count 81920 ... 81920 blocks read: OK
Preparing FDT...
Error: Android boot is not supported for am62x
dwc3-generic-peripheral usb@31000000: failed to enable ep0out
failed to start <NULL>: -110
g_dnl_register: failed!, error: -110

    Thanks,

    Ken

  • +1 in reply to Ken Lin
    TI__Intellectual 2835 points

    Hi,

    It's probably link to board_name variable was noy same on E3 board as previous revision so for now you can apply this patch on U-Boot to fix the boot.
    I'll check if i have a E3 revision somewhere to do a proper fix and commit it

    diff --git a/include/configs/am62x_evm.h b/include/configs/am62x_evm.h
index 406eba40e0..bd3e989bfe 100644
--- a/include/configs/am62x_evm.h
+++ b/include/configs/am62x_evm.h
@@ -151,8 +151,8 @@
  */
 #define PREPARE_FDT \
        "echo Preparing FDT...; " \
-       "if test $board_name = am62x_skevm; then " \
-               "echo \"  Reading DTB for am62x_skevm...\"; " \
+       "if test $board_name = am62x_skevm || test $board_name = am62x; then " \
+               "echo \"  Reading DTB for $board_name...\"; " \
                "setenv dtb_index 0;" \
        "else " \
                "echo Error: Android boot is not supported for $board_name; " \