-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[HELP] Using espnow on NuttX for espressif devices #15347
Comments
@tmedicci @eren-terzioglu please take a look ^ |
Hi @Laczen, It is not on our roadmap. But if this is really important for your application and you decide to get hands on, open a dedicated branch so we can help with ideas and suggestions. As a starting point for your reference, please consider ESP-IDF's |
Hi @tmedicci thanks for your reply. I think this would be a good addition for nuttx. From the ESP-IDF release/v5.1 branch it seems that espnow is supported and has its own library. Do you think it is a good idea to add support for espnow in a similar way as cc1101 and nrf24l01 ? |
It would be the easiest approach, but I don't think it's the most appropriate... In my opinion, I think it should be registered as a network device (possibly as a |
Thanks, I will have a look at this approach. |
Hi @tmedicci I have been studying the I would think that to add espnow as a network device I should take a similar approach to the Should Thanks in advance. |
Hi @Laczen, Usually, NuttX drivers are split into a lower-half and upper-half, as described here. Network drivers, however, doesn't seem to follow the same path. If you check about That being said, as ESPnow is specific for Espressif devices, I think you should implement it on |
Description
Hi, I would like to use the espnow from expressif to communicate between different esp32 based nodes. Can this be done using the raw packets net interface or is it better to create a dedicated driver?
If the raw packets net interface would work, has anyone already done this or has a good example on how to do this?
If a dedicated driver would be a better approach, can this driver be created while still maintaining normal wifi operation (of course on the same wifi channel)?
Verification
The text was updated successfully, but these errors were encountered: