Hi Sam,
I don’t see any current work with RTEMS on OpenAMP.
There is a porting guide for OpenAMP/libmetal (https://github.com/OpenAMP/open-amp/wiki/OpenAMP-Porting-GuideLine <https://github.com/OpenAMP/open-amp/wiki/OpenAMP-Porting-GuideLine>). There is also some support for Micro-blaze bare metal in the existing code base.
Regards,
Ed M
> On Jun 29, 2021, at 11:08 AM, Price, Samuel R. (GSFC-5960) via Openamp-rp <openamp-rp(a)lists.openampproject.org> wrote:
>
> Has someone put together an RTEMS port they could share?
>
>
> If not is there a good list of steps / tasks needed to get this to work
> for RTEMS I could reference?
>
> Specifically targeting micro-blaze processor.
>
>
> Most likely starting off with Linux Parent, bare metal child.
>
> Then transitioning to RTEMS parent, bare metal child.
>
>
> Thanks,
>
> Sam
> --
> Openamp-rp mailing list
> Openamp-rp(a)lists.openampproject.org
> https://lists.openampproject.org/mailman/listinfo/openamp-rp
Hi Sam,
I don’t see any current work with RTEMS on OpenAMP.
There is a porting guide for OpenAMP/libmetal
([1]https://github.com/OpenAMP/open-amp/wiki/OpenAMP-Porting-GuideLine)
. There is also some support for Micro-blaze bare metal in the existing
code base.
Regards,
Ed M
On Jun 29, 2021, at 11:08 AM, Price, Samuel R. (GSFC-5960) via
Openamp-rp <[2]openamp-rp(a)lists.openampproject.org> wrote:
Has someone put together an RTEMS port they could share?
If not is there a good list of steps / tasks needed to get this to
work
for RTEMS I could reference?
Specifically targeting micro-blaze processor.
Most likely starting off with Linux Parent, bare metal child.
Then transitioning to RTEMS parent, bare metal child.
Thanks,
Sam
--
Openamp-rp mailing list
[3]Openamp-rp(a)lists.openampproject.org
https://lists.openampproject.org/mailman/listinfo/openamp-rp
References
1. https://github.com/OpenAMP/open-amp/wiki/OpenAMP-Porting-GuideLine
2. mailto:openamp-rp@lists.openampproject.org
3. mailto:Openamp-rp@lists.openampproject.org
Has someone put together an RTEMS port they could share?
If not is there a good list of steps / tasks needed to get this to work for RTEMS I could reference?
Specifically targeting micro-blaze processor.
Most likely starting off with Linux Parent, bare metal child.
Then transitioning to RTEMS parent, bare metal child.
Thanks,
Sam
Has someone put together an RTEMS port they could share?
If not is there a good list of steps / tasks needed to get this to work
for RTEMS I could reference?
Specifically targeting micro-blaze processor.
Most likely starting off with Linux Parent, bare metal child.
Then transitioning to RTEMS parent, bare metal child.
Thanks,
Sam
All,
Both Mathieu and an I are unavailable this Thursday July 1.
I am canceling the call this week.
Thanks and Sorry,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
Branch: refs/heads/master
Home: https://github.com/OpenAMP/libmetal
Commit: e73f0b0139bf89710065bbc9f9d050ded6b58408
https://github.com/OpenAMP/libmetal/commit/e73f0b0139bf89710065bbc9f9d050de…
Author: Julien Massot <julien.massot(a)iot.bzh>
Date: 2021-06-17 (Thu, 17 Jun 2021)
Changed paths:
M cmake/syscheck.cmake
A lib/system/zephyr/arm/CMakeLists.txt
A lib/system/zephyr/arm/sys.c
A lib/system/zephyr/arm/sys.h
R lib/system/zephyr/cortexm/CMakeLists.txt
R lib/system/zephyr/cortexm/sys.c
R lib/system/zephyr/cortexm/sys.h
Log Message:
-----------
zephyr: enable support for Arm AArch32 processors
Arm AArch32 processors have the same WFI assembly instruction
and so can works with the existing cortexm support.
Rename cortexm directory to arm.
Build tested with stm32mp157c_dk2 for Cortex-M,
rcar_h3ulcb for Cortex-R.
Signed-off-by: Julien Massot <julien.massot(a)iot.bzh>
On Mon 07 Jun 10:26 CDT 2021, Hannes Tschofenig via Openamp-rp wrote:
> Hi all,
>
I thought I wrote an answer to this earlier, but I can't find it in my
Sent folder, so thanks Ed for bumping the thread.
>
> This might be a stupid question but I try it anyway.
>
It's certainly not a stupid question!
>
> I would like to use Wireshark to capture the communication over the
> OpenAMP/rpmsg stack from one processor to the other one.
>
I've had this problem several times, where I am in need to inspecting
some data traveling over my rpmsg channels. This has so far resulted in
various hacks.
In my case this all revolves around the Linux kernel, so looking at
prior art usbmon comes to mind. But I've so far fulfilled my needs
before reaching a point where my prototypes for something like this
could be reused.
> Wireshark has been used in used for all sorts of communication
> protocols and I believe it is applicable here as well. I could imagine
> that someone wrote such a Wireshark plugin already.
> Maybe someone of you knows. This could be useful for debugging.
>
As Ed says, Wireshark doesn't have any knowledge of any of our
protocols - but no tool does. So I don't think it's a bad idea to reuse
what they have - and usbmon shows up in this context again.
Regards,
Bjorn
Hi Hannes,
Unfortunately, I don’t believe there is any way to use Wireshark here. Wireshark depends on the underlying
protocol stack to provide user-space access to the communication. There are no such hooks in the Linux
kernel remoteproc implementation.
It does sound like a cool idea though.
Regards,
Ed M
> On Jun 7, 2021, at 8:26 AM, Hannes Tschofenig via Openamp-rp <openamp-rp(a)lists.openampproject.org> wrote:
>
> Hi all,
>
>
> This might be a stupid question but I try it anyway.
>
>
> I would like to use Wireshark to capture the communication over the
> OpenAMP/rpmsg stack from one processor to the other one.
>
> Wireshark has been used in used for all sorts of communication
> protocols and I believe it is applicable here as well. I could imagine
> that someone wrote such a Wireshark plugin already.
> Maybe someone of you knows. This could be useful for debugging.
>
>
> Ciao
>
> Hannes
>
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy
> the information in any medium. Thank you.
> --
> Openamp-rp mailing list
> Openamp-rp(a)lists.openampproject.org
> https://lists.openampproject.org/mailman/listinfo/openamp-rp
Branch: refs/heads/master
Home: https://github.com/OpenAMP/libmetal
Commit: 7e171668c59c324d031a8f1491a636dc41c2e6a4
https://github.com/OpenAMP/libmetal/commit/7e171668c59c324d031a8f1491a636dc…
Author: Mark-PK Tsai <mark-pk.tsai(a)mediatek.com>
Date: 2021-06-08 (Tue, 08 Jun 2021)
Changed paths:
M lib/io.c
Log Message:
-----------
io: add null pointer check in io block ops
metal_io_virt returns NULL on invalid input metal_io_region.
Check ptr before use it and remove the offset check which
is already tested in metal_io_virt.
Signed-off-by: Mark-PK Tsai <mark-pk.tsai(a)mediatek.com>
Hi all,
This might be a stupid question but I try it anyway.
I would like to use Wireshark to capture the communication over the OpenAMP/rpmsg stack from one processor to the other one.
Wireshark has been used in used for all sorts of communication protocols and I believe it is applicable here as well. I could imagine that someone wrote such a Wireshark plugin already.
Maybe someone of you knows. This could be useful for debugging.
Ciao
Hannes
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi all,
This might be a stupid question but I try it anyway.
I would like to use Wireshark to capture the communication over the
OpenAMP/rpmsg stack from one processor to the other one.
Wireshark has been used in used for all sorts of communication
protocols and I believe it is applicable here as well. I could imagine
that someone wrote such a Wireshark plugin already.
Maybe someone of you knows. This could be useful for debugging.
Ciao
Hannes
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended
recipient, please notify the sender immediately and do not disclose the
contents to any other person, use it for any purpose, or store or copy
the information in any medium. Thank you.