Integrate multi-directional control into your project, making it ideal for compact and efficient user interface designs
A
A
Hardware Overview
How does it work?
Joystick 4 Click is based on the 2434804-1, an ALCOSWITCH series 5-position tactile switch from TE Connectivity. This tactile switch features an extended top actuator for precise and reliable input detection. Built with a stainless steel contact base and silver contact plating, it ensures durability and resistance to corrosion, providing an operational lifespan of 100,000 cycles. With its low-profile design, the switch can handle a contact current rating of 50mA and can operate at a voltage of 12VDC, in general. These tactile switches are critical for providing tactile feedback due to their high reliability and are used in various applications, including portable devices, instrumentation, security systems, gaming consoles, remote controllers, and handheld devices. Joystick 4 Click leverages these attributes to deliver accurate and responsive input control, making it ideal for
interactive projects where dependable tactile feedback is essential. Whether designing a game controller or developing a user interface for a portable device, this board offers the functionality and durability necessary for the most accessible integration. This Click board™ is designed in a unique format supporting the newly introduced MIKROE feature called "Click Snap." Unlike the standardized version of Click boards, this feature allows the main sensor area to become movable by breaking the PCB, opening up many new possibilities for implementation. Thanks to the Snap feature, the switches can operate autonomously by accessing their signals directly on the pins marked 1-8. Additionally, the Snap part includes a specified and fixed screw hole position, enabling users to secure the Snap board in their desired location. Joystick 4 Click interfaces with the host MCU
through the TCA6408A port expander using the I2C interface. This port expander enables the control of the tactile switch and its associated control signals, including a dedicated signal for detecting joystick movements. When the tactile switch is activated, it provides an interrupt signal (INT) to the host MCU, ensuring immediate response to user inputs. Besides the I2C interface pins, the port expander also uses a reset (RST) pin and includes a jumper for selecting the I2C address labeled ADDR SEL. 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. Also, this 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
Clicker 2 for Kinetis is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for Joystick 4 Click driver.
Key functions:
joystick4_get_int_pin
- This function returns the INT pin logic state.joystick4_get_pins
- This function reads all input pins logic state.joystick4_get_position
- This function returns the joystick position flag extracted from the input pins state mask.
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 Joystick 4 Click example
*
* # Description
* This example demonstrates the use of the Joystick 4 click board by reading
* and displaying the joystick position.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Waits for the input change interrupt, reads the input pins mask, extracts
* the joystick position from those readings, and displays it on the USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "joystick4.h"
static joystick4_t joystick4;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
joystick4_cfg_t joystick4_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.
joystick4_cfg_setup( &joystick4_cfg );
JOYSTICK4_MAP_MIKROBUS( joystick4_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == joystick4_init( &joystick4, &joystick4_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( JOYSTICK4_ERROR == joystick4_default_cfg ( &joystick4 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
if ( JOYSTICK4_PIN_STATE_HIGH == joystick4_get_int_pin ( &joystick4 ) )
{
log_printf ( &logger, " Joystick position: IDLE\r\n\n" );
}
}
void application_task ( void )
{
uint8_t pin_mask = 0;
if ( JOYSTICK4_PIN_STATE_LOW == joystick4_get_int_pin ( &joystick4 ) )
{
if ( JOYSTICK4_OK == joystick4_get_pins ( &joystick4, &pin_mask ) )
{
log_printf ( &logger, " Joystick position: " );
switch ( joystick4_get_position ( pin_mask ) )
{
case JOYSTICK4_POSITION_IDLE:
{
log_printf ( &logger, "IDLE" );
break;
}
case JOYSTICK4_POSITION_CENTER:
{
log_printf ( &logger, "CENTER" );
break;
}
case JOYSTICK4_POSITION_CENTER_UP:
{
log_printf ( &logger, "CENTER-UP" );
break;
}
case JOYSTICK4_POSITION_CENTER_RIGHT:
{
log_printf ( &logger, "CENTER-RIGHT" );
break;
}
case JOYSTICK4_POSITION_CENTER_DOWN:
{
log_printf ( &logger, "CENTER-DOWN" );
break;
}
case JOYSTICK4_POSITION_CENTER_LEFT:
{
log_printf ( &logger, "CENTER-LEFT" );
break;
}
case JOYSTICK4_POSITION_UP:
{
log_printf ( &logger, "UP" );
break;
}
case JOYSTICK4_POSITION_UPPER_RIGHT:
{
log_printf ( &logger, "UPPER-RIGHT" );
break;
}
case JOYSTICK4_POSITION_RIGHT:
{
log_printf ( &logger, "RIGHT" );
break;
}
case JOYSTICK4_POSITION_LOWER_RIGHT:
{
log_printf ( &logger, "LOWER-RIGHT" );
break;
}
case JOYSTICK4_POSITION_DOWN:
{
log_printf ( &logger, "DOWN" );
break;
}
case JOYSTICK4_POSITION_LOWER_LEFT:
{
log_printf ( &logger, "LOWER-LEFT" );
break;
}
case JOYSTICK4_POSITION_LEFT:
{
log_printf ( &logger, "LEFT" );
break;
}
case JOYSTICK4_POSITION_UPPER_LEFT:
{
log_printf ( &logger, "UPPER-LEFT" );
break;
}
default:
{
log_printf ( &logger, "UNKNOWN" );
break;
}
}
log_printf ( &logger, "\r\n\n" );
}
}
}
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