Skip to content

Rpmsg multi services upstream cleanup - #115

Open
bentheredonethat wants to merge 5 commits into
OpenAMP:mainfrom
bentheredonethat:rpmsg-multi-services-upstream-cleanup
Open

Rpmsg multi services upstream cleanup#115
bentheredonethat wants to merge 5 commits into
OpenAMP:mainfrom
bentheredonethat:rpmsg-multi-services-upstream-cleanup

Conversation

@bentheredonethat

Copy link
Copy Markdown
Contributor

No description provided.

Configure the RPMsg multi-services example to use the AMD IPI mailbox on
Versal R5. Keep memory and linker placement outside the application so
generated platform inputs remain the source of the RPU memory layout.

Signed-off-by: Ben Levinsky <ben.levinsky@amd.com>
rsc_table_get() returns its address through a void double pointer. Receive
the address using the interface's declared type before assigning it to the
application's resource-table pointer, avoiding an incompatible pointer
type at the call site.

Signed-off-by: Ben Levinsky <ben.levinsky@amd.com>
RPU memory placement can be generated from a platform domain description,
but the example previously had no way to select that complete linker
script. Add an optional Kconfig path which enables Zephyr's custom linker
script support while preserving normal board and SoC selection when it is
unset.

Document how to pass the generated device tree and linker script together
so they describe one consistent memory layout.

Signed-off-by: Ben Levinsky <ben.levinsky@amd.com>
The raw responder did not terminate its text response, allowing clients
which printed it as a C string to display bytes beyond the received
payload. Bound and terminate raw responses, derive response lengths from
their prefixes, and terminate rpmsg_ping input at the length returned by
read().

Signed-off-by: Ben Levinsky <ben.levinsky@amd.com>
Linux can own the physical UART while loading an RPU application through
remoteproc. Disable serial support for the AMD RPU targets and use the RAM
console where required so the example does not contend for that UART.

Keep immediate logging for Versal Net, enable OpenAMP cache maintenance on
Versal2, and retain the executable-memory settings used by the generated
R52 memory policies.

Represent the supported platforms and tags as YAML sequences so Twister
retains every entry and can build all AMD RPU targets.

Signed-off-by: Ben Levinsky <ben.levinsky@amd.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant