Utilize serial EERAM in industrial machinery and automation systems, allowing quick recovery from power interruptions and ensuring minimal downtime and smooth operational continuity
A
A
Hardware Overview
How does it work?
EERAM 2 Click is based on the 48LM01, a 1024-Kbit SRAM with EEPROM backup in each memory cell from Microchip. The user can treat this device as a full symmetrical read/write SRAM with no limits on cell usage. The device handles backup to EEPROM on any power disruption, so the user can effectively view this device as an SRAM that never loses its data. The SRAM is organized as 131,072 x 8 bits with access via the SPI serial interface. The backup EEPROM is invisible and cannot be accessed by the user independently. The 48LM01 includes circuitry that detects VCC dropping below a certain threshold, shuts its connection to the outside environment, and transfers all SRAM data to the EEPROM portion of each cell for safekeeping. When VCC returns, the circuitry automatically returns the data to the SRAM, and the user’s interaction with the SRAM can continue with the same data set. When power is first
applied to the click board™, the VCAP capacitor is charged to VCC through the 48LM01 IC. During normal SRAM operation, the capacitor remains charged, and the device monitors the level of system VCC. If the system VCC drops below a set threshold, the device interprets this as a power-off or brown-out event. The device suspends all I/O operation, shuts off its connection with the VCC pin, and uses the saved energy in the capacitor to power the device through the VCAP pin as it transfers all SRAM data to EEPROM. On the next power-up of VCC, the data is transferred back to SRAM, the capacitor is recharged, and the SRAM operation continues. Besides standard 4-wire SPI lines, 48LM01 has an additional HOLD pin. This pin can be used for transmission suspension to the 48LM01 while in the middle of a serial sequence without retransmitting the entire sequence. It must be held high any time this function is not
being used. Once the device is selected and a serial sequence is underway, the HOLD pin may be pulled low to pause further serial communication without resetting the serial sequence. The 48LM01 is internally organized as a continuous SRAM array for reading and writing, along with a non-volatile EEPROM array that is not directly accessible to the user but can be refreshed or recalled on power cycles or software commands. The SRAM array is continuously addressable, so the entire array can be written without accessing pages. 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
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 EERAM 2 Click driver.
Key functions:
eeram2_set_on_hold_status
- Set On-hold status functioneeram2_set_command
- Set command functioneeram2_set_write_status
- Set write status 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
* \brief Eeram2 Click example
*
* # Description
* This example demonstrates the use of EERAM 2 click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and enables the click board.
*
* ## Application Task
* Writes a desired number of bytes to the memory and then verifies if it is written correctly
* by reading from the same memory location and displaying its content on the USB UART.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "eeram2.h"
// ------------------------------------------------------------------ VARIABLES
static eeram2_t eeram2;
static log_t logger;
static char demo_data[ 9 ] = { 'M', 'i', 'k', 'r', 'o', 'E', 13 ,10 , 0 };
static char read_data[ 9 ];
static uint8_t check_status;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
eeram2_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.
eeram2_cfg_setup( &cfg );
EERAM2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
eeram2_init( &eeram2, &cfg );
eeram2_set_on_hold_status( &eeram2, EERAM2_HOLD_DISABLE );
Delay_ms( 100 );
eeram2_set_write_status( &eeram2, EERAM2_WRITE_ENABLE );
Delay_ms( 100 );
}
void application_task ( void )
{
check_status = eeram2_write_continuous( &eeram2, 0x00543210, &demo_data[ 0 ], 9 );
if ( check_status == EERAM2_ERROR )
{
log_printf( &logger, " ERROR Writing \r\n" );
log_printf( &logger, "--------------------\r\n" );
for ( ; ; );
}
log_printf( &logger, " Writing... \r\n" );
log_printf( &logger, "--------------------\r\n" );
Delay_ms( 100 );
check_status = eeram2_read_continuous( &eeram2, 0x00543210, &read_data[ 0 ], 9 );
if ( check_status == EERAM2_ERROR )
{
log_printf( &logger, " Reading ERROR \r\n" );
log_printf( &logger, "--------------------\r\n" );
for ( ; ; );
}
log_printf( &logger, " Read data : %s", read_data );
log_printf( &logger, "--------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END