J784S4XEVM: While booting the kernel from OSPI NOR, getting this error,

Hi Manan,

What rootfs has been flashed at the 0x2700000 address?

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/920696/faq-tda4vm-flashing-the-tiny-rootfs-image-using-uniflash-on-ospi

There are many steps to flash the UBIFS file system.

- Keerthy

yes i am using 0x2700000 address for UBI tiny filesystem

 and i am trying with OSPI NOR mode to flash file system.

i am not using SDCARD, i am using OSPI NOR 0 - 3EF0000 address to flash all the binaries

Below is my offset where i am flashing images 

• sbl_cust_img_mcu1_0_release.tiimage at an offset of 0x0

• tifs.bin at an offset of 0x8000

• boot_app_ospi_linux_mcu1_0_freertos_TestApp_release.appimage at an offset of 0x100000

• stage1 image at an offset of 19E0000

• stage2 image at an offset of 2000000

• atf_optee.appimage at an offset of 200000

• tidtb_linux.appimage at an offset of 19C0000

• tikernelimage_linux.appimage at an offset of 2C0000

Manan

Are you using the SDK (which version?) to generate these images and trying things on the EVM?

Regards

Karan

Hi Karan, i am using SDK 8.6.1.3, and i am trying in EVM.

i need to configure k3-j784s4-evm.dts such a way that my ubi filesystem will detect by kernel.i mean rootfs will detect by kernel:

How to set my bootargs in device tree for booting kernel and filesystem from NOR

Manan

I need to replicate the issue and discuss with the team wrt what is missing in the kenel command line which you are passing via chosen node. I want to make sure you've looked at the FAQ below. The difference is that the FAQ uses u-boot instead of updating kernel command line directly.

Regards

Karan

After i configure the bootargs to  bootargs = "console=ttyS2,115200n8 earlycon=serial2 root=/dev/mtdblock8 rw rootfstype=ubifs rootwait"; 

as i added my partition as following

&ospi1 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&mcu_fss0_ospi1_pins_default>;

flash@0{
compatible = "jedec,spi-nor";
reg = <0x0>;
spi-tx-bus-width = <1>;
spi-rx-bus-width = <4>;
spi-max-frequency = <40000000>;
cdns,tshsl-ns = <60>;
cdns,tsd2d-ns = <60>;
cdns,tchsh-ns = <60>;
cdns,tslch-ns = <60>;
cdns,read-delay = <2>;
#address-cells = <1>;
#size-cells = <1>;
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;

partition@0 {
label = "ospi_nor.tiboot3";
reg = <0x0 0x80000>;
};
partition@80000 {
label = "ospi_nor.sysfw";
reg = <0x80000 0x80000>;
};
partition@100000 {
label = "ospi_nor.mcu1_0";
reg = <0x100000 0x100000>;
};
partition@200000 {
label = "ospi_nor.atf";
reg = <0x200000 0xc0000>;
};
partition@2C0000 {
label = "ospi_nor.kernel";
reg = <0x2C0000 0x1700000>;
};
partition@19C0000 {
label = "ospi_nor.dtb";
reg = <0x19C0000 0x20000>;
};
partition@19E0000 {
label = "ospi_nor.lateapp1";
reg = <0x19E0000 0x620000>;
};
partition@2000000 {
label = "ospi_nor.lateapp2";
reg = <0x2000000 0x700000>;
};
partition@2700000 {
label = "ospi_nor.rootfs";
reg = <0x2700000 0x1200000>;
};
partition@3FE0000 {
label = "ospi_nor.phypattern";
reg = <0x3FE0000 0x40000>;
};

};
};
};

getting this error -> 

could you please update on above issue