With its 20-channel capability and versatile PIXI™ technology, our solution empowers engineers to create complex systems that demand high-performance mixed-signal data conversion
A
A
Hardware Overview
How does it work?
PIXI Click is based on the MAX11300 from Analog Devices. The main feature of this IC is the proprietary PIXI™ technology. PIXI™ is an abbreviation for the Programmable mIXed signal In/Out, a technology that allows very flexible routing of both digital and analog signals. The MAX11300 IC has 20 configurable mixed-signal I/O ports. Each port can be independently configured as a DAC output, an ADC input, a GPI, a GPO, or an analog switch terminal. User-controllable parameters are available for each of those configurations. The device also features internal and external temperature sensors with ±1˚C accuracy. The device uses the SPI Mode 0 interface for communication with the controller, with the clock up to 20MHz. The MAX11300 device features a 12-bit successive approximation (SAR) ADC module, which can sample signals on a single port up to 400Ksmp/S. Like all the segments of this device, it also offers great flexibility; the signal can be unipolar or bipolar. Each ADC-configured port can be programmed for one of four input
voltage ranges: 0V to +10V, -5V to +5V, -10V to 0V, and 0V to +2.5V. There are two inputs for the reference voltage, but the internal reference voltage of 2.5V can also be used instead. The CNVT# pin can trigger the converter, routed to the PWM pin of the mikroBUS™. This pin has to stay in the LOW logic state for at least 0.5 µs to trigger the conversion. There are several conversion modes, including sampling on a single port or sweeping through all the configured ADC ports. ADC offers the averaging feature, too. It can average readings of the ADC-configured ports to blocks of 2, 4, 8, 16, 32, 64, or 128 conversion results. The buffered DAC converter is also 12-bit, which can output up to 25Ksmp/s on a single port. The output stage of the DAC is equipped with the driver, which offers ±10V on output and high current capability, using the dedicated power supplies (AVDDIO, AVSSIO pins of the PIXI™ header). The DAC module also uses internal or external reference voltage. The flexibility of the PIXI™ routing also allows monitoring of the DAC-configured ports
by utilizing the ADC module. All the DAC ports are protected from overcurrent, and such events can generate an interrupt on the INT pin, routed to the INT# pin on the mikroBUS™. Each of the PIXI™ ports can be configured as the general purpose input or general purpose output pin (GPI/GPO). When set as the GPI pin, the programmable threshold can be set by its data register from 0 to the AVDD voltage. The events like rising edges, falling edges, or both can be sensed this way, generating an interrupt. A GPO pin can have a programmed HIGH logic level, up to four times the DAC referent voltage. The host can set the logic state of GPO-configured ports through the corresponding GPO data registers. Combining GPI and GPO-configured ports allows unidirectional and bidirectional level translator paths to be formed, allowing all kinds of level shifters to be built. Bidirectional level translators are built using adjacent pairs of pins and are meant to work as the open drain drivers, so the pull-up resistors should be used to achieve proper voltage levels.
Features overview
Development board
Nucleo-64 with STM32F410RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU

Architecture
ARM Cortex-M4
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support
Library Description
This library contains API for PIXI Click driver.
Key functions:
pixi_write_reg
- Generic write functionpixi_read_reg
- Generic read function
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* \file
* \brief Pixi Click example
*
* # Description
* This example showcases how to initialize, configure and use the Pixi Click moduel. The Click
* features Maxim Integrated's versatile, proprietary PIXI™ technology - the industry's first
* configurable 20-channel mixed-signal data converter.
*
* The demo application is composed of two sections :
*
* ## Application Init
* This function initializes and configures the Click and logger modules. After the initial setup
* a device id check is performed which will stop the module if the check fails. Additional con-
* figurating is done in the default_cfg(...) function.
*
* ## Application Task
* This function sets the output signal on port 0 to different values every second.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "pixi.h"
// ------------------------------------------------------------------ VARIABLES
static pixi_t pixi;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( )
{
log_cfg_t log_cfg;
pixi_cfg_t cfg;
uint32_t res;
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, "---- Application Init ----" );
Delay_ms ( 100 );
// Click initialization.
pixi_cfg_setup( &cfg );
PIXI_MAP_MIKROBUS( cfg, MIKROBUS_1 );
pixi_init( &pixi, &cfg );
// Device ID check.
pixi_read_reg( &pixi, PIXI_REG_DEVICE_ID, &res );
if ( res != 1060 )
{
log_printf( &logger, "ERROR : WRONG DEVICE ID!\r\n" );
for( ; ; );
}
else
{
log_printf( &logger, "Driver Init - DONE!\r\n" );
}
// Default configuration.
pixi_default_cfg( &pixi );
}
void application_task ( )
{
pixi_write_reg( &pixi, PIXI_REG_GPO_DATA, 0x1 );
log_printf( &logger, "Led on\r\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
pixi_write_reg( &pixi, PIXI_REG_GPO_DATA, 0 );
log_printf( &logger, "Led off\r\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END