Skip to content

Add Initial Support for TI AM62L EVM (TMDS62LEVM) #8622

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add Initial Support for TI AM62L EVM (TMDS62LEVM) #8622

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3603f81
Add Initial Support for TI AM62L EVM (TMDS62LEVM)
Grippy98 Sep 12, 2025
f467454
Merge branch 'armbian:main' into Add-AM62L-EVM
Grippy98 Sep 12, 2025
3d39b44
Clean up comments - SR1.1 supports OPTEE
Grippy98 Sep 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions config/boards/ti-tmds62l-evm.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,32 @@
# Texas Instruments AM62L dual core 2GB 2xGBE OSPI HDMI
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggesting to rename this file since other TI boards also don't have the TI prefix in the file name to keep consistency..

Copy link
Contributor Author

@Grippy98 Grippy98 Sep 13, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue with this board is all the others we've added before were SK (Starter Kits), this one is a different larger form factor so the actual name is TMDS62LEVM.

To group them better should we rename future boards to TI- for official boards? So we'd end up with ti-am62b-sk ti-am64-sk etc? Open to ideas.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Renaming a board after it has been added is problematic so we can or should only make decision for the future rather than the past. I've learned that when trying to rename rpi4b to simple rpi but that was declined.
Overall there are both boards with and without vendor prefix at this time. So IMHO we should consider existing boards when naming new ones. For now at least.


BOARD_NAME="TI-TMDSAM62L-EVM"
BOARDFAMILY="k3"
BOARD_MAINTAINER="jsuhaas22"
BOOTCONFIG="am62lx_evm_defconfig"
BOOTFS_TYPE="fat"
BOOT_FDT_FILE="ti/k3-am62l3-evm.dts"
DEFAULT_CONSOLE="serial"
KERNEL_TARGET="current,edge"
KERNEL_TEST_TARGET="current"
SERIALCON="ttyS2"
ATF_BOARD="am62l"
EXTRA_ATF_TARGETS="build/k3/am62l/release/bl1.bin:bl1.bin"
OPTEE_ARGS="CFG_TEE_CORE_LOG_LEVEL=1"
OPTEE_PLATFORM="k3-am62lx"
EXTRA_BOOT_ARGS="BL1=bl1.bin"
CC33XX_SUPPORT="yes"

# Use these branches until BeagleY-AI goes upstream
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/BeagleY-AI/AM62L TF-A

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the beagle comment but what's the
AM62L TF-A? bit

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The thing we are waiting on is TF-A upstream support for AM62L, that is why we use these different branches, so the comment should be:

# Use these branches until AM62L TF-A goes upstream

substituting BeagleY-AI for AM62L TF-A in the comment makes the change needed.

function post_family_config__tmds62l_evm_overrides() {
display_alert "$BOARD" "AM62L OPTEE and SDK Tag Override for $BOARD - $BRANCH" "info"
declare -g SPD_OPTEED="" #AM62L doesn't use OPTEE, and support for it hasn't been added in k3conf
declare -g CORESDK_TAG="tag:11.00.15"
declare -g ATFBRANCH="commit:a70f82d5a439cb9e21426908c7410c4f2a646364"

declare -g KERNELBRANCH="${CORESDK_TAG}"
declare -g TI_LINUX_FIRMWARE_BRANCH="${CORESDK_TAG}"
declare -g BOOTBRANCH="${CORESDK_TAG}"
}


