Dev/BeagleBone/BeagleYAI - Revision history

Drizzt: /* Linux kernel Configuration options to be checked */

2025-03-25T16:34:14Z

Linux kernel Configuration options to be checked

← Older revision		Revision as of 18:34, 25 March 2025
Line 193:		Line 193:


			=== Bugs at runtime ===
			* wiz bus@f0000:phy@f000000: Unable to create SERDES platform device
			: at drivers/phy/ti/phy-j721e-wiz.c:1620 wiz_probe
			: wiz bus@f0000:phy@f000000: probe with driver wiz failed with error -12
			* wiz bus@f0000:phy@f010000: Unable to create SERDES platform device

			* alg: skcipher: cbc-aes-sa2ul encryption test failed (wrong result) on test vector 2, cfg="misaligned splits crossing pages, inplace"
			: alg: skcipher: ecb-aes-sa2ul encryption test failed (wrong result) on test vector 2, cfg="uneven misaligned splits, may sleep"
			: alg: self-tests for ecb(aes) using ecb-aes-sa2ul failed (rc=-22)
			: at crypto/testmgr.c:6026 alg_test
			* alg: aead: authenc(hmac(sha256),cbc(aes))-sa2ul encryption test failed (wrong result) on test vector 0, cfg="uneven misaligned splits, may sleep"
			: alg: self-tests for authenc(hmac(sha256),cbc(aes)) using authenc(hmac(sha256),cbc(aes))-sa2ul failed (rc=-22)
			: at crypto/testmgr.c:6026 alg_test

	=== File system ===		=== File system ===

Drizzt: /* Kernel config requiring user-space config at boot-time or runtime */

2025-03-25T15:56:34Z

Kernel config requiring user-space config at boot-time or runtime

