Create a secure and distinctive digital identity using DS2401 and PIC32MZ1024EFH064
Your ID, your signature!
Published Jun 21, 2023
Click board™
UNIQUE ID Click
Dev.Board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
Unlock a world of possibilities with your personalized digital ID!
A
A
Hardware Overview
How does it work?
Unique ID Click is based on the DS2401, a guaranteed unique 64-bit ROM ID chip from Analog Devices. The 64-bit ROM includes a unique 48-bit serial number, an 8-bit CRC, and an 8-bit Family Code (01h). Its internal ROM is accessed via a single data line with a communication speed of up to 16.3Kbps. In perspective, multiple DS2401 devices can reside on a common 1-Wire net, with a built-in multidrop controller that ensures compatibility with other 1-Wire devices. The
DS2401 features presence pulse acknowledgment when the reader first applies a voltage, where the power for reading and writing the device is derived from the data line itself. The Unique ID Click uses a 1-Wire bus interface to communicate to the host MCU through one of the GPIOs (GP0, GP1) of the mikroBUS™ socket, selectable by the onboard GPIO SEL jumper. This protocol defines bus transactions regarding the bus state during specified time slots initiated on the falling edge of
sync pulses from the host bus. All data is read and written the least significant bit first. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the PWR 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
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
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
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
Software Support
Library Description
This library contains API for Unique ID Click driver.
Key functions:
uniqueid_read_id- This function reads Family Code and Serial Number of device's ROM memory
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 UNIQUE ID Click example.
*
* # Description
* This example demonstrates the use of UNIQUE ID click board by reading and
* displaying Family Code and Serial Number on the UART Terminal.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes both logger config object and
* click config object.
*
* ## Application Task
* Demonstrates the usage of uniqueid_read_id function,
* which stores the Family Code and Serial Number of the click in
* family_code and serial_num variables. Both values will be displayed
* on the UART Terminal.
*
* @author Aleksandra Cvjeticanin
*
*/
#include "board.h"
#include "log.h"
#include "uniqueid.h"
static uniqueid_t uniqueid;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
uniqueid_cfg_t uniqueid_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
uniqueid_cfg_setup( &uniqueid_cfg );
UNIQUEID_MAP_MIKROBUS( uniqueid_cfg, MIKROBUS_1 );
if ( ONE_WIRE_ERROR == uniqueid_init( &uniqueid, &uniqueid_cfg ) )
{
log_error( &logger, " Initialization error." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint8_t family_code;
uint8_t serial_num[ 6 ];
if ( UNIQUEID_OK == uniqueid_read_id( &uniqueid, &family_code, &serial_num[ 0 ] ) )
{
log_printf( &logger, "Family Code = 0x%.2X\r\n", ( uint16_t ) family_code );
log_printf( &logger, "Serial Number = 0x%.2X%.2X%.2X%.2X%.2X%.2X\r\n",
( uint16_t ) serial_num[ 0 ], ( uint16_t ) serial_num[ 1 ],
( uint16_t ) serial_num[ 2 ], ( uint16_t ) serial_num[ 3 ],
( uint16_t ) serial_num[ 4 ], ( uint16_t ) serial_num[ 5 ] );
}
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
