Torsten Robitzki
Torsten Robitzki
Sorry, for the confusion. I created that branch just to test if this is sufficient to get it build by gitlab. But of cause, it's not.
Yes, I don't think that reusing from the link_layer makes sense. At least not if you are not going to base the implementation on the `scheduled_radio` hardware abstraction. Most of...
Well, I mostly looked at the calling side in main(). Looks good to me. I think, if you use functions instead of struct, you could even deduct the buffer size...
I've started a new branch (HCI_2) to sketch, how an HCI binding could look like. We have a link_layer implementation that is based on a schedule_radio implementation and we would...
An interesting feature could be to be able to configure the link layer so that it provides support for only a limited number of HCI versions.
Zephire could be used to program a Nordic eval board as HCI controller that communicates via UART.
moved sketch to sci_3 branch as merge of master created tons of conflicts
This should compile and end up in a Peripheral, that support link layer encryption, but no pairing: using blinky_server = server< service< service_uuid< 0xC11169E1, 0x6252, 0x4450, 0x931C, 0x1B43A318783B >, characteristic<...
Well, I guess that Visual Studio would freeze even more when I switch Bluetoe to one of the libraries mentioned at metaben.ch.
Assumed, we would set up a Jenkins server on our own: We could run HIL tests (based on the Scheduled Radio Interface) for nrf51 and nrf52.