This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Bluetooth Specification Nightmare

Hi, we're using an nRF8001. Trying to find the relevant Bluetooth Specifications, we found the following mess (pardon my french!):

  • Core Specification 4.0, 2300 pages, June 2010
  • 3 Core Specification Addenda, >100 pages each
  • 1 Core Specification Supplement
  • 3 Errata Service Releases since 2010
  • multitude of GATT profile specifications

Is there a single document that describes the current specification we should try to follow?

Which "version" of the Specification does the nRF8001 conform to?

  • Core Specification 4.0, 2300 pages, June 2010

    This should be your main source of information.

    3 Core Specification Addenda, >100 pages each

    1 Core Specification Supplement

    3 Errata Service Releases since 2010

    You can pretty much safely ignore those for now until the spec is actually approved.

    multitude of GATT profile specifications

    You will need those if you plan to implement SIG-approved profiles and not your own, proprietary profile.

    Which "version" of the Specification does the nRF8001 conform to?

    Core Specification 4.0

  • Is there a need to get proprietary profiles certified by the SIG or Bluetooth.org?

  • Is there a need to get proprietary profiles certified by the SIG or Bluetooth.org?

    No, but you will obviously have to control both sides (central and peripheral), which in many cases means writing a smartphone app, and you need to use Vendor Specific 128-bit UUIDs. Other than that, no certification needed.

  • The nRF8001 datasheet has the mapping of the different features of the nRF8001 to the specific Bluetooth 4.0 specification. This makes it easy to just look at the specifics instead of looking at the entire Bluetooth specification.

    Each feature or ACI message in the nRF8001 will mention the "Bluetooth low energy procedures used" and this will refer to the specific section in the Bluetooth document that will give you more details.

    For example: ACI command Change Timing Request mentions the Bluetooth low energy procedures used as : The following GAP procedures are used to change connection timing:

    • Connection Parameter Update Procedure Bluetooth Core specification v4.0, Vol. 3, Part C (GAP), Sect. 9.3.9

    This allows you to pick and choose the relevant portions of the specifications without drowning in the entire specification.

Related