Embeded Linux (and more) Wiki by Nathael - User contributions [en]

Dev/OPi/OPiZero2

2025-10-06T21:58:48Z

Drizzt: /* Description */

{{DISPLAYTITLE:Orange Pi Zero 2}}

== Description ==
Official website : [http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-2.html orangepi.org/Orange Pi Zero2/] ([[Dev/OPi/OpiZero2/Backup_presentation|Backup]]) 

The OrangePi Zero 2 board is an Open-source Single Board Computer (SBC) of 53x60mm created and sold by Xunlong.

Sunxi Wiki page : [https://linux-sunxi.org/Xunlong_Orange_Pi_Zero2 Orange Pi Zero2]

== Base system ==
* [[Dev/OPi/OPiZero2/From_Scratch|Create initial system from scratch (sources)]]: all the steps, using u-boot and Linux kernel sources.
* [[Dev/Embedded/Rootfs|Rootfs guide]] to create either a minimal system using Busybox or a full Devuan GNU/Linux system.
* The "SD card creation" section from the [[Dev/OPi/OPiZero2/From_Scratch|"from scratch" page]] : also provides information to use u-boot, kernel, and Devuan root filesystem I built. 

== Connection and startup ==
=== USB-UART serial console connection ===
[[File:OPi_Zero_2_UART.jpg|150px|thumbnail|UART debug port]]

On the J3 connector (3 pins male 2.54mm, right behind the USB port, pin 1 on the 2x26pins connector side) :
: pin 1 - GND
: pin 2 - UART RX
: pin 3 : UART TX

=== SD card boot ===
The OrangePi Zero 2 board boots from the SD card which has to be prepared following specific steps. Follow the "SD card creation" section from the [[Dev/OPi/OPiZero2/From_Scratch|"from scratch" page]]

== Extension ports ==
The OrangePi Zero 2 board has two extension ports using common 2.54mm (0.1inch) pitch:
* con4 : 2x13
* con5 : 1x13

[[File:Orange_Pi_Zero_2_Expansion_Header.jpg|300px|thumbnail|Orange Pi Zero Plus Expansion Header]]

{| class="wikitable" style="width:550px;"
! colspan=4 | con4 : 2x13 Header
|-
| 1 || ''3.3V''
| 2 || ''5V''
|-
| 3 || TWI0_SDA / PA12 / GPIO12
| 4 || ''5V''
|-
| 5 || TWI0_SCK / PA11 / GPIO11
| 6 || ''GND''
|-
| 7 || PWM1 / PA06 / GPIO6
| 8 || UART1_TX / PG06 / GPIO198
|-
| 9 || ''GND''
| 10 || UART1_RX / PG07 / GPIO199
|-
| 11 || UART2_RX / PA01 / GPIO1
| 12 || SIM_CLK/PA_EINT7 / PA07 / GPIO7
|-
| 13 || UART2_TX / PA00 / GPIO0
| 14 || ''GND''
|-
| 15 || UART2_CTS / PA03 / GPIO3
| 16 || TWI1-SDA / PA19 / GPIO19
|-
| 17 || ''3.3V''
| 18 || TWI1-SCK / PA18 / GPIO18
|-
| 19 || SPI1_MOSI / PA15 / GPIO15
| 20 || ''GND''
|-
| 21 || SPI1_MISO / PA16 / GPIO16
| 22 || UART2_RTS / PA02 / GPIO2
|-
| 23 || SPI1_CLK / PA14 / GPIO14
| 24 || SPI1_CS / PA13 / GPIO13
|-
| 25 || ''GND''
| 26 || SIM_DET/PA_EINT10 / PA10 / GPIO10
|}

{| class="wikitable" style="width:300px;"
! colspan=2 | con5 1x13 Header
|-
| 1 || ''5V''
|-
| 2 || ''GND''
|-
| 3 || USB-DM2
|-
| 4 || USB-DP2
|-
| 5 || USB-DM3
|-
| 6 || USB-DP3
|-
| 7 || LINEOUTR
|-
| 8 || LINEOUTL
|-
| 9 || TV-OUT
|-
| 10 || MIC-BIAS
|-
| 11 || MIC1P
|-
| 12 || MIC1N
|-
| 13 || CIR-RX
|}

Dev/Embedded/Rootfs/BusyBox/Example2

2025-10-06T21:40:45Z

Drizzt:

{{DISPLAYTITLE:BusyBox example 2 : Toward a more complex system}}
__TOC__
If you want to use BusyBox as the heart of an almost complete but light system, with multi-user, many services (possibly including SSH for remote access) you will need some more stuff than the pretty small configuration from the previous example.

This example explains how to create a more complex Linux based system using BusyBox as a base for the userland part of the system.

'''Note :''' 
'''THIS IS CURENTLY *VERY* INCOMPLETE.''' 
I simply created the "second example" page in order to "store" the bits which were going too far for the first "simple example".

== Complex system configuration ==
''' FIXME''' : Add link to example complex config

''' TO BE COMPLETED '''

Notes and warnings :
* Keep in mind that some tools may depend on specific kernel features (and includes) and that you may need to install your own kernel hearders and reference them instead of those comming with the libc. This is the case for the "tc" network applet which is included in the "defconfig".
* Adding headers or additionnal external libraries is done in the "Settings" part of the configuration, under "Additional LDFLAGS" and "Additional LDLIBS".
* As of 2025-01-03 selinux has deprecated "security_context_t" and "matchpathcon()" (at least) and you'll need to update the selinux related code if you need it.

== Directories ==
You will not need a full set of directories from the [https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS] but this can be a good place to get information if you do not know what you need. 
* The default busybox installation process has created four "*bin" directories for you, which is a good starting point (though you can merge them to get two if you want to follow the usermerge way, or even go further and get a single one bin directory). : /bin - /sbin - /usr/bin - /usr/sbin
* Then you will usually want somewhere to mount proc, sysfs ans devtmpfs : /proc - /sys - /dev
* You should also stick to the standard and place your text configuration under /etc
* Then you will need a place for your libraries. This can be a single place, or many, it's up to you (it's actually a real mess on some distributions, with multiarch support, 32 and 64 bits support, usrmerge, and maybe other funny stuff getting in the way). Maybe you should consider keeping it as simple as possible (refer to the next section to make your choices about this part). On a Devuan or Debian distribution you usually get those three at least : /lib - /usr/lib - /usr/lib/*arch-triplet* - ...
* A place to put "shared ressources" (architecture-independent data, but you're building an embedded system, so this may not have much sense put this way, simply consider it as a place for data used by the tools you'll need) : /usr/share
* A place for "variable files". As stated on the FHS page : "files whose content is expected to continually change during normal operation of the system, such as logs and spool files". These are files which you want to keep accross reboots : /var/log - /var/spool - ...
* A place for "run-time" files, which you do not want to keep accross reboots : /run
* A place for temporary files. Could be either one of the following : /tmp - /run/tmp
* A user home directory (or many if you're not building a single user, single task system) : /root - /home/....
* Somewhere you can mount removable stuff ? : /mnt
* If you need them, a place for modules and firmwares : /lib/modules - /lib/firmware
* And last but not least, some place specific for your application if you do not want it merged to the base system. Can be any or all of these : /opt - /srv - /usr/local ...

Of course, this may seem to be a lot, and it can be reduced to something simpler, depending on your needs ! 

And another with many more directories (see below for the "triplet" you'll need) :
triplet=
mkdir -p dev etc mnt proc root run sys tmp usr/{lib/{${triplet},firmware,modules},share} var/{cache,lib,log,spool}
ln -s usr/lib lib
ln -s run/tmp tmp
ln -s ../run/tmp var/tmp

As some in the second example, many can also be links to other ones ... once again it's up to you and your needs !

== Libraries ==
If you chose to use shared libraries (shared object files) when you compiled your binaries then you need to include them in your final system image.

This step is not very difficult in itself, but not as simple as busybox compilation and installation.

=== First, the answer about the "triplet" ===
I mentioned this "triplet" twice in the above section.

An inclomplete way to answer is that it is composed of three fields which identify the target for which you're building your system, though it is somehow much more complicated (it can be only two fields, or four), and there is not "one" answer. It is more of a convention which is not shared by all of the interested parties. You can get some information on [https://wiki.osdev.org/Target_Triplet osdev.org Wiki], on [https://wiki.debian.org/Multiarch/Tuples debian.org Wiki], or in [https://www.gnu.org/software/autoconf/manual/autoconf-2.65/html_node/System-Type.html#System-Type GNU autoconf manual] ([https://www.gnu.org/software/autoconf/manual/autoconf-2.65/html_node/Specifying-Target-Triplets.html also here]).

Most of the time it looks like '''"arch"-"os"-"abi"''', though the names are not these ones. 
It's usually what "-dumpmachine" or "-print-multiarch" option to the gcc from your toolchain will print, which is also the cross-compilation toolchain prefix. 

As I'm using Devuan/Debian's cross-toolchains I stick to the convention adopted by the Debian project.

=== Which are the required libraries ? ===
In order to know which libraries are required on your system you get a few option.
* Makefiles and build process output
* Use ldd
* Use "readelf -d"

The first option is some kind of theoretical approach. Have a look at the makefiles or the build output for the libraries used for the linking stage of the build process, for all your binaries. This could be a pretty hard task, and is not my choice.

The second option, which I'm using most of the time (because I never remember the last one, which is the best one) is to use ldd on a target sharing the architecture (the triplet mentionned above) of your target system. 
ldd is a command (script) which lists what shared libraries are used by given dynamically-linked executables (read comments in /bin/ldd for more information). 
The main limitation is that you need to have a target running a full-blown distribution at hand. 
On the other hand, it lists more than the libraries linked, and tells you whether it found them on the system, and which file is used (save for "linux-vdso.so.1" which is not a file but a "virtual dynamic shared object" provided by the Linux kernel : look at the [https://man7.org/linux/man-pages/man7/vdso.7.html vdso manpage] : man 7 vdso). 
Of course, you'll need to run this for all your binaries, but that's something you can perform with a succession of commands and filters (or a script), and get a list with single entries for the required libraries. 
Here is an example output of ldd :
$ ldd /bin/bash
linux-vdso.so.1 (0x00007fbb70314000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007fbb70170000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fbb6ff7a000)
/lib64/ld-linux-x86-64.so.2 (0x00007fbb70316000)

The last option, directly available on your host, is to use the readelf tool from the binutils part of your cross-toolchain. 
The main limitation for this third option is that it does not tell you about the dynamic linker/loader (ld-linux-*.so) 
Once again, you'll need to run it on all your binaries. 
Here is the interesting part of the output of "readelf -d" for the bash binary on my host system :
$ readelf -d /bin/bash
Tag Type Name/Value
0x0000000000000001 (NEEDED) Shared library: [libtinfo.so.6]
0x0000000000000001 (NEEDED) Shared library: [libc.so.6]

=== The minimal list ===
I cannot give you a full list, but if you chose to have dynamically linked binaries (which is usually a good idea if your system has more than one or two binaries) you will always need these two :
* The dynamic linker/loader (name depending on the target architecture/triplet) : ld-linux-*.so.*
* the libc

=== Where do they go ? ===
Now that you know which libraries you need, you'll need to figure which files to put in which directory for each library.

Unless you specified an absolute or relative pathname during the linking stage of the compilation of your binaries, there is no "fixed" location for each library file, save maybe the dynamic linker/loader (ld-linux-*.so.*), which usually goes under "/lib", and the dynamic linker will end up looking for libraries in some "default" path which usually includes "/lib".

So the easy way is to create a single "/lib" directory especially if you chose to desactivate the use of "/usr" in busybox configuration.

If you want to build a base system closer to what you find in common distributions and use the "/usr", here are some information you should be aware of :
: The dynamic linker will end up looking for libraries in some "default" path, which varies depending on it's configuration and the architecture (usually "/lib" and then "/usr/lib", or '/lib64" and then "/usr/lib64"). 
Even if the linker/loader will first look at the "cache" file ("/etc/ld.so.cache") which is generated using "ldconfig" it is not of much use in our case because this "ldconfig" is a binary which knows only of one architecture, so (as for ldd) this command must be run on a target of the same architecture with a complete running system.

(but is under "/usr/lib/**triplet**/" in a Debian, whith a link from "/usr/lib64/")
''' UNDER REDACTION '''

