Explore the limitless possibilities of data storage with our EEPROM solution.
A
A
Hardware Overview
How does it work?
EEPROM 11 Click is based on the S-34C04AB, an EEPROM memory for DIMM serial presence detection from ABLIC. The EEPROM uses a Schmitt trigger and noise filter on the I2C bus for noise suppression. The S-34C04AB has a timeout function that can reset the I2C interface and return to standby mode. This timeout is typically 30ms. The EEPROM also allows you to write a byte or a page. The page write mode allows up to 16
bytes to be written in a single operation. The IC also has set protection for block n, clear write protection for all blocks, and read protection status for block n. As for reading, you can read a current address, a random read, or a sequential read. EEPROM 11 Click uses a standard 2-wire I2C interface to communicate with the host MCU, supporting clock frequencies of up to 1MHz. You can set the desired I2C address over three ADDR
SEL jumpers, with 0s selected by default. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. 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
Nucleo-64 with STM32G071RB MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
36864
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
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 EEPROM 11 Click driver.
Key functions:
eeprom11_page_write
- EEPROM 11 page write function.eeprom11_clear_page
- EEPROM 11 page clear function.eeprom11_set_page_addr
- EEPROM 11 set page address 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 EEPROM 11 Click example
*
* # Description
* This is an example that demonstrates the use of the EEPROM 11 Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and USB UART logging, disables write protection.
*
* ## Application Task
* Writes a desired number of data bytes to the EEPROM 11 memory into a specified address,
* and verifies that it is written correctly by reading from the same memory location.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "eeprom11.h"
#define TX_DATA "EEPROM 11 Click"
#define MEMORY_ADDRESS 0x00
static eeprom11_t eeprom11;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
eeprom11_cfg_t eeprom11_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.
eeprom11_cfg_setup( &eeprom11_cfg );
EEPROM11_MAP_MIKROBUS( eeprom11_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == eeprom11_init( &eeprom11, &eeprom11_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( EEPROM11_ERROR == eeprom11_default_cfg ( &eeprom11 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
err_t error_flag = EEPROM11_OK;
uint8_t rx_data[ 16 ] = { 0 };
uint8_t tx_data[ 16 ] = TX_DATA;
eeprom11_clear_page( &eeprom11, MEMORY_ADDRESS );
Delay_ms( 1000 );
error_flag = eeprom11_page_write( &eeprom11, MEMORY_ADDRESS, tx_data );
if ( EEPROM11_OK == error_flag )
{
log_printf( &logger, " Write data: %s \r\n", tx_data );
}
else
{
log_error( &logger, " Write operation failed!!! " );
}
Delay_ms( 1000 );
error_flag = eeprom11_generic_read( &eeprom11, MEMORY_ADDRESS, rx_data, 15 );
if ( EEPROM11_OK == error_flag )
{
log_printf( &logger, "Read data: %s \r\n", rx_data );
}
else
{
log_error( &logger, " Write operation failed!!! " );
}
log_printf( &logger, " - - - - - - - - - - - \r\n" );
Delay_ms( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END