Tool/software:
hello
In SDK 10.6, we want to use the UFS + OSPI boot mode. What areas need to be modified?
thanks
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Tool/software:
hello
In SDK 10.6, we want to use the UFS + OSPI boot mode. What areas need to be modified?
thanks
Adjust the boot mode to opsi + ufs
Hi,
To Begin with, Do you have OSPI boot verified. That should be easy to get working.
Are you trying things out on Custom Board or EVM?
What is the boot flow you will be using? SPL or SBL?
We do not have SDK 10.6. We only have SDK 10.0 and 10.1. The next is going to be SDK 11.0.
Regards,
Tanmay
hello Tanmay Patil
We haven't verified the OSPI boot yet; we are currently using SD card boot.
We are developing on a custom board.
We want to use SBL boot.
I apologize for the version number mistake; it should be SDK 10.0.
Does it support the boot mode of OSPI + UFS?
BR,
liupt
Hi
Does it support the boot mode of OSPI + UFS?
BR,
Yes, It should not be an issue to do this.
OSPI SBL is supported out of box. For having the ufs file system, please consult this FAQ
I am assuming that all your bootloader images (r5-sbl, atf, optee*, a72-spl*, u-boot* and kernel) (* marked items are optional in SBL) will be in OSPI and the filesystem to be used will be in UFS. Let me know if this is not the case.
Regards,
Tanmay
hi Tanmay Patil
setenv bootargs console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02880000 root=/dev/sdb1 rootwait
setenv bootcmd "ufs init; scsi scan; ext4load scsi 1 0x82000000 boot/Image; ext4load scsi 1 0x81200000 boot/dtb/ti/k3-j784s4-evm.dtb; booti 0x82000000 - 0x81200000"
boot
After doing this, do I need to change the boot mode? Because there is no UFS mode not in the boot mode settings.
If I want to use the OSPI + UFS boot method:
psdkla/board-support/ti-linux-kernel-6.6.32+git-ti/arch/arm64/boot/dts/ti/k3-j721e-common-proc-board.dts
file to change:dts
chosen {
stdout-path = "serial2:115200n8";
bootargs = "console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 root=/dev/sdb1 rw rootfstype=ext4 rootwait";
};
Is that all I need to do?
Now there is another issue: In SDK 10.1, psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos
seems to be deprecated. Currently, we are using ipc_rtos_echo_test
.
To support the OSPI + UFS boot method, should I port boot.c
from psdkra/mcusw/mcuss_demos/boot_app_mcu_rtos
to boot_app_mcu_rtos
?
BR,
liupt
Hi,
I want to get further clarity on the boot flow you will be using. Can you just list what stages of boot binary will be in which memory?
Regards,
Tanmay
hello
In our previous project, we used OSPI + eMMC for booting.
The boot files in the diagram are located in the NOR flash.
BR
liupt
Hi,
The boot files in the diagram are located in the NOR flash.
If this is the case, then you don't need a UFS boot mode right. OSPI boot mode will work for you.
Then your filesystem seems to be in UFS which can be attached from u-boot/kernel. It seems that you used optimised SBL boot flow in previous project. In this case kernel can initialise the UFS and mount it to access the filesystem. This is the same as what is done in the FAQ.
Regards,
Tanmay
hi
"In SDK10, the MCU software being used is ipc_rtos_echo_test
. Is there a patch available to add all boot-related functionalities into this program?"
Hi,
I recommend raising a new E2E for this as this has nothing related to UFS. This helps us get the right experts to answer.
Closing this thread.
Best Regards,
Keerthy