libc.so

== bootup script ==
* inittab
* rc script(s)
''' TO BE COMPLETED '''

== configuration files ==
''' TO BE COMPLETED '''

== application binaries ==
''' TO BE COMPLETED '''

== application related files ==
''' TO BE COMPLETED '''

== Possible compilation problems ==
=== Networking ===
I ran into this problem when trying to build a FULL busybox :
* https://lists.busybox.net/pipermail/busybox/2024-July/090821.html
: Obviously not only Ubuntu related as I'm not using Ubuntu but Devuan, though the compiler and libs may be shared as both share Debian as origin.
: Disabling tc applet allows for compilation, but does not solve the problem if you need tc applet (Show / manipulate traffic control settings).

Courses/LinuxAdmin

2025-10-05T11:44:05Z

Drizzt: Created page with "*Introduction *Licences *Distributions"

*[[Courses/LinuxAdmin/Intro|Introduction]]
*[[Courses/LinuxAdmin/Licences|Licences]]
*[[Courses/LinuxAdmin/Distributions|Distributions]]

Courses

2025-10-05T11:42:52Z

Drizzt:

*[[Courses/LinuxAdmin|Linux Administration]]
*[[Courses/C|C language]]
*[[Courses/Electronics|Electronics]]

Courses/Distributions/Intro

2025-10-05T11:40:55Z

Drizzt: Drizzt moved page Courses/Distributions/Intro to Courses/LinuxAdmin/Distributions

#REDIRECT [[Courses/LinuxAdmin/Distributions]]

Courses/LinuxAdmin/Distributions

2025-10-05T11:40:55Z

Drizzt: Drizzt moved page Courses/Distributions/Intro to Courses/LinuxAdmin/Distributions

When people start considering "Linux" as a solution (whatever the problem), one of the first question is "Where do I start", which quickly leads to "Which distribution should I use", even without understanding (and often wondering) what a "distribution" is.

