Are there any limitations that will not allow me to make the ble_app_hids_keyboard example with FreeRTOS?
If no, is there any examples that will help me easier to migrate provided sample code to include FreeRTOS?
Thanks
Are there any limitations that will not allow me to make the ble_app_hids_keyboard example with FreeRTOS?
If no, is there any examples that will help me easier to migrate provided sample code to include FreeRTOS?
Thanks
Hi
I'm sorry, but we do not have an example already featuring ble_app_hids_keyboard and FreeRTOS. However, it shouldn't be a problem adding the HID keyboard service to the ble_app_hrs_freertos example, which is a FreeRTOS project already, where adding services from other examples shouldn't be an issue.
Best regards,
Simon
Hi Simon, thank you for the quick response. Unfortunately ble_app_hrs_freertos example is not quite a good starting point - see here: https://devzone.nordicsemi.com/f/nordic-q-a/56390/bugs-in-ble_app_hrs_freertos-example/230271#230271 so either myself or your colleague who is working on the reported issues need first to fix the hrs_freertos example, then eventually will try to migrate HID services there.
BTW I'll use s112, hrs freertos example is provided with s132 - any known issues or limitations if I migrate the code to s112?
Thanks
Hi
There are a few limitations with the S112 Softdevice versus the S132. First, the S132 supports concurrent central, observer, peripheral, and broadcaster roles with up to 20 concurrent connections along with one Observer and one Broadcaster, while the S112 supports up to four peripheral connections and one broadcaster running concurrently. So the S112 will not be able to be part of a central device, as it is made for peripherals.
S132 supports Extended advertising, L2CAP with LE Credit-based Flow control, and LE data packet length extension, the S112 doesn't.
The S132 has memory isolation between the application and the protocol stack for robustness and security, the S112 doesn't.
Best regards,
Simon