1 change: 1 addition & 0 deletions config/kernel/linux-k3-current.config
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -800,6 +800,7 @@ CONFIG_RTC_DRV_TI_K3=m
CONFIG_DMADEVICES=y
CONFIG_BCM_SBA_RAID=m
CONFIG_TI_K3_UDMA=y
CONFIG_TI_K3_UDMA_AM62L=y
CONFIG_TI_K3_UDMA_GLUE_LAYER=y
CONFIG_DMABUF_HEAPS=y
CONFIG_DMABUF_HEAPS_SYSTEM=y
Expand Down
1 change: 1 addition & 0 deletions config/kernel/linux-k3-edge.config
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -773,6 +773,7 @@ CONFIG_DMADEVICES=y
CONFIG_BCM_SBA_RAID=m
CONFIG_DW_EDMA=m
CONFIG_TI_K3_UDMA=y
CONFIG_TI_K3_UDMA_AM62L=y
CONFIG_TI_K3_UDMA_GLUE_LAYER=y
CONFIG_DMABUF_HEAPS=y
CONFIG_DMABUF_HEAPS_SYSTEM=y
Expand Down
14 changes: 8 additions & 6 deletions config/sources/families/k3.conf
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,9 +61,9 @@ case "${BRANCH}" in
esac

ATF_PLAT="k3"
ATF_TARGET_MAP="PLAT=$ATF_PLAT TARGET_BOARD=$ATF_BOARD ${SPD_OPTEED} ${ATF_K3_USART_OFFSET} bl31;;build/$ATF_PLAT/$ATF_BOARD/release/bl31.bin:bl31.bin"
ATF_TARGET_MAP="PLAT=$ATF_PLAT TARGET_BOARD=$ATF_BOARD ${SPD_OPTEED} ${ATF_K3_USART_OFFSET} ;;build/$ATF_PLAT/$ATF_BOARD/release/bl31.bin:bl31.bin ${EXTRA_ATF_TARGETS}"

UBOOT_TARGET_MAP="BL31=bl31.bin TEE=${SRC}/cache/sources/optee-os/out/arm-plat-k3/core/tee-raw.bin BINMAN_INDIRS=${SRC}/cache/sources/ti-linux-firmware all;;tiboot3.bin ${SYSFW_FILE:+sysfw.itb} tispl.bin u-boot.img"
UBOOT_TARGET_MAP="BL31=bl31.bin ${EXTRA_BOOT_ARGS} TEE=${SRC}/cache/sources/optee-os/out/arm-plat-k3/core/tee-raw.bin BINMAN_INDIRS=${SRC}/cache/sources/ti-linux-firmware all;;tiboot3.bin ${SYSFW_FILE:+sysfw.itb} tispl.bin u-boot.img"

# To match what our current SDK produces
BOOT_FS_LABEL="boot"
Expand All @@ -75,7 +75,6 @@ function add_host_dependencies__k3_python3_dep() {
}

function compile_k3_bootgen() {
# Source code checkout
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why drop this comment?

(fetch_from_repo "https://github.com/TexasInstruments/ti-linux-firmware" "ti-linux-firmware" ${TI_LINUX_FIRMWARE_BRANCH})

pushd ${SRC}/cache/sources/u-boot-worktree/${BOOTDIR}/${BOOTBRANCH##*:} || exit
Expand All @@ -96,10 +95,13 @@ function compile_k3_optee() {
function pre_config_uboot_target__build_first_stage() {
# Compile first stage bootloader
compile_k3_optee
compile_k3_bootgen

cp ${SRC}/cache/sources/u-boot-worktree/${BOOTDIR}/${BOOTBRANCH##*:}/build-r5/${TIBOOT3_FILE} tiboot3.bin
cp ${SRC}/cache/sources/u-boot-worktree/${BOOTDIR}/${BOOTBRANCH##*:}/build-r5/${SYSFW_FILE} sysfw.itb || true
if [ ! -z ${TIBOOT3_BOOTCONFIG} ] ; then
compile_k3_bootgen

cp ${SRC}/cache/sources/u-boot-worktree/${BOOTDIR}/${BOOTBRANCH##*:}/build-r5/${TIBOOT3_FILE} tiboot3.bin
cp ${SRC}/cache/sources/u-boot-worktree/${BOOTDIR}/${BOOTBRANCH##*:}/build-r5/${SYSFW_FILE} sysfw.itb || true
fi
}

function post_uboot_custom_postprocess__update_uboot_names() {
Expand Down
Loading