AM6442: Problems loading demo project into R5F from Linux

Hello,

You are probably missing the resource table. This will be covered in the new AM64x Multicore academy (I have already written it, but publication date is TBD as I am waiting on some other documentation to be written as well).

In the meantime, please refer to the AM62x Multicore academy, section "Application Development on Remote Cores":
https://dev.ti.com/tirex/explore/node?node=A__AVn3JGT9fqm0PbS.pegO-g__AM62-ACADEMY__uiYMDcq__LATEST

The section you care about is "How to create remote core firmware that can be initialized by Linux", but it might be helpful to read the whole document.

Regards,

Nick

Upon rereading, I see that you have already found the FAQ that was the first draft of the document I linked above. You should still review the Multicore academy page, as I added a bunch of additional information that is useful.

I would suggest just trying to get hello world to load first. After that is working, then you can try making additional changes, like to the UARTs.

I've attached the patch files for AM64x here:

From 8b52174f88348901cb256fa662c283c9853a69e3 Mon Sep 17 00:00:00 2001
From: Nick Saulnier <nsaulnier@ti.com>
Date: Wed, 4 Oct 2023 16:08:27 -0500
Subject: [PATCH] AM64x SDK 9.0 add Linux IPC in SysConfig

Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
---
 .../am64x-sk/r5fss0-0_freertos/example.syscfg       | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/examples/hello_world/am64x-sk/r5fss0-0_freertos/example.syscfg b/examples/hello_world/am64x-sk/r5fss0-0_freertos/example.syscfg
index 9af2a6c7bf49..c4f37b4c98cf 100644
--- a/examples/hello_world/am64x-sk/r5fss0-0_freertos/example.syscfg
+++ b/examples/hello_world/am64x-sk/r5fss0-0_freertos/example.syscfg
@@ -1,13 +1,14 @@
 /**
  * These arguments were used when this file was generated. They will be automatically applied on subsequent loads
  * via the GUI or CLI. Run CLI with '--help' for additional information on how to override these arguments.
- * @cliArgs --device "AM64x" --package "ALV" --part "Default" --context "r5fss0-0" --product "MCU_PLUS_SDK@07.03.01"
- * @versions {"tool":"1.9.0+2015","templates":null}
+ * @cliArgs --device "AM64x" --package "ALV" --part "Default" --context "r5fss0-0" --product "MCU_PLUS_SDK_AM64x@09.00.00"
+ * @versions {"tool":"1.17.0+3128"}
  */
 
 /**
  * Import the modules used in this configuration.
  */
+const ipc        = scripting.addModule("/drivers/ipc/ipc");
 const debug_log  = scripting.addModule("/kernel/dpl/debug_log");
 const mpu_armv7  = scripting.addModule("/kernel/dpl/mpu_armv7", {}, false);
 const mpu_armv71 = mpu_armv7.addInstance();
@@ -20,8 +21,10 @@ const mpu_armv76 = mpu_armv7.addInstance();
 /**
  * Write custom configuration values to the imported modules.
  */
+ipc.enableLinuxIpc = true;
+
 debug_log.enableUartLog        = true;
-debug_log.enableCssLog         = true;
+debug_log.enableMemLog         = true;
 debug_log.uartLog.$name        = "CONFIG_UART_CONSOLE";
 debug_log.uartLog.UART.$assign = "USART0";
 
@@ -59,5 +62,5 @@ mpu_armv76.size     = 31;
  * version of the tool will not impact the pinmux you originally saw.  These lines can be completely deleted in order to
  * re-solve from scratch.
  */
-debug_log.uartLog.UART.RXD.$suggestSolution = "ball.D15";
-debug_log.uartLog.UART.TXD.$suggestSolution = "ball.C16";
+debug_log.uartLog.UART.RXD.$suggestSolution = "UART0_RXD";
+debug_log.uartLog.UART.TXD.$suggestSolution = "UART0_TXD";
-- 
2.34.1

and

From 5a4f97f7533a8fd6b038e23a8a36ccf25e19a4ff Mon Sep 17 00:00:00 2001
From: Nick Saulnier <nsaulnier@ti.com>
Date: Wed, 4 Oct 2023 21:59:10 -0500
Subject: [PATCH] AM64x SDK 9.0: no IPC, add linker.cmd file

Add a DDR location for a resource table. The resource table may
be automatically generated (e.g., by adding Linux IPC to the MCU+ project's
SysConfig file), or manually written.

The location of the resource table must align with the Linux devicetree file's
memory allocation. Different cores will put the resource table at different
addresses. Reference the Multicore academy, section "How to allocate memory" for
more information.

Signed-off-by: Nick Saulnier <nsaulnier@ti.com>
---
 .../r5fss0-0_freertos/ti-arm-clang/linker.cmd       | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/examples/hello_world/am64x-sk/r5fss0-0_freertos/ti-arm-clang/linker.cmd b/examples/hello_world/am64x-sk/r5fss0-0_freertos/ti-arm-clang/linker.cmd
index c4848c38cce3..8673e690efd6 100644
--- a/examples/hello_world/am64x-sk/r5fss0-0_freertos/ti-arm-clang/linker.cmd
+++ b/examples/hello_world/am64x-sk/r5fss0-0_freertos/ti-arm-clang/linker.cmd
@@ -69,6 +69,12 @@ SECTIONS
         .stack:  {} palign(8)   /* This is where the main() stack goes */
     } > MSRAM
 
+    /* add the resource table */
+    GROUP {
+        /* This is the resource table used by linux to know where the IPC "VRINGs" are located */
+        .resource_table: {} palign(4096)
+    } > DDR_0
+
     /* This is where the stacks for different R5F modes go */
     GROUP {
         .irqstack: {. = . + __IRQ_STACK_SIZE;} align(8)
@@ -133,6 +139,13 @@ MEMORY
      */
     MSRAM     : ORIGIN = 0x70080000 , LENGTH = 0x40000
 
+    /* Resource table must be placed at the start of the "external code/data mem"
+     * section that Linux allocates for the core.
+     * R5F0_0 default allocation is at 0xa0100000
+     */
+    DDR_0       : ORIGIN = 0xa0100000 , LENGTH = 0x1000
+
+
     /* This section can be used to put XIP section of the application in flash, make sure this does not overlap with
      * other CPUs. Also make sure to add a MPU entry for this section and mark it as cached and code executable
      */
-- 
2.34.1