Upgrade project's visual impact with ring of red LEDs, SN74HC595 and PIC32MZ1024EFH064
Ring of brilliance: Elevate your project with red LED magic!
Published Sep 04, 2023
Click board™
Led ring R Click
Dev Board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
Our solution featuring a ring of 32 red LEDs delivers a captivating and versatile lighting option for your projects, perfect for applications requiring attention-grabbing visuals and dynamic effects
A
A
Hardware Overview
How does it work?
LED ring R Click is based on four SN74HC595, an 8-bit serial-in, parallel-out 3-state shift register output latches from Texas Instruments. The SN74HC595s are connected in a daisy chain from one’s serial data output pin to another serial data input pin. Both the shift and storage registers have separate clocks. The data in the shift register is transferred to the storage register on a LOW-to-HIGH transition of the LAT pin. If both clocks are logic state timed together, the shift register will always be one clock pulse ahead of the storage
register. Data in the storage register appears at the output whenever the output enable pin (OE) is LOW (in this case, always since the OE pin is connected to GND and is always low). The LED Ring R Click uses an SPI serial interface to communicate with the host MCU via the mikroBUS™ socket. The CLK pin serves as a shift register clock input, while the LAT pin serves as a storage register clock input for all four SN74HC595. The MR pin is a master reset pin with active LOW and will reset all four SN74HC595 shift registers at
once. All four SN74HC595 outputs are enabled by default, as they are pulled down, and the enabling feature on this Click board™ is not given to the user. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the 3.3V 5V 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
PIC32MZ Clicker 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 PIC32MZ microcontroller with FPU from Microchip, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access anywhere and under
any circumstances. Each part of the PIC32MZ Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the PIC32MZ Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for PIC, dsPIC, or PIC32 programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB Micro-B connection can provide up to 500mA of current, which is more than enough to operate all onboard
and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. PIC32MZ Clicker 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
PIC32
MCU Memory (KB)
1024
Silicon Vendor
Microchip
Pin count
64
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the PIC32MZ clicker as your development board.
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 LED ring R Click driver.
Key functions:
ledringr_write_data- Generic write functionledringr_turn_on_led- Turn On LED by positionledringr_led_ring_set- Set led
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 LedringR Click example
*
* # Description
* LED ring R click is a mikroBUS™ add-on board with a ring of 32 red LEDs driven.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes SPI driver and performs device configuration.
*
* ## Application Task
* Show functionality of Led_Ring_R Click, rotating and turn on/off led's, using the SPI interface.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "ledringr.h"
// ------------------------------------------------------------------ VARIABLES
static ledringr_t ledringr;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
ledringr_cfg_t cfg;
/**
* 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.
ledringr_cfg_setup( &cfg );
LEDRINGR_MAP_MIKROBUS( cfg, MIKROBUS_1 );
ledringr_init( &ledringr, &cfg );
}
void application_task ( void )
{
uint32_t ring_led_on = 0x00000001;
uint8_t ring_led_counter;
uint8_t number_led;
ledringr_led_ring_set( &ledringr );
for ( ring_led_counter = 32; ring_led_counter > 0; ring_led_counter--)
{
ledringr_turn_on_led( &ledringr, ring_led_counter );
Delay_100ms( );
}
Delay_100ms( );
while ( ring_led_on < 0xFFFFFFFF )
{
ledringr_write_data( &ledringr, ring_led_on );
ring_led_on = ring_led_on | (ring_led_on << 1);
Delay_100ms( );
}
ledringr_write_data( &ledringr, ring_led_on );
while ( ring_led_on > 0x00000001 )
{
ledringr_write_data( &ledringr, ring_led_on );
ring_led_on = ring_led_on >> 1;
Delay_100ms( );
}
ledringr_write_data( &ledringr, ring_led_on );
Delay_100ms( );
ring_led_on = 0x11111111;
for ( ring_led_counter = 0; ring_led_counter < 32; ring_led_counter++ )
{
ledringr_write_data( &ledringr, ring_led_on );
ring_led_on *= 2;
if ( ring_led_on == 0x88888888 )
{
ring_led_on = 0x11111111;
}
Delay_100ms( );
}
for ( ring_led_counter = 0; ring_led_counter < 16; ring_led_counter++ )
{
ledringr_write_data( &ledringr, 0xAAAAAAAA );
Delay_100ms( );
ledringr_write_data( &ledringr, 0x55555555 );
Delay_100ms( );
}
ledringr_led_ring_reset( &ledringr );
Delay_1sec( );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
