AM6442: sbl_emmc_linux

Hi Meet,

Thank you for your support and patience. It works fine now with your suggestion. I modify address in config file. I have an another problem when linux start remoteproc driver although I've set the resources table correctly

#-----------------------------------------------------------------------------#
#                                                                             #
#      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
#                               FOR HS DEVICE                                 #
#                                                                             #
#-----------------------------------------------------------------------------#
#
# By default this config file,
# - points to pre-built flash writer, bootloader for this HS EVM
# - The application image points to relative path of the ipc rpmsg linux application image for this HS EVM
#   - Make sure this application is built before running this script
# - You can customized this config file to point to your own bootloader and/or application images
# - You can use --operation=flashverify if you just want to verify the flash contents and not flash the file.
#

# First point to sbl_uart_uniflash binary, which function's as a server to flash one or more files
--flash-writer=sbl_prebuilt/am64x-evm/sbl_uart_uniflash.release.hs_fs.tiimage

# Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

# Program the OSPI PHY tuning attack vector
--operation=flash-phy-tuning-data

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0
--file=sbl_prebuilt/am64x-evm/sbl_ospi_linux.debug.hs_fs.tiimage --operation=flash --flash-offset=0x0

# Linux image is flashed at 0x800000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/linuxAppimageGen/linux.appimage.hs_fs --operation=flash --flash-offset=0x100000

## u-boot is flashed at 0x300000 car le u-boot.cfg du spl contient #define CONFIG_SYS_SPI_U_BOOT_OFFS 0x300000   
--file=../../tools/boot/u-boot.img --operation=flash --flash-offset=0x300000

# When sending application image, make sure to flash at offset 0x80000 (default) or to whatever offset your bootloader is configured for
--file=../../MesSources/fsi_loopback_interrupt_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash --flash-offset=0x80000

# send the XIP image for this application, no need to specify flash offset since flash offset is specified within the image itself
--file=../../MesSources/fsi_loopback_interrupt_am64x-evm_r5fss0-0_nortos_ti-arm-clang.appimage_xip --operation=flash-xip

DMSC Firmware Version 10.0.8--v10.00.08 (Fiery Fox)
DMSC Firmware revision 0xa
DMSC ABI revision 4.0

KPI_DATA: [BOOTLOADER_PROFILE] Boot Media       : undefined 
KPI_DATA: [BOOTLOADER_PROFILE] Boot Image Size  : 0 KB 
KPI_DATA: [BOOTLOADER_PROFILE] Cores present    : 
KPI_DATA: [BOOTLOADER PROFILE] System_init                      :     376139us 
KPI_DATA: [BOOTLOADER PROFILE] Drivers_open                     :        317us 
KPI_DATA: [BOOTLOADER PROFILE] Board_driversOpen                :      36013us 
KPI_DATA: [BOOTLOADER PROFILE] App_loadImages                   :      30275us 
KPI_DATA: [BOOTLOADER PROFILE] App_loadLinuxImages              :      80377us 
KPI_DATA: [BOOTLOADER_PROFILE] SBL Total Time Taken             :     523123us 

Image loading done, switching to application ...
Starting linux and RTOS/Baremetal applications
NOTICE:  BL31:E v2R.10.R0(rOeleasRe)::v2. 10.0-367-g00f1ec6b8
NOTICE:  BL31: Built : 15:04:15, Dec 10 2024
I/TC: 
I/TC: OP-TEE version: 4.2.0-dev (gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)) #2 Tue Dec 10 15:45:49 UTC 2024 aarch64
I/TC: WARNING: This OP-TEE configuration might be insecure!
I/TC: WARNING: Please check https://optee.readthedocs.io/en/latest/architecture/porting_guidelines.html
I/TC: Primary CPU initializing
I/TC: GIC redistributor base address not provided
I/TC: Assuming default GIC group status and modifier
I/TC: SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
I/TC: HUK Initialized
I/TC: Activated SA2UL device
I/TC: Enabled firewalls for SA2UL TRNG device
I/TC: SA2UL TRNG initialized
I/TC: SA2UL Drivers initialized
I/TC: Primary CPU switching to normal world boot

U-Boot SPL 2024.04-dirty (Dec 10 2024 - 15:38:24 +0100)
SYSFW ABI: 4.0 (firmware rev 0x000a '10.0.8--v10.00.08 (Fiery Fox)')
Trying to boot from SPI
Authentication passed
Authentication passed


U-Boot 2024.04-dirty (Dec 10 2024 - 13:41:21 +0100)