Distributions (Ubuntu, Kali, Debian, RedHat, ... ([https://en.wikipedia.org/wiki/List_of_Linux_distributions find a certainly incomplete list on Wikipedia])) are only different ways to distribute the same softwares.

What is called a "distribution" is in fact a project shared with you by a (small or big) group of people to ease the installation, configuration, maintainance and upgrade of a (GNU/)Linux system.

The main differences between them is the packaging tool used to build and distribute the packages and the distribution (apt, emerge, pacman, yum, ...), and the configuration the package maintainers choose for each package.
Aside from this, which represents a great work, but is nothing compared to the amount of of packages available, and is only a "side tool", not used by the "runtime" part of the system, the sources are the same. The shell bash is from the same source code (though the distributions sometimes add patches to some softwares), and will run the same on Debian, Kali, RedHat and so on.
The kernel is also the same one (though the version and configuration will likely differ), with a libc on top of it and as a base for the whole userspace, and hundreds of userspace tools which you'll find on every distribution, which are the same, and work in exactly the same way.
And more important, most of the time the kernel from one distribution can be used on any other one (in fact, it should ALWAYS be the case). This is one of the core principles of the UNIX philosophy and POSIX requirements.
I hope this helps you understanding the GNU/Linux ecosystem a little bit more.
If you haven't found a solution since your message, I can provide some support (I'm working as freelance).

Courses

2025-10-05T11:40:19Z

Drizzt:

*[[Courses/LinuxAdmin|Linux Administration]]
:[[Courses/LinuxAdmin/Distributions|Distributions]]

Courses

2025-10-05T11:40:03Z

Drizzt: Created page with "Linux Administration Distributions"

[[Courses/LinuxAdmin|Linux Administration]]
[[Courses/LinuxAdmin/Distributions|Distributions]]

Courses/LinuxAdmin/Distributions

2025-10-05T11:35:16Z

Drizzt: Created page with "When people start considering "Linux" as a solution (whatever the problem), one of the first question is "Where do I start", which quickly leads to "Which distribution should I use", even without understanding (and often wondering) what a "distribution" is. Distributions (Ubuntu, Kali, Debian, RedHat, ... ([https://en.wikipedia.org/wiki/List_of_Linux_distributions find a certainly incomplete list on Wikipedia])) are only different ways to distribute the same softwares...."

Dev/BeagleBone

2025-09-19T16:17:28Z

Drizzt: /* Boards */

{{DISPLAYTITLE:BeagleBone}}

== Common description ==
BeagleBone Boards are small Open Source SBC's (Single Board Computer) initially designed by [https://beagleboard.org/ BeagleBoard.org] and initially manufactured by CircuitCo, though others started to produce them and even created derivatives from the best-seller BeagleBone Black.

Most information can be found by looking at [https://beagleboard.org/bone BeagleBoard.org] official website, and many more all over the web.

I've been using the BeagleBone Black while teaching embedded Linux at ESCPE Lyon since the very first days (managed to get them a few days before the official release in April 2013), and used them for many professional projects too. 
The performances were very good when the board was released, and I still prefer it over some fake open-source competitors (hint : they started the "fruit-based" names*), which are no more available, while the BeagleBone Black is still sold for the same price (December 2024, 11 years later).

'* : raspberry Pi boards are not open-source

== Boards ==
=== [[Dev/BeagleBone/BBB|BeagleBone Black]] ===
=== [[Dev/BeagleBone/Green|BeagleBone Green]] ===
=== [[Dev/BeagleBone/PocketBeagle|Pocket Beagle]] ===
=== [[Dev/BeagleBone/PocketBeagle2|Pocket Beagle 2]] ===
=== [[Dev/BeagleBone/BeagleYAI|BeagleY-AI]] ===

Dev/BeagleBone/PocketBeagle

2025-09-19T16:14:42Z

Drizzt: Created page with "{{DISPLAYTITLE: Pocket Beagle}} == Description == Official website : [https://www.beagleboard.org/boards/pocketbeagle-original PocketBeagle] on [https://beagleboard.org/ beagleboard.org] [http://elinux.org/Beagleboard:BeagleBoneBlack Official BeagleBone Black Wiki] maintained and supported by BeagleBoard.org. The PocketBeagle is a Single Board Computer (SBC) which uses the Texas instrument AM3358 processor and has 512MB of RAM, one USB otg (micro USB), one µSD..."

{{DISPLAYTITLE: Pocket Beagle}}

== Description ==
Official website : [https://www.beagleboard.org/boards/pocketbeagle-original PocketBeagle] on [https://beagleboard.org/ beagleboard.org] 
[http://elinux.org/Beagleboard:BeagleBoneBlack Official BeagleBone Black Wiki] maintained and supported by BeagleBoard.org.

The PocketBeagle is a Single Board Computer (SBC) which uses the Texas instrument AM3358 processor and has 512MB of RAM, one USB otg (micro USB), one µSD card slot, and two 2x18 pins (72 pins total) expansion ports which allows for a great variety of "Capes", like this [https://www.beagleboard.org/boards/gamepup PocketBeagle GamePup Cape].

The PocketBeagle is the little sister of the BeagleBone Black board.

in order to achieve the very small footprint, it uses a "SiP" (System in Package) from Octavo Systems : [https://octavosystems.com/octavo_products/osd335x/ OSD335x]

== Base system ==
* TODO !
* Note that the steps found on the [[Dev/BeagleBone/BBB/From_Scratch|BeagleBone Black "from scratch"]] pages should be a very good starting point, as the processor is the same.
* [[Dev/Embedded/Rootfs|Rootfs guide]] to create either a minimal system using Busybox or a full Devuan GNU/Linux system.
* The "SD card creation" section from the [[Dev/BeagleBone/BBB/From_Scratch|"from scratch" page]] also provides information to use the u-boot, kernel image, and Devuan root filesystem I built for the BeagleBone Black.

== Connection and startup ==
==== USB-UART serial console connection ====
* TODO !

==== SD card boot ====
* TODO !

== Extension ports ==
The PocketBeagle board has two extension ports using common 2.54mm (0.1inch) pitch:
* P1 : 2x18
* P2 : 2x18

{| class="wikitable" style="width:550px;"
! colspan=4 | P1 : 2x18 Header
|-
| 1 || ''''
| 2 || ''''
|-
| 3 ||
| 4 || ''''
|}

{| class="wikitable" style="width:550px;"
! colspan=4 | P2 : 2x18 Header
|-
| 1 || ''''
| 2 || ''''
|-
| 3 ||
| 4 || ''''
|}

== External links ==
* [https://www.beagleboard.org/boards/pocketbeagle-original PocketBeagle] on beagleboard.org
* [https://docs.beagleboard.org/boards/pocketbeagle/ch06.html Hardware design] and [https://git.beagleboard.org/beagleboard/pocketbeagle Design files]
* [https://octavosystems.com/octavo_products/osd335x/ OSD335x]

Dev/Embedded/FromScratch/UBoot

2025-07-27T17:12:34Z

Drizzt: /* Configure */

== U-Boot ==
=== Introduction ===
For most of the boards I have I'm using U-Boot as bootloader (some may be supported by other bootloaders, but I usually stick to the bootloader proposed by the board manufacturer).

"Das U-Boot" (https://www.denx.de/project/u-boot/) is one of the most used bootloader for embedded systems running Linux.
It supports a wide range of hardware and many boot mechanisms (serial, ethernet, flash, USB, SD card, emmc, ...) to load the necessary images required to boot the system. 
Details will be found in u-boot documentation.

=== Get the sources ===
Most of the time the official u-boot sources (from denx.de) are fine :
git clone git://git.denx.de/u-boot.git

If your board is not supported by the official u-boot sources, refer to your board documentation to get the bootloader sources.
Depending on your hardware, you may need to use a specific release of u-boot. Use git checkout to get the right one.

=== Configure ===
If your hardware is supported by u-boot you should find a "<board_name>_defconfig" file in the "configs" directory at the root of the git tree. 
If you do not know which one to use, you can refer to your board's documentation, or to u-boot documentation under "doc/board". 
Then the configuration is made in two steps :
board_name=
compiler_prefix=
make CROSS_COMPILE=${compiler_prefix} ${board_name}_defconfig
make CROSS_COMPILE=${compiler_prefix} menuconfig

If the default configuration fits your needs the second step (menuconfig) is not required.

=== Compile ===
Once you're done with the configuration step, the compilation is made by running make from the source tree root with the "CROSS_COMPILE" variable set.

Note that for boards which require an ARM trusted firmware image it may be required to export a variable with it's path first :
platform=
target=
path_to_atf=
export BL31=${path_to_atf}/build/${platform}/debug/${target}.bin
Refer to the "ARM trusted firmware" section bellow to build this firmware image first.

And compile :
compiler_prefix=
make CROSS_COMPILE=${compiler_prefix}

The result is at the root of the source tree. The image name to use depends on your target.

How to use this image is highly dependent on your target board and SoC, so refer to the board specific information for this step !

=== U-Boot environment ===
Part of u-boot configuration includes a default environment, which holds various variables used to help loading and starting the Linux kernel. 
Some of these variables have predefined meaning and other are user defined to help configure u-boot behavior. 
Depending on your hardware, the default variables can be overridden from the content of a saved environment from a flash location, or from the content of a script. This helps save board specific boot configuration and select boot mechanism used to load and start the required binaries. 
Whatever the mechanism used to get them, it usually boils down to loading the Linux kernel image, an optional initramfs or initrd image (which may also be included in the Linux kernel image or not required at all), and a device tree blob (dtb) if it is not included within the Linux kernel image. 
The bootloader also has to provide a command line to the Linux kernel, unless the Linux kernel image has a default command line compiled in. This is done by setting the "bootargs" environment variable. 
The effective boot is done then by running one of the boot commands supported by the u-boot image. 
Refer to each board description for a list of board specific configurations and for example boot scripts when supported.

== ARM trusted firmware (or Trusted Firmware-A) ==
If you are building U-Boot for an arm64/aarch64 device, you need to include the "ARM trusted firmware" (ATF) or "Trusted Firmware-A" (TF-A).

=== Get the sources ===
You can get this either from the trustedfirmware.org git repository :
git clone https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
These sources are also available from the arm-trusted-firmware git repository on github : https://github.com/ARM-software/arm-trusted-firmware.git 
Note that both repository seems to have the same code, only some of the tags appear to be different.

=== Configure ===
There's no configuration stage for this part, though you'll need to know the "platform" name and the "target" name you want to build.

You can run "'''make help'''" to get the list of supported platform and the target names.

You can refer to the documentation for your SoC (processor) under "docs/plat" directory.

I'll indicate the right plaform and target on the pages dedicated to each board when I get my hands on them :)

=== Compile ===
To build this firmware part get to the root of the git tree and run:
platform=
target=
compiler_prefix=
make CROSS_COMPILE=${compiler_prefix} PLAT=${platform} DEBUG=1 ${target}

Set "platform" and "target" according to your needs as identified in the "Configure" section above

== Flash and Use ==
Once your bootloader image is ready, with the eventual firmware loader if any is required, you must then put it somewhere where your processor will be able to read it.

There are many options, all depending on your hardware (the processor of course, but also the board you are using, which may have only some of the interfaces available, or specific "bootconfig" settings hardwired). 
Here is a short list of the common interfaces which may be available :
* Serial (one of the UARTs)
* Onboard Flash (NAND, NOR or SPI Flash chips)
* EMMC and/or SD (or µSD) Card
* Ethernet (usually using BOOTP + TFTP)
* USB flash drive (or USB connected Hard drive or SSD)
* Sata drive
* ....

Some options will require specific tools or services installed on your host, while others will require special configuration of a storage device (µSD card, USB key, ...).

I'll provide some information on this Wiki for the boards I have (on the board dedicated page), but if you want complete information about the possibilities you can have with a specific board the right place to look at is at the documentation. The board documentation may provide some information, though not necessarily all of it, so the best is to have a look at the processor documentation to know all the supported boot modes, and then at the board schematics (provided you have them) to know which ones are effectively available given the hardware configuration.

== Next ==
* Back to [[Dev/Embedded/FromScratch|"From Scratch" page]].
* Move to [[Dev/Embedded/FromScratch/LinuxKernel|the linux kernel part]] (though you should go on reading [[Dev/Embedded/FromScratch#Linux_Kernel|the next step (Linux Kernel) from the "From Scratch" page]] if you came from there).

Dev/Embedded

2025-07-27T17:11:46Z

Drizzt: /* Create your system from scratch */

== Introduction ==
Well, this may be obvious for most of you, but within the pages in this wiki I will allways consider you are running a GNU/Linux system as your development host. 
Sometimes I will even give you information specific to Debian based GNU/Linux systems, or even the Devuan distribution I'm using.

For those using another GNU/Linux distribution, you'll need to "translate" to your own distribution. You may find help for this on archlinux wiki's [https://wiki.archlinux.org/title/Pacman/Rosetta pacman roseta stone]. They made a '''really''' great job.

On the other hand, if you're not using a GNU/Linux distribution, maybe the first step is to move your development host to a GNU/Linux box ! 
I'm sorry to have to tell you so, but trying to develop an embedded Linux system implies knowing how a GNU/Linux system works, not only the basics of the shell like "ls" and "cd". 
And in order to learn this, there's no better way than using it on an everyday basis, for everything. 
Well, you can also call me and ask me to give you some help, or teach you thoses basics in order to be on tracks much faster : I'm providing [https://www.ed3l.fr/ development and support services] as well as [https://www.ed3l.fr/index.php?page=formations remote training courses].

== General ==
* [[Dev/Embedded/NotOEYocto|Do not use Yocto or OpenEmbeded]] (or their predecessors).
* [[Dev/Embedded/Openness|Open-source matters]] (or why I don't use RaspberryPi boards)
* [[Courses/Distributions/Intro|What is a ((GNU/)Linux) distribution]]

== Cross-compilation ==
[[Dev/Embedded/CrossCompile|Setup cross-compilation environnement on Devuan GNU/Linux]]

== Create your system from scratch ==
[[Dev/Embedded/FromScratch|Build everything from scratch]] (or almost) : build your bootloader, your Linux Kernel and your base system. These are generic information, which may need specific versions or patches depending on the board you are using. 
The main [[Dev/Embedded/FromScratch|"FromScratch"]] page also holds a lot more information which you may find interesting (or so do I hope). 
Here are direct links to :
* '''[[Dev/Embedded/FromScratch/UBoot|the page dedicated to the U-Boot part]]''' (including info about SPL, ATF, ...)
* '''[[Dev/Embedded/FromScratch/LinuxKernel|the page dedicated to the Linux Kernel part]]'''
though you really should consider reading all the information you will find on [[Dev/Embedded/FromScratch|the main page about building your system from scratch]].

== Rootfs and UserLand ==
[[Dev/Embedded/Rootfs|Create and configure the base system]] :
* [[Dev/Embedded/Rootfs/BusyBox|Busybox]]
* [[Dev/Embedded/Rootfs/Devuan/FromScratch|Devuan rootfs creation from scratch]] and [[Dev/Embedded/Rootfs/Devuan/Config|configuration]]

[[Dev/Embedded/Rootfs/Backup|Rootfs backup or copy]] (doing it the right way)

== Embedded targets ==
* [[Dev/BeagleBone|BeagleBone boards]]
* [[Dev/OPi|OrangePi boards]]

Dev/Embedded

2025-07-27T17:11:21Z

Drizzt: /* Create your system from scratch */

== Introduction ==
Well, this may be obvious for most of you, but within the pages in this wiki I will allways consider you are running a GNU/Linux system as your development host. 
Sometimes I will even give you information specific to Debian based GNU/Linux systems, or even the Devuan distribution I'm using.

For those using another GNU/Linux distribution, you'll need to "translate" to your own distribution. You may find help for this on archlinux wiki's [https://wiki.archlinux.org/title/Pacman/Rosetta pacman roseta stone]. They made a '''really''' great job.

On the other hand, if you're not using a GNU/Linux distribution, maybe the first step is to move your development host to a GNU/Linux box ! 
I'm sorry to have to tell you so, but trying to develop an embedded Linux system implies knowing how a GNU/Linux system works, not only the basics of the shell like "ls" and "cd". 
And in order to learn this, there's no better way than using it on an everyday basis, for everything. 
Well, you can also call me and ask me to give you some help, or teach you thoses basics in order to be on tracks much faster : I'm providing [https://www.ed3l.fr/ development and support services] as well as [https://www.ed3l.fr/index.php?page=formations remote training courses].

== General ==
* [[Dev/Embedded/NotOEYocto|Do not use Yocto or OpenEmbeded]] (or their predecessors).
* [[Dev/Embedded/Openness|Open-source matters]] (or why I don't use RaspberryPi boards)
* [[Courses/Distributions/Intro|What is a ((GNU/)Linux) distribution]]

== Cross-compilation ==
[[Dev/Embedded/CrossCompile|Setup cross-compilation environnement on Devuan GNU/Linux]]

== Create your system from scratch ==
[[Dev/Embedded/FromScratch|Build everything from scratch]] (or almost) : build your bootloader, your Linux Kernel and your base system. These are generic information, which may need specific versions or patches depending on the board you are using. 
The main [[Dev/Embedded/FromScratch|"FromScratch"]] page also holds a lot more information which you may find interesting (or so do I hope). 
Here are direct links to :
* '''[[Dev/Embedded/FromScratch/UBoot|the page dedicated to the U-Boot part]]''' (and possible SPL, ATF, ...)
* '''[[Dev/Embedded/FromScratch/LinuxKernel|the page dedicated to the Linux Kernel part]]'''
though you really should consider reading all the information you will find on [[Dev/Embedded/FromScratch|the main page about building your system from scratch]].

== Rootfs and UserLand ==
[[Dev/Embedded/Rootfs|Create and configure the base system]] :
* [[Dev/Embedded/Rootfs/BusyBox|Busybox]]
* [[Dev/Embedded/Rootfs/Devuan/FromScratch|Devuan rootfs creation from scratch]] and [[Dev/Embedded/Rootfs/Devuan/Config|configuration]]

[[Dev/Embedded/Rootfs/Backup|Rootfs backup or copy]] (doing it the right way)

== Embedded targets ==
* [[Dev/BeagleBone|BeagleBone boards]]
* [[Dev/OPi|OrangePi boards]]

Dev/Embedded

2025-07-22T10:21:35Z

Drizzt: /* Introduction */

== Introduction ==
Well, this may be obvious for most of you, but within the pages in this wiki I will allways consider you are running a GNU/Linux system as your development host. 
Sometimes I will even give you information specific to Debian based GNU/Linux systems, or even the Devuan distribution I'm using.

For those using another GNU/Linux distribution, you'll need to "translate" to your own distribution. You may find help for this on archlinux wiki's [https://wiki.archlinux.org/title/Pacman/Rosetta pacman roseta stone]. They made a '''really''' great job.

On the other hand, if you're not using a GNU/Linux distribution, maybe the first step is to move your development host to a GNU/Linux box ! 
I'm sorry to have to tell you so, but trying to develop an embedded Linux system implies knowing how a GNU/Linux system works, not only the basics of the shell like "ls" and "cd". 
And in order to learn this, there's no better way than using it on an everyday basis, for everything. 
Well, you can also call me and ask me to give you some help, or teach you thoses basics in order to be on tracks much faster : I'm providing [https://www.ed3l.fr/ development and support services] as well as [https://www.ed3l.fr/index.php?page=formations remote training courses].

== General ==
* [[Dev/Embedded/NotOEYocto|Do not use Yocto or OpenEmbeded]] (or their predecessors).
* [[Dev/Embedded/Openness|Open-source matters]] (or why I don't use RaspberryPi boards)
* [[Courses/Distributions/Intro|What is a ((GNU/)Linux) distribution]]

== Cross-compilation ==
[[Dev/Embedded/CrossCompile|Setup cross-compilation environnement on Devuan GNU/Linux]]

== Create your system from scratch ==
[[Dev/Embedded/FromScratch|Build everything from scratch]] (or almost) : build your bootloader, your Linux Kernel and your base system. These are generic information, which may need specific versions or patches depending on the board you are using. 
The main [[Dev/Embedded/FromScratch|"FromScratch"]] page also holds a lot more information which you may find interesting (or so do I hope). 
Here are direct links to :
* '''[[Dev/Embedded/FromScratch/UBoot|the page dedicated to the U-Boot part]]'''
* '''[[Dev/Embedded/FromScratch/LinuxKernel|the page dedicated to the Linux Kernel part]]'''
though you really should consider reading all the information you will find on [[Dev/Embedded/FromScratch|the main page about building your system from scratch]].

== Rootfs and UserLand ==
[[Dev/Embedded/Rootfs|Create and configure the base system]] :
* [[Dev/Embedded/Rootfs/BusyBox|Busybox]]
* [[Dev/Embedded/Rootfs/Devuan/FromScratch|Devuan rootfs creation from scratch]] and [[Dev/Embedded/Rootfs/Devuan/Config|configuration]]

[[Dev/Embedded/Rootfs/Backup|Rootfs backup or copy]] (doing it the right way)

== Embedded targets ==
* [[Dev/BeagleBone|BeagleBone boards]]
* [[Dev/OPi|OrangePi boards]]

Dev/Embedded/Openness

2025-07-22T10:20:04Z

Drizzt: /* Introduction */

{{DISPLAYTITLE:Why open-source matters}}

== Introduction ==
Well, from my point of view open-source should always be the only way, for everything. The reasons are not only technical, but ethical and environmental. 
I may spend some time explaining the ethical and environmental parts here someday if they are not obvious, but let's start with the technical ones.

== A note on what "Open source" means here ==
Well, this should be obvious too, but I often get feedback showing me that it's not, and even people accustomed to these concepts often disagree on the exact definition.

Open source means that you have access to the sources.

It does not mean "free" (not even as in "freedom"). It does not mean that everything is released to the public domain for anyone to do anything with it.

Open-source simply means that you can read the source code, the schematics, the plans, and know how "it" is built, and fix "it" if necessary. It means that you "own" what you bought. 
You do not get the right to reproduce or sell copies (which is what you get with "logiciel libre" (free software, but with "free" as in "freedom", not necessarily free beer) or equivalent open-source hardware licences). You can read more on this [https://en.wikipedia.org/wiki/Free_software_movement here (wikipedia : Free software movement)], [https://en.wikipedia.org/wiki/Open_source here (wikipedia : Open Source)], or [https://www.fsf.org/about/ here (FSF website)]

== Technical part ==
'''TO BE COMPLETED'''

== Further discussions ==

''' TO BE COMPLETED'''

Dev/Embedded

2025-07-22T10:16:17Z

Drizzt: /* General */

== Introduction ==
Well, this may not be obvious for everyone, but within the pages in this wiki I will allways consider you are running a GNU/Linux system as your development host.
Sometimes I will even give you information specific to Debian based GNU/Linux systems, or even the Devuan distribution I'm using.

For those using another GNU/Linux distribution, you'll need to "translate" to your own distribution. You may find help for this on archlinux wiki's [https://wiki.archlinux.org/title/Pacman/Rosetta pacman roseta stone]. They made a '''really''' great job.

On the other hand, if you're not using a GNU/Linux distribution, maybe the first step is to move your development host to a GNU/Linux box ! 
I'm sorry to have to tell you so, but trying to develop an embedded Linux system implies knowing how a GNU/Linux system works, not only the basics of the shell like "ls" and "cd". 
And in order to learn this, there's no better way than using it on an everyday basis, for everything. 
Well, you can also call me and ask me to give you some help, or teach you thoses basics in order to be on tracks much faster : I'm providing [https://www.ed3l.fr/ development and support services] as well as [https://www.ed3l.fr/index.php?page=formations remote training courses].

== General ==
* [[Dev/Embedded/NotOEYocto|Do not use Yocto or OpenEmbeded]] (or their predecessors).
* [[Dev/Embedded/Openness|Open-source matters]] (or why I don't use RaspberryPi boards)
* [[Courses/Distributions/Intro|What is a ((GNU/)Linux) distribution]]

== Cross-compilation ==
[[Dev/Embedded/CrossCompile|Setup cross-compilation environnement on Devuan GNU/Linux]]

== Create your system from scratch ==
[[Dev/Embedded/FromScratch|Build everything from scratch]] (or almost) : build your bootloader, your Linux Kernel and your base system. These are generic information, which may need specific versions or patches depending on the board you are using. 
The main [[Dev/Embedded/FromScratch|"FromScratch"]] page also holds a lot more information which you may find interesting (or so do I hope). 
Here are direct links to :
* '''[[Dev/Embedded/FromScratch/UBoot|the page dedicated to the U-Boot part]]'''
* '''[[Dev/Embedded/FromScratch/LinuxKernel|the page dedicated to the Linux Kernel part]]'''
though you really should consider reading all the information you will find on [[Dev/Embedded/FromScratch|the main page about building your system from scratch]].

== Rootfs and UserLand ==
[[Dev/Embedded/Rootfs|Create and configure the base system]] :
* [[Dev/Embedded/Rootfs/BusyBox|Busybox]]
* [[Dev/Embedded/Rootfs/Devuan/FromScratch|Devuan rootfs creation from scratch]] and [[Dev/Embedded/Rootfs/Devuan/Config|configuration]]

[[Dev/Embedded/Rootfs/Backup|Rootfs backup or copy]] (doing it the right way)

== Embedded targets ==
* [[Dev/BeagleBone|BeagleBone boards]]
* [[Dev/OPi|OrangePi boards]]

Dev/BeagleBone/BeagleYAI

2025-03-25T16:34:14Z

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

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* 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, 64bits aarch64 Armv8.x-A, VFPv4) (Still haven't found which is the .x in Armv8.x)
: - two C7x DSP cores
: - 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).
* 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.

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-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.

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

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* 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 ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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

== Linux kernel Configuration options to be checked ==
=== Global Kernel options ===
==== Kernel features ====
* ARM errata workarounds : Need to activate other workarounds than the A53 ones ??
* Find which 'x' is in ARMv8.x for the AM67A ARM-Cortex-A53 cores and select appropriate architectural features.
* Use BPF ? (https://www.kernel.org/doc/html/v4.19/bpf/index.html)

==== ACPI/UEFI Support ====
Was enabled in Robert Nelson kernel. 
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 ====
* Disabled all suspend to RAM and Disk
* Check for subsystems powermanagement

==== Memory ====
* Memory hotplug
* HWPoison pages injector
* Device memory (pmem, HMM, etc...) hotplug support

=== Networking ===
==== Networking options ====
Currently reduced to the set used on other boards, to be tuned and checked ....

==== Wireless (Wifi) ====
Checked for 802.11 options and RFkill using GPIO.

==== Bluetooth ====
* To be checked ... which protocol for the device driver ? which extensions ? ...

=== Device drivers ===
Get list of loaded drivers :
ls /sys/bus/platform/drivers/
Need to find a way to check those which are really used.
==== Global ====
* Test the netlink-based uevent source/mechanism
==== PCI support ====
* Check for PCI PRI and PCI PASID support : none --> remove
* Check for PCI controller driver : "Cadence-based TI J721E" or "DesignWare-based TI Keystone" PCIe controller ??
Note that the PCIe module can work either as "root complex (RC)" or as "endpoint (EP)". This has to be chosen here, and the documentation states that this should be configured "during initial power-up", which will need to be done by U-Boot (or earlier ?).
* Need to "Enable PCI quirk workarounds" ?
==== Misc devices ====
* Generic on-chip SRAM driver ?
==== SCSI ====
* Why "LSI Logic MegaRAID SAS RAID Module" ?
==== Net ====
* Test net eth0
* Add cc33xx driver from ti for wireless module

=== 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 ===
Reduced to the bare minimum (proc, sys, tmpfs, vFat, ext4 and NFS)

=== Security options ===
Update to your needs

=== Cryptographic API ===
Check for algorithms you'll be using, those available, and disable all others.

=== Kernel libs and kernel debugging ===
Left only the bare minimum parts, update to your needs.

Select only drivers that don't need compile-time external firmware - Cadence MHDP8546
UPD drivers/base/firmware_loader/builtin/cadence/mhdp8546.bin.gen.S
make[6]: *** Aucune règle pour fabriquer la cible « /home/drizzt/Opt/git/linux/firmware/cadence/mhdp8546.bin », nécessaire pour « drivers/base/firmware_loader/builtin/cadence/mhdp8546.bin.gen.o ». Arrêt.

== Kernel config requiring user-space config at boot-time or runtime ==
* 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)
* Power management
* Configure the "safesetid" (SECURITY_SAFESETID) whitelist

== Liens officiels ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-25T15:56:34Z

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

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* 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, 64bits aarch64 Armv8.x-A, VFPv4) (Still haven't found which is the .x in Armv8.x)
: - two C7x DSP cores
: - 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).
* 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.

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-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.

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

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* 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 ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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

== Linux kernel Configuration options to be checked ==
=== Global Kernel options ===
==== Kernel features ====
* ARM errata workarounds : Need to activate other workarounds than the A53 ones ??
* Find which 'x' is in ARMv8.x for the AM67A ARM-Cortex-A53 cores and select appropriate architectural features.
* Use BPF ? (https://www.kernel.org/doc/html/v4.19/bpf/index.html)

==== ACPI/UEFI Support ====
Was enabled in Robert Nelson kernel. 
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 ====
* Disabled all suspend to RAM and Disk
* Check for subsystems powermanagement

==== Memory ====
* Memory hotplug
* HWPoison pages injector
* Device memory (pmem, HMM, etc...) hotplug support

=== Networking ===
==== Networking options ====
Currently reduced to the set used on other boards, to be tuned and checked ....

==== Wireless (Wifi) ====
Checked for 802.11 options and RFkill using GPIO.

==== Bluetooth ====
* To be checked ... which protocol for the device driver ? which extensions ? ...

=== Device drivers ===
Get list of loaded drivers :
ls /sys/bus/platform/drivers/
Need to find a way to check those which are really used.
==== Global ====
* Test the netlink-based uevent source/mechanism
==== PCI support ====
* Check for PCI PRI and PCI PASID support : none --> remove
* Check for PCI controller driver : "Cadence-based TI J721E" or "DesignWare-based TI Keystone" PCIe controller ??
Note that the PCIe module can work either as "root complex (RC)" or as "endpoint (EP)". This has to be chosen here, and the documentation states that this should be configured "during initial power-up", which will need to be done by U-Boot (or earlier ?).
* Need to "Enable PCI quirk workarounds" ?
==== Misc devices ====
* Generic on-chip SRAM driver ?
==== SCSI ====
* Why "LSI Logic MegaRAID SAS RAID Module" ?
==== Net ====
* Test net eth0
* Add cc33xx driver from ti for wireless module

=== File system ===
Reduced to the bare minimum (proc, sys, tmpfs, vFat, ext4 and NFS)

=== Security options ===
Update to your needs

=== Cryptographic API ===
Check for algorithms you'll be using, those available, and disable all others.

=== Kernel libs and kernel debugging ===
Left only the bare minimum parts, update to your needs.

Select only drivers that don't need compile-time external firmware - Cadence MHDP8546
UPD drivers/base/firmware_loader/builtin/cadence/mhdp8546.bin.gen.S
make[6]: *** Aucune règle pour fabriquer la cible « /home/drizzt/Opt/git/linux/firmware/cadence/mhdp8546.bin », nécessaire pour « drivers/base/firmware_loader/builtin/cadence/mhdp8546.bin.gen.o ». Arrêt.

== Kernel config requiring user-space config at boot-time or runtime ==
* 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)
* Power management
* Configure the "safesetid" (SECURITY_SAFESETID) whitelist

== Liens officiels ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-25T15:56:27Z

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

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* 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, 64bits aarch64 Armv8.x-A, VFPv4) (Still haven't found which is the .x in Armv8.x)
: - two C7x DSP cores
: - 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).
* 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.

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-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.

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

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* 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 ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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

== Linux kernel Configuration options to be checked ==
=== Global Kernel options ===
==== Kernel features ====
* ARM errata workarounds : Need to activate other workarounds than the A53 ones ??
* Find which 'x' is in ARMv8.x for the AM67A ARM-Cortex-A53 cores and select appropriate architectural features.
* Use BPF ? (https://www.kernel.org/doc/html/v4.19/bpf/index.html)

==== ACPI/UEFI Support ====
Was enabled in Robert Nelson kernel. 
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 ====
* Disabled all suspend to RAM and Disk
* Check for subsystems powermanagement

==== Memory ====
* Memory hotplug
* HWPoison pages injector
* Device memory (pmem, HMM, etc...) hotplug support

=== Networking ===
==== Networking options ====
Currently reduced to the set used on other boards, to be tuned and checked ....

==== Wireless (Wifi) ====
Checked for 802.11 options and RFkill using GPIO.

==== Bluetooth ====
* To be checked ... which protocol for the device driver ? which extensions ? ...

=== Device drivers ===
Get list of loaded drivers :
ls /sys/bus/platform/drivers/
Need to find a way to check those which are really used.
==== Global ====
* Test the netlink-based uevent source/mechanism
==== PCI support ====
* Check for PCI PRI and PCI PASID support : none --> remove
* Check for PCI controller driver : "Cadence-based TI J721E" or "DesignWare-based TI Keystone" PCIe controller ??
Note that the PCIe module can work either as "root complex (RC)" or as "endpoint (EP)". This has to be chosen here, and the documentation states that this should be configured "during initial power-up", which will need to be done by U-Boot (or earlier ?).
* Need to "Enable PCI quirk workarounds" ?
==== Misc devices ====
* Generic on-chip SRAM driver ?
==== SCSI ====
* Why "LSI Logic MegaRAID SAS RAID Module" ?
==== Net ====
* Test net eth0
* Add cc33xx driver from ti for wireless module

=== File system ===
Reduced to the bare minimum (proc, sys, tmpfs, vFat, ext4 and NFS)

=== Security options ===
Update to your needs

=== Cryptographic API ===
Check for algorithms you'll be using, those available, and disable all others.

=== Kernel libs and kernel debugging ===
Left only the bare minimum parts, update to your needs.

Select only drivers that don't need compile-time external firmware - Cadence MHDP8546
UPD drivers/base/firmware_loader/builtin/cadence/mhdp8546.bin.gen.S
make[6]: *** Aucune règle pour fabriquer la cible « /home/drizzt/Opt/git/linux/firmware/cadence/mhdp8546.bin », nécessaire pour « drivers/base/firmware_loader/builtin/cadence/mhdp8546.bin.gen.o ». Arrêt.

== Kernel config requiring user-space config at boot-time or runtime ==
* 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)
* Power management

== Liens officiels ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-24T12:49:26Z

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

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* 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, 64bits aarch64 Armv8.x-A, VFPv4) (Still haven't found which is the .x in Armv8.x)
: - two C7x DSP cores
: - 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).
* 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.

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-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.

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

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* 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 ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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

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

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

=== Memory ===
* Memory hotplug
* HWPoison pages injector
* Device memory (pmem, HMM, etc...) hotplug support

== Kernel config requiring user-space config at boot-time or runtime ==
* 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)
* Power management

== Liens officiels ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-24T12:45:31Z

Drizzt:

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* 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, 64bits aarch64 Armv8.x-A, VFPv4) (Still haven't found which is the .x in Armv8.x)
: - two C7x DSP cores
: - 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).
* 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.

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-FS (High Security - Functional Safety) variant is more geared toward functional safety requirements.

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

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* 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 ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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

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

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

=== Memory ===
* Memory hotplug
* HWPoison pages injector
* Device memory (pmem, HMM, etc...) hotplug support

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

== Liens officiels ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-24T10:13:33Z

Drizzt: /* Liens officiels */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* 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)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - 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)
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>.
: 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 BeagleY-AI board uses an AM67A which is a TDA4AEN variant and not a TDA4VM, and it is a HS-FS variant.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* 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 ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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

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

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

=== Memory ===
* Memory hotplug
* HWPoison pages injector
* Device memory (pmem, HMM, etc...) hotplug support

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

== Liens officiels ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-20T01:48:49Z

Drizzt: /* Description */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* 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)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - 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)
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>.
: 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 BeagleY-AI board uses an AM67A which is a TDA4AEN variant and not a TDA4VM, and it is a HS-FS variant.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* 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 ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-19T23:05:57Z

Drizzt: /* Processor */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* 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)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - 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)
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>.
: 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 BeagleY-AI board uses an AM67A which is a TDA4AEN variant and not a TDA4VM, and it is a HS-FS variant.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== The Boot process ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-19T23:04:01Z

Drizzt: /* Processor */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* 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)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - 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)
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".
: 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 BeagleY-AI board uses a TDA4AEN and not a TDA4VM, and it is a HS-FS variant.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== The Boot process ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-19T18:35:27Z

Drizzt:

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* The board has a TI Jacinto J722S ([https://www.ti.com/product/TDA4AEN-Q1 TDA4AEN]) AM67A SOC with
: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - two additional Arm Cortex-R5F cores (Device management and Run-time management).
* BXS-4-64 GPU
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".
: 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 BeagleY-AI board uses a TDA4AEN

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== The Boot process ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: 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.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/ti-u-boot/ti-u-boot.git (or use the one from openbeagle.org)
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.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]

=== BeagleBone ===
* https://openbeagle.org/beagleboard/u-boot.git - tag "v2023.04-ti-09.02.00.009-BeagleY-AI"
: tag : v2025.04-rc3-BeagleY-AI

=== Others ===
* https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git
: 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.

== Build the images ==
The sources which proved most usefull in order to rebuild all the images (all but ti firmwares ...) :
* https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
* 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 ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-18T20:41:46Z

Drizzt: /* Description */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* The board has a TI Jacinto J722S ([https://www.ti.com/product/TDA4AEN-Q1 TDA4AEN]) AM67A SOC with
: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - two additional Arm Cortex-R5F cores (Device management and Run-time management).
* BXS-4-64 GPU
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".
: This HS-SE 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.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== The Boot process ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: This firmware image is also called "SYSFW" and may be included inside '''tiboot3.bin'''.
: It is used for the "Secure Management Services" (SMS), to be run on the corresponding R5F MCU.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/processor-sdk/psdk_fw.git
* 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/processor-firmware/ti-linux-firmware.git

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]

=== BeagleBone ===
* 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

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

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 ==
=== U-Boot ===
make ARCH=arm O=../Build/u-boot/r5 am67a_beagley_ai_r5_defconfig
make ARCH=arm O=../Build/u-boot/a53 am67a_beagley_ai_a53_defconfig

=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-18T17:54:52Z

Drizzt: /* The Boot process */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* The board has a TI Jacinto J722S ([https://www.ti.com/product/TDA4AEN-Q1 TDA4AEN]) AM67A SOC with
: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - two additional Arm Cortex-R5F cores (Device management and Run-time management).
* BXS-4-64 GPU
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.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== The Boot process ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

You may find the documentation within U-Boot sources to be pretty complete : https://docs.u-boot.org/en/latest/board/ti/j722s_evm.html
: Note that it does not directly targets the BeagleY-AI board but the J722S-EVM one

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: This firmware image is also called "SYSFW" and may be included inside '''tiboot3.bin'''.
: It is used for the "Secure Management Services" (SMS), to be run on the corresponding R5F MCU.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/processor-sdk/psdk_fw.git
* 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/processor-firmware/ti-linux-firmware.git

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]

=== BeagleBone ===
* 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

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

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 ==
=== U-Boot ===
make ARCH=arm O=../Build/u-boot/r5 am67a_beagley_ai_r5_defconfig
make ARCH=arm O=../Build/u-boot/a53 am67a_beagley_ai_a53_defconfig

=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/Embedded/CrossCompile

2025-03-17T23:42:58Z

Drizzt: /* Add tools for specific projects */

'''!!!!!!!!!!!!!!!!!!!!! Ongoing work : This is only a collection of notes right now '''!!!!!!!!!!!!!!!!!!!!!

== The basics ==

== Building your own : using Crosstool-NG ==
* https://github.com/crosstool-ng/crosstool-ng

== Installation of Devuan/Debian cross-toolchain ==
=== (Cross-)Compiler part ===
apt-get install binutils-aarch64-linux-gnu cpp-aarch64-linux-gnu gcc-aarch64-linux-gnu libc6-dev:arm64

=== Add architecture support ===
dpkg --print-foreign-architectures
dpkg --add-architecture <arch>

=== Add libs ===
apt-get install libc6-dev:arm64

=== Add tools for specific projects ===
for the Linux Kernel :
apt-get install bc bison flex
apt-get install libncurses-dev libssl-dev

for uboot :
apt-get install python3-setuptools swig libgnutls28-dev libssl-dev
apt-get install yamllint python3-jsonschema # U-boot on beagley-ai

for mtd images creation and manipulation :
apt-get install mtd-utils squashfs-tools

== Some more ==
* https://wiki.debian.org/Multiarch/Implementation
* https://wiki.debian.org/fr/Multiarch/HOWTO

Dev/Embedded/CrossCompile

2025-03-17T23:41:11Z

Drizzt: /* Add tools for specific projects */

'''!!!!!!!!!!!!!!!!!!!!! Ongoing work : This is only a collection of notes right now '''!!!!!!!!!!!!!!!!!!!!!

== The basics ==

== Building your own : using Crosstool-NG ==
* https://github.com/crosstool-ng/crosstool-ng

== Installation of Devuan/Debian cross-toolchain ==
=== (Cross-)Compiler part ===
apt-get install binutils-aarch64-linux-gnu cpp-aarch64-linux-gnu gcc-aarch64-linux-gnu libc6-dev:arm64

=== Add architecture support ===
dpkg --print-foreign-architectures
dpkg --add-architecture <arch>

=== Add libs ===
apt-get install libc6-dev:arm64

=== Add tools for specific projects ===
for the Linux Kernel :
apt-get install bc bison flex
apt-get install libncurses-dev libssl-dev

for uboot :
apt-get install python3-setuptools swig libgnutls28-dev libssl-dev
apt-get install yamllint # U-boot on beagley-ai

for mtd images creation and manipulation :
apt-get install mtd-utils squashfs-tools

== Some more ==
* https://wiki.debian.org/Multiarch/Implementation
* https://wiki.debian.org/fr/Multiarch/HOWTO

Dev/BeagleBone/BeagleYAI

2025-03-14T15:32:34Z

Drizzt: /* Sources */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* The board has a TI Jacinto J722S ([https://www.ti.com/product/TDA4AEN-Q1 TDA4AEN]) AM67A SOC with
: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - two additional Arm Cortex-R5F cores (Device management and Run-time management).
* BXS-4-64 GPU
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.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== The Boot process ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: This firmware image is also called "SYSFW" and may be included inside '''tiboot3.bin'''.
: It is used for the "Secure Management Services" (SMS), to be run on the corresponding R5F MCU.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/processor-sdk/psdk_fw.git
* 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/processor-firmware/ti-linux-firmware.git

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]

=== BeagleBone ===
* 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

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

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 ==
=== U-Boot ===
make ARCH=arm O=../Build/u-boot/r5 am67a_beagley_ai_r5_defconfig
make ARCH=arm O=../Build/u-boot/a53 am67a_beagley_ai_a53_defconfig

=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-13T16:38:48Z

Drizzt: /* Sources */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* The board has a TI Jacinto J722S ([https://www.ti.com/product/TDA4AEN-Q1 TDA4AEN]) AM67A SOC with
: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - two additional Arm Cortex-R5F cores (Device management and Run-time management).
* BXS-4-64 GPU
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.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== The Boot process ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: This firmware image is also called "SYSFW" and may be included inside '''tiboot3.bin'''.
: It is used for the "Secure Management Services" (SMS), to be run on the corresponding R5F MCU.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/processor-sdk/psdk_fw.git
* git://git.ti.com/ti-u-boot/ti-u-boot.git
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git

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]

=== BeagleBone ===
* 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

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

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 ==
=== U-Boot ===
make ARCH=arm O=../Build/u-boot/r5 am67a_beagley_ai_r5_defconfig
make ARCH=arm O=../Build/u-boot/a53 am67a_beagley_ai_a53_defconfig

=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-13T16:37:39Z

Drizzt: /* Sources */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* The board has a TI Jacinto J722S ([https://www.ti.com/product/TDA4AEN-Q1 TDA4AEN]) AM67A SOC with
: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - two additional Arm Cortex-R5F cores (Device management and Run-time management).
* BXS-4-64 GPU
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.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== The Boot process ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: This firmware image is also called "SYSFW" and may be included inside '''tiboot3.bin'''.
: It is used for the "Secure Management Services" (SMS), to be run on the corresponding R5F MCU.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/processor-sdk/psdk_fw.git
* git://git.ti.com/ti-u-boot/ti-u-boot.git
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git

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]

=== BeagleBone ===
* 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

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

== Configs ==
=== U-Boot ===
make ARCH=arm O=../Build/u-boot/r5 am67a_beagley_ai_r5_defconfig
make ARCH=arm O=../Build/u-boot/a53 am67a_beagley_ai_a53_defconfig

=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-13T16:35:55Z

Drizzt: /* Where to get more information */

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* The board has a TI Jacinto J722S ([https://www.ti.com/product/TDA4AEN-Q1 TDA4AEN]) AM67A SOC with
: - four Arm Cortex-A53 cores (main cores, 1.4Ghz)
: - two C7x DSP cores
: - one user Arm Cortex-R5F core (MCU channel with FFI, 800Mhz)
: - two additional Arm Cortex-R5F cores (Device management and Run-time management).
* BXS-4-64 GPU
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.

=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== The Boot process ==

=== Overview ===
From chapter "[https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/developer_notes_bootloaders.html 9.2. Understanding bootloaders in Processor SDK J722S (RTOS/Linux)] and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components/U-Boot/UG-General-Info.html Processor SDK Linux for AM67A, chapter 3.1.1.1 - U-Boot - General Information] :
: The boot process on the J722S processor requires two different U-Boot images and some firmwares, which will run on different cores.
Information is a little bit confused, maybe because there may be different ways to achieve the boot process.

* '''tiboot3.bin'''
: The first "Secondary Program Loader" (SPL) that the ROM bootloader will load and execute on the MCU R5F Core0
: It seems to be an agregate of an U-Boot image (u-boot-spl.bin) and the TIFS firmware (sysfw)
: It will try to load two images : "tifs.bin" (embedded) and "tispl.bin" (from SD card)
* '''tifs.bin'''
: TI Foundational Security (TIFS)
: This firmware image is also called "SYSFW" and may be included inside '''tiboot3.bin'''.
: It is used for the "Secure Management Services" (SMS), to be run on the corresponding R5F MCU.
* '''tispl.bin'''
: The second "Secondary Program Loader" (SPL). This one will run on one of the A53 cores.
: This image includes the "ARM Trusted Firmware" (ATF or Trusted Firmware-A) and the "Trusted Execution Environment" (TEE, provided by OP-TEE).
: It also includes the "Device Management" (DM) firmware which will run on one of the R5F cores. It provides the services refered to as Resource Management (RM) and Power Management (PM).
: And then the "SPL" proper, which may be a reduced U-Boot image, commonly refered to as the "first-stage bootloader" which will mainly initialise the A53 core, the DDR memory, and the required subsystems so that the full U-Boot image can run.
* '''uboot.img'''
: This is the final U-Boot image, also called "second-stage bootloader", which will also run on one of the A53 cores.
: This one will provide a prompt and load the Linux kernel.

=== Where to get more information ===
Credits : I started finding useful and accurate information on [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b this post on medium by Olof Astrand : Building u-boot and the linux kernel for the beagleY AI board], though these rely on TI SDK, which I'd like to avoid as much as possible, both in order to understand everything, make things clear as what code is required (or binary blobs if any) and avoid huge unnecessary amounts of data which usually comes whith such SDK bundles.

Anyway, this post references some useful sources :
* [https://software-dl.ti.com/tisci/esd/latest/1_intro/TISCI.html Texas Instruments System Controller Interface] (TISCI)
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/index.html Processor SDK RTOS J722S]
* [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/index.html Processor SDK Linux Software Developer’s Guide], mainly chapter 3 : Foundational Components.

TI even provides access to the sources of these documentations : https://github.com/TexasInstruments/processor-sdk-doc !!

This patchset by Jacob Stiffler for Yocto also provides information : https://lore.kernel.org/all/1535138718-6772-2-git-send-email-j-stiffler@ti.com/T/

* Trusted Firmware-A : https://trustedfirmware-a.readthedocs.io/en/latest/index.html (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_ATF.html Trusted Firmware-A related section in processor SDK documentation for Linux on AM67A])
* OP-TEE : https://optee.readthedocs.io/en/latest/ (and [https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/linux/Foundational_Components_OPTEE.html OP-TEE related section in processor SDK documentation for Linux on AM67A])

== Sources ==
=== TI ===
* git://git.ti.com/processor-sdk/psdk_fw.git
* git://git.ti.com/ti-u-boot/ti-u-boot.git
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git

Sources, branches and tags are referenced here : https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-am67a/latest/exports/docs/devices/J7_Family/linux/Release_Specific_Release_Notes.html

=== BeagleBone ===
* 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

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

== Configs ==
=== U-Boot ===
make ARCH=arm O=../Build/u-boot/r5 am67a_beagley_ai_r5_defconfig
make ARCH=arm O=../Build/u-boot/a53 am67a_beagley_ai_a53_defconfig

=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-03-13T16:32:22Z

Drizzt: /* Processor */

Dev/BeagleBone/BeagleYAI

2025-03-13T16:27:29Z

Drizzt: /* Processor */

Dev/BeagleBone/BeagleYAI

2025-03-13T12:25:46Z

Drizzt:

Dev/BeagleBone/BeagleYAI

2025-03-04T16:22:41Z

Drizzt: /* Configs */

Dev/BeagleBone/BeagleYAI

2025-03-04T14:12:14Z

Drizzt: /* Description */

Dev/BeagleBone/BeagleYAI

2025-03-04T11:37:14Z

Drizzt:

== Description ==
* https://docs.beagle.cc/boards/beagley/ai/03-design.html
=== Processor ===
* The board has a TI Jacinto XJ722S (TDA4AEN) SOC which seems to be an AM67A with
: four Arm Cortex-A53 cores (main cores, 1.4Ghz)
: two C7x DSP cores
: three Arm Cortex-R5F cores (MCU channel with FFI (user apps, 800Mhz), Device management and Run-time management).
* BXS-4-64 GPU
=== Memory ===
* 4Go LPDDR4
* EEPROM (FT24C32A) on I2C0
* microSD Card

== Additional tools ==
=== TI Firmware Builder ===
* https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/firmware_builder.html

== Sources ==
=== TI ===
* git://git.ti.com/processor-sdk/psdk_fw.git
* git://git.ti.com/ti-u-boot/ti-u-boot.git
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git

== Configs ==
=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
* [https://olof-astrand.medium.com/building-u-boot-and-the-linux-kernel-for-the-beagley-ai-board-0942565ab28b Building u-boot and the linux kernel for the beagleY AI board]
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-02-27T00:50:17Z

Drizzt:

== Additional tools ==
=== TI Firmware Builder ===
* https://software-dl.ti.com/jacinto7/esd/processor-sdk-rtos-j722s/09_02_00_05/exports/docs/psdk_rtos/docs/user_guide/firmware_builder.html

== Sources ==
=== TI ===
* git://git.ti.com/processor-sdk/psdk_fw.git
* git://git.ti.com/ti-u-boot/ti-u-boot.git
* git://git.ti.com/ti-linux-kernel/ti-linux-kernel.git

== Configs ==
=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

* Tag connect clip : https://www.printables.com/model/879533-beagley-ai-tagconnect-clip-10pin

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

== Links ==
* BeagleBoard linux git repository : https://git.beagleboard.org/beagleboard/linux
* BeagleY-AI design and detailed specifications : https://docs.beagle.cc/boards/beagley/ai/03-design.html
*
* [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review BeagleY-AI Review - Part 1] and [https://community.element14.com/products/devtools/single-board-computers/next-genbeaglebone/b/blog/posts/beagley-ai-review---part-2 BeagleY-AI Review - Part 2] on element 14 community.

Dev/BeagleBone/BeagleYAI

2025-02-19T12:16:54Z

Drizzt: /* Debug port Connection */

== Configs ==
=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web (even [https://docs.beagle.cc/boards/beagley/ai/03-design.html#uart within official beagleboard online documentation]), the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your preferred components supplier.

Dev/BeagleBone/BeagleYAI

2025-02-06T02:28:49Z

Drizzt: /* Onboard connector */

Dev/BeagleBone/BeagleYAI

2025-02-06T02:23:06Z

Drizzt:

== Configs ==
=== Linux ===
* 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 ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

== Pinout ==
* https://pinout.beagley.ai/

== Debug port Connection ==
=== Onboard connector ===
Despite what some have published about everywhere on the Web, the connector '''IS NOT''' a JST connector. Some stupid guy made a confusion between the name of the footprint on the schematics or in the BOM and the name of the manufacturer. 
The official BOM gives all the information :
* Manufacturer : MTCONN
* Manufacturer part number : MTWF63-103SRN-01163

=== Where to find mating connector ===
I did not find the exact connector reference on MTCONN website, but they have another one which seems to be the same one : https://www.mtconntech.com/wafer-conn-2-product/ which reference is "WTB10-XX-02-2" ... but I do not know where to get these, much less the mating connector. 
Some googling gave me another manufacturer with a compatible reference : [https://www.we-online.com/en/components/products/em/connectors/wire-to-board/wr_wtb/wr_wtb_1_00_mm Wurth Elektronik]. 
What's nice with Wurth Elektronik is that they have an efficient website, with all the information, and their references are easy to order using Mouser or Digikey for example. 
Here are the references/links for all the parts :
* [https://www.we-online.com/en/components/products/WTB_1_00_SMT_MALE_VERTICAL_SHROUDED_HEADER_6653XX124022 WR-WTB 1.00 mm SMT Male Vertical Shrouded Header]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_TERMINAL_HOUSING_6650XX113322 WR-WTB 1.00 mm Female Terminal Housing]
* [https://www.we-online.com/en/components/products/WTB_1_00_FEMALE_CRIMP_CONTACT_665X0113722 WR-WTB 1.00 mm Female Crimp Terminal]
* [https://www.we-online.com/en/components/products/WTB_PRE-CRIMPED_CABLE_1_00 WR-WTB Pre-crimped wire]
* And even the [https://www.we-online.com/en/components/products/WTB_MANUAL_CRIMPING_TOOL_11#600665232280 WR-WTB Manual Crimping Tool]
Choose the number of positions you need (3 for the debug port, but there's also a 2 positions and a 4 positions connector on the BeagleY-AI board), and either ask for samples or look for the corresponding parts reference number on your selected

Dev/BeagleBone/BeagleYAI

2025-02-05T01:45:45Z

Drizzt:

Dev/BeagleBone/BeagleYAI

2025-02-03T18:59:50Z

Drizzt: Created page with "== Liens officiels == * https://www.beagleboard.org/boards/beagley-ai * [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]"

== Liens officiels ==
* https://www.beagleboard.org/boards/beagley-ai
* [https://www.mouser.fr/ProductDetail/BeagleBoard-by-Seeed-Studio/102991834?qs=dbcCsuKDzFXY1JA%252BEGwyow%3D%3D Achat chez Mouser à 77€]

Dev/BeagleBone

2025-02-03T18:58:02Z

Drizzt: /* Boards */

Dev/Embedded/Rootfs/BusyBox/Example1

2025-02-03T18:48:43Z

Drizzt:

{{DISPLAYTITLE:BusyBox Example 1 : Simple system}}

Most of the time when you start with BusyBox as the heart of your system you do not plan for a multi-user desktop box, but rather aim for a small, single purpose embedded system, so you won't need too many stuff to get it running.

This example explains how to create a minimal Linux based base system using BusyBox as a base for the userland part of the system.

== Minimal configuration ==
You can start with this '''[http://data.nathael.net/Dev/Base/BusyBox/config_mini_example_2025-01-10 example minimal config]'''. 
Some information about my choices :
* This configuration is based upon the "defaultconfig", but with many modifications (not all listed here)
* No "/usr" support (all binaries under /bin and /sbin)
* Archival utilities limited to tar with "xz" and "bz2" support
* Removed console utilities
* Removed most users handling utilities : users should be known when building the system (or added by direct editting of the files)
* Removed disk partitionning and formatting utilities save for UBIFS
* Removed runit support
* Removed all commands I never used on a full blown system

== Compile using uClibc ==
The options selected for a minimal configuration should not impact the compilation process, unless you want a really small system, which is common when using BusyBox due to storage size constraints. 
In this case using uClibc instead of the GNU libc is a good idea. 
Most information about using uClibc in a cross-compilation toolchain can be found [https://www.uclibc.org/ on uClibc website]. 
You will then need to use the cross-compilation prefix of your toolchain to build BusyBox.

With a stripped down BusyBox, you may well end up with :
Final link with: <none>
But note that in this case you'll still need the selected libc (uClibc) !

== Directories and links ==
Here is a very simple set of directories for a configuration without "/usr", according to the minimal configuration given above :
mkdir -p dev etc lib/{modules,firmware} proc root run sys var/{log,spool/cron}
Then add some links :
ln -s run/tmp tmp
ln -s ../run/tmp var/tmp

== Libraries ==
As this is a very simple system the set of libraries should be very limited. You may need additional ones for your application binaries so I cannot give you a full list, but if you chose to have dynamically linked binaries (which is usually a good idea if your system has more than one or two binaries) you will always need these two :
* The dynamic linker/loader (name depending on the target architecture/triplet) : ld-linux-*.so.*
* the libc : libc.so.6
In order to check for additional library requirements, have a look at this part in the second example.

Once you know which libraries you need, you'll need to figure which files to put in which directory for each library.

Unless you specified an absolute or relative pathname during the linking stage of the compilation of your binaries, there is no "fixed" location for each library file, save maybe the dynamic linker/loader (ld-linux-*.so.*), which usually goes under "/lib", and the dynamic linker will end up looking for libraries in some "default" path which usually includes "/lib". 
So the easy way is to create a single "/lib" directory (remember that we chose to desactivate the use of "/usr" in BusyBox configuration).

As for the files, for the dynamic linker/loader and the libc, the files should be shipped with your cross-compilation toolchain. If you're using the toolchain packaged by Debian, then you will find them under "/usr/${triplet}/lib/" if you installed "libc6-*-cross" package, or under "/usr/lib/${triplet}/" if you installed "libc6:*" package (* is for the Debian architecture name, while you should [[Dev/Embedded/Rootfs/BusyBox/Example2#First,_the_answer_about_the_"triplet"|read the bits I collected about the ${triplet} in the second BusyBox example page]]).

== Bootup script(s) ==
Now Busybox seems to support two init systems : the historic one sharing similarities to SysVinit (without the runlevels) and one similar to runnit.
I choose to disable runnit support in this minimal configuration, so the "init" applet will look for the "/etc/inittab" configuration file. 
There is an example one under "examples/" in BusyBox source tree. 
Anyway, even without this file the applet will look for a script called "/etc/init.d/rcS" and, even if it found none, start an "askfirst" shell (display the message "Please press Enter to activate this console." which would then give you a prompt). All the details are explained in the example inittab file in BusyBox sources.

So here is a short list of files for the init part of the base system :
* /etc/inittab
* /etc/init.d/rcS
* Other service or configuration script(s)

What you put in each file depends on your application and your needs, even if some parts are hard to avoid and thus common to every system, like the initial mounts of /dev and /proc at least.

In SysVinit the rcS script (called by init according to inittab content) calls "/etc/init.d/rc" for the runlevel S, which will start all scripts from "/etc/rcS.d", and after this, init will change to the default runlevel configured in inittab, which will call "/etc/init.d/rc" for the default runlevel (usually 2) which in turn will start all scripts from the corresponding "/etc/rcN.d" directory.

In busybox there are no runlevels, and usually much less configuration to perform, with this configuration being more "static". 
As such, I usually create a single "startup" script (the "/etc/init.d/rcS" one) which does all the usual system configuration and setup (hostname, mounts, hwclock, modules, sysctl, random init, ...) then the network configuration (static IP or DHCP, firewall, ...) 
Having everything started sequentially by a single script which does not try to read a hundred configuration files is not that much slower than using a heavy, complicated system which tries to run everything in parallel but needs to be heavily configured to avoid race conditions and handle dependencies.

In order to start the services (sshd, inetd, ...) and the main application(s) you have some options :
* add them at the end of the rcS script (using start-stop-daemon if need be for respawn)
* create a separate script for them (or one for each) and call them at the end of the rcS one (still using start-stop-daemon if need be)
* use the "wait", "once" or "respawn" actions in inittab
I usually use the inittab solution, sometimes with a wrapper script.

== Configuration files ==
The list of configuration files depend on what you have selected in you BusyBox configuration and on what you write in your scripts. 
And their content depends on your needs, of course. 
In order to know which ones you'll need, there is no easy way (as far as I know). 
* Some of them are listed within BusyBox configuration menu and help for each entry, so you can start there, reading the help for each entry you have activated (save thoses you think would not need a configuration file, like archiving related utilities).
* You can also look at the content of "/etc" on your development host
* Another solution is to try running the system, try to start the services you want, and check the messages on the console.
Here is a short list of those I have listed/created for this simple example :
* /etc/nologin
* /etc/securetty
* /etc/shells
* /etc/{passwd,shadow,groups}
* ''' TO BE COMPLETED '''

== Application binaries and related files ==
This part is really only up to you and your application.

As this simple BusyBox example does not include any kind of "application packaging" support there's not need (save for your mental health) to stick to any particular organisation for your files.

Remember that if your binaries rely on some more libs than those you already put under "/lib" (or any other place you chose for them), then you'll need to add them to your base file system too.

Dev/Embedded/Rootfs/BusyBox/Example1

2025-01-18T02:28:22Z

Drizzt: /* Bootup script(s) */

{{DISPLAYTITLE:Example 1 : Simple system}}

Most of the time when you start with BusyBox as the heart of your system you do not plan for a multi-user desktop box, but rather aim for a small, single purpose embedded system, so you won't need too many stuff to get it running.

This example explains how to create a minimal Linux based base system using BusyBox as a base for the userland part of the system.

== Minimal configuration ==
You can start with this '''[http://data.nathael.net/Dev/Base/BusyBox/config_mini_example_2025-01-10 example minimal config]'''. 
Some information about my choices :
* This configuration is based upon the "defaultconfig", but with many modifications (not all listed here)
* No "/usr" support (all binaries under /bin and /sbin)
* Archival utilities limited to tar with "xz" and "bz2" support
* Removed console utilities
* Removed most users handling utilities : users should be known when building the system (or added by direct editting of the files)
* Removed disk partitionning and formatting utilities save for UBIFS
* Removed runit support
* Removed all commands I never used on a full blown system

== Compile using uClibc ==
The options selected for a minimal configuration should not impact the compilation process, unless you want a really small system, which is common when using BusyBox due to storage size constraints. 
In this case using uClibc instead of the GNU libc is a good idea. 
Most information about using uClibc in a cross-compilation toolchain can be found [https://www.uclibc.org/ on uClibc website]. 
You will then need to use the cross-compilation prefix of your toolchain to build BusyBox.

With a stripped down BusyBox, you may well end up with :
Final link with: <none>
But note that in this case you'll still need the selected libc (uClibc) !

== Directories and links ==
Here is a very simple set of directories for a configuration without "/usr", according to the minimal configuration given above :
mkdir -p dev etc lib/{modules,firmware} proc root run sys var/{log,spool/cron}
Then add some links :
ln -s run/tmp tmp
ln -s ../run/tmp var/tmp

== Libraries ==
As this is a very simple system the set of libraries should be very limited. You may need additional ones for your application binaries so I cannot give you a full list, but if you chose to have dynamically linked binaries (which is usually a good idea if your system has more than one or two binaries) you will always need these two :
* The dynamic linker/loader (name depending on the target architecture/triplet) : ld-linux-*.so.*
* the libc : libc.so.6
In order to check for additional library requirements, have a look at this part in the second example.

Once you know which libraries you need, you'll need to figure which files to put in which directory for each library.

Unless you specified an absolute or relative pathname during the linking stage of the compilation of your binaries, there is no "fixed" location for each library file, save maybe the dynamic linker/loader (ld-linux-*.so.*), which usually goes under "/lib", and the dynamic linker will end up looking for libraries in some "default" path which usually includes "/lib". 
So the easy way is to create a single "/lib" directory (remember that we chose to desactivate the use of "/usr" in BusyBox configuration).

As for the files, for the dynamic linker/loader and the libc, the files should be shipped with your cross-compilation toolchain. If you're using the toolchain packaged by Debian, then you will find them under "/usr/${triplet}/lib/" if you installed "libc6-*-cross" package, or under "/usr/lib/${triplet}/" if you installed "libc6:*" package (* is for the Debian architecture name, while you should [[Dev/Embedded/Rootfs/BusyBox/Example2#First,_the_answer_about_the_"triplet"|read the bits I collected about the ${triplet} in the second BusyBox example page]]).

== Bootup script(s) ==
Now Busybox seems to support two init systems : the historic one sharing similarities to SysVinit (without the runlevels) and one similar to runnit.
I choose to disable runnit support in this minimal configuration, so the "init" applet will look for the "/etc/inittab" configuration file. 
There is an example one under "examples/" in BusyBox source tree. 
Anyway, even without this file the applet will look for a script called "/etc/init.d/rcS" and, even if it found none, start an "askfirst" shell (display the message "Please press Enter to activate this console." which would then give you a prompt). All the details are explained in the example inittab file in BusyBox sources.

So here is a short list of files for the init part of the base system :
* /etc/inittab
* /etc/init.d/rcS
* Other service or configuration script(s)

What you put in each file depends on your application and your needs, even if some parts are hard to avoid and thus common to every system, like the initial mounts of /dev and /proc at least.

In SysVinit the rcS script (called by init according to inittab content) calls "/etc/init.d/rc" for the runlevel S, which will start all scripts from "/etc/rcS.d", and after this, init will change to the default runlevel configured in inittab, which will call "/etc/init.d/rc" for the default runlevel (usually 2) which in turn will start all scripts from the corresponding "/etc/rcN.d" directory.

In busybox there are no runlevels, and usually much less configuration to perform, with this configuration being more "static". 
As such, I usually create a single "startup" script (the "/etc/init.d/rcS" one) which does all the usual system configuration and setup (hostname, mounts, hwclock, modules, sysctl, random init, ...) then the network configuration (static IP or DHCP, firewall, ...) 
Having everything started sequentially by a single script which does not try to read a hundred configuration files is not that much slower than using a heavy, complicated system which tries to run everything in parallel but needs to be heavily configured to avoid race conditions and handle dependencies.

In order to start the services (sshd, inetd, ...) and the main application(s) you have some options :
* add them at the end of the rcS script (using start-stop-daemon if need be for respawn)
* create a separate script for them (or one for each) and call them at the end of the rcS one (still using start-stop-daemon if need be)
* use the "wait", "once" or "respawn" actions in inittab
I usually use the inittab solution, sometimes with a wrapper script.

== Configuration files ==
The list of configuration files depend on what you have selected in you BusyBox configuration and on what you write in your scripts. 
And their content depends on your needs, of course. 
In order to know which ones you'll need, there is no easy way (as far as I know). 
* Some of them are listed within BusyBox configuration menu and help for each entry, so you can start there, reading the help for each entry you have activated (save thoses you think would not need a configuration file, like archiving related utilities).
* You can also look at the content of "/etc" on your development host
* Another solution is to try running the system, try to start the services you want, and check the messages on the console.
Here is a short list of those I have listed/created for this simple example :
* /etc/nologin
* /etc/securetty
* /etc/shells
* /etc/{passwd,shadow,groups}
* ''' TO BE COMPLETED '''

== Application binaries and related files ==
This part is really only up to you and your application.

As this simple BusyBox example does not include any kind of "application packaging" support there's not need (save for your mental health) to stick to any particular organisation for your files.

Remember that if your binaries rely on some more libs than those you already put under "/lib" (or any other place you chose for them), then you'll need to add them to your base file system too.