← Older revision		Revision as of 17:56, 25 March 2025
Line 218:		Line 218:
	* TCP SYN-Cookies (https://cr.yp.to/syncookies.html) : (echo 1 > /proc/sys/net/ipv4/tcp_syncookies)		* TCP SYN-Cookies (https://cr.yp.to/syncookies.html) : (echo 1 > /proc/sys/net/ipv4/tcp_syncookies)
	* Power management		* Power management
			* Configure the "safesetid" (SECURITY_SAFESETID) whitelist

	== Liens officiels ==		== Liens officiels ==

Drizzt: /* Linux kernel Configuration options to be checked */

2025-03-25T15:56:27Z

Linux kernel Configuration options to be checked

@@ Line 142: / Line 142: @@
 == Linux kernel Configuration options to be checked ==
-=== ACPI/UEFI Support ===
+=== Global Kernel options ===
 Was enabled in Robert Nelson kernel.<br />
-Must check whether it is really usefull, as it should be concurent to the device-tree mechanism which is the one used here.
+Must check whether it is really usefull, as it should be concurent to the device-tree mechanism which is the one used here (See https://docs.kernel.org/arch/arm64/arm-acpi.html).
 * Boot option --> CONFIG_EFI : UEFI runtime support (Required for ACPI)
 * CONFIG_ACPI : ACPI (Advanced Configuration and Power Interface) Support
-=== Power management ===
+==== Power management ====
-* Disabled all suspend to RAN and Disk
+* Disabled all suspend to RAM and Disk
 * Check for subsystems powermanagement
-=== Memory ===
+==== Memory ====
 * Memory hotplug
 * HWPoison pages injector
 * Device memory (pmem, HMM, etc...) hotplug support
 == Kernel config requiring user-space config at boot-time or runtime ==

Drizzt: /* Kernel config requiring user-space config at boot-time or runtime */

2025-03-24T12:49:26Z

Kernel config requiring user-space config at boot-time or runtime

← Older revision		Revision as of 14:49, 24 March 2025
Line 159:		Line 159:

	== Kernel config requiring user-space config at boot-time or runtime ==		== Kernel config requiring user-space config at boot-time or runtime ==
	* CPU frequency		* CPU frequency and CPU hotplug (/sys/devices/system/cpu)
	* TCP SYN-Cookies (https://cr.yp.to/syncookies.html) : (echo 1 > /proc/sys/net/ipv4/tcp_syncookies)		* TCP SYN-Cookies (https://cr.yp.to/syncookies.html) : (echo 1 > /proc/sys/net/ipv4/tcp_syncookies)
	* Power management		* Power management


	== Liens officiels ==		== Liens officiels ==

Drizzt at 12:45, 24 March 2025

2025-03-24T12:45:31Z

Drizzt: /* Liens officiels */

2025-03-24T10:13:33Z

Liens officiels

@@ Line 140: / Line 140: @@
 * Device tree : arch/arm64/boot/dts/ti/k3-am67a-beagley-ai.dts
 * Kernel config file : https://git.beagleboard.org/beagleboard/linux/-/blob/d89bfdd19e7161ddba4ce4f5e34425ae6020a6db/arch/arm64/configs/bb.org_defconfig
 == Liens officiels ==

Drizzt: /* Description */

2025-03-20T01:48:49Z

Description

← Older revision		Revision as of 03:48, 20 March 2025
Line 20:		Line 20:
	* EEPROM (FT24C32A) on I2C0		* EEPROM (FT24C32A) on I2C0
	* microSD Card		* microSD Card

			=== Design, Shematics and Mechanical ===
			* https://openbeagle.org/beagley-ai/beagley-ai
			* https://docs.beagle.cc/boards/beagley/ai/03-design.html

	== The Boot process ==		== The Boot process ==

Drizzt: /* Processor */

2025-03-19T23:05:57Z

Processor

← Older revision		Revision as of 01:05, 20 March 2025
Line 10:		Line 10:
	The complete [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/processors.html list of processors] and [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/hosts.html cores]. Note that a physical processor can have multiple Host IDs (cores) depending on context and domain.		The complete [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/processors.html list of processors] and [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/hosts.html cores]. Note that a physical processor can have multiple Host IDs (cores) depending on context and domain.

	According to chat GPT (which is wrong), "The BeagleY-AI board uses the TDA4VM SoC in the HS-SE variant".		According to chat GPT (which is wrong), <s>"The BeagleY-AI board uses the TDA4VM SoC in the HS-SE variant"</s>.
	: The HS-SE (High Security - Single Edition) variant is focused on applications where data security and confidentiality are critical.		: The HS-SE (High Security - Single Edition) variant is focused on applications where data security and confidentiality are critical.
	: The HS-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.		: The HS-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.

	The BeagleY-AI board uses a TDA4AEN and not a TDA4VM, and it is a HS-FS variant.		The BeagleY-AI board uses an AM67A which is a TDA4AEN variant and not a TDA4VM, and it is a HS-FS variant.

	=== Memory ===		=== Memory ===

Drizzt: /* Processor */

2025-03-19T23:04:01Z

Processor

← Older revision		Revision as of 01:04, 20 March 2025
Line 2:		Line 2:
	* https://docs.beagle.cc/boards/beagley/ai/03-design.html		* https://docs.beagle.cc/boards/beagley/ai/03-design.html
	=== Processor ===		=== Processor ===
	* The board has a TI ~~Jacinto J722S (~~[https://www.ti.com/product/TDA4AEN~~-Q1 TDA4AEN]~~) ~~AM67A~~ SOC with		* The board has a TI [https://www.ti.com/product/AM67A AM67A] (from the Jacinto J722S TDA4AEN familly) SOC with
	: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)		: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)
	: - two C7x DSP cores		: - two C7x DSP cores
	: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)		: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
	: - two additional Arm Cortex-R5F cores (Device management and Run-time management).		: - two additional Arm Cortex-R5F cores (Device management and Run-time management).
	* BXS-4-64 GPU		* IMG BXS-4-64 GPU (OpenGL ES3.2 and Vulkan 1.2 API support)
	The complete [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/processors.html list of processors] and [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/hosts.html cores]. Note that a physical processor can have multiple Host IDs (cores) depending on context and domain.		The complete [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/processors.html list of processors] and [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/hosts.html cores]. Note that a physical processor can have multiple Host IDs (cores) depending on context and domain.

Line 14:		Line 14:
	: The HS-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.		: The HS-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.

	The BeagleY-AI board uses a TDA4AEN		The BeagleY-AI board uses a TDA4AEN and not a TDA4VM, and it is a HS-FS variant.

	=== Memory ===		=== Memory ===

Drizzt at 18:35, 19 March 2025

2025-03-19T18:35:27Z

← Older revision		Revision as of 20:35, 19 March 2025
Line 10:		Line 10:
	The complete [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/processors.html list of processors] and [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/hosts.html cores]. Note that a physical processor can have multiple Host IDs (cores) depending on context and domain.		The complete [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/processors.html list of processors] and [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/hosts.html cores]. Note that a physical processor can have multiple Host IDs (cores) depending on context and domain.

	According to chat GPT, "The BeagleY-AI board uses the TDA4VM SoC in the HS-SE ~~(High Security - Single Edition)~~ variant".		According to chat GPT (which is wrong), "The BeagleY-AI board uses the TDA4VM SoC in the HS-SE variant".
	: ~~This~~ HS-SE variant is focused on applications where data security and confidentiality are critical.		: The HS-SE (High Security - Single Edition) variant is focused on applications where data security and confidentiality are critical.
	: The HS-FS (High Security - Functional Safety) variant~~, on the other hand,~~ is more geared toward functional safety requirements.		: The HS-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.

			The BeagleY-AI board uses a TDA4AEN

	=== Memory ===		=== Memory ===
Line 35:		Line 37:
	* '''tifs.bin'''		* '''tifs.bin'''
	: TI Foundational Security (TIFS)		: TI Foundational Security (TIFS)
	: This firmware image is also called "SYSFW" and ~~may be~~ included inside '''tiboot3.bin'''.		: This firmware image is also called "SYSFW" and is included inside '''tiboot3.bin'''.
	: It is used for the "Secure Management Services" (SMS), to be run on the corresponding R5F MCU.		: It is used for the "Secure Management Services" (SMS), to be run on the corresponding R5F MCU.
	* '''tispl.bin'''		* '''tispl.bin'''
Line 64:		Line 66:
	== Sources ==		== Sources ==
	=== TI ===		=== TI ===
	* git://git.ti.com/processor-sdk/psdk_fw.git		* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
	* git://git.ti.com/ti-u-boot/ti-u-boot.git		* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
	* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git
	* git://git.ti.com/processor-firmware/ti-linux-firmware.git		* git://git.ti.com/processor-firmware/ti-linux-firmware.git
			: branch : ti-linux-firmware
			: Note that a very small subset is required from this 2.4Go repository (see below in "Build the images" section).

	Sources, branches and tags are referenced in the [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/Release_Specific_Release_Notes.html Linux Release Specific Release Notes]		Sources, branches and tags are referenced in the [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/Release_Specific_Release_Notes.html Linux Release Specific Release Notes]
Line 73:		Line 76:
	=== BeagleBone ===		=== BeagleBone ===
	* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"		* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
	: ~~git switch v2023~~.04-~~ti-09.02.00.009~~-BeagleY-AI		: tag : v2025.04-rc3-BeagleY-AI

	=== Others ===		=== Others ===
	* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git		* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
	* https://github.com/OP-TEE/optee_os/		: tag : lts-v2.12.1
			* https://github.com/OP-TEE/optee_os.git
			: tag : 4.5.0

	Also refer to the [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/Release_Specific_Release_Notes.html Linux Release Specific Release Notes] for branches and tags.		Also refer to the [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/Release_Specific_Release_Notes.html Linux Release Specific Release Notes] for branches and tags.

	== ~~Configs~~ ==		== Build the images ==
	=== U-Boot ===		The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
	make ARCH=~~arm~~ O=../~~Build~~/u-~~boot~~/r5 am67a_beagley_ai_r5_defconfig		* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
	make ARCH=arm O=../~~Build~~/u-boot~~/a53 am67a_beagley_ai_a53_defconfig~~		* https://openbeagle.org/beagleboard/repos-arm64/-/blob/main/bb-u-boot-beagley-ai/suite/bookworm/debian/rules

			=== Compiler ===
			The AM67A processor has R5 and A53 cores.
			: The R5 cores need a 32bits compiler : arm-linux-gnueabi
			CC32="arm-linux-gnueabi-"
			: The A53 ones need a 64bits compiler : aarch64-linux-gnu
			CC64="aarch64-linux-gnu-"

			=== U-Boot config ===
			You'll need "ARM Trusted Firmware" (see above for sources and git tag I used)
			TFA_BOARD=lite
			TFA_EXTRA_ARGS="SPD=opteed"
			make CROSS_COMPILE=${CC64} ARCH=aarch64 PLAT=k3 ${TFA_EXTRA_ARGS} TARGET_BOARD=${TFA_BOARD} bl31
			Result is "build/k3/${TFA_BOARD}/release/bl31.bin"

			You'll also need a "Trusted Execution Environnment" (see above for sources and git tag I used)
			OPTEE_PLATFORM=k3-j722s
			OPTEE_EXTRA_ARGS="CFG_WITH_SOFTWARE_PRNG=y CFG_ARM64_core=y"
			make -j 12 CROSS_COMPILE=${CC32} CROSS_COMPILE64=${CC64} ${OPTEE_EXTRA_ARGS} PLATFORM=${OPTEE_PLATFORM}
			Result is "core/tee-pager_v2.bin" which is in the output dir (either the one specified with "O=" option or under "out/.../").

			And a last one : some ti firmwares found in TI's Linux firmware repository (see above for sources and git tag I used).
			If you don't want to keep the 2.4Go of firmwares, keep at most these ones :
			: ti-linux-firmware/ti-dm/j722s/*
			: ti-linux-firmware/ti-ipc/j722s/*
			: ti-linux-firmware/ti-sysfw/ti-fs-firmware-j722s-hs-*
			: ti-linux-firmware/ti-sysfw/cert.bin
			And set this variable according to where you put them :
			LNX_FW_PATH="..../ti-linux-firmware/"

			And at last, the U-Boot part (remember that you will need two uboot images, once again, see above for the sources and tag I used) :
			* One for the R5 core :
			make ARCH=arm am67a_beagley_ai_r5_defconfig
			make ARCH=arm -j 12 CROSS_COMPILE=${CC32} BINMAN_INDIRS=${LNX_FW_PATH}
			: this one provides "tiboot3-j722s-hs-fs-evm.bin" which will be "tiboot3.bin"
			* And one for the A53 cores :
			: Set bl31 and bl32 variables to the results of ARM Trusted firmware (bl31) and Trusted Execution Environment (bl32) compilation
			bl31="...../build/k3/${TFA_BOARD}/release/bl31.bin"
			bl32="...../core/tee-pager_v2.bin"
			make ARCH=arm am67a_beagley_ai_a53_defconfig
			make ARCH=arm -j 12 CROSS_COMPILE=${CC64} BINMAN_INDIRS=${LNX_FW_PATH} BL31=${bl31} TEE=${bl32}
			: this one provides both "tispl.bin" and "u-boot.img".

	=== Linux ===		=== Linux ===

← Older revision		Revision as of 14:45, 24 March 2025
Line 2:		Line 2:
	* https://docs.beagle.cc/boards/beagley/ai/03-design.html		* https://docs.beagle.cc/boards/beagley/ai/03-design.html
	=== Processor ===		=== Processor ===
	* The board has a TI [https://www.ti.com/product/AM67A AM67A] (from the Jacinto J722S TDA4AEN familly) SOC with		* The board has a TI [https://www.ti.com/product/AM67A AM67A] (from the Jacinto J722S TDA4AEN familly) SOC, HS-FS variant, with
	: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)		: - four Arm Cortex-A53 cores (main cores, 1.4Ghz, 64bits aarch64 Armv8.x-A, VFPv4) (Still haven't found which is the .x in Armv8.x)
	: - two C7x DSP cores		: - two C7x DSP cores
	: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)		: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz, Armv7-R, VFPv3)
	: - two additional Arm Cortex-R5F cores (Device management and Run-time management).		: - two additional Arm Cortex-R5F cores (Device management and Run-time management).
	* IMG BXS-4-64 GPU (OpenGL ES3.2 and Vulkan 1.2 API support)		* IMG BXS-4-64 GPU (OpenGL ES3.2 and Vulkan 1.2 API support)
	The complete [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/processors.html list of processors] and [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/hosts.html cores]. Note that a physical processor can have multiple Host IDs (cores) depending on context and domain.		The complete [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/processors.html list of processors] and [https://software-dl.ti.com/tisci/esd/latest/5_soc_doc/j722s/hosts.html cores]. Note that a physical processor can have multiple Host IDs (cores) depending on context and domain.

	According to chat GPT (which is wrong), <s>"The BeagleY-AI board uses the TDA4VM SoC in the HS-SE variant"</s>.		Note : According to chat GPT (which is wrong), <s>"The BeagleY-AI board uses the TDA4VM SoC in the HS-SE variant"</s>.
	: The HS-SE (High Security - Single Edition) variant is focused on applications where data security and confidentiality are critical.		: The HS-SE (High Security - Single Edition) variant is focused on applications where data security and confidentiality are critical.
	: The HS-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.		: The HS-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.
Line 142:		Line 142:

	== Linux kernel Configuration options to be checked ==		== Linux kernel Configuration options to be checked ==
	== ACPI/UEFI Support ==		=== ACPI/UEFI Support ===
	Was enabled in Robert Nelson kernel.<br />		Was enabled in Robert Nelson kernel.<br />
	Must check whether it is really usefull, as it should be concurent to the device-tree mechanism which is the one used here.		Must check whether it is really usefull, as it should be concurent to the device-tree mechanism which is the one used here.
Line 148:		Line 148:
	* CONFIG_ACPI : ACPI (Advanced Configuration and Power Interface) Support		* CONFIG_ACPI : ACPI (Advanced Configuration and Power Interface) Support

	== Power management ==		=== Power management ===
	* Disabled all suspend to RAN and Disk		* Disabled all suspend to RAN and Disk
	* Check for subsystems powermanagement		* Check for subsystems powermanagement