[PATCH v4 00/16] Introduce initial TI's J784S4 and AM69 support

Kumar, Udit u-kumar1 at ti.com
Fri Nov 17 05:02:45 CET 2023


On 11/17/2023 4:26 AM, Enric Balletbo i Serra wrote:
> Hi Maxime
>
>
> On Wed, Nov 15, 2023 at 2:54 PM Maxime Ripard <mripard at redhat.com> wrote:
>> Hi,
>>
>> On Sun, Oct 01, 2023 at 10:25:29PM +0530, Apurva Nandan wrote:
>>> This series will introduce basic support (SD and UART) support for Texas
>>> Instruments J784S4 EVM.
>>>
>>> The J784S4 SoC device tree patches are taken from kernel patch submissions
>>> and will be updated as they are accepted and merged to the kernel tree.
>>> All other patches are specific to SPL and u-boot and do not have
>>> dependency on other trees. Appreciate a review for acceptance to u-boot
>>> tree.
>>>
>>> Here are some of the salient features of the J784S4 automotive grade
>>> application processor:
>>>
>>> The J784S4 SoC belongs to the K3 Multicore SoC architecture
>>> platform, providing advanced system integration in automotive,
>>> ADAS and industrial applications requiring AI at the network edge.
>>> This SoC extends the K3 Jacinto 7 family of SoCs with focus on
>>> raising performance and integration while providing interfaces,
>>> memory architecture and compute performance for multi-sensor, high
>>> concurrency applications.
>>>
>>> Some highlights of this SoC are:
>>> * Up to 8 Cortex-A72s, four clusters of lockstep capable dual Cortex-R5F MCUs,
>>>    4 C7x floating point vector DSPs with Matrix Multiply Accelerator(MMA) for
>>>    deep learning and CNN.
>>> * 3D GPU: Automotive grade IMG BXS-4-64 MC1
>>> * Vision Processing Accelerator (VPAC) with image signal processor and Depth
>>>    and Motion Processing Accelerator (DMPAC)
>>> * Three CSI2.0 4L RX plus two CSI2.0 4L TX, two DSI Tx, one eDP/DP and one
>>>    DPI interface.
>>> * Integrated gigabit ethernet switch, up to 8 ports (TDA4VH), two ports
>>>    support 10Gb USXGMII; Two 4 lane PCIe-GEN3 controllers, USB3.0 Dual-role
>>>    device subsystems, Up to 20 MCANs, among other peripherals.
>>>
>>> See J784S4 Technical Reference Manual (SPRUJ52 - JUNE 2022)
>>> for further details: http://www.ti.com/lit/zip/spruj52
>>>
>>> In addtion, the J784S4 EVM board is designed for TI J784S4 SoC. It
>>> supports the following interfaces:
>>> * 32 GB DDR4 RAM
>>> * x2 Gigabit Ethernet interfaces capable of working in Switch and MAC mode
>>> * x1 Input Audio Jack, x1 Output Audio Jack
>>> * x1 USB2.0 Hub with two Type A host and x1 USB 3.1 Type-C Port
>>> * x2 4L PCIe connector
>>> * x1 UHS-1 capable micro-SD card slot
>>> * 512 Mbit OSPI flash, 1 Gbit Octal NAND flash, 512 Mbit QSPI flash,
>>>    UFS flash.
>>> * x6 UART through UART-USB bridge
>>> * XDS110 for onboard JTAG debug using USB
>>> * Temperature sensors, user push buttons and LEDs
>>> * 40-pin User Expansion Connector
>>> * x2 ENET Expansion Connector, x1 GESI expander, x2 Display connector
>>> * x1 15-pin CSI header
>>> * x6 MCAN instances
>> I've tested this series on top of 2024.01-rc2, and while it worked fine
>> before, the (external) MMC is now broken:
>>
>> U-Boot SPL 2024.01-rc2-00021-g8e3ced8fbad8 (Nov 15 2023 - 12:07:18 +0100)
>> SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.2--v09.01.02 (Kool Koala)')
>> SPL initial stack usage: 13416 bytes
>> Trying to boot from MMC2
>> Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
>> Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
>> Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
>> Loading Environment from nowhere... OK
>> Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
>> Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
>> Starting ATF on ARM64 core...
>>
>> NOTICE:  BL31: v2.9(release):v2.9.0
>> NOTICE:  BL31: Built : 12:07:09, Nov 15 2023
>> I/TC:
>> I/TC: OP-TEE version: 4.0.0 (gcc version 13.2.1 20230728 (Red Hat Cross 13.2.1-1) (GCC)) #1 Wed Nov 15 11:07:14 UTC 2023 aarch64
>> I/TC: WARNING: This OP-TEE configuration might be insecure!
>> I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
>> I/TC: Primary CPU initializing
>> I/TC: SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.2--v09.01.02 (Kool Koala)')
>> I/TC: HUK Initialized
>> I/TC: Activated SA2UL device
>> I/TC: Enabled firewalls for SA2UL TRNG device
>> I/TC: SA2UL TRNG initialized
>> I/TC: SA2UL Drivers initialized
>> I/TC: Primary CPU switching to normal world boot
>>
>> U-Boot SPL 2024.01-rc2-00021-g8e3ced8fbad8 (Nov 15 2023 - 12:07:30 +0100)
>> SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.2--v09.01.02 (Kool Koala)')
>> Trying to boot from MMC2
>> Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
>> Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
>>
>>
>> U-Boot 2024.01-rc2-00021-g8e3ced8fbad8 (Nov 15 2023 - 12:07:30 +0100)
>>
>> SoC:   J784S4 SR1.0 HS-FS
>> Model: Texas Instruments J784S4 EVM
> Maybe something changed but I'm surprised about it reporting an EVM
> board. I was expecting something like
>
> Model: Texas Instruments AM69 SK
> Board: AM69-SK rev E2
>
> Did you use the am69_sk_a72/r5  defconfigs?

Please apply AM69 config fragment

https://lore.kernel.org/all/20231001165545.494212-16-a-nandan@ti.com/

make ARCH=arm j784s4_evm_a72_defconfig am69_sk_a72.config
make ARCH=arm

OR

make ARCH=arm j784s4_evm_r5_defconfig am69_sk_r5.config
make ARCH=arm

>
>> DRAM:  32 GiB
>> Core:  90 devices, 31 uclasses, devicetree: separate
>> Flash: 0 Bytes
>> MMC:   mmc at 4f80000: 0, mmc at 4fb0000: 1
>> Loading Environment from nowhere... OK
>> In:    serial at 2880000
>> Out:   serial at 2880000
>> Err:   serial at 2880000
>> am65_cpsw_nuss ethernet at 46000000: K3 CPSW: nuss_ver: 0x6BA02102 cpsw_ver: 0x6BA82102 ale_ver: 0x00293904 Ports:1 mdio_freq:1000000
>> Net:   eth0: ethernet at 46000000port@1
>> Hit any key to stop autoboot:  0
>> => boot
>> i2c_write: error waiting for data ACK (status=0x116)
>> pca953x gpio at 22: Error reading output register
>> Card did not respond to voltage select! : -110
>> mmc_init: -95, time 114
>>
>> Maxime


More information about the U-Boot mailing list