SK-AM62: Android will auto-reboot continuously with the prebuild image

And when the EVM auto reboot few times, the console will dump this:

The log seems the EMMC is missing to cause this.

BR Rio

?
U-Boot SPL 2021.01-g2dd2e1d366 (Sep 24 2022 - 18:35:58 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.7--v08.04.07 (Jolly Jellyfi')
Trying to boot from MMC1
Loading Environment from MMC... OK
init_env from device 9 not supported!
Starting ATF on ARM64 core...

NOTICE: BL31: v2.7(release):v2.7.0-dirty
NOTICE: BL31: Built : 00:19:16, Sep 24 2022

U-Boot SPL 2021.01-g2dd2e1d366 (Sep 24 2022 - 18:36:08 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.7--v08.04.07 (Jolly Jellyfi')
Trying to boot from MMC1

U-Boot 2021.01-g2dd2e1d366 (Sep 24 2022 - 18:36:08 +0000)

SoC: AM62X SR1.0 GP
Model: Texas Instruments AM625 SK
EEPROM not available at 0x50, trying to read at 0x51
Board: AM62-SKEVM rev E2
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: No bootable slot was found.
Android boot failed, error -22.
A/B cmdline addition: androidboot.slot_suffix=_
Running without AVB...
mmc - MMC sub system

Usage:
mmc info - display info of the current MMC device
mmc read addr blk# cnt
mmc write addr blk# cnt
mmc erase blk# cnt
mmc rescan [mode]
mmc part - lists available partition on current mmc device
mmc dev [dev] [part] [mode] - show or set current mmc device [partition] and set mode
- the required speed mode is passed as the index from the following list
[MMC_LEGACY, MMC_HS, SD_HS, MMC_HS_52, MMC_DDR_52, UHS_SDR12, UHS_SDR25,
UHS_SDR50, UHS_DDR50, UHS_SDR104, MMC_HS_200, MMC_HS_400, MMC_HS_400_ES]
mmc list - lists available devices
mmc wp - power on write protect boot partitions
mmc hwpartition [args...] - does hardware partitioning
arguments (sizes in 512-byte blocks):
[user [enh start cnt] [wrrel {on|off}]] - sets user data area attributes
[gp1|gp2|gp3|gp4 cnt [enh] [wrrel {on|off}]] - general purpose partition
[check|set|complete] - mode, complete set partitioning completed
WARNING: Partitioning is a write-once setting once it is set to complete.
Power cycling is required to initialize partitions after set to complete.
mmc bootbus dev boot_bus_width reset_boot_bus_width boot_mode
- Set the BOOT_BUS_WIDTH field of the specified device
mmc bootpart-resize <dev> <boot part size MB> <RPMB part size MB>
- Change sizes of boot and RPMB partitions of specified device
mmc partconf dev [boot_ack boot_partition partition_access]
- Show or change the bits of the PARTITION_CONFIG field of the specified device
mmc rst-function dev value
- Change the RST_n_FUNCTION field of the specified device
WARNING: This is a write-once field and 0 / 1 / 2 are the only valid values.
mmc setdsr <value> - set DSR register value

Failed to boot Android...
dwc3-generic-peripheral usb@31000000: failed to enable ep0out
failed to start <NULL>: -110
g_dnl_register: failed!, error: -110
=>

Hello Rio,

Please make sure you are using a monitor or a HDMI dongle and that Android is booting : you have the Android logo on screen if you are using a monitor.

Thank you,

Safae

Hi Safae:

So, this is a bug / know-issue or a limitation?

Customer is asking how to solve this if thee is no HDMI.

BR Rio

Hello Rio,

Virtual display is an option. I will get back to you after further tests on my end.

Thank you,

Safae

Hello Rio,

Virtual display is not supported yet. There is however a "fake" one and the board should not reboot.

I am not reproducing this issue on my board and  with the release binaries.

Please make sure you have an Input USB device connected to Type-A connector on the board.

The flash script (flashall.sh) should not return any error.

Could you please send the output of ./flashall.sh ?

Thank you,

Safae

Hi Safae:

Okay, Please let me make this issue with simple question:

If you don't plug the mouse/ HDMI display, does your EVM auto reboot all the time? <-- please answer this.

BTW, you need to wait about ~3 or 4 mins, then, you will see the EVM auto reboot with unknow reason.

If yes, how to prevent this permanently?

Due to my 2 customers and me face this annoying issue, if the EVM auto reboot continuously, they cannot evaluate the performance with longer period.

BTW, this issue is 100% reproduce-able.

BR Rio

Hello Rio,

>> If you don't plug the mouse/ HDMI display, does your EVM auto reboot all the time?

Yes. The board reboots if no Input USB device is connected to Type-A connector.

Using the release binaries, you need to plug an input device (mouse) to prevent this, as mentioned in the release documentation notes:

https://software-dl.ti.com/processor-sdk-android/esd/AM62X/08_04_00/docs/android/Overview_Flashing.html#emmc-flashing

The reason is that Android needs an input device to boot.

Thank you,

Safae

-->The reason is that Android needs an input device to boot.

Hi Safae:

Okay, is there any Android document to address this sentence? Please share to us. We will talk with Customer.

So,

Q1. do you mean, When Android Mobile phone booting, the Touch Screen or something input device connected will make the Android boot-able?

Q2. If this is the case, then, the Industrial Customer HMI product needs to have the USB keyboard/Mouse connected to make the Android boot-able?

Q3. Try to image the Customer Production line, they need to connect the USB mouse to test their PCB  boot completed?

Please comment for each, thanks.

BR Rio

Hey Rio,

>> Okay, is there any Android document to address this sentence? Please share to us. We will talk with Customer.

I will get back to you If I find any Android documentation about that

>> Q1. do you mean, When Android Mobile phone booting, the Touch Screen or something input device connected will make the Android boot-able?

Yes adding a touch screen or another input device will allow a complete Android boot

>> Q2. If this is the case, then, the Industrial Customer HMI product needs to have the USB keyboard/Mouse connected to make the Android boot-able?

1 input device is enough. You do not need to add a keyboard/mouse if you have a touch screen connected.

>> Q3. Try to image the Customer Production line, they need to connect the USB mouse to test their PCB  boot completed?

No. They will be testing with their final product which has input devices ( touch screen ... )

Best regards,

Safae