v01d commented on pull request #2140:
URL: https://github.com/apache/incubator-nuttx/pull/2140#issuecomment-761891370


   I'm working again on nordic chips and I would eventually like to use BLE. I 
keep coming back to all this work I've done, and while it was fairly functional 
and most likley needs some robustness improvements, debugging this was really 
painful (since it is at the limit of what you can introspect with a logic 
analyzer and a packet sniffer, and placing a breakpoint on time-critical code 
breaks everything).
   
   But overall, I don't like the idea that only me knows this code well enough 
to find any issues. Ideally, someone else would be willing to take over what 
I've done, test it and help maintain it. But I think it is just too much of a 
task.
   
   So, I'm currently considering going the softdevice route. To me at least it 
makes sense since I can assume the controller code is well tested and 
up-to-date with recent standards. Also, I feel it may not be that hard to make 
it work (at least not that hard as it is to debug RADIO code). @acassis I 
remember you mentioned the zGlue project (and I think there was even someone 
from that project that you mentioned could offer help). It would be cool to 
know at least about the general strategy they followed, since I see the 
softdevice uses an SVCall interface and it would probably require some careful 
consideration to tie it into NuttX.
   
   Anyway, just wanted to let you know about my current thoughts. I realize it 
is quite a lot of work that may end up nowhere but I'd rather continue putting 
effort in something that I can trust and works well.
   
   cc: @btashton (since I think you have experience with BLE stuff you may have 
an opinion about it)
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to