This lab presents the steps to setup an environment for using the EVAL-CN0235-SDPZ evaluation board together with the BeMicro SDK USB stick, the Nios II Embedded Development Suite (EDS) and the Micrium µC-Probe run-time monitoring tool. Below is presented a picture of the EVAL-CN0235-SDPZ Evaluation Board with the BeMicro SDK Platform.
For component evaluation and performance purposes, as opposed to quick prototyping, the user is directed to use the part evaluation setup. This consists of:
The SDP-B controller board is part of Analog Devices System Demonstration Platform (SDP). It provides a high speed USB 2.0 connection from the PC to the component evaluation board. The PC runs the evaluation software. Each evaluation board, which is an SDP compatible daughter board, includes the necessary installation file required for performance testing.
Note: it is expected that the analog performance on the two platforms may differ.
Below is presented a picture of SDP-B Controller Board with the EVAL-CN0235-SDPZ Evaluation Board.
The circuit from the EVAL-CN0235-SDPZ board is a fully isolated lithium ion battery monitoring and protection system. Lithium ion (Li-Ion) battery stacks contain a large number of individual cells that must be monitored correctly in order to enhance the battery efficiency, prolong the battery life, and ensure safety.
The AD7280A contains all the functions required for general-purpose monitoring of stacked lithium ion batteries as used in hybrid electric vehicles, battery backup applications, and power tools. The part has multiplexed cell voltage and auxiliary ADC measurement channels for up to six cells of battery management. An internal ±3 ppm/°C reference is provided that allows a cell voltage accuracy of ±1.6 mV. The ADC resolution is 12 bits and allows conversion of up to 48 cells within 7 us.
The AD8280 is a hardware-only safety monitor for lithium ion battery stacks. The part has inputs to monitor six battery cells and two temperature sensors (either NTC or PTC thermistors). The part is designed to be daisy-chained with other AD8280 devices to monitor a stack of significantly more than six cells without the need for numerous isolators. Its output can be configured for an independent or shared alarm state.
The first objective is to ensure that you have all of the items needed and to install the software tools so that you are ready to create and run the evaluation project.
Below is presented the list of required hardware items:
Below is presented the list of required software tools:
The Quartus II design software and the Nios II EDS is available via the Altera Complete Design Suite DVD or by downloading from the web.
The Micrium uC/Probe Trial version 2.5 is available via download from the web at http://micrium.com/tools/ucprobe/trial/. After installation add to the “Path” system variable the entry “%QUARTUS_ROOTDIR%\bin\“ on the third position in the list.
Create a folder called “ADIEvalBoardLab” on your PC and extract the cn0235_evalboardlab.zip archive to this folder. Make sure that there are NO SPACES in the directory path. After extracting the archive the following folders should be present in the ADIEvalBoardLab folder: FPGA, Software, ucProbeInterface, NiosCpu.
After the Quartus II and Nios II software packages are installed, you can plug the BeMicro SDK board into your USB port. Your Windows PC will find the new hardware and try to install the driver.
Since Windows cannot locate the driver for the device the automatic installation will fail and the driver has to be installed manually. In the Device Manager right click on the USB-Blaster device and select Update Driver Software.
In the next dialog box select the option Browse my computer for driver software. A new dialog will open where it is possible to point to the driver’s location. Set the location to altera\<version number>\quartus\drivers\usb-blaster and press Next.
If Windows presents you with a message that the drivers have not passed Windows Logo testing, please click “Install this driver software anyway”. Upon installation completion a message will be displayed to inform that the installation is finished.
The next sections of this lab present all the steps needed to create a fully functional project that can be used for evaluating the operation of the ADI platform. It is possible to skip these steps and load into the FPGA an image that contains a fully functional system that can be used together with the uC-Probe interface for the ADI platform evalution. The first step of the quick evaluation process is to program the FPGA with the image provided in the lab files. Before the image can be loaded the Quartus II Web Edition tool or the Quartus II Programmer must be installed on your computer. To load the FPGA image run the program_fpga.bat batch file located in the ADIEvalBoardLab/FPGA folder. After the image was loaded the system must be reset. Now the FPGA contains a fully functional system and it is possible to skip directly to the DEMONSTRATION PROJECT USER INTERFACE section of this lab.
The lab is delivered together with a set of design files that are used to evaluate the ADI part. The FPGA image that must be loaded into the BeMicroSDK FPGA is included in the design files. This section presents the components included in the FPGA image and also the procedure to load the image into the FPGA.
The following components are implemented in the FPGA design:
|EPCS FLASH CONTROLLER||1800||2|
To load the FPGA image the following steps must be performed:
After finishing, the image is permanently loaded to the configuration Flash and the system will start with a blinking LED after reset or power up.
This section presents the steps for developing a software application that will run on the BeMicroSDK system and will be used for controlling and monitoring the operation of the ADI evaluation board.
Launch the Nios II SBT from the Start → All Programs → Altera → Nios II EDS 11.0 → Nios II 11.0 Software Build Tools for Eclipse (SBT).
NOTE: Windows 7 users will need to right-click and select Run as administrator. Another method is to right-click and select Properties and click on the Compatibility tab and select the Run This Program As An Administrator checkbox, which will make this a permanent change.
The tool will create two new software project directories. Each Nios II application has 2 project directories in the Eclipse workspace.
Since you chose the blank project template, there are no source files in the application project directory at this time. The BSP contains a directory of software drivers as well as a system.h header file, system initialization source code and other software infrastructure.
The software project provided in this lab does not make use of an operating system. All stdout, stdin and stderr messages will be directed to the jtag_uart.
In addition to the board support package settings configured using the BSP Editor, there are other compilation settings managed by the Eclipse environment such as compiler flags and optimization level.
In Windows Explorer locate the project directory which contains a directory called Software. In Windows Explorer select all the files and directories from the Software folder and drag and drop them into the Eclipse software project ADIEvalBoard.
Just as you configured the optimization level for the BSP project, you should set the optimization level for the application software project ADIEvalBoard as well.
Application code can be conveniently organized in a directory structure. This section shows how to define these paths in the makefile.
These 2 steps will compile and build the associated board support package, then the actual application software project itself. The result of the compilation process will be an Executable and Linked Format (.elf) file for the application, the ADIEvalBoard.elf file.
The BeMicroSDK hardware is designed with a System ID peripheral. This peripheral is assigned a unique value based on when the hardware design was last modified in the SOPC Builder tool. SOPC Builder also places this information in the .sopcinfo hardware description file. The BSP is built based on the information in the .sopcinfo file.
To run the software project on the Nios II processor:
This will re-build the software project to create an up–to-date executable and then download the code into memory on the BeMicroSDK hardware. The debugger resets the Nios II processor, and it executes the downloaded code. Note that the code is verified in memory before it is executed.
The code size and start address might be different than the ones displayed in the above screenshot.
A notable challenge in embedded systems development is to overcome the lack of feedback that such systems typically provide. Many developers resort to blinking LEDs or instrumenting their code with printf() in order to determine whether or not their systems are running as expected. Micrium provides a unique tool named µC-Probe to assist these developers. With this tool, developers can effortlessly read and write the variables on a running embedded system. This section presents the steps required to install the Micrium uC-Probe software tool and to run the demonstration project for the ADI evaluation board. A description of the uC-Probe demonstration interface is provided.
Launch uC-Probe from the Start → All Programs → Micrium → uC-Probe.
Select uC-Probe options.
Set target board communication protocol as JTAG UART
Setup JTAG UART communication settings
The following figures present the uC-Probe interface that can be used for monitoring and controlling the operation of the EVAL-CN0235-SDPZ evaluation board.
Section A is used to activate the board and monitor activity. The communication with the board is activated / deactivated by toggling the ON/OFF switch. The Activity LED turns green when the communication is active. If the ON/OFF switch is set to ON and the Activity* LED is BLACK it means that there is a communication problem with the board. See the Troubleshooting section for indications on how to fix the communication problems.
Section B is used to acquire data from the two AD7280As from the circuit. When pressing the Convert All button a conversion and a read will be initiated. The data read will be then converted to voltages before being displayed on the interface.
Section C is used to perform self test for both AD7280As. The data from the Self test registers will be displayed as voltage.
Section D displays the status of the ALERT pin on the master AD7280A. By default, the alert is not activated, so a configuration of the Alert register and Overvoltage/Undervoltage register is needed before the alerts can be displayed.
Section E allows to toggle the PD pin. If the pin is low, the AD7280As will be powered down.
Section F is used to activate/deactivate the AD8280s, used as secondary safety monitor. By hardware, the Overvoltage is set to 4 V and Undervoltage is set to 2 V. In case one of the cells goes beyound these voltages, the LEDs will indicate that. By pressing the Self Test button, the self test feature can be evaluated.
Section G is used to perform readings of any of the registers on the 2 AD7280a devices. Before pressing the Read button, the device on which the read is to be performed must be selected and also the register number. When reading from the Slave device, the LED will be ON. As a response the device address, register address and register data will be displayed, all in decimal.
Section A is used to select the address of the devive on which the register should be configured. The LED is on when the Slave device is selected.
Section B is used to configure the Control High Byte register. The first slider from left to right will select the conversion inputs. The second slider will select the conversion results that should be read. The third button configures the conversion start format. The forth slider enables/disables conversion averaging. The fith button selects the power-down format.
Section C is used to configure the Control Low Byte register. The first button from left to right will perform a software reset. The second slider will set the acquisition time. The third button will enable/disable the thermistor termination resistor. The fourth button can be used to lock the part to the new device address. The fith button allows incrementing the device address. THe last button will enable/disable the daisy chain register readback.
Section D is used to configure the Alert register and the Undevoltage/Overvoltage registers. By default no alert signals are generated or passed. When moving the sliders for the undervoltage/overvoltage registers, the voltage corresponding to that value will be displayed.
Section E is used to configure the Cell Balance register. By default the register is set to 0.
Section F is used to configure the Cell Balance timers registers. By default the timers are set to 0.
Section G is used to configure the Power Down timer. By default the timer is set to 0.
In case there is a communication problem with the board the follwing actions can be perfomed in order to try to fix the issues: