RSS
Sort by » date activity comments

280 blog posts

0
comments
by Eirik Midttun

#HackDublin article with videos

I recently blogged about Nordic and Hackathons, but didn't include too much information; I knew already there was something coming. And now it is finally published: #HackDublin - Ireland's First Design & Hardware Hackathon. In this comprehensive article by InspiredStartups you will find videos of the idea pitches, team interviews, final pitches, and some presentation. If you are involved in the maker movement you probably want to see the talk by Mark Hatch, the founder of TechShop.

If you click on the image below you will see an interview with my favourite team, the CITY+ team. They used the nRF51...

0
comments
by QuickLogic

QuickLogic Announces TAG-N Wearable Sensor Hub Eval Kit

Today, QuickLogic announced the availability of our TAG-N Wearable Sensor Hub evaluation kit for the Nordic Semi nRF51 DK, Nordic’s all-in-one, multiprotocol development kit for ultra-low power wireless development on the nRF51822 SoC. We’re very excited to be part of the Nordic ecosystem, and just as excited to offer system designers an off-the-shelf, proven sensor hub for immediate integration.

image description

System Description:

The TAG-N system is a self-contained system. It contains the QuickLogic’s ArcticLink 3 S2 sensor hub, running our Gesture and Context Catalog CSSP technology. The TAG-N is Arduino-compatible, enables a direct plug-in into the Nordic DK...

1
comment
by Krzysztof Loska

Native support for nRF51 SDK in Keil IDE

Recently we introduced support for CMSIS-Pack into our nRF51 SDK. The nRF51 SDK is natively supported in the Keil IDE. This means that nRF51 SDK latest version and example software for nRF51 are easily found in the Keil IDE. To do this install the Keil IDE and use the build-in “Pack Installer” (it is important to use Keil 5.12 or later). This tool also informs you of newest released versions of the SDK. It also has a nice browser to look through available examples.

Here is a short tutorial on using these features.

1.Install Keil IDE 5.12...

4
comments
by Milan

Programming nRF51 with ST-Link & uVision

Hi,

I am planning to design a device based on nRF51-dk but with external programmer. I have ST-Link available so I thought I just provide a simple walk through showing how to set it up.

Firstly, here is shown how to wire up the programmer with dk. I used only four wires so only one ground pin. On the devkit P18 connector these are the pins 1,2,3,4.

image description

Next set the debug interface and go to settings.

image description

Select SW port instead of JTAG and if your device is powered and wired up correctly you should see the SW...

4
comments
by Eliot Stock

Visualising your memory usage

The linker in the GCC toolchain, ld, produces a *.Map file which shows you how the memory on your micro is being used. This file is a goldmine of information but it's a bit difficult for humans to absorb.

I've whipped up a web page which uses the excellent D3.js library to draw a visualisation of your memory usage, using the *.Map file as input. Blocks of memory are drawn proportionally so it's easy to see how much memory you have left and where it's all being used. Click on a block to zoom in...

3
comments
by Stefan Birnir Sverrisson

Using the ADC with the S110 SoftDevice

A good place to start with getting to know how to use the ADC with the S110 SoftDevice is by using one of the BLE ADC code examples provided on Nordic's Github page, where BLE examples have the "ble_" prefix.

Sampling frequency limitations

During a BLE transmission event the CPU will be blocked. This will limit the sampling frequency of the ADC. The ADC will be able to process up to 50 k samples per second but the SoftDevice will block the CPU during a radio event and limit the ADC sampling frequency. This is because the ADC has...

3
comments
by Eirik Midttun

Nordic sponsoring hackathons

Right before Web Summit - the "Davos for Geeks" - Nordic Semiconductor sponsored its second Hackathon in Dublin: the Hardware Hackathon. As a sponsor Nordic provides hardware and mentors for the participants at the event. Earlier this year we had our first participation at such an event in Las Vegas at the AT&T Code for car and home hackathon, where we also sponsored a cash prize. The experiences have been good so far, and the plan is to sponsor more events.

Prototype of traffic safety concept

Image: Prototype of a traffic safety concept from the AT&T HAckathon in Las Vegas

For both hackathons there were...

3
comments
by Asbjørn

Nordic beacons and iOS

