2

I am using a nordic BLE SOC: nrf52 dk, along with s130 and sdk 14.2.0 I want to secure an advertised BLE packet with AES CCM encryption. The board contains a co-processor for AES calculation that is not accessible while using the soft device that I am using to generate packets and advertise.

The solution is to use timeslot API but I do not know how to do it. There is a tutorial but it's only valid for nRF5 SDK 11.

  • 1
    What have you tried so far? Without knowing what part of the implementation you're unable to accomplish there'll unlikely be anyone able to help you. – Helmar Jun 12 '19 at 20:28
  • I will edit the question and specify exactly what was the problem in implementation, I have the answer already and I posted a link but think this might help the others – Abyr Jun 13 '19 at 6:59
1

I have posted this question in nordic devzone and I got this answer:

https://devzone.nordicsemi.com/f/nordic-q-a/48518/softdevice-handler-h-is-missing The same question has been answered before so I am posting the other answer as well, as it has longer discussion: https://devzone.nordicsemi.com/f/nordic-q-a/48025/not-finding-softdevice_handler-h-in-nrf52_sdk_15-0-3

|improve this answer|||||

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.