Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ble_app_hids_keyboard example with FreeRTOS?

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

Parents
  • 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

Reply
  • 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

Children
No Data
Related