The nanoDac+ Mbed support software can be used as a starting point for developing your own code for Analog Devices nanoDAC+ products in your own environment utilizing the benefits of the Mbed platform. Analog Devices is an MBED Partner and develops code on the platform for multiple products. The Analog Devices Mbed code-repo can be found in the links below.
This guide will focus on the Analog Devices SDP-K1 controller board, as it is directly compatible with the nanoDAC+ family of evaluation boards and is an MBED-Enabled device. Customers are of course, not limited to using the SDP-K1 board for code development, given that any ARM-based, MBED-enabled board that satisfies a small set of requirements can use the provided code and it will work with only minor changes to the source (see below).
It is further assumed that SDP-K1 board will be connected to the appropriate nanoDAC+ eval-board such as the EVAL-AD5686R Evaluation board.
For developing firmware code for controller boards on the Mbed platform go the link below.
At this time Analog Devices supports Mbed code development only on the Mbed online-compiler. See here for instructions on setting up an account and using the compiler. Analog Devices may, at a later date support other offline-IDE's. This guide focuses on the SDP-K1, connected to the EVAL-AD5686R evaluation board, but it should be general enough to cover any compatible controller board (the controller board should be Mbed-enabled, and expose at least SPI or I2C and some GPIO's).
The software described below allows for an Mbed enabled controller board to be connected with an Analog Devices evaluation board from the nanoDAC+ family. Unmodified, the code will communicate over any serial terminal emulator (CoolTerm, putty, etc) using the UART provided by the controller board over USB.
The software provides a basic user-interface for interacting with the evaluation-board. All the main functionality of the nanoDAC+ is provided in the application-code in abstracted form and the user is free to customize the software to suit their own needs for working with the nanoDAC+.
If you have some familiarity with the Mbed platform, the following is a basic list of steps required to start running the code, see below for more detail.
The SDP-K1 board has two ways to connect to the EVAL-AD5686R board, it can use the 120-pin SDP connector on the underside of the board, or the Arduino connector can be used, together with jumper wires as described below. If the SDP-K1 controller board is not used, then connect to the Arduino headers using short jumper wires.
The Getting Started with Mbed page describes the Arduino Uno Header, the SDP connector, pin-outs and other information related to understanding the SDP-K1 controller board.
Connecting the EVAL-AD5686R evaluation board using the SDP connector on the K1 is the simplest and most convenient way to get up and running quickly, simply mate the two boards to together, no jumpers are required. The user guide for the evaluation board should be consulted when configuring the jumper settings on the evaluation board, but it will work if the PWR_SEL jumper is set to 3.3V, and P1 should be removed.
When using any controller board other than the SDP-K1 it will be necessary to use ports exposed on the controller connected using wires to the evaluation board. This is shown here for a ST Nucleo board connected to the EVAL-AD5686R evaluation board using the Arduino Header, but different boards might have their SPI/I2C/GPIO ports exposed differently. The pins on the Arduino header must be shorted to the evaluation board as follows. The pin mappings for these are controlled in the app_config.h file and should match your controller board.
|Arduino PIN||MBED NAME||EVAL-AD5686R PIN|
* Map these pins to any spare GPIO - shown here according to ADI's app_config.h mapping
ARM provide a guide to setting-up and using their online-compiler here. For the SDP-K1 the following guide can also be used to help understand the process. Specifically for the EVAL-AD5686R evaluation board and the SDP-K1, the following steps can be used.
The firmware is delivered as a basic, text-based user-interface that operates through a UART on the controller board using the same USB cable that is used to flash the firmware to the boards. Any terminal-emulator should work, but it is not possible for Analog Devices to test every one. It is necessary to connect a serial terminal-emulator to interact with the running firmware.
Here CoolTerm is used as an example, Analog Devices does not endorse any particular program for this, but CoolTerm works well and is made freely available, other terminals such as Tera Term, or PuTTY will work just as well. Set the baud-rate for 115200 and keep the defaults for everything else. The actual values used can be found by looking at the source code in main.cpp
The software is designed to be intuitive to use, and requires little explanation, simply enter a number corresponding to the required command and follow the on-screen prompts. The code is also written with a view to keeping things simple, you do not have to be a coding-ninja to understand and expand upon the delivered functions.
It is hoped that the most common functions of the nanoDAC+ family are coded, but it's likely that some special functionality is not implemented.
The software comes with an app_config.h file which (at the moment) serves two purposes.
The software supports most products in nanoDAC+ family, change the #define ACTIVE_DEVICE ID_ADXXXXX found in app_config.h to suit your selected device. The products supported are enumerated in the ad5686_type, which is an enum found in AD5686.h, the software defaults to the AD5686R device.