Re: [PATCH] board: ti: am62x: Add variable device tree in env

2023-07-31 Thread Jason Kacines
On Mon, Jul 31, 2023 at 09:36:38AM -0500, Andrew Davis wrote:
> On 7/31/23 9:27 AM, Jason Kacines wrote:
> > Added variable default_device_tree that grabs from defconfig. Prevents
> > needing to change this variable in two locations if using a separate
> > device tree. In the future, it would be a good idea to remove this logic
> > completely, but this will help reduce complications.
> > 
> 
> If there are more than one possible DT for a given configuration, then
> we should have logic in `findfdt` to handle that. Not sure what having
> this set from kconfig will help in practice.
> 
> Plus this kconfig is the DT bundled with SPL/U-Boot, but here you are using
> it to set the name of the DT to load for kernel (in theory these should have
> the same name but it still feels like a misuse).

This is a good point, not directly related to kconfig. Thank you. Ignore
this patch.

Jason

> 
> How about we just skip to removing this logic as you suggest, set name_fdt
> directly and remove the `default_device_tree` env var.
> 
> Andrew
> 
> > Signed-off-by: Jason Kacines 
> > ---
> >   board/ti/am62x/am62x.env | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/board/ti/am62x/am62x.env b/board/ti/am62x/am62x.env
> > index bb37d21de6..ee3d5a6b5f 100644
> > --- a/board/ti/am62x/am62x.env
> > +++ b/board/ti/am62x/am62x.env
> > @@ -1,7 +1,7 @@
> >   #include 
> >   #include 
> > -default_device_tree=ti/k3-am625-sk.dtb
> > +default_device_tree=CONFIG_DEFAULT_DEVICE_TREE.dtb
> >   findfdt=
> > setenv name_fdt ${default_device_tree};
> > setenv fdtfile ${name_fdt}


[PATCH] board: ti: am62x: Add variable device tree in env

2023-07-31 Thread Jason Kacines
Added variable default_device_tree that grabs from defconfig. Prevents
needing to change this variable in two locations if using a separate
device tree. In the future, it would be a good idea to remove this logic
completely, but this will help reduce complications.

Signed-off-by: Jason Kacines 
---
 board/ti/am62x/am62x.env | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/board/ti/am62x/am62x.env b/board/ti/am62x/am62x.env
index bb37d21de6..ee3d5a6b5f 100644
--- a/board/ti/am62x/am62x.env
+++ b/board/ti/am62x/am62x.env
@@ -1,7 +1,7 @@
 #include 
 #include 
 
-default_device_tree=ti/k3-am625-sk.dtb
+default_device_tree=CONFIG_DEFAULT_DEVICE_TREE.dtb
 findfdt=
setenv name_fdt ${default_device_tree};
setenv fdtfile ${name_fdt}
-- 
2.34.1



[PATCH] docs: boards: ti: add openocd spl debugging docs

2023-07-21 Thread Jason Kacines
Add documentation on how to use OpenOCD to debug U-Boot for TI K3
Generation boards.

Signed-off-by: Jason Kacines 
---
 doc/board/ti/am62x_openocd.rst | 248 +
 doc/board/ti/k3.rst|  20 ++-
 2 files changed, 265 insertions(+), 3 deletions(-)
 create mode 100644 doc/board/ti/am62x_openocd.rst

