SK-AM62: AM62 Android fastboot 0 issue

Hi ,

I have merged this patch and tested onto E2 EVM, however, there is no console output.

https://e2e.ti.com/support/processors-group/processors---internal/f/processors---internal-forum/1113666/sk-am62-android-demo-on-early-board-e1-or-previous?tisearch=e2e-sitesearch&keymatch=AM62%20Android#

Any solution?

BR Rio

Your problem look to be link to usb issue, try with an other usb port/hub.

can you confirm you do in uboot console this  : 
env default -f -a
run set_android_boot

send me result of a printenv command in uboot.
and complete boot log too.

thanks

Hi G:

#1. My testing EVM is E2, we are waiting the E3 EVM to come.

#2. By merging the patch, the E2 EVM won't have any console.

#3. So, I only can have the console log by using the native SDK8.4 image on E2, the attached is the log you request.

Plz help.

BR Rio

AM62_Fastboot_Issue_EV2_Default_SDK_No_Patch.txt

Hello Rio,

- Could you please confirm you have run the following commands after interrupting u-boot :

env default -f -a
run set_android_boot

- Have you ever tried to flash the release binaries before ? : https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-8cVNlmT7Aa/08.04.00/AM62x_08.04.00_emmc.tgz

- You can always boot from an sdcard and flash a new bootloader, please see the steps here : https://software-dl.ti.com/processor-sdk-android/esd/AM62X/08_04_00/docs/android/Overview_Flashing.html

-> you can then flash the emmc and switch to booting from emmc.

- Could you please confirm after the last step the release binaries are working on your board.

Thank you,

Safae

Hi Safae:

#1. If I take the patch, the E2 EVM won't give me any console log. How do I test those cmds you need me to do at this moment?

#2. If you read the log I posted, (testing with the Native uboot 3 files.) , You can see those logs.

BR Rio

Failed to boot Android...
dwc3-generic-peripheral usb@31000000: failed to enable ep0out
failed to start <NULL>: -110
g_dnl_register: failed!, error: -110
=> env default -f -a
## Resetting to default environment
=> run set_android_boot
Saving Environment to MMC... Writing to MMC(0)... OK
=> boot
GUID Partition Table Header signature is wrong: 0x0 != 0x5452415020494645
gpt_verify_headers: *** ERROR: Invalid GPT ***
Verify GPT: error!
Broken MMC partition scheme
Running Fastboot...
dwc3-generic-peripheral usb@31000000: failed to enable ep0out
failed to start <NULL>: -110
g_dnl_register: failed!, error: -110
Error: mmc 0:misc read failed (-1)
Warning: BCB is corrupted or does not exist
Loading Android boot partition...
switch to partitions #0, OK
mmc0(part 0) is current device
misc partition not found
A/B cmdline addition: androidboot.slot_suffix=_
Running without AVB...
mmc - MMC sub system

Hello Rio,

To have the console back. you can to boot from an sdcard:

- Please see the steps here : https://software-dl.ti.com/processor-sdk-android/esd/AM62X/08_04_00/docs/android/Overview_Flashing.html

Please let me know if you need help with that.

1- After booting from an sdcard, Please interrupt u-boot and redo :

env default -f -a
run set_android_boot

2- Reset (Power cycle) the board and interrupt u-boot then do :

fastboot 0

3- flash the release images using the flashall.sh script

Thank you,

Safae

Hi Safae:

I describe my problem in detail again.

#1. I ONLY TEST the SD card here, I don't test with the EMMC, please note this.

#2. I'm asking u:

        A. Do we be able to put all the uboot + rootfs (Both, and all together) into a SD card to boot the AM62 EVM ?

             Please confirm this.

       B. Please confirm if there is needing any patch for "BOOTing " the SD card okay, (not the EMMC).

       C. Please check if the current SDK is okay to boot the E2 EVM or not.

BR Rio

Hi Safae:

