openamp / openamp-system-reference Goto Github PK

@tnmysh I am building the kv260_r5 board from examples/zephyr/examples/zephyr/rpmsg_multi_services

There are a few things that look strange to me. Can you please investigate.

[138/143] Linking C executable zephyr/zephyr_pre0.elf
/home/bill/top/zephyr-sdk-0.16.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: warning: **orphan section .resource_table' from zephyr/libzephyr.a(resource_table.c.obj)' being placed in section .resource_table'** [143/143] Linking C executable zephyr/rpmsg_multi_services.elf /home/bill/top/zephyr-sdk-0.16.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: warning: orphan section .resource_table' from zephyr/libzephyr.a(resource_table.c.obj)' being placed in section .resource_table'
Memory region Used Size Region Size %age Used
FLASH: 0 GB 32 MB 0.00%
RAM: 43524 B 64 MB 0.06%
OCM: 0 GB 256 KB 0.00%
IDT_LIST: 0 GB 2 KB 0.00%

1. Is the resource table being placed somewhere reasonable? Why the warning? I don't get that warning on stm32mp157c_dk2

2. Those FLASH and RAM sizes should be KB not MB. I presume FLASH and RAM are TCM right now correct? I would think they would be 64K and 64K in the universal binary case or for either split mode. For lockstep they should be 128K and 128K.
   This assumes TCM A is used for code and TCM B is used for RAM which would be a reasonable default. (Might have the specifics of the TCM names wrong but hopefully you understand.)

zephyr dts for xilinx mailbox is here: https://github.com/zephyrproject-rtos/zephyr/blob/main/dts/arm/xilinx/zynqmp_rpu.dtsi#L35

Current example dts for zcu102 does not contain counter part of this node.
Currently lockstep mode is supported only for zephyr. So, lockstep mode dts need to be updated to make zephyr demo work on zcu102.

Also, kv260 device-tree needs to be pushed from latest petalinux.

Discussed during 2024-02-21 OpenAMP System Reference call. Creating a GitHub issue as a reminder.

Arnaud pointed out that there is a PR in zephyr that proposes a shell over rpmsg:
"Simple to test updating the samples/subsys/ipc/openamp_rsc_table sample. it's working on the stm32mp1-dk board without hardware dependency. Not yet robust as some freezes occur. but at term could be added in the list of system reference demos
zephyrproject-rtos/zephyr#68764 "

• Arnaud can try to modify his CI to try submodule, to see how easy to work with it

• Bill will experiment Zephyr integration idea with West

(Filing GH Issues for relevant action items from System Reference calls. From https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Reference-Working-Group-Meeting-Notes#user-content-Action_items-4)

From https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Reference-Meeting-Notes-2023#user-content-20230322

(Filing GH Issues for relevant action items from System Reference calls)

• What gaps in release test plan?
• What else can we automate in release test plan?
• What can we get to run on every PR?

(Filing GH Issues for relevant action items from System Reference calls. From https://github.com/OpenAMP/openamp-system-reference/wiki/OpenAMP-System-Reference-Meeting-Notes-2023#user-content-Action_items-5 )

The Zephyr project seems open to examples and already has some for OpenAMP[0].

Examples here as a downstream will have the normal issues downstream projects tend to have (maintenance of keeping things in sync means we have these demos locked to a specific Zephyr version. Upstream they would be migrated with changes in Zephyr for any given version).

We should move the two current Zephyr examples into upstream Zephyr and update the docs (examples/zephyr/README.md) to explain how to find and build those examples in the Zephyr tree instead.

[0] https://github.com/zephyrproject-rtos/zephyr/tree/main/samples/subsys/ipc