You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to create a "serial link" between NRF5340 NET & APP CPU - on APP i want to keep
Zephyr but on NET CPU i want to implement the link using OpenAMP.
The spinel inplementation for NRF5340 is using the Zephyr IPC Service and looks promising blueprint but it seems much more complex to implement than the rpmsg_service samples - why is this so? What would be the advantages using the Zephyr IPC service ?
Looking at the even lower layers, it appears the simplest way in this case would be based upon the OpenAMP directly? That seems to be the thinnest porting layer.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I need to create a "serial link" between NRF5340 NET & APP CPU - on APP i want to keep
Zephyr but on NET CPU i want to implement the link using OpenAMP.
The spinel inplementation for NRF5340 is using the Zephyr IPC Service and looks promising blueprint but it seems much more complex to implement than the rpmsg_service samples - why is this so? What would be the advantages using the Zephyr IPC service ?
Looking at the even lower layers, it appears the simplest way in this case would be based upon the OpenAMP directly? That seems to be the thinnest porting layer.
Best
Peter
Beta Was this translation helpful? Give feedback.
All reactions