Ensure higher protection against unauthorized access by incorporating serial EERAM to store encryption keys, secure boot information, and authentication credentials
A
A
Hardware Overview
How does it work?
EERAM 3 Click is based on the 48L256, an SPI nonvolatile EERAM memory IC designed to retain data when power is disrupted from Microchip. The user can treat this Click board™ as a full symmetrical read/write SRAM: it allows symmetrical reads and writes and has no limits on cell usage. It is structured as a 256-Kbit SRAM with EEPROM backup in each memory cell, where SRAM is organized as 32,768x8 bits. The 48L256 specifies 100.000 endurance cycles with data retention of a minimum of 10 years, which gives the 48L256 the unique capability to handle unlimited reads/writes to the memory. The backup EEPROM is invisible to the user and cannot be accessed by the user independently. The 48L256 includes circuitry that detects VCC voltage 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. The 48L256 communicates with MCU through a standard SPI interface that enables very high clock speeds up to 66MHz, supporting the two most common SPI modes - SPI Mode 0 and 3, and a proper logic voltage level conversion performed by the appropriate voltage level translator. The VCC logic level provides a needed reference voltage for one side of the TXB0106, a 6-bit bidirectional level shifting, and a voltage translator with automatic direction sensing from Texas Instruments. On another side of the level shifter, the reference voltage is taken from the 3.3V mikroBUS™ power rail. Another feature of this Click board™
represents the configurable HOLD function labeled as HLD routed on the INT pin of the mikroBUS™ socket. The HLD pin suspends transmission to the 48L256 while in the middle of a serial sequence without re-transmitting 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 HLD pin may be pulled low to pause further serial communication without resetting the serial sequence. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC 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
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
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 3 Click driver.
Key functions:
eeram3_memory_secure_write
- This function securely writes a desired number of data bytes starting from the selected memory addresseeram3_memory_secure_read
- This function securely reads a desired number of data bytes starting from the selected memory addresseeram3_set_block_protection
- This function sets the block protection bits of the Status register.
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 EERAM3 Click example
*
* # Description
* This example demonstrates the use of EERAM 3 click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Writes a desired number of bytes to the memory and then verifies that it's written correctly
* by reading from the same memory location and displaying the memory content on the USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "eeram3.h"
#define DEMO_TEXT_MESSAGE "MikroE - EERAM 3 click board"
#define STARTING_ADDRESS 0x1000
static eeram3_t eeram3;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
eeram3_cfg_t eeram3_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.
eeram3_cfg_setup( &eeram3_cfg );
EERAM3_MAP_MIKROBUS( eeram3_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == eeram3_init( &eeram3, &eeram3_cfg ) )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
eeram3_default_cfg ( &eeram3 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint8_t data_buf[ 64 ] = { 0 };
if ( EERAM3_OK == eeram3_memory_secure_write ( &eeram3, STARTING_ADDRESS,
DEMO_TEXT_MESSAGE, strlen ( DEMO_TEXT_MESSAGE ) ) )
{
log_printf ( &logger, "Data written to address 0x%.4X: %s\r\n", ( uint16_t ) STARTING_ADDRESS,
( char * ) DEMO_TEXT_MESSAGE );
}
Delay_ms ( 100 );
if ( EERAM3_OK == eeram3_memory_secure_read ( &eeram3, STARTING_ADDRESS,
data_buf, strlen ( DEMO_TEXT_MESSAGE ) ) )
{
log_printf ( &logger, "Data read from address 0x%.4X: %s\r\n\n", ( uint16_t ) STARTING_ADDRESS,
data_buf );
}
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
/*!
* @file main.c
* @brief EERAM3 Click example
*
* # Description
* This example demonstrates the use of EERAM 3 click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Writes a desired number of bytes to the memory and then verifies that it's written correctly
* by reading from the same memory location and displaying the memory content on the USB UART.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "eeram3.h"
#define DEMO_TEXT_MESSAGE "MikroE - EERAM 3 click board"
#define STARTING_ADDRESS 0x1000
static eeram3_t eeram3;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
eeram3_cfg_t eeram3_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.
eeram3_cfg_setup( &eeram3_cfg );
EERAM3_MAP_MIKROBUS( eeram3_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == eeram3_init( &eeram3, &eeram3_cfg ) )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
eeram3_default_cfg ( &eeram3 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
uint8_t data_buf[ 64 ] = { 0 };
if ( EERAM3_OK == eeram3_memory_secure_write ( &eeram3, STARTING_ADDRESS,
DEMO_TEXT_MESSAGE, strlen ( DEMO_TEXT_MESSAGE ) ) )
{
log_printf ( &logger, "Data written to address 0x%.4X: %s\r\n", ( uint16_t ) STARTING_ADDRESS,
( char * ) DEMO_TEXT_MESSAGE );
}
Delay_ms ( 100 );
if ( EERAM3_OK == eeram3_memory_secure_read ( &eeram3, STARTING_ADDRESS,
data_buf, strlen ( DEMO_TEXT_MESSAGE ) ) )
{
log_printf ( &logger, "Data read from address 0x%.4X: %s\r\n\n", ( uint16_t ) STARTING_ADDRESS,
data_buf );
}
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