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.

TDA4VL-Q1: TDA4VM/TDA4VL/TDA4AL/TDA4VH/DRA821: How can we make the Jacinto SDK 9.x compatible for device variants?

Part Number: TDA4VL-Q1
Other Parts Discussed in Thread: TDA4VL

BSP: SDK 9.2

SoC: TDA4VL

Ref URL: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1227640/faq-tda4vm-tda4vl-tda4al-tda4vh-dra821-how-can-we-make-the-jacinto-sdk-compatible-for-device-variants-yxz/4666783#4666783

Dear supporter,

    We are going to migrate SDK from 8.6 to 9.x on J721S2 (TDA4VL) by referring above information. Found out some portions on 9.x are gone. Should we ignore them while porting? Thanks.

- Wilson

Differences:

A. SPL

1. Reduction in the number of DDR Instances

  •  U-boot (following codes not found)

diff --git a/board/ti/j721s2/evm.c b/board/ti/j721s2/evm.c
index 90b7ca1150..51e50fa9c5 100644
--- a/board/ti/j721s2/evm.c
+++ b/board/ti/j721s2/evm.c
@@ -67,8 +67,8 @@ int dram_init_banksize(void)
 #ifdef CONFIG_PHYS_64BIT
 	/* Bank 1 declares the memory available in the DDR high region */
 	gd->bd->bi_dram[1].start = CONFIG_SYS_SDRAM_BASE1;
-	gd->bd->bi_dram[1].size = 0x37fffffff;
-	gd->ram_size = 0x400000000;
+	gd->bd->bi_dram[1].size = 0x17fffffff;
+	gd->ram_size = 0x200000000;
 #endif

3. Disabling/removing the additional cores

  •  U-boot (following codes not found)

diff --git a/arch/arm/dts/k3-j721s2-common-proc-board.dts b/arch/arm/dts/k3-j721s2-common-proc-board.dts
index 5b7e33490f..ffd9c8568b 100644
--- a/arch/arm/dts/k3-j721s2-common-proc-board.dts
+++ b/arch/arm/dts/k3-j721s2-common-proc-board.dts
@@ -32,8 +32,6 @@
 		remoteproc1 = &mcu_r5fss0_core1;
 		remoteproc2 = &main_r5fss0_core0;
 		remoteproc3 = &main_r5fss0_core1;
-		remoteproc4 = &main_r5fss1_core0;
-		remoteproc5 = &main_r5fss1_core1;
 		remoteproc6 = &c71_0;
 		remoteproc7 = &c71_1;
 	};

  • Linux (following codes not found)

diff --git a/arch/arm/dts/k3-j721s2-common-proc-board.dts b/arch/arm/dts/k3-j721s2-common-proc-board.dts
index 5b7e33490f..ffd9c8568b 100644
--- a/arch/arm/dts/k3-j721s2-common-proc-board.dts
+++ b/arch/arm/dts/k3-j721s2-common-proc-board.dts
@@ -32,8 +32,6 @@
 		remoteproc1 = &mcu_r5fss0_core1;
 		remoteproc2 = &main_r5fss0_core0;
 		remoteproc3 = &main_r5fss0_core1;
-		remoteproc4 = &main_r5fss1_core0;
-		remoteproc5 = &main_r5fss1_core1;
 		remoteproc6 = &c71_0;
 		remoteproc7 = &c71_1;
 	};

  • Hi,

    1. Reduction in the number of DDR Instances

    •  U-boot (following codes not found)

    This can be ignored.

    Disabling/removing the additional cores

    •  U-boot (following codes not found)

    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    diff --git a/arch/arm/dts/k3-j721s2-common-proc-board.dts b/arch/arm/dts/k3-j721s2-common-proc-board.dts
    index 5b7e33490f..ffd9c8568b 100644
    --- a/arch/arm/dts/k3-j721s2-common-proc-board.dts
    +++ b/arch/arm/dts/k3-j721s2-common-proc-board.dts
    @@ -32,8 +32,6 @@
    remoteproc1 = &mcu_r5fss0_core1;
    remoteproc2 = &main_r5fss0_core0;
    remoteproc3 = &main_r5fss0_core1;
    - remoteproc4 = &main_r5fss1_core0;
    - remoteproc5 = &main_r5fss1_core1;
    remoteproc6 = &c71_0;
    remoteproc7 = &c71_1;
    };
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

    • Linux (following codes not found)

    This is a u-boot change (not linux change), Let me check internally and get back to you.

    Regards,

    Nikhil

  • Hi,

    The remoteproc aliasing is removed from u-boot, as this is not being used by u-boot. 

    So you could bypass this change and check if you are able to achieve the verification outputs by only incorporating the other changes.

    Regards,

    Nikhil

  • Hi, Nikhil,

    I would like to confirm whether your answer can solve this issue or not, but I run into another problem: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1356812/tda4vl-q1-no-rule-to-make-target-firmware_scrub-stop

    I cannot click green button or grey one until SDK 9.2 runs fine on our TDA4VL successfully.

    - Wilson

  • Sure. 

    I have responded to the other thread. Please let me know once you have verified this, so that we could close this issue.

    Regards,

    Nikhil