CCS/AM6548: Enable U-boot console logs for R5 Controller

Hi Sarfaraz,

1. R5 SPL jumps to A53 ATF-->OPTEE-->A53SPL-->A53 U-boot.That is the flow.

"U-Boot SPL 2019.01-ged486a2e91-dirty (Mar 26 2020 - 19:50:460530)
SYSFW ABI: 2.7 (firmware rev 0x0013 '19.9.0-v2019.09 (Trific Llama')
Trying to boot from MMC2
Starting ATF on ARM64 core..."

The above logs are from R5 SPL.


"NOTICE:  BL31: v2.2(release):ti2019.05-rc1
NOTICE:  BL31: Built : 03:39:18, Jan  5 2020
I/TC:
I/TC: OP-TEE version: ti2019.05-rc1-dev (gcc version 8.3.0 (G Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel.36))) #1 Sun Jan  5 03:38:30 UTC 2020 aarch64
I/TC: Initialized"

The above are ATF & OPTEE Logs

"U-Boot SPL 2019.01-ged486a2e91-dirty (Mar 26 2020 - 19:49:100530)
Detected: SER-PCIEUSBEVM rev E3
Trying to boot from MMC2
cannot find image node 'k3-am654-pcie-usb3.dtbo': -1"

The above is logs from A53 SPL.


"U-Boot 2019.01-ged486a2e91-dirty (Mar 26 2020 - 19:49:10 +30)

SoC:   AM654 PG 1.0
Model: Texas Instruments AM654 Base BoardBoard: AM6-COMPROCEVM rev E3
DRAM:  4 GiB
MMC:   sdhci@4f80000: 0, sdhci@04FA0000: 1
Loading Environment from MMC... OK
In:    serial
Out:   serial
Err:   serial
Detected: SER-PCIEUSBEVM rev E3
Net:   eth0: cpsw_nuss@046000000, eth1: pruss2_eth
Hit any key to stop autoboot:  0 "

Finally A53 u-boot Logs.

That is a sample for you. So we cannot really halt at R5 u-boot as there
is not u-boot for R5.

2) currently we do not support that on our SDK as the ROM brings up R5 and it's R5 that is then passing
on the control to A53.

As explained tiboot3-.bin is only containing SPL of R5 and not u-boot is present for R5 so no question of
R5 u-boot prompt.

Hope the above answers all your doubts.

Regards,
Keerthy