Create a reliable and non-volatile data storage solution with M95M02-DR and MK64FN1M0VDC12
Harnessing data with EEPROM magic!
Published Aug 23, 2023
Click board™
EEPROM 2 Click
Dev Board
Clicker 2 for Kinetis
Compiler
NECTO Studio
MCU
MK64FN1M0VDC12
By incorporating EEPROM memory, our solution enables seamless configuration updates and calibration adjustments, enhancing the flexibility and adaptability of your systems
A
A
Hardware Overview
How does it work?
EEPROM 2 Click is based on the M95M02, a 2-Mbit serial SPI bus EEPROM from STMicroelectronics. EEPROM density of 2Mbit is expressed in bits, so exactly 2,097,152 bits are organized in units or words of 8 bits, which gives 262,144 bytes of data memory. Furthermore, the EEPROM is organized in memory pages. One page holds 256 bytes, and there are 1024 pages (1024 pages x 256 bytes = 262,144 bytes total). Having insight into how the memory cells are organized is important for Write and Erase operations. One of the key features of
the M95M02 IC is the Error Correction Code logic (ECC), which allows error correction and is done internally. Another feature of the M95M02 IC is an identification memory page, 256 bytes long, which can be used to store an ID or other sensitive data, and once written, it can be permanently locked. EEPROM 2 Click uses a standard 4-Wire SPI interface to communicate with the host MCU, supporting clock frequency of up to 5MHz. There are several instruction codes, such as Write Enable and Disable, Write and Read from memory array,
Read and Write to Status register, and so on. It also includes a write protection of the specific part or the whole memory array. 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. 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
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.
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 EEPROM 2 Click driver.
Key functions:
eeprom2_write- This function writes a single byte of data to the given memory addresseeprom2_write_bytes- This function writes bytes of data to the given memory addresseeprom2_read_bytes- This function reads bytes from the given memory address.
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 Eeprom2 Click example
*
* # Description
* This application demonstrates the process of writing and
* reading of data from EEPROM.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes EEPROM 2 driver.
*
* ## Application Task
* Writing data to EEPROM and then reading that data and writing it via UART.
*
* *note:*
* <NOTE>
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "eeprom2.h"
// ------------------------------------------------------------------ VARIABLES
static eeprom2_t eeprom2;
static log_t logger;
uint8_t text[ 6 ] = { 'M','i','k','r','o','e' };
char mem_value[ 6 ];
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
eeprom2_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.
eeprom2_cfg_setup( &cfg );
EEPROM2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
eeprom2_init( &eeprom2, &cfg );
}
void application_task ( void )
{
eeprom2_write_bytes ( &eeprom2, 0x01, text, 6 );
log_printf ( &logger, "Writing Mikroe to EEPROM 2 click\r\n" );
Delay_ms( 1000 );
eeprom2_read_bytes ( &eeprom2, 0x01 , mem_value, 6);
log_printf ( &logger, "Data read: %s\r\n", mem_value );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
