- Getting Started
- Getting Started
- nRF52 tutorial that works?
- Bluetooth low energy Services, a beginner's tutorial
- Bluetooth low energy Services, a beginner's tutorial
Getting StartedOther kits, dongles and software versions might work as well, but this is what I have used. This tutorial will not cover how to install and setup the software. Please search the forum if you run into trouble before posting questions here. This tutorial is intended to be a natural continuation of the tutorial " BLE Advertising, a beginner's tutorial ". It is recommended, but not necessary, to go through this tutorial first. It is expected that you have basic knowledge of how to use Keil, nRF Connect and nrfjprog and how to download your application to your kit. If you run into troubles please browse devzone, look for documentation on our Infocenterand read the user guides for your kits. I urge you to post any questions you might have on the forum and not below the tutorial. This makes it is easier for other users and Nordic employees to see and search for your question and you will actually most likely get a faster response! This structure defines basic elements such as services and characteristics, used in a profile. In other words, it is a set of rules describing how to bundle, present and transfer data using BLE. Read the Bluetooth Core Specification v4. It might be a little heavy reading, but it will certainly pay off in the end. In other words, a service is a collection of information, like e. For example they have defined a service called Heart Rate service. The reason why they have done this is to make it easier for developers to make apps and firmware compatible with the standard Heart Rate service. However, this does not mean that you can't make your own heart rate sensor based on your own ideas and service structures. Sometimes people mistakenly assumes that since Bluetooth SIG has predefined some services they can only make applications abiding by these definitions. This is not the case. It is no problem to make custom services for your custom applications. In other words, the characteristic is where the actual values and information is presented. Security parameters, units and other metadata concerning the information are also encapsulated in the characteristics. An analogy might be a storage room filled with filing cabinets and each filing cabinet has a number of drawers. The GATT profile in this analogy is the storage room. The cabinets are the services, and the drawers are characteristics holding various information. Some of the drawers might also have locks on them restricting the access to its information. Imagine a heart rate monitor watch for example. Watches like this typically use at least two services:. Now why bother with this? Why not just send whatever data you need directly without the fuzz of bundling it in characteristics and services? The reasons are flexibility, efficiency, cross platform compatibilities and ease of implementation. If a device contains more than one service you are free to pick and choose the services and characteristics you like. By bundling information this way devices can quickly discover what information is anrfvailable and communicate only what is strictly needed and thereby save precious time and energy. Remember that BLE is all about low energy. To continue the analogy: the storage room is located in a small business office and has two filing cabinets. The first cabinet is used by the accountants. The drawers contain files with financial details of the business, sorted by date. The drawers are locked and only the accountants and the upper management have access to them. The second cabinet is used by Human Resources and contains records over the employees, sorted in alphabetical order. These drawers are also locked and only HR and upper management have access to them.
Site Search User. Tech Support Community Nordic content. Nordic DevZone Nordic content Short-range guides. Getting Started Fundamental topics to get you started. Bluetooth low energy BLE-centric material, some basic and some more specific. Mocking CoreBluetooth 1 month ago. Mostly practical guides. Hardware and layout Hardware and layout guides and examples. Automating Power Profiler Kit measurements from the command line 8 months ago. Design Examples Practical hardware design examples. Capacitive Touch on the nRF52 series over 4 years ago. All posts. By date By view count By comment count Descending Ascending. Therefore, you can use nRF to emulate the functionality of nRF This blog…. Bluetooth low energy: Mocking CoreBluetooth. It is easy to start with, if one…. What is the difference between SDK and Softdevice? How can we select SDK and Softdevice versions? How can we understand the SDK directory…. Bluetooth low energy: Concurrent Advertising. I have been asked several times about variations of the following advertising scenario, so I decided to make a blog post that I can refer to, and hope it might prove useful for others out there that are…. Hardware and layout: Automating Power Profiler Kit measurements from the command line. Nordic's Power Profiler Kit PPK is an inexpensive piece of hardware that can provide a significant amount of insight into the operation and performance of your project. Although there is a lot that….
nRF52 tutorial that works?
Other kits, dongles and software versions might work as well, but this is what I have used. This tutorial will not cover how to install and setup the software. Please search the forum if you run into trouble before posting questions here. Please browse the Tutorial section and the Infocenter to find guides on how to use your equipment and compile your first BLE application. Here is an excellent blogpost that I highly recommend you read. It provides a more in depth explanation on how advertising works and is a natural supplement to this tutorial. If you run into troubles please browse devzone, look for documentation on our Infocenterand read the user guides for your kits. I urge you to post any questions you might have on the forum and not below the tutorial. This makes it is easier for other users and Nordic employees to see and search for your question and you will actually most likely get a faster response! First thing first: download the example code from github. It is based on the template example found in the SDK V There is still quite a lot of code left though, which is used to initiate and utilize processes running in the background. The code is not essential for this tutorial and can be left as is. If you are curious of what it is anyway then here are some links to documentation on some of the modules that are used in the code:. Your main. If you need help with this please have a look at this thread on devzone: Compiling github projects. It should compile without any errors or warnings. Now, let us have some fun right away. Then hit the download button in SES and load the example onto your kit as well. Now expand the "HelloWorld" device tree by clicking on the little cross to the left. You should see something similar to the next image. Address type as defined in the Bluetooth Core specification. See this post on devzone for more on address types. You should see that after each reset your device shows up with a different address in the device list. This functionality might be handy in certain situations demanding higher security. To keep it simple there are two advertising types; connectable and non-connectable. Non-connectable might be useful if you just need one-way communication and only need to broadcast a couple of bytes. One use case for this might for example be location awareness. If you want to send more data to a specific device, on the other hand, you need a connectable device. Examples here might be a heart rate sensor connected to an app on your phone or a Bluetooth headset. Now to the fun part! The advertising packet in this example already contains your full device name. It also contains flags defining some of the advertising options. The flag field is mandatory, but we will discuss it here.
Bluetooth low energy Services, a beginner's tutorial
I have an nRF52 board here from Nordic, and a cacophony of tools. I have a million sample projects from nordic, with no sane docs, and some soft devices with no sane docs either. I am no novice- i've been working on embedded all my life, and work on Cortex-M chips for a few years already. I erased my device. What now? I have to have one? I tried gcc, I tried keil. I tried jlink, i tried nrfjprog, i tried a normal SWD debugger to load code. Is it the right one? Digging further, I do see the bootloader having an SVC handler, except nowhere is it found in the source code. Disassembly shows a rather large-switch case based on passed params. As a sanity check I would like to point you to some documentation, if these are the ones you have been struggling with we do appreciate feedback. First off there's this introductory tutorial to development with Keil that goes through first flashing of the kit and a simple introduction to BLE. Our documentation is gathered at infocenter. Here you can find the product specification for nRF You can find documentation for the Software Development Kit and its examples, the SDK can be downloaded from developer. As with any hex file there are numerous ways of programming it, this is just my preference. The documentation for the SoftDevices can be found here. Also make sure to check the compatibility matrixwhere you can find information on which revision of the chips is supported by which version of the SDK and SoftDevice. Finally I would like to point you to the tutorial and blog sections here on devzone, older questions also often have answers to problems that might be relevant to you. I can relate so much to this but get most of it working eventually. But I agree, the comments in the tutorials feel very much ignored. I am in the same situation as you. SDK functions change from one version to an other, no real doc, "template" examples are not really "template". I have been spendind 4 days trying to make a service but nothing works at all That would be great if there is a real big tutorial, step by step, to understand how to use the nRF52DK and after how to program an nRF5x chip with SWD pins for example. For the moment, most of the links I see on the devzone are outdated because the links have moved in the infocenter Site Search User. Tech Support Community Nordic content. Attachments 0. Nordic Case Info. Case ID: Share More Cancel. I tried them all. No, really. This is the worst situation I've seen in any vendor's libraries and support systems. Literally there is no step-by-step to get a simple BLE app to run. Which of the ways to program it should I use? Sample App?