PROCESSOR-SDK-AM65X: EVM cannot boot with pre-built image

Hi Vishnu,

You need to use USB0. On my side, I am using /dev/ttyUSB0. I have Ubuntu 16.04 64-bit.

Make sure you are connecting your USB cable to UART J42 port. Also your SD card size should be 16GB or greater.

Check also If the create-sdcard.sh script run successful. Check below what I have on my side when I run this script:

################################################################################

	Copying files now... will take minutes

################################################################################

Copying boot partition



tispl.bin copied


tiboot3.bin copied


sysfw.itb copied


u-boot.img copied

uEnv.txt copied

Copying rootfs System partition
                                                                                                                                                       

Syncing...
 
Un-mount the partitions 
 
Remove created temp directories 
 
Operation Finished
 

And below is my boot log:

pbotev@lin-0306:~$ picocom -b 115200 /dev/ttyUSB0
picocom v1.7

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
escape is      : C-a
local echo is  : no
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : sz -vv
receive_cmd is : rz -vv
imap is        :
omap is        :
emap is        : crcrlf,delbs,

Terminal ready

U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:46:46 +0000)
SYSFW ABI: 2.6 (firmware rev 0x0013 '19.4.1-v2019.04a (Curious Crow)')
Trying to boot from MMC2
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.1(release):ti2019.01-rc2
NOTICE:  BL31: Built : 04:28:26, Jul  7 2019
I/TC:
I/TC: OP-TEE version: 3.2.0-583-g251f7c6-dev #1 Sun Jul  7 04:40:43 UTC 2019 aarch64
I/TC: Initialized

U-Boot SPL 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)
Trying to boot from MMC2


U-Boot 2019.01-g8b90adfb16 (Jul 07 2019 - 05:09:26 +0000)

Regards,
Pavel

Vishnu,

ttyUSB0 is used for the main console (u-boot, kernel, rootfs). This port correspond to AM65x MAIN_UART0 module (serial2).

ttyUSB1 is used for the very initial console, ROM Code and R5 SPL messages. This port correspond to AM65x MCU_UART0 (serial1). I have below message when use ttyUSB1:

�sdhci_reset: Reset 0x1 never completed.

ttyUSB2 is used for debug UART of the system firmware (SYSFW). This port correspond to AM65x WKUP_UART0 module (serial0). I have below message when use ttyUSB2:

System v-v2019.04a: am65x-gp- initialized.
                                          0x0

Please refer to below pointers for more details:

u-boot-2019.01/board/ti/am65x/README

UART:
-----
ROM supports booting from MCU_UART0 via X-Modem protocol. The entire UART-based boot process up to U-Boot (proper) prompt goes through different stages and uses different UART peripherals as follows:

  WHO         | Loading WHAT  |  HW Module      |  Protocol
----------+---------------+-------------+------------
Boot ROM  |  tiboot3.bin         |  MCU_UART0  |  X-Modem(*)
R5 SPL       |  sysfw.itb           |  MCU_UART0  |  Y-Modem(*)
R5 SPL       |  tispl.bin             |  MAIN_UART0 |  Y-Modem
A53 SPL     |  u-boot.img        |  MAIN_UART0 |  Y-Modem

(*) Note that in addition to X/Y-Modem related protocol timeouts the DMSC watchdog timeout of 3min (typ.) needs to be observed until System Firmware is fully loaded (from sysfw.itb) and started.

https://e2e.ti.com/support/processors/f/791/p/849357/3142038#3142038

https://e2e.ti.com/support/processors/f/791/t/800007

Regards,
Pavel