Re: [PR] esp32: espnow improvements [nuttx]

2025-03-15 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2710596259 Hi @tmedicci thanks for your remarks, Regarding item 1: I think the udpclient & server test program are meant to be started when the link is up and there might be an init problem whe

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-12 Thread via GitHub
tmedicci commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2718028055 @acassis and @xiaoxiang781216 can you please take a second look? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
acassis commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2711109087 https://nuttx.apache.org/docs/latest/contributing/documentation.html -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and u

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2711031826 > Thanks @Laczen :-) Would it be possible to fix problems identified by @tmedicci maybe with simple checks and error returns when operation is not possible until better solution is availab

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
cederom commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2712185805 > @Laczen: @tmedicci @cederom the first problem is caused by udp_input, it also appears when both network interfaces are up before starting the client but the server is not running. The p

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
acassis commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2710971818 @Laczen could you please update the documentation with this complete log that @tmedicci printed here? I noticed that the Documentation/ has only the commands, it should be nice to have th

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
acassis commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2711026100 > > Also I noticed the Documentation format is strange: https://nuttx.apache.org/docs/latest/platforms/xtensa/esp32/boards/esp32-devkitc/index.html > > everything is in a single line:

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2711291476 @tmedicci @cederom the first problem is caused by udp_input, it also appears when both network interfaces are up before starting the client but the server is not running. The problem is th

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2711101898 > > > Also I noticed the Documentation format is strange: https://nuttx.apache.org/docs/latest/platforms/xtensa/esp32/boards/esp32-devkitc/index.html > > > everything is in a single line

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2711016690 > Also I noticed the Documentation format is strange: https://nuttx.apache.org/docs/latest/platforms/xtensa/esp32/boards/esp32-devkitc/index.html > > everything is in a single line:

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
tmedicci commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2714146344 > > So if I understand this correctly, NuttX is still missing network implementation that would allow a proper use case of ESPNOW? > > I don't think this is true. NuttX is missing

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2714241135 > Please, @Laczen , can you open the following issues: > > 1. One for the sixlowpan issue reported [here](https://github.com/apache/nuttx/pull/15962#issuecomment-2711291476).

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2714050209 > So if I understand this correctly, NuttX is still missing network implementation that would allow a proper use case of ESPNOW? I don't think this is true. NuttX is missing some lov

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
acassis commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2714002010 > > > @Laczen: @tmedicci @cederom the first problem is caused by udp_input, it also appears when both network interfaces are up before starting the client but the server is not running. T

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
fdcavalcanti commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2713857978 > > > @Laczen: @tmedicci @cederom the first problem is caused by udp_input, it also appears when both network interfaces are up before starting the client but the server is not runni

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2713301580 > > @Laczen: @tmedicci @cederom the first problem is caused by udp_input, it also appears when both network interfaces are up before starting the client but the server is not running. The

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2713129962 @acassis I have updated the documentation. After building the documentation locally I am now faced with a change on my branch of the file `Documentation/Pipfile.lock`, is this someth

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-11 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2711007947 > @Laczen could you please update the documentation with this complete log that @tmedicci printed here? I noticed that the Documentation/ has only the commands, it should be nice to have t

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-10 Thread via GitHub
acassis commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2710979047 Also I noticed the Documentation format is strange: https://nuttx.apache.org/docs/latest/platforms/xtensa/esp32/boards/esp32-devkitc/index.html everything is in a single line:

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-10 Thread via GitHub
cederom commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2710983503 Thanks @Laczen :-) Would it be possible to fix problems identified by @tmedicci maybe with simple checks and error returns when operation is not possible until better solution is availabl

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-10 Thread via GitHub
tmedicci commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2710484773 Hi @Laczen , thanks for submitting it! I have no comments regarding the code. The changes are welcomed! But I've found two possible bugs: 1. If I start the _client_ device b

Re: [PR] esp32: espnow improvements [nuttx]

2025-03-10 Thread via GitHub
Laczen commented on PR #15962: URL: https://github.com/apache/nuttx/pull/15962#issuecomment-2709953735 @tmedicci, fyi. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To un

[PR] esp32: espnow improvements [nuttx]

2025-03-10 Thread via GitHub
Laczen opened a new pull request, #15962: URL: https://github.com/apache/nuttx/pull/15962 ## Summary The PR proposes improvements to espnow pktradio, it separates the rx from the tx and simplifies the addressing used by espnow for sixlowpan. It also enables future expansion for ciphe