This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Access Gazelle from coprocessor

Note: this question was previously a reply on my other question, but I accidentally marked it as an answer so the thread got locked. I have now deleted that reply and am posting this as a separate question. I apologize for flooding. 

What should I do to access Gazell from another processor over some interface, like SPI, UART, or L2/Thread? Is my best bet to create a wrapper for RPCs? Do I implement Zephyr's network buffer? Can I implement an OpenThread driver? Which is the best, and which is the easiest? Also, does anything exist for accessing Gazelle from a second processor already that won't require an implementation on my end?

Parents
  • Hi,

    does anything exist for accessing Gazelle from a second processor already that won't require an implementation on my end?

    No, we don't have any ready implementation that does this. If you want to e.g. serialize the function calls, then RPC is the way to go. If you don't need that much control over things at that level, e.g. just need some start/stop, send payload functionality, then maybe a simpler message interface scheme approach is better. e.g. as illustrated in this post.

Reply
  • Hi,

    does anything exist for accessing Gazelle from a second processor already that won't require an implementation on my end?

    No, we don't have any ready implementation that does this. If you want to e.g. serialize the function calls, then RPC is the way to go. If you don't need that much control over things at that level, e.g. just need some start/stop, send payload functionality, then maybe a simpler message interface scheme approach is better. e.g. as illustrated in this post.

Children
No Data
Related