• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 62 subscribers
  • Views 1206 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 107194
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Gazell libraries Details

Bryan

We are looking at using the Gazell protocol for a project. There isn't much information out there except for the "Gazell Link Layer User's Guide"

developer.nordicsemi.com/.../a00113.html

Can someone explain what the differences are between the two libraries that are referenced and when to use one vs the other?

  1. gzll_arm.lib
  2. gzll_sd_resources_arm.lib (reusing the same resources used by the S1xx Bluetooth Smart softdevice library from Nordic)
  • 0

    Hi

    If you want to combine Gazell and BLE in the same application, by using the Gazell library through the timeslot API in the SoftDevice, you should use the gzll_sd_resources_arm.lib. The reason for this is that this Gazell version uses a subset of the timers, PPI channels and software interrupts already used by the SoftDevice, which means there are more timers, PPI channels and software interrupts left over for the application.

    If you use the gzll_arm.lib with the SoftDevice you will only have one timer, 5 PPI channels and no software interrupts left.

    If you don't combine Gazell with BLE it doesn't really matter which version you use.

    Regards Torbjørn

Related

core_v2_widget.Hide()