The beacon market is going in various directions with regard to format and limitations, but the nRF51822 can support all the various BLE based beacons as it’s just a specific type of non-connectable BLE advertising. The difference is that the content of the advertising package may differ between various beacon implementations. The structure of the beacon package is described well in the spec description from AltBeacon (http://altbeacon.org/) and this figure.

You can with the nRF51822 be compatible with different beacon implementations by changing the content of the advertising package. There’s also an option to use the...

4
comments
by Jason

Make your own "Remote Control" app

Flow us to make your own RC App to control everything so easy.

web-site

image description

0
comments
by Jason

Now, uCXpresso.NRF provides the free evaluation license on the GitHub

uCXpresso.NRF is a RTOS C/C++ Framework,

Features:

  1. Develop on Mac OS/X, Linux and Windows with LPCXpresso IDE (free).
  2. Multi-Tasking RTOS supported
  3. Enhanced BLE C++ framework
  4. Tickless Low Power technology ready. Activity avg. @ 26uA (Min. 6uA)
  5. Using SoftDevice 7.1

Go on the GitHub:https://github.com/ucxpresso/nano51822

2
comments
by mira67

change device name through BLE

  1. Build a custom BLE service and enable the write attribute
  2. Configure the characteristic "attr_char_value.max_len = MAX_LEN"; max_len should be larger than your device name
  3. In the BLE event handler, read back the data like below

     if ((write_evt->handle == m_custom_service_char.value_handle) && (write_evt->data[0] == RENAME))
     {
                     //device name limited to 10bytes
                     for (uint8_t i = 0; i < MAX_DEVICE_NAME_LEN; i++){
                         device_name[i] = write_evt->data[i+1];
                     }
    
                     ble_gap_conn_sec_mode_t sec_mode;
                     BLE_GAP_CONN_SEC_MODE_SET_OPEN(&sec_mode);
                     err_code = sd_ble_gap_device_name_set(&sec_mode,(const uint8_t *)device_name,MAX_DEVICE_NAME_LEN);
                     APP_ERROR_CHECK(err_code);
     }
    
6
comments
by Stefan Birnir Sverrisson

nRF51822/nRF51422 getting started and documentation overview

BLE and ANT development kit

Nordic Semiconductor offers the nRF51 series for BLE and/or ANT wireless connectivity. The nRF51 (nRF51422 or nRF51822) is a System on Chip, which means it has internal microcontroller to perform various operations. There are onboard peripherals like UART, SPI, ADC, timers, configurable GPIOs, etc. For nRF51, there are number of protocol stacks to develop on, BLE peripheral stack (S110), BLE central stack (S120), BLE central+peripheral stack (S130), ANT stack (S210) (for nRF51422 only) and ANT+BLE stack (S310) (for nRF51422 only). For nRF51 development with any of those stacks, we provide the nRF51...

0
comments
by scytulip

Keil in-line program through DFU BLE

I am investigating Master Emulator API and found something interesting that can help you program your device through BLE DFU in Keil. This method calls the python script used in MCP. If you can use MCP DFU to program your device, it will also works for your Keil. BTW, this method emulates the exact BLE DFU procedure and the application is available just after a successful upload. No modification on bootloader or application code is required.

Requirement

A device (like PCA10000) running Master Emulator.

Setup

  1. Download and install the newest IronPython (Python with .Net support) from http://ironpython.codeplex.com...

2
comments
by scytulip

Nordic Semiconductor nRF51822 Firmware for Background Data Recording

Nordic Semiconductor nRF51822 Firmware for Background Data Recording

Updating on https://github.com/scytulip/nrf51-back-rec


Design Objective

This firmware is designed for low-cost long-time low-power unattended data recording.

  • Low-cost: All collected data is preserved in nRF51822, sharing the FLASH memory with the SoftDevice and the program.
  • Unattended: The firmware executes automatic data collection and preservation until data memory area in the FLASH is full.
  • Low-power: The firmware automatically turns off BLE and redundant hardware to extend battery life.

BLE Link could be intentionally enabled to transfer data. When a BLE connection is created, the firmware will report the data reading...

1
comment
by Hugh

Nordic nRF51822 ARM Cortex-M0 Development using emIDE

Nordic nRF51822 ARM Cortex-M0 Development using emIDE

To avoid the hefty charges with commercial compilers I tried emIDE with some success; here are the settings I used for the EV Kit

Official emIDE website: http://www.emide.org/

Ev Kit: https://www.nordicsemi.com/eng/Products/Bluetooth-Smart-Bluetooth-low-energy/nRF51822-Evaluation-Kit

Exception Vectors

Any code compiled with a resident Soft Device has a vector table at the link address (eg, Soft Device 110 v7 requires user code to be at 0x16000, so the vector table will be at that address). The reset vector at 0x16004 will be the start address of the user...

3
comments
by Salman

Beacon Kit - Mistake in Ref_Design_UG_v1.0

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.image description(/attachment/e0adb43d9ba15501224dce2c643476ba)

15
comments
by Salman

SD card interfacing

Hi,

I have written SD & SDHC card routine for reading, writing and erasing data from SD card. It used the hardware SPI of nRF51822.

NOTE:

1)Define the PINs of SD card first before initialing.

2)Define MOSI, MISO and SCK pins only, define the CS pin to some other pin that is not being used( these pin are define in spi_master_config.h )

3)CS pin should be separately define in SD_Routines.c by the name #define MMCSD_PIN_SELECT 29

4)If you are facing problem in using my library then first test you SPI separately.

SD_Routines.c SD_Routines.h

0
comments
by Stefan Birnir Sverrisson

How different BLE packet types influence throughput

There are several types of write operations, write request with authorization, write request without authorization and write command. You can see message sequence charts for those messages here and here.

Write command is a write without acknowledgement and write request is write with acknowledgement. As described in the sequence chart, the ATT will automatically send ack when you transmit write request from the central device. Write Command on the client side should generate BLE_GATTS_EVT_WRITE(WRITE_CMD, data) event on the server (nRF51822) side.

Packet exchange with Write Requests and Indications

When transferring data with a write request from GATT client or...

4
comments
by Sebastian

RSSI Viewer

This summer, we offered several internships in our Krakow office, where students could work on various projects. One of these projects was the RSSI viewer developed by Piotr Czerwiec, a set of programs to visualize 2.4 GHz band usage. The RSSI viewer scans this band, records signal level on particular frequencies, and presents combined results in several ways. The tool can be used to look for interferers and to check how channels are utilized. I hope you find the tool useful! Comments and suggestions for improvements are welcome in the comments section.

PC application

There are several ways to...

4
comments
by Stefan Birnir Sverrisson

Measuring Lithium battery voltage with nRF51

Here is an example of a hardware setup to measure the voltage on a Lithium battery with a voltage divider and a connected capacitor. The Lithium battery typically has a voltage range of 2.7 - 4.2 V and we (Nordic) recommend that you divide the battery voltage with two resistors, R1 = 10 MΩ and R2 = 2.2 MΩ. After you do this you need to connect a 22 nF capacitor (C2 in the figure below) from your ADC analog input pin (AIN) to ground. With this configuration you can sample up to 20 Hz for 8-bit sampling and up...

« 1 ... 11 12 13 14 »

Tags