SoC:   AM64X SR2.0 HS-FS
Model: Texas Instruments AM642 EVM
Board: AM64-EVM rev C
DRAM:  2 GiB
Core:  98 devices, 31 uclasses, devicetree: separate
NAND:  0 MiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
ti_sci system-controller@44043000: Message not acknowledged
ti-sci-pm-domains power-controller: ti_sci_power_domain_on: get_device(82) failed (-19)
prueth icssg1-eth: error getting the pruss dev
Failed to probe prueth driver
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1

remote proc driver problem

[ 11.618512] platform 78000000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
[ 11.634372] platform 78000000.r5f: configured R5F for IPC-only mode
[ 11.646741] platform 78000000.r5f: assigned reserved memory node r5f-dma-memory@a0000000
[ 11.676071] k3-m4-rproc 5000000.m4fss: assigned reserved memory node m4f-dma-memory@a4000000
[ 11.688658] k3-m4-rproc 5000000.m4fss: configured M4 for remoteproc mode
[ 11.698208] remoteproc remoteproc0: 78000000.r5f is available
[ 11.705205] k3-m4-rproc 5000000.m4fss: local reset is deasserted for device
[ 11.715013] remoteproc remoteproc0: attaching to 78000000.r5f
[ 11.728195] platform 78000000.r5f: R5F core initialized in IPC-only mode
[ 11.736329] remoteproc remoteproc1: 5000000.m4fss is available
[ 11.750325] rproc-virtio rproc-virtio.0.auto: assigned reserved memory node r5f-dma-memory@a0000000
[ 11.763062] remoteproc remoteproc1: powering up 5000000.m4fss
[ 11.769216] remoteproc remoteproc1: Booting fw image am64-mcu-m4f0_0-fw, size 88248
[ 11.784351] rproc-virtio rproc-virtio.1.auto: assigned reserved memory node m4f-dma-memory@a4000000
[ 11.795119] virtio_rpmsg_bus virtio0: rpmsg host is online
[ 11.800786] virtio_rpmsg_bus virtio0: creating channel ti.ipc4.ping-pong addr 0xd
[ 11.808753] virtio_rpmsg_bus virtio0: creating channel rpmsg_chrdev addr 0xe
[ 11.816479] rproc-virtio rproc-virtio.1.auto: registered virtio0 (type 7)
[ 11.823456] remoteproc remoteproc1: remote processor 5000000.m4fss is now up
[ 11.832148] virtio_rpmsg_bus virtio1: rpmsg host is online
[ 11.837994] rproc-virtio rproc-virtio.0.auto: registered virtio1 (type 7)
[ 11.845066] remoteproc remoteproc0: remote processor 78000000.r5f is now attached
[ 11.856254] platform 78200000.r5f: R5F core may have been powered on by a different host, programmed state (0) != actual state (1)
[ 11.870380] platform 78200000.r5f: configured R5F for IPC-only mode
[ 11.882392] platform 78200000.r5f: assigned reserved memory node r5f-dma-memory@a1000000
[ 11.922670] remoteproc remoteproc2: 78200000.r5f is available
[ 11.945761] remoteproc remoteproc2: attaching to 78200000.r5f
[ 11.951741] Unable to handle kernel paging request at virtual address ffff800085ffffff
[ 11.960352] Mem abort info:
[ 11.963341] ESR = 0x0000000096000007
[ 11.967246] EC = 0x25: DABT (current EL), IL = 32 bits
[ 11.972609] SET = 0, FnV = 0
[ 11.975735] EA = 0, S1PTW = 0
[ 11.979020] FSC = 0x07: level 3 translation fault
[ 11.984029] Data abort info:
[ 11.987081] ISV = 0, ISS = 0x00000007, ISS2 = 0x00000000
[ 11.992779] CM = 0, WnR = 0, TnD = 0, TagAccess = 0
[ 11.998031] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[ 12.007771] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0000000082fba000
[ 12.028484] [ffff800085ffffff] pgd=10000000fffff003, p4d=10000000fffff003, pud=10000000ffffe003, pmd=1000000085f1a003, pte=0000000000000000
[ 12.090576] gpio-mux mux-controller: 2-way mux-controller registered
[ 12.127223] Internal error: Oops: 0000000096000007 [#1] PREEMPT SMP
[ 12.133526] Modules linked in: pru_rproc icss_iep mux_gpio(+) phy_can_transceiver rti_wdt ti_k3_m4_remoteproc ti_k3_r5_remoteproc(+) k3_j72xx_bandgap sa2ul authenc pwm_tiecap m_can_platform pruss overlay at24 m_can can_dev spi_omap2_mcspi cfg80211 bluetooth ecdh_generic ecc rfkill cryptodev(O) fuse drm drm_panel_orientation_quirks backlight ipv6
[ 12.164207] CPU: 1 PID: 169 Comm: (udev-worker) Tainted: G O 6.6.32-ti-g6de6e418c80e-dirty #1
[ 12.174114] Hardware name: Texas Instruments AM642 EVM (DT)
[ 12.179677] pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 12.186630] pc : rproc_handle_resources.constprop.0+0x64/0x18c
[ 12.192476] lr : rproc_boot+0x37c/0x57c
[ 12.196311] sp : ffff800081d636a0
[ 12.199617] x29: ffff800081d636a0 x28: ffff000005e5bf80 x27: ffff0000045e9880
[ 12.206753] x26: ffff0000045e9880 x25: 0000000000000000 x24: ffff800085ffffff
[ 12.213885] x23: 0000000000000000 x22: ffff000006e05038 x21: ffff800081334118
[ 12.221018] x20: 0000000000000000 x19: ffff000006e05000 x18: 0000000000000006
[ 12.228150] x17: 0000000000000000 x16: 0000000000000000 x15: ffffffffffffffff
[ 12.235283] x14: ffffffffffffffff x13: ffffffffffffffff x12: ffffffffffffffff
[ 12.242416] x11: fffffffffffeffff x10: ffffffffffffffff x9 : ffffffffffffffff
[ 12.249548] x8 : ffffffffbfffffff x7 : ffffffffffffffff x6 : ffffffffffffffff
[ 12.256681] x5 : ffff000005c27300 x4 : ffff800086000000 x3 : 00000000000000fd
[ 12.263814] x2 : 00000000ffffffff x1 : ffff800086000003 x0 : ffff800086000000
[ 12.270947] Call trace:
[ 12.273387] rproc_handle_resources.constprop.0+0x64/0x18c
[ 12.278871] rproc_boot+0x37c/0x57c
[ 12.282359] rproc_add+0x184/0x190
[ 12.285760] k3_r5_probe+0x794/0xd3c [ti_k3_r5_remoteproc]
[ 12.291259] platform_probe+0x68/0xc4

