The EV-Tempsense-ARDZ Mbed support software can be used as a starting point for developing your own code for Analog Devices EV-TempSense-ARDZ board 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 TempSense evaluation board 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 ADT74XX/ADT73XX eval-board such as the EV-TempSense-ARDZ Evaluation board which has the ADT7320 (SPI) and ADT7420 (I2C) built in with the ability to connect external sensor via headers on the 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 EV-Tempsense-ARDZ 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. 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 ADT73XX (SPI) and ADT74XX (I2C) 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 sensors
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-TempSense-ARDZ board, it can use the 120-pin SDP connector on the underside of the board, or the Arduino connector can be used.
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 EV-TempSense 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.
The EV-TempSense-ARDZ board supports remote ADT74XX and ADT73XX devices. These can be connected to pins at the top of the eval board using ribbon cables or jumper wires, these pins are marked in the image below. SPI devices (EVAL-ADT7320-MBZ) and I2C devices (EV-ADT7420-MBZ) connect to their respective header pins by matching the pins on the board to those labelled on the remote board.
There is no need to adjust the source code to start using the remote sensors. Selecting these devices can be done within the provided application which is described below.
This section briefs on the usage of MBED firmware. This also explains the steps to compile and build the application using mbed and make based build.
Source code is hosted here:
Build Guide for Precision Converters MBED firmware (Use below link):
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.
Set the baud-rate for 115200 and select the connected controller board’s COM port. If using CoolTerm you should be able to keep the defaults, however adjustments may need to be made to how carriage return (CR) is handled in order for everything to display correctly.
The software is designed to be straight forward to use, and requires little explanation. Simply select which interface (SPI/I2C) you would like to use, whether you want to use the internal sensor or a remote one and then 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 features of the ADT73XX and ADT74XX are coded, but it's likely that some special functionality is not implemented.