On 18/04/22 8:26 pm, Andrew Davis wrote:
On 4/15/22 9:09 AM, Vignesh Raghavendra wrote:
Add info of boot flow and build steps for AM62x SK.
Signed-off-by: Vignesh Raghavendra vigneshr@ti.com
doc/board/ti/am62x_sk.rst | 231 ++++++++++++++++++++++++++++++++++++++
This isn't specific to the SK, more the AM62x in general, suggest name am62x.rst.
Agreed
[...]
+Build procedure: +---------------- +1. ATF:
+.. code-block:: text
- $ make CROSS_COMPILE=aarch64-none-linux-gnu- ARCH=aarch64 PLAT=k3
TARGET_BOARD=lite SPD=opteed
These compiler names might not be the same as installed by some current package managers (-none), maybe we start by setting up two env vars to point to the two compilers we use:
export CROSS_COMPILE32=arm-none-linux-gnueabihf- export CROSS_COMPILE64=aarch64-none-linux-gnu-
Then just use those below, that way we only have to switch these first two commands if we have a different compiler.
CROSS_COMPILE=$CROSS_COMPILE32
Good idea, thanks!
etc..
+2. OPTEE:
+.. code-block:: text
- $ make PLATFORM=k3 CFG_ARM64_core=y
CROSS_COMPILE=arm-none-linux-gnueabihf- CROSS_COMPILE64=aarch64-none-linux-gnu-
+3. U-Boot:
+* 3.1 R5:
+.. code-block:: text
- $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf-
am62x_evm_r5_defconfig O=/tmp/r5
Lets not pollute directories outside of the current one, suggest `O=build/r5` and the same below.
Sure, will fix!
Regards Vignesh