From: Felix Kuhlmann <felix-kuhlmann@gmx.de>
To: linux-remoteproc@vger.kernel.org
Subject: Question regarding optimisation of RPMsg round trip times on Xilinx ZynqMP hardware
Date: Sat, 26 Oct 2024 12:57:33 +0200 [thread overview]
Message-ID: <ZxzLHcWpjeo9sJGN@fedora> (raw)
Hello everybody,
I need your help concerning an error that was returned while trying to
use the AMD Xilinx implementation of remoteproc. I hope that this is
the right place to ask for help.
I'm currently working on a project that requires Remoteproc and
RPMsg. The hardware I am working with is a Trenz SoM containing a
AMD Zynq UltraScale+ MPSoC, CG variant, DDR3 external RAM and a few
additional components.
One of the targets of the project is that the communication between
the RPU and the APU should happen under soft realtime conditions. The
issue with the communication examples provided by Xilinx is that they
use the external RAM for the buffers for RPMsg. This results in highly
non-deterministic communication delay jitter, which is most likely due
to the fact that DDR RAM is not suited for those applications.
Given that the SoC already has an On-Chip Memory that is designed for such
applications, I am curious whether changing the shared memory location
for RPMsg to reside inside of the OCM of the SoC result in a performance
boost. Do you have any experience with such performance benefits?
I'm currently developing a solution, trying to adopt the examples AMD
provides, but when trying to boot the fw image, Remoteproc complains that
it is unable to allocate the memory, saying the fw image size doesn't
fit the len request. This results in Remoteproc throwing error "-12",
which simply indicates that booting of the RPU failed. More information
isn't logged.
I have tried to read the documentation, but I can't really decide which
aspects I need to bear in mind when trying to adopt my code to use a
different memory region as a whole.
My previous attempts at circumventing this issue failed, resulting in
the error above.
A few of the things I've tried are:
- Changing the shared memory and the vring addresses to be inside of
the OCM
- Adding the OCM and the remoteproc buffers to the device tree
- Attempting to increase the requested carveout for the firmware
I hope this provides a sufficient overview of my situation. If you need
further information or logs in order to figure out what went wrong,
feel free to ask for that.
Thank you in advance and best regards,
Felix Kuhlmann
next reply other threads:[~2024-10-26 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-26 10:57 Felix Kuhlmann [this message]
2024-10-28 15:17 ` Question regarding optimisation of RPMsg round trip times on Xilinx ZynqMP hardware Mathieu Poirier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZxzLHcWpjeo9sJGN@fedora \
--to=felix-kuhlmann@gmx.de \
--cc=linux-remoteproc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).