Transform your hardware management with DS2413 and STM32F411RE
Say goodbye to complicated device control
Published Apr 24, 2023
Click board™
1-Wire Switch Click
Dev Board
UNI-DS v8
Compiler
NECTO Studio
MCU
STM32F411RE
Take your device control to the next level with a programmable I/O 1-Wire switch - the easy way to remotely switch and sense devices
A
A
Hardware Overview
How does it work?
1-Wire Switch Click is based on the DS2413, a dual-channel addressable switch from Analog Devices. The DS2413 combines two programmable I/O pins and a fully featured 1-Wire interface in a single package, ensuring that PIO output changes occur error-free. The PIO outputs are configured as open-drain, operate at up to 28V (provide a high level of fault tolerance in the end application), and have an ON-resistance of 20Ω maximum. By monitoring the voltage at its programmable I/O pins, the DS2413 lets you read back the state of the load, in this case, the state of the button, which in this configuration is in the role of input, while the output state is visually detected through the red LED marked with OUT. The DS2413's power is supplied parasitically from the 1-Wire bus,
a system with a single bus controller and one or more peripherals. With that in mind, this Click board™ has one additional unpopulated header, which enables the connection of other external 1-Wire devices, thus forming a line with several peripherals on one controller. The DS2413 also has a 64-bit long registration number that guarantees unique identification. This number addresses the device in a multidrop 1-Wire network environment, where multiple devices reside on a common 1-Wire bus and operate independently. As mentioned, the 1-Wire Switch Click communicates with MCU using the 1-Wire interface that, by definition, requires only one data line (and ground) for communication with MCU. The 1-Wire communication line is routed to the SMD jumper
labeled as I/O SEL, which allows routing of the 1-Wire communication either to the GP0 pin or the GP1 pin of the mikroBUS™ socket. These pins are labeled, respectively, the same as the SMD jumper positions, making the selection of the desired pin simple and straightforward. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. However, the Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
UNI-DS v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different STM32, Kinetis, TIVA, CEC, MSP, PIC, dsPIC, PIC32, and AVR MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, UNI-DS v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the UNI-DS v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART, USB
HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. UNI-DS v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
131072
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the UNI-DS v8 as your development board.
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
Software Support
Library Description
This library contains API for 1-Wire Switch Click driver.
Key functions:
c1wireswitch_set_pio_state1-Wire Switch write specific programmable I/O state function.c1wireswitch_get_pio_state1-Wire Switch read specific programmable I/O state function.c1wireswitch_get_pio_latch_state1-Wire Switch read programmable I/O latch state function.
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* @file main.c
* @brief 1-Wire Switch Click Example.
*
* # Description
* This library contains API for 1-Wire Switch Click driver.
* The library initializes and defines the 1-Wire bus drivers to
* write and read data for state programmable I/O,
* as well as the default configuration.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs default configuration and sets
* the PIO A to OFF and PIO B to ON state.
*
* ## Application Task
* This example demonstrates the use of the 1-Wire Switch Click board by changing the PIO A state,
* which is controlling the LED, every time the state of PIO B changes.
* Change on the PIO B happens when the button is pushed.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "c1wireswitch.h"
static c1wireswitch_t c1wireswitch;
static log_t logger;
static uint8_t state = 0;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
c1wireswitch_cfg_t c1wireswitch_cfg; /**< Click config object. */
/**
* 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 " );
// Click initialization.
c1wireswitch_cfg_setup( &c1wireswitch_cfg );
C1WIRESWITCH_MAP_MIKROBUS( c1wireswitch_cfg, MIKROBUS_1 );
if ( ONE_WIRE_ERROR == c1wireswitch_init( &c1wireswitch, &c1wireswitch_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( C1WIRESWITCH_ERROR == c1wireswitch_default_cfg ( &c1wireswitch ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
c1wireswitch_set_pio_state( &c1wireswitch, C1WIRESWITCH_PIOA_OFF, C1WIRESWITCH_PIOB_ON );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint8_t pio_a = 0;
uint8_t pio_b = 0;
c1wireswitch_get_pio_state( &c1wireswitch, &pio_a, &pio_b );
if ( pio_b == C1WIRESWITCH_PIOB_OFF )
{
if ( state == 0 )
{
c1wireswitch_set_pio_state( &c1wireswitch, C1WIRESWITCH_PIOA_ON, C1WIRESWITCH_PIOB_ON );
log_printf( &logger, " Button is pressed, LED is ON. \r\n " );
state = 1;
}
else
{
c1wireswitch_set_pio_state( &c1wireswitch, C1WIRESWITCH_PIOA_OFF, C1WIRESWITCH_PIOB_ON );
log_printf( &logger, " Button is pressed, LED is OFF. \r\n " );
state = 0;
}
Delay_ms( 100 );
}
Delay_ms( 100 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