Now, I'm having the E3 EVM to test, and I just know The Android only gives the EMMC boot.

Below is my flashall.sh error.

Please guide me how to solve.

THanks.

root@ubuntu:/opt/AM62_804/emmc_image# sudo ./flashall.sh
Fastboot: /usr/bin/fastboot
Image location: ./

Fastboot - device detected: 0000000000000013

8+0 records in
8+0 records out
8388608 bytes (8.4 MB, 8.0 MiB) copied, 0.175406 s, 47.8 MB/s
mkfs.fat 4.1 (2017-01-24)
Create GPT partition table
...
OKAY [ 0.023s]
finished. total time: 0.023s
Flashing tiboot3.....
tiboot3bin: ./tiboot3.bin
target reported max download size of 788529152 bytes
sending 'tiboot3' (320 KB)...
OKAY [ 0.063s]
writing 'tiboot3'...
FAILED (remote: cannot find partition)
finished. total time: 0.075s
bootloader: ./bootloader.img
target didn't report max-download-size
sending 'bootloader' (8192 KB)...
FAILED (command write failed (Success))
finished. total time: 0.000s
Flash android partitions
target didn't report max-download-size
sending 'super' (1331212 KB)...
FAILED (command write failed (Success))
finished. total time: 0.000s
Flashing Boot Image
target didn't report max-download-size
sending 'boot_a' (34760 KB)...
FAILED (command write failed (Success))
finished. total time: 0.000s
target didn't report max-download-size
sending 'boot_b' (34760 KB)...
FAILED (command write failed (Success))
finished. total time: 0.000s
Flashing userdata Image
target didn't report max-download-size
sending 'userdata' (2560 KB)...
FAILED (command write failed (Success))
finished. total time: 0.000s
Erasing misc partitions
erasing 'misc'...
FAILED (command write failed (Success))
finished. total time: 0.000s
Formatting metadata partition
FAILED (command write failed (Success))
root@ubuntu:/opt/AM62_804/emmc_image#

What is the meaning of this line:

FAILED (command write failed (Success))  

Can you tell me if this is the "failed or success"? because those 2 words appeared in the same line.

And this is the console error logs while reboot.

Loading Android boot partition...
switch to partitions #0, OK
mmc0(part 0) is current device
misc partition number:0x4
ANDROID: Invalid CRC-32 (expected 807077e9, found 00000000),re-initializing A/B metadata.
ANDROID: Attempting slot a, tries remaining 7
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...
Reading DTB for am62x_skevm...
Error: Boot Image header is incorrect
cp - memory copy

Usage:
cp [.b, .w, .l, .q] source target count
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
Running Android...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Failed to boot Android...

Hello Rio,

- I can confirm the 08.04.00 SDK is ok to boot the E2 EVM.

- I do not think you can put the rootfs on an sd card. As far as I know only the bootloader partitions are supported. To be confirmed by Guillaume.

- The only change you need to do to the board to boot from the sdcard is setting the switches:

Boot mode DIP Switch:
SW1: 11000010 SW2: 01000000

As explained here : software-dl.ti.com/.../Overview_Flashing.html

Thus, if you put a valid bootloader (the release binaries for instance) on a bootable sdcard you should be able to have u-boot and be able to interrupt it. The next step shall be flashing the rest of the partitions to emmc.

Thank you,

Safae

Hello Rio,

I can not reproduce this error on my end : `FAILED (command write failed (Success)) `

But it is certainly a fail since the partitions are not flashed.

After investigation this may be a usb-cable/setup problem, This may help:

- Please change to a USB-C cable that supports file transfer.

- Try to change ADB/Fastboot versions:

I am using :

Android Debug Bridge version 1.0.41
Version 32.0.0-8006631

and

fastboot version 31.0.3-7562133

Thank you,

Safae

Hello Rio,

Could you provide the output of the following cmd (if you are able to interrupt u-boot) ?:

printenv

Thank you,

Safae