Hello Nishanth
On 4/19/2025 1:09 AM, Nishanth Menon wrote:
We just have sd/mmc, so set things up for the same
Signed-off-by: Nishanth Menon <n...@ti.com>
---
Changes Since v1:
- None
V1: https://lore.kernel.org/r/20250411225717.3117370-6...@ti.com
board/beagle/beagley-ai/beagley-ai.env | 2 ++
1 file changed, 2 insertions(+)
diff --git a/board/beagle/beagley-ai/beagley-ai.env
b/board/beagle/beagley-ai/beagley-ai.env
index 16a03acfca3c..26f12c8814cc 100644
--- a/board/beagle/beagley-ai/beagley-ai.env
+++ b/board/beagle/beagley-ai/beagley-ai.env
@@ -1,5 +1,6 @@
#include <env/ti/ti_common.env>
#include <env/ti/mmc.env>
+#include <env/ti/k3_dfu.env>
#if CONFIG_CMD_REMOTEPROC
#include <env/ti/k3_rproc.env>
@@ -20,5 +21,6 @@ mmcdev=1
bootpart=1:2
bootdir=/boot
rd_spec=-
+dfu_alt_info=${dfu_alt_info_mmc}
IMO dfu_alt_info_ram could be another valid target for DFU ,
Other platform, set this dfu_alt_info variable before using,
Can we consider this as similar to other platforms ?
rproc_fw_binaries= 0 /lib/firmware/j722s-mcu-r5f0_0-fw 2 /lib/firmware/j722s-main-r5f0_0-fw 3 /lib/firmware/j722s-c71_0-fw 4 /lib/firmware/j722s-c71_1-fw
