Save calibration data and system logs with M95P32-I and STM32F091RC
Infinite ideas, instant recall
Published Feb 26, 2024
Click board™
EEPROM 9 Click
Dev. board
Nucleo-64 with STM32F091RC MCU
Compiler
NECTO Studio
MCU
STM32F091RC
Our EEPROM solution guarantees secure data storage, which is ideal for sensitive information such as encryption keys, boot sequences, and critical system parameters
A
A
Hardware Overview
How does it work?
EEPROM 9 Click is based on the M95P32-I, a 32Mbit SPI page EEPROM device from STMicroelectronics, divided into 8192 erasable pages of 512 bytes (organized either as 1024 erasable sectors of 4 Kbytes, 64 erasable blocks of 64 Kbytes or as an entirely erasable array). The M95P32-I is manufactured with ST's advanced proprietary NVM technology and offers byte flexibility, page alterability, high page cycling performance, and ultra-low power consumption. It is highly reliable, lasting 500k write cycles with 100 years of data retention (10 years after 500k cycles), which makes it suitable for various applications where dependable nonvolatile memory storage is essential. This Click board™ communicates with MCU using the SPI serial interface that supports the two most common modes, SPI Mode 0 and 3, with a maximum SPI frequency of 80MHz.
As mentioned, the M95P32-I offers byte and page write instructions of up to 512 bytes. Write instructions consist of self-timed auto-erase and program operations, resulting in flexible data byte management. It also accepts page/block/sector/chip erase commands to set the memory to an erased state. The memory can then be fast-programmed by pages of 512 bytes and further optimized using the "page program with buffer load" to hide the SPI communication latency. Additional status, configuration, and volatile registers set the desired device configuration, while the safety register gives device status information. In addition to the SPI communication, the EEPROM 9 Click has two additional pins used for Write Protection and Communication Hold function routed to the WP and HLD pins of the mikroBUS™ socket.
The HLD pin of the mikroBUS™ socket can be used to pause the serial communication with the M95P32-I without deselecting the device. The configurable Write Protection function routed to the WP pin of the mikroBUS™ socket allows the user to freeze the memory area protected against Write instructions in a read-only mode (as specified by the values in the BPx and TB bits of the STATUS register). 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, it comes equipped with a library containing functions and an example code that can be used, as a reference, for further development.
Features overview
Development board
Nucleo-64 with STM32F091RC 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)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo-64 with STM32F091RC MCU 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 9 Click driver.
Key functions:
eeprom9_set_write_enable- EEPROM 9 enable write functioneeprom9_read_memory- EEPROM 9 memory reading functioneeprom9_block_erase- EEPROM 9 memory block erase function.
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 main.c
* @brief EEPROM 9 Click example
*
* # Description
* This is an example that demonstrates the use of the EEPROM 9 Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and USB UART logging, disables hold and write protection.
*
* ## Application Task
* Writes a desired number of data bytes to the EEPROM 9 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 "eeprom9.h"
static eeprom9_t eeprom9;
static log_t logger;
static char demo_data[ 9 ] = { 'M', 'i', 'k', 'r', 'o', 'E', 13 ,10 , 0 };
#define MEMORY_ADDRESS 0x0300
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
eeprom9_cfg_t eeprom9_cfg; /**< Click config object. */
id_data_t id_data;
/**
* 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.
eeprom9_cfg_setup( &eeprom9_cfg );
EEPROM9_MAP_MIKROBUS( eeprom9_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == eeprom9_init( &eeprom9, &eeprom9_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
eeprom9_read_identification( &eeprom9, &id_data );
if ( EEPROM9_ST_MANUFACTURER_CODE != id_data.manufact_code )
{
log_error( &logger, " Communication error." );
for ( ; ; );
}
log_printf( &logger, " Manufacturer code: 0x%.2X \r\n", ( uint16_t ) id_data.manufact_code );
log_printf( &logger, " Disabling Hold \r\n" );
eeprom9_set_hold( &eeprom9, EEPROM9_HOLD_DISABLE );
Delay_ms ( 100 );
log_printf( &logger, " Disabling Write Protection \r\n" );
eeprom9_set_write_protection( &eeprom9, EEPROM9_WRITE_PROTECT_DISABLE );
Delay_ms ( 100 );
log_info( &logger, " Application Task " );
log_printf( &logger, " - - - - - - - - - - - \r\n" );
}
void application_task ( void )
{
char rx_data[ 9 ] = { 0 };
eeprom9_set_write_enable( &eeprom9, EEPROM9_WRITE_ENABLE );
Delay_ms ( 10 );
eeprom9_write_memory( &eeprom9, MEMORY_ADDRESS, demo_data, 9 );
log_printf( &logger, " Write data: %s", demo_data );
Delay_ms ( 100 );
eeprom9_read_memory( &eeprom9, MEMORY_ADDRESS, rx_data, 9 );
log_printf( &logger, " Read data: %s", rx_data );
log_printf( &logger, " - - - - - - - - - - - \r\n" );
Delay_ms ( 1000 );
}
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