diff --git a/doc/board/ti/am62x_openocd.rst b/doc/board/ti/am62x_openocd.rst
new file mode 100644
index 00..4e33bd6f58
--- /dev/null
+++ b/doc/board/ti/am62x_openocd.rst
@@ -0,0 +1,248 @@
+.. SPDX-License-Identifier: GPL-2.0+ OR BSD-3-Clause
+.. sectionauthor:: Jason Kacines 
+
+Debugging SPL in OpenOCD
+
+
+The following section demonstrates how to connect a board to OpenOCD and
+load the SPL symbols for debugging with a K3 generation device. For the 
+guide below, users are expected to generate custom binaries, boot their 
+board from an SD card and work with OpenOCD in a Linux environment. This 
+guide uses the AM625-SK for device specific examples but can be extended 
+to any K3 generation device.
+
+Step 1: Downloading OpenOCD
+---
+
+Download OpenOCD using the following command.
+
+.. code-block:: bash
+   
+   sudo apt-get install openocd
+
+.. note:: 
+   
+   OpenOCD version 0.12.0 is required to connect to the AM625-SK. Some 
+   major GNU/Linux distros do not support version 0.12.0. Check the 
+   version of OpenOCD with ``openocd -v``
+   
+**For OpenOCD installations prior to version 0.12.0:**
+   
+Clone the OpenOCD source code (https://openocd.org/).
+
+.. code-block:: bash
+
+   git clone https://git.code.sf.net/p/openocd/code openocd-code
+
+Move the required config files to the package installation of OpenOCD.
+
+.. code-block:: bash
+
+   cd {OpenOCD Source}
+   cp tcl/board/ti_am625evm.cfg /usr/local/share/openocd/scripts/board
+   cp tcl/target/ti_k3.cfg /usr/local/share/openocd/scripts/target
+
+Now you can move on to SK/EVM Setup to prepare your SK/EVM for debugging.
+
+Step 2: SK/EVM Setup
+
+
+Make the appropriate board cable connections.
+
+.. note:: 
+   
+   Ensure that the BOOT MODE switches are set appropriately for an SD 
+   Card boot (refer to the TRM for boot mode switch settings). For 
+   AM62x devices, refer to :doc:`/board/ti/am62x_sk`.
+
+After connecting each of the cables from the figure above, run the
+following command to ensure that each connection is established.
+
+.. code-block:: bash
+
+   sudo dmesg | grep tty
+
+An output similar to the figure below should appear.
+
+::
+
+   [XX.XX] usb 1-5.3.2.2: FTDI USB Serial Device converter now 
attached to ttyUSB0 <- Used for UART Flashing, UART boot, Linux Kernel, 
U-Boot
+   [XX.XX] usb 1-5.3.2.2: FTDI USB Serial Device converter now 
attached to ttyUSB1
+   [XX.XX] usb 1-5.3.2.2: FTDI USB Serial Device converter now 
attached to ttyUSB2 <- Used for Console for DM R5F (WKUP R5F)
+   [XX.XX] usb 1-5.3.2.2: FTDI USB Serial Device converter now 
attached to ttyUSB3 <- Used for Console on MCU M4F
+   [XX.XX] cdc_acm 1-5.3.1:1.0: ttyACM0: USB ACM device
+   [XX.XX] cdc_acm 1-5.3.1:1.3: ttyACM1: USB ACM device
+
+Open a serial connection with a baud rate of 115200 to view the kernel
+and U-Boot logs. Use the following command or a serial monitor of your
+choice.
+
+.. code-block:: bash
+
+   sudo picocom -b 115200 /dev/ttyUSB0
+
+Step 3: OpenOCD Debugging
+-
+
+Now that OpenOCD has been configured, launch an OpenOCD server with the
+following command.
+
+.. code-block:: bash
+
+   openocd -f board/ti_am625evm.cfg
+
+Below is an example of what the output of this command will print.
+
+::
+
+   Info : Listening on port  for tcl connections
+   Info : Listening on port  for telnet connections
+   Info : XDS110: connected
+   Info : XDS110: vid/pid = 0451/bef3
+   Info : XDS110: firmware version = 3.0.0.20
+   Info : XDS110: hardware version = 0x002f
+   Info : XDS110: connected to target via JTAG
+   Info : XDS110: TCK set to 2500 kHz
+   Info : clock speed 2500 kHz
+   Info : JTAG tap: am625.cpu tap/device found: 0x0bb7e02f (mfg: 0x017 
(Texas Instruments), part: 0xbb7e, ver: 0x0)
+   Info : starting gdb server for am625.cpu.sysctrl on 
+   Info : Listening on port  for gdb connections
+   Info : starting gdb server for am625.cpu.a53.0 on 3334
+   Info : Listening on port 3334 for gdb connections
+   Info : starting gdb server for am625.cpu.a53.1 on 3335
+   Info : Listening on port 3335 for gdb connections
+   Info : starting gdb server for am625.cpu.a53.2 on 3336
+   Info : Listening on port 3336 for gdb connections
+   Info : starting gdb server for am625.cpu.a53.3 on 3337
+   Info : Listening on port 3337 for gdb co

[RFC PATCH 3/3] board: ti: am62x: Add am62x_evm defconfig fragments

2023-07-11 Thread Jason Kacines
Introduce am62x_evm defconfig fragments that will be used on top of the
base wakeup defconfigs. The usage will be as follows:

make <...> am62x_r5_defconfig am62x_evm_r5.config
make <...> am62x_a53_defconfig am62x_evm_a53.config

This will use the Makefile changes previously mentioned to access the
.config fragments from /board/../

Also remove the original am62x_evm defconfigs now that fragments will be
used to support to the board.

Signed-off-by: Jason Kacines 
---
 board/ti/am62x/am62x_evm_a53.config |  38 +
 board/ti/am62x/am62x_evm_r5.config  |  51 +++
 configs/am62x_evm_a53_defconfig | 104 ---
 configs/am62x_evm_r5_defconfig  | 127 
 4 files changed, 89 insertions(+), 231 deletions(-)
 create mode 100644 board/ti/am62x/am62x_evm_a53.config
 create mode 100644 board/ti/am62x/am62x_evm_r5.config
 delete mode 100644 configs/am62x_evm_a53_defconfig
 delete mode 100644 configs/am62x_evm_r5_defconfig

diff --git a/board/ti/am62x/am62x_evm_a53.config 
b/board/ti/am62x/am62x_evm_a53.config
new file mode 100644
index 00..383bb4597a
--- /dev/null
+++ b/board/ti/am62x/am62x_evm_a53.config
@@ -0,0 +1,38 @@
+# CONFIG_TI_SECURE_DEVICE is not set
+CONFIG_SF_DEFAULT_SPEED=2500
+CONFIG_SPL_DM_SPI=y
+CONFIG_DEFAULT_DEVICE_TREE="k3-am625-sk"
+CONFIG_SPL_OF_LIST="k3-am625-sk"
+CONFIG_OF_LIST="k3-am625-sk"
+CONFIG_SPL_SPI_FLASH_SUPPORT=y
+CONFIG_SPL_SPI=y
+CONFIG_SPL_SYS_REPORT_STACK_F_USAGE=y
+CONFIG_SPL_DM_SPI_FLASH=y
+# CONFIG_SPL_SPI_FLASH_TINY is not set
+CONFIG_SPL_SPI_FLASH_SFDP_SUPPORT=y
+CONFIG_SPL_SPI_LOAD=y
+CONFIG_SYS_SPI_U_BOOT_OFFS=0x28
+CONFIG_SPL_YMODEM_SUPPORT=y
+CONFIG_SYS_BOOTM_LEN=0x80
+CONFIG_CMD_PXE=y
+CONFIG_CMD_DHCP=y
+CONFIG_NET_RANDOM_ETHADDR=y
+CONFIG_DMA_CHANNELS=y
+CONFIG_TI_K3_NAVSS_UDMA=y
+CONFIG_MMC_SDHCI_ADMA=y
+CONFIG_SPL_MMC_SDHCI_ADMA=y
+CONFIG_DM_SPI_FLASH=y
+CONFIG_SPI_FLASH=y
+CONFIG_SPI_FLASH_SFDP_SUPPORT=y
+CONFIG_SPI_FLASH_SOFT_RESET=y
+CONFIG_SPI_FLASH_SOFT_RESET_ON_BOOT=y
+CONFIG_SPI_FLASH_SPANSION=y
+CONFIG_SPI_FLASH_S28HX_T=y
+CONFIG_NET=y
+CONFIG_PHY_TI_DP83867=y
+CONFIG_PHY_FIXED=y
+CONFIG_TI_AM65_CPSW_NUSS=y
+CONFIG_PHY=y
+CONFIG_SPI=y
+CONFIG_DM_SPI=y
+CONFIG_CADENCE_QSPI=y
diff --git a/board/ti/am62x/am62x_evm_r5.config 
b/board/ti/am62x/am62x_evm_r5.config
new file mode 100644
index 00..5dffab74f6
--- /dev/null
+++ b/board/ti/am62x/am62x_evm_r5.config
@@ -0,0 +1,51 @@
+# CONFIG_TI_SECURE_DEVICE is not set
+CONFIG_SYS_MALLOC_LEN=0x0800
+CONFIG_SYS_MALLOC_F_LEN=0x9000
+CONFIG_NR_DRAM_BANKS=2
+CONFIG_SF_DEFAULT_SPEED=2500
+CONFIG_SF_DEFAULT_MODE=0
+CONFIG_ENV_SIZE=0x2
+CONFIG_GPIO=y
+CONFIG_DM_GPIO=y
+CONFIG_SPL_DM_SPI=y
+CONFIG_DEFAULT_DEVICE_TREE="k3-am625-r5-sk"
+CONFIG_SPL_DRIVERS_MISC=y
+CONFIG_SPL_SPI_FLASH_SUPPORT=y
+CONFIG_SPL_SPI=y
+CONFIG_I2C=y
+CONFIG_INPUT=y
+CONFIG_NET=y
+CONFIG_BOOTDEV_ETH=y
+CONFIG_SPL_DM_SPI_FLASH=y
+CONFIG_SPL_RAM_SUPPORT=y
+CONFIG_SPL_RAM_DEVICE=y
+# CONFIG_SPL_SPI_FLASH_TINY is not set
+CONFIG_SPL_SPI_FLASH_SFDP_SUPPORT=y
+CONFIG_SPL_SPI_LOAD=y
+CONFIG_SYS_SPI_U_BOOT_OFFS=0x8
+CONFIG_SPL_YMODEM_SUPPORT=y
+CONFIG_CMD_ASKENV=y
+CONFIG_CMD_DFU=y
+CONFIG_SPL_MULTI_DTB_FIT=y
+CONFIG_SPL_MULTI_DTB_FIT_NO_COMPRESSION=y
+CONFIG_SYS_RELOC_GD_ENV_ADDR=y
+CONFIG_DA8XX_GPIO=y
+CONFIG_SPL_MISC=y
+CONFIG_ESM_K3=y
+CONFIG_MMC_SDHCI_ADMA=y
+CONFIG_SPL_MMC_SDHCI_ADMA=y
+CONFIG_DM_SPI=y
+CONFIG_DM_SPI_FLASH=y
+CONFIG_SPI=y
+CONFIG_SPI_FLASH=y
+CONFIG_SPI_FLASH_SFDP_SUPPORT=y
+CONFIG_SPI_FLASH_SOFT_RESET=y
+CONFIG_SPI_FLASH_SOFT_RESET_ON_BOOT=y
+CONFIG_SPI_FLASH_SPANSION=y
+CONFIG_SPI_FLASH_S28HX_T=y
+CONFIG_CADENCE_QSPI=y
+CONFIG_PINCTRL=y
+# CONFIG_PINCTRL_GENERIC is not set
+CONFIG_SPL_PINCTRL=y
+# CONFIG_SPL_PINCTRL_GENERIC is not set
+CONFIG_PINCTRL_SINGLE=y
diff --git a/configs/am62x_evm_a53_defconfig b/configs/am62x_evm_a53_defconfig
deleted file mode 100644
index 7c3bc184cf..00
--- a/configs/am62x_evm_a53_defconfig
+++ /dev/null
@@ -1,104 +0,0 @@
-CONFIG_ARM=y
-CONFIG_ARCH_K3=y
-CONFIG_TI_SECURE_DEVICE=y
-CONFIG_SYS_MALLOC_F_LEN=0x8000
-CONFIG_SPL_LIBCOMMON_SUPPORT=y
-CONFIG_SPL_LIBGENERIC_SUPPORT=y
-CONFIG_NR_DRAM_BANKS=2
-CONFIG_SOC_K3_AM625=y
-CONFIG_K3_ATF_LOAD_ADDR=0x9e78
-CONFIG_TARGET_AM625_A53_EVM=y
-CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=y
-CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x80b8
-CONFIG_SF_DEFAULT_SPEED=2500
-CONFIG_SPL_DM_SPI=y
-CONFIG_DEFAULT_DEVICE_TREE="k3-am625-sk"
-CONFIG_SPL_TEXT_BASE=0x8008
-CONFIG_OF_LIBFDT_OVERLAY=y
-CONFIG_DM_RESET=y
-CONFIG_SPL_MMC=y
-CONFIG_SPL_SERIAL=y
-CONFIG_SPL_STACK_R_ADDR=0x8200
-CONFIG_SPL_SIZE_LIMIT=0x4
-CONFIG_SPL_SIZE_LIMIT_PROVIDE_STACK=0x800
-CONFIG_SPL_FS_FAT=y
-CONFIG_SPL_LIBDISK_SUPPORT=y
-CONFIG_SPL_SPI_FLASH_SUPPORT=y
-CONFIG_SPL_SPI=y
-# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set
-CONFIG_SPL_LOAD_FIT=y
-CONFIG_SPL_LOAD_FIT_ADDRESS=0x8100
-CONFIG_DISTRO_DEFAULTS=y
-CONFIG_BOOTCOMMA

[RFC PATCH 2/3] configs: Add am62x wakeup defconfigs

2023-07-11 Thread Jason Kacines
Introduce a minimal platform wakeup configuration for am62x devices.
These defconfigs are meant to serve as a foundation for custom boards to
build upon by only including necessary components to boot the device.

Defconfig fragments will be used to expand upon these base files.

Signed-off-by: Jason Kacines 
---
 configs/am62x_a53_defconfig | 78 ++
 configs/am62x_r5_defconfig  | 94 +
 2 files changed, 172 insertions(+)
 create mode 100644 configs/am62x_a53_defconfig
 create mode 100644 configs/am62x_r5_defconfig

diff --git a/configs/am62x_a53_defconfig b/configs/am62x_a53_defconfig
new file mode 100644
index 00..baaa229b34
--- /dev/null
+++ b/configs/am62x_a53_defconfig
@@ -0,0 +1,78 @@
+CONFIG_ARM=y
+CONFIG_ARCH_K3=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_SYS_MALLOC_F_LEN=0x8000
+CONFIG_SPL_LIBCOMMON_SUPPORT=y
+CONFIG_SPL_LIBGENERIC_SUPPORT=y
+CONFIG_NR_DRAM_BANKS=2
+CONFIG_SOC_K3_AM625=y
+CONFIG_K3_ATF_LOAD_ADDR=0x9e78
+CONFIG_TARGET_AM625_A53_EVM=y
+CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=y
+CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x80b8
+CONFIG_DEFAULT_DEVICE_TREE="k3-am625-sk"
+CONFIG_SPL_TEXT_BASE=0x8008
+CONFIG_OF_LIBFDT_OVERLAY=y
+CONFIG_DM_RESET=y
+CONFIG_SPL_MMC=y
+CONFIG_SPL_SERIAL=y
+CONFIG_SPL_STACK_R_ADDR=0x8200
+CONFIG_SPL_SIZE_LIMIT=0x4
+CONFIG_SPL_SIZE_LIMIT_PROVIDE_STACK=0x800
+CONFIG_SPL_FS_FAT=y
+CONFIG_SPL_LIBDISK_SUPPORT=y
+# CONFIG_CMD_PXE is not set
+# CONFIG_CMD_DHCP is not set
+# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set
+CONFIG_SPL_LOAD_FIT=y
+CONFIG_SPL_LOAD_FIT_ADDRESS=0x8100
+CONFIG_DISTRO_DEFAULTS=y
+CONFIG_BOOTCOMMAND="run findfdt; run envboot; run init_${boot}; run 
get_kern_${boot}; run get_fdt_${boot}; run get_overlay_${boot}; run run_kern; 
setenv fdtfile ti/${name_fdt}; run distro_bootcmd"
+CONFIG_SPL_MAX_SIZE=0x58000
+CONFIG_SPL_HAS_BSS_LINKER_SECTION=y
+CONFIG_SPL_BSS_START_ADDR=0x80c8
+CONFIG_SPL_BSS_MAX_SIZE=0x8
+CONFIG_SPL_SYS_MALLOC_SIMPLE=y
+CONFIG_SPL_STACK_R=y
+CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR=y
+CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR=0x1400
+CONFIG_SPL_FS_LOAD_PAYLOAD_NAME="u-boot.img"
+CONFIG_SPL_DM_MAILBOX=y
+CONFIG_SPL_POWER_DOMAIN=y
+CONFIG_CMD_MMC=y
+CONFIG_OF_CONTROL=y
+CONFIG_SPL_OF_CONTROL=y
+CONFIG_MULTI_DTB_FIT=y
+CONFIG_SPL_MULTI_DTB_FIT=y
+CONFIG_SPL_MULTI_DTB_FIT_NO_COMPRESSION=y
+# CONFIG_NET is not set
+CONFIG_SPL_DM=y
+CONFIG_SPL_DM_SEQ_ALIAS=y
+CONFIG_REGMAP=y
+CONFIG_SPL_REGMAP=y
+CONFIG_SPL_OF_TRANSLATE=y
+CONFIG_CLK=y
+CONFIG_SPL_CLK=y
+CONFIG_CLK_TI_SCI=y
+CONFIG_TI_SCI_PROTOCOL=y
+CONFIG_DM_MAILBOX=y
+CONFIG_K3_SEC_PROXY=y
+CONFIG_MMC_SDHCI=y
+CONFIG_MMC_SDHCI_AM654=y
+CONFIG_PINCTRL=y
+CONFIG_SPL_PINCTRL=y
+CONFIG_PINCTRL_SINGLE=y
+CONFIG_POWER_DOMAIN=y
+# CONFIG_SPL_YMODEM_SUPPORT is not set
+CONFIG_TI_SCI_POWER_DOMAIN=y
+CONFIG_K3_SYSTEM_CONTROLLER=y
+CONFIG_REMOTEPROC_TI_K3_ARM64=y
+CONFIG_RESET_TI_SCI=y
+CONFIG_DM_SERIAL=y
+CONFIG_SOC_DEVICE=y
+CONFIG_SOC_DEVICE_TI_K3=y
+CONFIG_SOC_TI=y
+CONFIG_SYSRESET=y
+CONFIG_SPL_SYSRESET=y
+CONFIG_SYSRESET_TI_SCI=y
+CONFIG_FS_FAT_MAX_CLUSTSIZE=16384
diff --git a/configs/am62x_r5_defconfig b/configs/am62x_r5_defconfig
new file mode 100644
index 00..64ae24bc90
--- /dev/null
+++ b/configs/am62x_r5_defconfig
@@ -0,0 +1,94 @@
+CONFIG_ARM=y
+CONFIG_ARCH_K3=y
+CONFIG_TI_SECURE_DEVICE=y
+CONFIG_SPL_LIBCOMMON_SUPPORT=y
+CONFIG_SPL_LIBGENERIC_SUPPORT=y
+CONFIG_SOC_K3_AM625=y
+CONFIG_TARGET_AM625_R5_EVM=y
+CONFIG_HAS_CUSTOM_SYS_INIT_SP_ADDR=y
+CONFIG_CUSTOM_SYS_INIT_SP_ADDR=0x43c3a7f0
+CONFIG_ENV_IS_NOWHERE=y
+CONFIG_DEFAULT_DEVICE_TREE="k3-am625-r5-sk"
+CONFIG_SPL_TEXT_BASE=0x43c0
+CONFIG_DM_RESET=y
+CONFIG_SPL_MMC=y
+CONFIG_SPL_SERIAL=y
+CONFIG_SPL_STACK_R_ADDR=0x8200
+CONFIG_SPL_SYS_MALLOC_F_LEN=0x7000
+CONFIG_SPL_SIZE_LIMIT=0x3A7F0
+CONFIG_SPL_SIZE_LIMIT_PROVIDE_STACK=0x3500
+CONFIG_SPL_FS_FAT=y
+CONFIG_SPL_LIBDISK_SUPPORT=y
+CONFIG_SPL_LOAD_FIT=y
+CONFIG_SPL_LOAD_FIT_ADDRESS=0x8008
+CONFIG_SPL_FIT_IMAGE_POST_PROCESS=y
+# CONFIG_LEGACY_IMAGE_FORMAT is not set
+# CONFIG_DISPLAY_CPUINFO is not set
+CONFIG_SPL_SIZE_LIMIT_SUBTRACT_GD=y
+CONFIG_SPL_SIZE_LIMIT_SUBTRACT_MALLOC=y
+CONFIG_SPL_MAX_SIZE=0x3B000
+CONFIG_SPL_PAD_TO=0x0
+CONFIG_SPL_HAS_BSS_LINKER_SECTION=y
+CONFIG_SPL_BSS_START_ADDR=0x43c3b000
+CONFIG_SPL_BSS_MAX_SIZE=0x3000
+CONFIG_SPL_SYS_REPORT_STACK_F_USAGE=y
+CONFIG_SPL_SYS_MALLOC_SIMPLE=y
+CONFIG_SPL_STACK_R=y
+CONFIG_SPL_SEPARATE_BSS=y
+CONFIG_SYS_SPL_MALLOC=y
+CONFIG_HAS_CUSTOM_SPL_MALLOC_START=y
+CONFIG_CUSTOM_SYS_SPL_MALLOC_ADDR=0x8400
+CONFIG_SYS_SPL_MALLOC_SIZE=0x100
+CONFIG_SPL_EARLY_BSS=y
+CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_USE_SECTOR=y
+CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR=0x400
+CONFIG_SPL_DM_MAILBOX=y
+CONFIG_SPL_DM_RESET=y
+CONFIG_SPL_POWER_DOMAIN=y
+CONFIG_SPL_REMOTEPROC=y
+# CONFIG_SPL_YMODEM_SUPPORT is not set
+CONFIG_HUSH_PARSER=y
+CONFIG_CMD_GPT=y
+CONFIG_CMD_MMC=y
+CONFIG_CMD_REMOTEPROC=y
+# CONFIG_C

[RFC PATCH 1/3] scripts: kconfig: Add config fragment support in board/../

2023-07-11 Thread Jason Kacines
Add support to config fragments (.config) located in the /board
directory. This will allow only base defconfigs to live in /configs and
all fragments to live in their respective device directory in /board/..

Signed-off-by: Jason Kacines 
---
 scripts/kconfig/Makefile | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/scripts/kconfig/Makefile b/scripts/kconfig/Makefile
index 12e525ee31..2d97aab8d2 100644
--- a/scripts/kconfig/Makefile
+++ b/scripts/kconfig/Makefile
@@ -99,7 +99,9 @@ endif
 %_config: %_defconfig
@:
 
-configfiles=$(wildcard $(srctree)/kernel/configs/$@ 
$(srctree)/arch/$(SRCARCH)/configs/$@)
+configfiles=$(wildcard $(srctree)/kernel/configs/$@ \
+   $(srctree)/arch/$(SRCARCH)/configs/$@ \
+   $(shell find $(srctree)/board -name "$@"))
 
 %.config: $(obj)/conf
$(if $(call configfiles),, $(error No configuration exists for this 
target on this architecture))
-- 
2.34.1



[RFC PATCH 0/3] Minimal platform configuration

2023-07-11 Thread Jason Kacines
When someone attempts to bring up a custom board using TI SoCs (am62x in
this case), it often takes several days for someone to reduce the
current configuration from the TI EVM/SK boards to a configuration that
works for their board.

The goal of these changes is to allow for a minimal boot configuration
to exist within UBoot that someone can access directly in order to
test their boards for a sign of life before beginning development. This
is all done with the hope to increase ease of use and reduce the
upbringing process from several days to a few hours.

With the use of fragments, the base defconfigs reside in configs/ and
the config fragments reside in board/../

There is still quite a lot of board specific code inside board_init_f()
that will need attention later, however this series begins the process
of splitting the am62x's configs into a separate generic defconfig
everyone can use for new board wakeups with individual board/ti/*.config
fragments for each board varient.

Jason Kacines (3):
  scripts: kconfig: Add config fragment support in board/../
  configs: Add am62x wakeup defconfigs
  board: ti: am62x: Add am62x_evm defconfig fragments

 board/ti/am62x/am62x_evm_a53.config   | 38 +
 board/ti/am62x/am62x_evm_r5.config| 51 ++
 ..._evm_a53_defconfig => am62x_a53_defconfig} | 34 ++--
 ...2x_evm_r5_defconfig => am62x_r5_defconfig} | 53 ---
 scripts/kconfig/Makefile  |  4 +-
 5 files changed, 106 insertions(+), 74 deletions(-)
 create mode 100644 board/ti/am62x/am62x_evm_a53.config
 create mode 100644 board/ti/am62x/am62x_evm_r5.config
 rename configs/{am62x_evm_a53_defconfig => am62x_a53_defconfig} (72%)
 rename configs/{am62x_evm_r5_defconfig => am62x_r5_defconfig} (66%)

-- 
2.34.1