Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to access rpmsg device /sys/bus/rpmsg/devices/virtio0.rpmsg-openamp-demo-channel.-1.0 #16

Open
SrMujjiga opened this issue Jan 11, 2022 · 0 comments

Comments

@SrMujjiga
Copy link

SrMujjiga commented Jan 11, 2022

Xilinx Zynq UltraScale+ MpSoc ZCU102,
Xilinx Linux Kernel 4.19 with debian rfs on A53
Included through BSP:
FreeRTOS v10
OpenAMP: v1.5
Libmetal: v2.0

Zynq remoteproc driver is statically built into the linux kernel. Once the board comes up, Applications on the master ( A53 ) can run echo stop and echo start to bring up the RPU Core. In some cases it is observed that echo stop/echo start does not help to bring up the RPU core. Not able to access rpmsg device /sys/bus/rpmsg/devices/virtio0.rpmsg-openamp-demo-channel.-1.0 message is seen . Rebooting the board seems to be the only way to address this problem which we would like to avoid. As a first step, made zynq remote proc driver as loadable kernel module and insmod/rmmod the driver prior to echo start/echo stop. But this also seems to be not helping once access failure for virtio0.rpmsg-openamp-demo-channel.-1.0 is seen.

Can some one help with below questions.
Why is the access failure reported ?
How to recover from this state without rebooting the board ?

Thanks.

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

No branches or pull requests

1 participant