Over the last few months, work has been done to create a new Developer Zone on a more robust and future-proof foundation. Today, we're finally launching the result of this effort.
We've been tremendously happy with the way the community have built on this site over the past year or so a lot stays the same:
Apple’s newest technology known as iBeacon has taken the retail world by storm, and should definitely be considered as a mobile marketing tactic for all companies. iBeacon is an indoor positioning system retailers use to notify nearby IOS device users of their presence. iBeacon also sends push notifications or text messages to customers letting them know about special promotions companies are offering. Customers can even search for specific items using iBeacon to find the best deals at the closest locations. The best part about the iBeacon technology is that it is low cost, making mobile marketing easy to afford...
Do you not use Windows but OS X or Linux? Do you use Windows but find the old tools expensive and terrible to deal with? Are you a hobbyist who doesn't have $2000 and an annual fee to spend on a toolset you don't like?
I am some of those things. I'm an OS X user, I don't love using parallels unless I can't help it, I find Keil to be a pretty poor product (sorry Keil but I do) and way beyond what I'm prepared to spend to fund a hobby.
Votes on QUESTIONS tells the users which questions that are great and useful.
Votes on QUESTIONS quantifies the interest of getting an answer to a question.
Sort your search on votes to find the most voted, useful and great questions.
Votes on ANSWERS tells the users which answers that are great and useful. The answers with the most votes inside a question will rise to the top.
Votes increases the reputation of the user who asked the question, or answered it.
Thank the user by voting!
Comments to a question or answer should only be used to ask for more information or for clarification of a question or answer.
Edit your question or answer to be as good as possible, fix mistakes, improve formatting, or clarify its meaning.
Editing is very important for making questions and answers useful to others, and getting more votes.
Nordic Semiconductor offer two gateways for asking questions about anything connected to their products, the MyPage support portal and Nordic Developer Zone. Questions in the support portal are only visible to, and answered by the application engineers in the Nordic Semiconductor’s support team. Questions in Nordic Developer Zone can be answered by anyone, the support team, other developers, and even yourself. Questions in the MyPage support portal are private, while in Nordic Developer Zone they are public.
Please search the Nordic Developer Zone before asking. Your question may be answered already. This gives you the answer faster, and limits...
Before you ask your question, please remember to check if it is suited for Nordic Developer Zone, and that it has not been asked before. Please search Nordic Developer Zone, if you find your question, please vote on it.
A question should be clear and concise, leaving no doubt about what you are asking. Include details about what you have tried and exactly what you are trying to achieve. Avoid asking multiple unrelated questions in one question, ask...
You should never ask your question as an answer to another question. Add it as a new question, and link to the question if it’s relevant.
You should never ask your question as a comment to another question, if you aren’t asking for more information or for clarification of that question. Add it as a new question, and link to the question if it’s relevant.
You should never ask your question as a comment to an answer, if you aren’t asking for more information or for clarification of that answer. Add it as a new question...
If you bought nRF51822 Development Kit and want to quickly and easily begin development without the need to own nRFgo Starter Kit, you can check the BLE DEVKIT.N R2 main board at ebay. More information and documentation you can find at the product page here.
This blog post will not take installation of above dependencies into consideration.
Configuring a project for CMSIS-DAP debugger:
Open a project in Keil, and go to Options for Target, and select CMSIS-DAP Debugger under the debug tab:
Check that the "Use Debug Driver" is checked under Utilities tab:
Now go into the debugger settings and verify that the nRF51xxx programming algorithm is chosen:
Go to tab "debug" and see that the debugger and device...
I created this blog post to document the bugs reported on nRF51 SDK v6.0.0
The workaround for each bug would also be provided here as a temporary solution before the bug is fixed in the future release of the SDK.
Our most advanced Bluetooth Smart SoftDevice to date is now - S130. We're excited in a big way about this one covering as it does so many different options in one protocol stack.
Again, we always value feedback from you guys toiling hard out there making great and cool stuff that the world gets to see and use, or just making things because it's fun and cool. So please let us know here - what's great, what's not, improvements, tweaks, it's all great for us, and you in the long run.
cheers, The Nordic Team
You may have a nRF51 chip that is "bricked" and both nRFGo Studio and nrfjprog recover option doesn't work. You can try to use J-link Commander to recover. In some case, J-link Commander showed that it can recover the chip when nrfjprog and nRFGo Studio couldn't.
Jlink Commander should be installed automatically when you install Jlink driver. Here is the screen when you start J-Link Commander and select the J-link programmer (if you have more than one):
When you have the command line ready you can type:
w4 4001e504 2
w4 4001e50c 1
w4 4001e514 1
Atomwear is a micro, modularized, open source, wearable BLE device for DIYers. It makes any BLE(Bluetooth Low Energy) projects easier
Overview - What’s the Atomwear?
Atomwear is a BLE product based on a Nordic BLE chipset. It’s different from other wrist straps available in the market, such as gearfit and jawbone.
Atomwear is designed specifically for DIYers. just like building blocks for kids, Atomwear components allow you to build it into whatever you like, be it a bracelet or otherwise!
Atomwear is fully open source. The aim of Atomwear is to speed up your development cycle. Choose Atomwear...
Updated version here (21.04.15): https://devzone.nordicsemi.com/tutorials/7/development-with-gcc-and-eclipse/
I have noticed that there have been several questions on development with Eclipse and GCC, and I have also been trying myself for quite some time to make it work properly. It finally seems like I have figured out an approach that works for me. I.e., successfully importing and debugging of example projects from the nRF51 SDK. So I thought I could make a blog post to share my setup and hopefully help others who are also new to Eclipse and GCC.
Inspired by other devzone...
Since I wrote about CrossWorks a few weeks ago, several people have mailed me and asked me if I have any sample projects. I didn't, so I just created some.
I've created projects which build blinky_example and ble_app_hrs for each of the three boards NRF6310, PCA10001 and PCA10000.
The projects follow the same directory structure that Nordic's examples do and are designed to unpack into the SDK directory (if this concerns you please make a copy of it first). So for instance the current nrf6310 blinky_example directory looks something like this
Board/nrf6310/blinky_example /arm/ /gcc/ /iar...
Em::Blocks supports now the nRF51 devices from Nordic. You can select in the new project wizard which device family (51422 or 51822) and if soft devices are needed or not.
The templates for the softdevices are empty after first installation. The packages must be downloaded from the Nordic download section (after login) and unpacked inside the wizard template sub directories. After the execution of the convSD.bat file there will be c-array files and API includes generated which can be used by the wizard.
The softdevices are placed at the right location by the linker so you don't...
I connected the programming header as described in "nRF6930_Beacon_Ref_Design_UG_v1.0.pdf" 5.5.4 Programming interface. I was trying to program Beacon Kit but failed many times then I compared it with schematic of of Beacon Kit. I found out that there is a mistake in the documentation. In P2 pin number 6 is not ground its actually P0.11 and pin number 5 is not P0.11 its ground.
Many of you must be facing this same problem.
I am attaching screen shot that will clearly indicate the mistake.(/attachment/e0adb43d9ba15501224dce2c643476ba)
I recently decided to try the nRF51 SDK on Mac OS X to see how it was to compile and program the example applications. It worked nicely, and it wasn't even that hard to figure out. But evidently there were things to find out, and before things were actually working there was always the fear of discovering that some of the setup was wrong and you have wasted hours on a stupid mistake.
The questions are many: Do I have the right tools? Where do get started in the SDK? Are there other changes needed? And from experience there...
In this project, we will control two motors over BLE using the Nordic nRF51-DK. To do this, we will use a motor driver based on the Toshiba TB6612FNG chip. We will use GPIOs and PWM to communicate with this board.
Read details here: