The ADuCM3029_demo_ad5592r_ad5593r project provides a solution to control a configurable input/output system using the EVAL-AD5592R-PMDZ or the EVAL-AD5593R-PMDZ and the EVAL-ADICUP3029. Both boards use a minimalist 8-channel, 12-bit, configurable ADC/DAC/GPIO device with either a SPI interface for EVAL-AD5592R-PMDZ and I2C interface for EVAL-AD5593R-PMDZ. The boards are SPI and I2C, respectively, PMOD form factor.

The ADuCM3029_demo_ad5592r_ad5593r project uses the EVAL-AD5592R-PMDZ or EVAL-AD5593R-PMDZ to provide a low-cost alternatives to the full-featured product evaluation boards, with terminal block connections and no extra signal conditioning. The application makes full use of the configurable 8 channels capability of the AD5592R and AD5593R, as every channel can be individually set to be either ADC, DAC, input GPIO or output GPIO. This provides a compact and highly flexible solution to signal acquisition and output control.

The application is controlled by the user with a CLI implemented using the serial UART core in the ADuCM3029 controller. The CLI is displayed on a connected PC using a serial terminal connection.

The program is divided in 2 parts: the setup part in which the present module is discovered and the main process. To do the discovery routine in the setup stage, the application first initializes the board SPI driver and tries to do a write and a read to a register to see if any device responds. If there is no SPI the application does the same test for the I2C device. If no device is found the application returns with an error message displayed on the serial connection. If any of the devices is found the program displays the active device and continues to the main process loop. If both PMODs are connected at the same time the one with SPI will be activated. The main process loop starts with the mirror mode. This mode sets up 4 channels as input and the other 4 as output, and then mirrors the inputs on the outputs. For example, if input channel 0 is driven externally to 1V the corresponding output channel, channel 7, will be driven to 1V as well by the application. The channels are linked as follows:

• Channel 0 (ADC) → Channel 7 (DAC);
• Channel 1 (ADC) → Channel 6 (DAC);
• Channel 2 (input GPIO) → Channel 5 (output GPIO);
• Channel 3 (input GPIO) → Channel 4 (output GPIO).

More information about the CLI commands can be found here.

The following is a list of items needed in order to replicate this demo.

• Hardware
  • EVAL-ADICUP3029
  • EVAL-AD5592R-PMDZ or EVAL-AD5593R-PMDZ
  • Mirco USB to USB cable
  • PC or Laptop with a USB port
• Software
  • ADuCM3029_demo_ad5592r_ad5593r demo application
  • CrossCore Embedded Studio (2.8.0 or higher)
  • ADuCM302x DFP (3.2.0 or higher)
  • ADICUP3029 BSP (1.1.0 or higher)
  • Serial Terminal Program
    • Such as Putty or Tera Term

1. Connect EVAL-AD5592R-PMDZ or EVAL-AD5593R-PMDZ board to the EVAL-ADICUP3029 as seen in the pictures below:
   EVAL-AD5593R-PMDZ conforms to Pmod spec 1.1.0. This is physically compatible with Pmod platforms conforming to earlier Pmod specifications, provided that the VCC, GND, SDA, SCL pins are aligned with the corresponding signals on the platform board, leaving INT and RESET disconnected as shown.
2. Connect a micro-USB cable to P10 connector of the EVAL-ADICUP3029 and connect it to a computer.
   Refer to https://blog.digilentinc.com/announcing-the-digilent-pmod-interface-specification-1-1-0/ for details on the Pmod specification.

The configuration parameters can be found in the config.h file.

AD5593R_A0_STATE - This define contains the logic state of the A0 pin of the AD5593R device. This pin factors in the device I2C address and is by default logic “0” so no change is necessary to the define. If the pin state is changed by moving the pull-down resistor to be a pull-up resistor, this define needs to be changed to logic “1” too for the program to work.

   #define AD5593R_A0_STATE 0

Typing help or h after initial calibration sequence will display the list of commands and their short versions. Bellow is the short command list:

• For the “h”, “stts”, “m” and “t” commands press Enter without inserting any space afterwards.
• For the “ao”, “ai”, “do” and “di” commands, to invoke in application instructions, write just the command without parameters, insert a space afterwards and press Enter.

We recommend not opening the project directly, but rather import it into CrossCore Embedded Studios and make a local copy in your workspace.

The source code and include files of the ADuCM3029_demo_ad5592r_ad5593r can be found here:

The official tool we promote for use with the EVAL-ADICUP3029 is CrossCore Embedded Studio. For more information on downloading the tools and a quick start guide on how to use the tool basics, please check out the Tools Overview page.

For more detailed instructions on importing this application/demo example into the CrossCore Embedded Studios tools, please view our How to import existing projects into your workspace section.

For more detailed instructions on importing this application/demo example into the CrossCore Embedded Studios tools, please view our How to configure the debug session section.

Project structure includes:

• AD559xR driver module with files: ad5592r-base.c, ad5592r-base.h, ad5592r.c, ad5592r.h, ad5593r.c, ad5593r.h;
• Main file ADuCM3029_demo_aiodiopdmz.c
• Application module with files: aio_dio_pdmz.c, aio_dio_pdmz.h;
• CLI module with files: cli.c, cli.h;
• Configuration file config.h
• Communication and GPIO driver module with files: platform_drivers.c, platform_drivers.h;
• Power core initialization module with files: power.c, power.h;
• Timer and delay driver module with files: timer.c, timer.h.

End of Document