My memory mapping

MEMORY CONFIGURATION

name origin length used unused attr fill
---------------------- -------- --------- -------- -------- ---- --------
R5F_VECS 00000000 00000040 00000040 00000000 RWIX
R5F_TCMA 00000040 00007fc0 00000000 00007fc0 RWIX
R5F_TCMB0 41010000 00008000 00000000 00008000 RWIX
FLASH 60100000 00080000 00000000 00080000 RWIX
NON_CACHE_MEM 70060000 00008000 00000000 00008000 RWIX
MSRAM 70080000 00040000 0002c728 000138d8 RWIX
USER_SHM_MEM 701d0000 00000080 00000000 00000080 RWIX
LOG_SHM_MEM 701d0080 00003f80 00000000 00003f80 RWIX
RTOS_NORTOS_IPC_SHM_M 701d4000 0000c000 00000000 0000c000 RWIX
DDR_RESOURCE_TABLE a0100000 00001000 00001000 00000000 RWIX

SEGMENT ALLOCATION MAP

run origin load origin length init length attrs members
---------- ----------- ---------- ----------- ----- -------
00000000 00000000 00000040 00000040 r-x
00000000 00000000 00000040 00000040 r-x .vectors
70080000 70080000 0001a1b0 0001a1b0 r-x
70080000 70080000 00018c80 00018c80 r-x .text
70098c80 70098c80 00001530 00001530 r-- .rodata
7009a200 7009a200 0000f600 00000000 rw-
7009a200 7009a200 00003600 00000000 rw- .bss
7009d800 7009d800 00008000 00000000 rw- .sysmem
700a5800 700a5800 00004000 00000000 rw- .stack
700a9800 700a9800 00001418 00001418 r-x
700a9800 700a9800 00000ae0 00000ae0 r-x .text.hwi
700aa2e0 700aa2e0 000004a0 000004a0 r-x .text.cache
700aa780 700aa780 000002d0 000002d0 r-x .text.mpu
700aaa50 700aaa50 000001c0 000001c0 r-x .text.boot
700aac10 700aac10 00000008 00000008 r-x .text:abort
700aac18 700aac18 00000760 00000760 rw-
700aac18 700aac18 00000760 00000760 rw- .data
700ab378 700ab378 00001400 00000000 r--
700ab378 700ab378 00000100 00000000 r-- .irqstack
700ab478 700ab478 00000100 00000000 r-- .fiqstack
700ab578 700ab578 00001000 00000000 r-- .svcstack
700ac578 700ac578 00000100 00000000 r-- .abortstack
700ac678 700ac678 00000100 00000000 r-- .undefinedstack
a0100000 a0100000 00001000 00001000 r--
a0100000 a0100000 00001000 00001000 r-- .resource_table

-------------------------------------------------------------------------------------------------

Modification of my  DTS for SRAM allocation

&main_r5fss0_core0 {
	bootph-all;
	mboxes = <&mailbox0_cluster2 &mbox_main_r5fss0_core0>;
	memory-region = <&main_r5fss0_core0_dma_memory_region>,
			<&main_r5fss0_core0_memory_region>;
	sram = <&r5f0_0_sram>;
};

&main_r5fss0_core1 {
	bootph-all;
	mboxes = <&mailbox0_cluster2 &mbox_main_r5fss0_core1>;
	memory-region = <&main_r5fss0_core1_dma_memory_region>,
			<&main_r5fss0_core1_memory_region>;
};

&main_r5fss1_core0 {
	bootph-all;
	mboxes = <&mailbox0_cluster4 &mbox_main_r5fss1_core0>;
	memory-region = <&main_r5fss1_core0_dma_memory_region>,
			<&main_r5fss1_core0_memory_region>;
};

&main_r5fss1_core1 {
	bootph-all;
	mboxes = <&mailbox0_cluster4 &mbox_main_r5fss1_core1>;
	memory-region = <&main_r5fss1_core1_dma_memory_region>,
			<&main_r5fss1_core1_memory_region>;
};

&mcu_m4fss {
	bootph-all;
	mboxes = <&mailbox0_cluster6 &mbox_m4_0>;
	memory-region = <&mcu_m4fss_dma_memory_region>,
			<&mcu_m4fss_memory_region>;
	sram = <&m4f_sram>;	
  status = "okay";
};

&cbass_main {
	oc_sram: sram@70000000 {
		compatible = "mmio-sram";
		reg = <0x00 0x70000000 0x00 0x200000>;
		#address-cells = <1>;
		#size-cells = <1>;
		ranges = <0x0 0x00 0x70000000 0x200000>;

		m4f_sram: m4f_sram@40000 {
			reg = <0x40000 0x40000>;
		};

		r5f0_0_sram: r5f0_0_sram@80000 {
			reg = <0x80000 0x40000>;
		};

	        r5f0_1_sram: r5f0_1_sram@C0000 {
		        reg = <0xC0000 0x40000>;
		};

	        r5f1_0_sram: r5f1_0_sram@100000 {
			reg = <0x100000 0x40000>;
		};

	        r5f1_1_sram: r5f1_1_sram@140000 {
			reg = <0x140000 0x40000>;
		};
	
		tfa-sram@1c0000 {
			reg = <0x1c0000 0x20000>;
		};

		dmsc-sram@1e0000 {
			reg = <0x1e0000 0x1c000>;
		};

		sproxy-sram@1fc000 {
			reg = <0x1fc000 0x4000>;
		};
	};

Do you have an idea ? 

Hi Sebastian,

Could you please let me know if you have made any changes in the firmware, as with the default files I am able to boot linux without any issues. Also please let me know the MCU + SDK and the Processor SDK version you are using at your end.

Hi Meet,

see attached my project and sbl_ospi_linux. I used the latest mcu_plus_sdk_am64x_10_00_00_20 on TMDS64EVM starter Kit (TMDS64EVM Evaluation board | TI.com).   

fsi_loopback_interrupt_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rarsbl_ospi_linux_am64x-evm_r5fss0-0_nortos_ti-arm-clang.rar

Hi Sebastien,

Could you please clarify which boot flow are you facing this issue with? As our earlier discussion was on EMMC booting linux but the file that you have attached is for OSPI booting linux.

Hi Meet,

Sorry Meet, to move forward, I've adopted a new strategy. I put R5F image and boot sequence in OSPI Flash (u-boot included) . After that I boot Linux from eMMC.The aim is to secure the startup of the R5F application.     

Hi Sebastian,

Thanks for the confirmation. Please allow me some time to test this on my EVM and get back to you.

Hi Sebastian,

If your goal is to load application only on the r5f0-0 then you can ignore the remotproc error message for now, you should still be able to boot the linux kernel and run the FSI example, please let me know if your linux kernel is not booting or if the FSI example is not working as expected.

Best Regards,

Meet.

Hi Meet,

My goal is to exchange data of FSI beetween Linux and R5f0-0. So it is important that Linux have no memory issue and in the near future, I plan to use an another core. On your side, do you have noticed the same problem on your EVM ?  

Hi Sebastien,

Currently you see this issue because you are only booting R5f0-0 while the Linux expects all the cores to be booted. If you try an example like ipc_rpmsg_echo_linux System Freertos example, then you won't see this issue as it is booting up all the cores. You can try this example at your end and verify the same.

Meet,

Ok, but is it possible to disable unused cores in the remoteproc driver. If yes, how can I do that ? I tried to disable mailbox in DTS but without succes

Sebastien,

You can disable the remote core by modifying the device tree, here this guide will provide you with more details on how exactly you can do that: Disabling remote cores in Linux. Please refer to this and let me know if you have any additional questions on this.