On Mon, 12 Jul 2021 at 08:25, Bill Mills via Openamp-rp
<openamp-rp(a)lists.openampproject.org> wrote:
>
> All,
>
> I will be unavailable on July 15 for this weeks call.
> I suggest we cancel unless on someone else volunteers to host.
> I was going to suggest we move to next week but that conflicts with a
> Linaro meeting some of you may need to attend.
>
Unless someone comes up with something urgent to discuss I suggest we
cancel this one.
> Thanks,
> Bill
>
> --
> Bill Mills
> Principal Technical Consultant, Linaro
> +1-240-643-0836
> TZ: US Eastern
> Work Schedule: Tues/Wed/Thur
> --
> Openamp-rp mailing list
> Openamp-rp(a)lists.openampproject.org
> https://lists.openampproject.org/mailman/listinfo/openamp-rp
All,
I will be unavailable on July 15 for this weeks call.
I suggest we cancel unless on someone else volunteers to host.
I was going to suggest we move to next week but that conflicts with a
Linaro meeting some of you may need to attend.
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
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.
Branch: refs/heads/master
Home: https://github.com/OpenAMP/libmetal
Commit: ecac36a4c90ac116d275675eb1884c5a03db3ef0
https://github.com/OpenAMP/libmetal/commit/ecac36a4c90ac116d275675eb1884c5a…
Author: Carlo Caione <ccaione(a)baylibre.com>
Date: 2021-05-28 (Fri, 28 May 2021)
Changed paths:
M lib/system/zephyr/cache.h
Log Message:
-----------
zephyr: cache: Use new Zephyr cache APIs
Zephyr ships now a different API for cache management. Instead of
hijacking the call into Zephyr, use the proper API directly in libmetal.
Signed-off-by: Carlo Caione <ccaione(a)baylibre.com>
Branch: refs/heads/master
Home: https://github.com/OpenAMP/open-amp
Commit: 294ba3da95b2b12b36d4597c6d4aae86723688fa
https://github.com/OpenAMP/open-amp/commit/294ba3da95b2b12b36d4597c6d4aae86…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2021-05-28 (Fri, 28 May 2021)
Changed paths:
M .github/actions/build_ci/entrypoint.sh
Log Message:
-----------
CI: Zephyr test: copy whole libmetal directory for test
When only the libmetal/lib is copied, some files such as
VERSION or CmakeList.txt are not copied. This can lead to
a test error or false positives.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Branch: refs/heads/master
Home: https://github.com/OpenAMP/libmetal
Commit: 4faa1c9d3649337eb68b287c0e6c809aebfa24c6
https://github.com/OpenAMP/libmetal/commit/4faa1c9d3649337eb68b287c0e6c809a…
Author: Lane Kolbly <lane.kolbly(a)ni.com>
Date: 2021-05-28 (Fri, 28 May 2021)
Changed paths:
M lib/system/linux/device.c
Log Message:
-----------
linux: device: unmap regions for linux device
This unmaps the device regions which were opened during metal_uio_dev_open.
Failure to do this results in a file descriptor leak.
Signed-off-by: Lane Kolbly <lane.kolbly(a)ni.com>
Branch: refs/heads/v2021.04
Home: https://github.com/OpenAMP/libmetal
Commit: 5983d207df41841ffb425c49695837c2e2a67a0a
https://github.com/OpenAMP/libmetal/commit/5983d207df41841ffb425c49695837c2…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2021-05-06 (Thu, 06 May 2021)
Changed paths:
M CMakeLists.txt
M cmake/options.cmake
Log Message:
-----------
cmake: fix VERSION file path
cmake fails when the variable CMAKE_SOURCE_DIR does not point to
the libmetal directory.
This is the case, for example, for the Zephyr project.
Fix by defining LIBMETAL_ROOT_DIR in the main CmakeLists.txt.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
All,
Tomorrow's meeting is canceled. I will update and then delete the invite.
Thanks,
Bill
--
Bill Mills
Principal Technical Consultant, Linaro
+1-240-643-0836
TZ: US Eastern
Work Schedule: Tues/Wed/Thur
All,
I have a conflict for tomorrow (TF-A tech meeting which I need to be on.)
Do we want to cancel or someone else run it?
(I have not done my document experiments yet.)
I will get the wiki notes updated before tomorrow.
Thanks,
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: 04cf5d9e0ef562d676cd3f58530fed4e1901f428
https://github.com/OpenAMP/libmetal/commit/04cf5d9e0ef562d676cd3f58530fed4e…
Author: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
Date: 2021-05-04 (Tue, 04 May 2021)
Changed paths:
M CMakeLists.txt
M cmake/options.cmake
Log Message:
-----------
cmake: fix VERSION file path
cmake fails when the variable CMAKE_SOURCE_DIR does not point to
the libmetal directory.
This is the case, for example, for the Zephyr project.
Fix by defining LIBMETAL_ROOT_DIR in the main CmakeLists.txt.
Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen(a)foss.st.com>
This is to announce the release of version 2021.04 of the OpenAMP and
libmetal libraries.
Release notes can be found at:
https://github.com/OpenAMP/libmetal/releases/tag/v2021.04.0https://github.com/OpenAMP/open-amp/releases/tag/v2021.04.0
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.
Branch: refs/heads/v2021.04
Home: https://github.com/OpenAMP/open-amp
Commit: c3f12991991d187d47637d88e8a66076f23d0c8c
https://github.com/OpenAMP/open-amp/commit/c3f12991991d187d47637d88e8a66076…
Author: Ed Mooring <ed.mooring(a)linaro.org>
Date: 2021-04-30 (Fri, 30 Apr 2021)
Changed paths:
M VERSION
Log Message:
-----------
Semantic Versioning: Update library version to 1.0.0.
With the introduction of semantic versioning, update the library version
accordingly.
Signed-off-by: Ed Mooring <ed.mooring(a)linaro.org>
Branch: refs/heads/master
Home: https://github.com/OpenAMP/open-amp
Commit: c3f12991991d187d47637d88e8a66076f23d0c8c
https://github.com/OpenAMP/open-amp/commit/c3f12991991d187d47637d88e8a66076…
Author: Ed Mooring <ed.mooring(a)linaro.org>
Date: 2021-04-30 (Fri, 30 Apr 2021)
Changed paths:
M VERSION
Log Message:
-----------
Semantic Versioning: Update library version to 1.0.0.
With the introduction of semantic versioning, update the library version
accordingly.
Signed-off-by: Ed Mooring <ed.mooring(a)linaro.org>