Enjoy the perks of FRAM memory with MB94R330 and STM32F446RE
Improve your data storage capabilities
Published Oct 08, 2024
Click board™
FRAM 3 Click
Dev Board
Nucleo 64 with STM32F446RE MCU
Compiler
NECTO Studio
MCU
STM32F446RE
Upgrade your design with FRAM memory for unmatched performance and endurance
A
A
Hardware Overview
How does it work?
FRAM 3 Click is based on the MB94R330, a FRAM (Ferroelectric Random Access Memory) authentication IC from Fujitsu Semiconductor, made using ferroelectric and silicon gate CMOS process technologies to form nonvolatile memory cells. The MB94R330 adopts an original communication protocol based on the two-wire serial interface (I2C BUS), a hardware cryptographic macro, and a proprietary control core. It is suitable for detecting cloned peripherals and accessories used in electric equipment such as printers and multifunction printers. Ferroelectric technology is still being developed and perfected, but the advantages have already been demonstrated. This technology exploits the properties of ferroelectric materials to retain the electric field after exposure, the same way the ferromagnetic materials retain their magnetic field. This phenomenon is employed to polarize the FRAM cells and store the information.
One area that still needs improvement is the thermal instability, especially at high temperatures. When the ferroelectric material reaches the Curie temperature, its properties are degraded. Therefore, the high temperature might damage the content of the FRAM module. This is illustrated by the data retention period: while working at 55˚C, the data retention period is ten years. Still, combined with the endurance of 1010 read/write cycles at bus write speed, this type of memory still represents an ideal solution for applications with frequent writing to nonvolatile memory locations. This Click board™ uses the I2C communication protocol, allowing fast serial clock rates. The device employs certain protection mechanisms to ensure reliable data transactions and avoid accidental writing to the memory array. The MB94R330 supports the I2C bus and operates as a peripheral device. The role of the communication for the I2C bus is different from
the "Master" side and the "Slave" side. The master side has the authority to initiate control. Furthermore, the party line can be connected, which connects two or more peripheral devices to one master. In this case, the slave side has a unique address, respectively, and after specifying the address on the slave side, the master side starts to communicate. The FRAM 3 click is suitable for detecting cloned peripherals and accessories used in electric equipment such as printers, multifunction printers, and more. 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 STM32F446RE 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-M4
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
131072
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
Start by selecting your development board and Click board™. Begin with the Nucleo 64 with STM32F446RE MCU as your development board.
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 FRAM 3 Click driver.
Key functions:
fram3_read_free_access_memory- Memory read functionfram3_write_free_access_memory- Memory write 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 FRAM3 Click example
*
* # Description
* This application writes data in memmory and reads data from memmory.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes device init
*
* ## Application Task
* Writes and then reads data from memory
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "fram3.h"
// ------------------------------------------------------------------ VARIABLES
static fram3_t fram3;
static log_t logger;
static char write_data[ 7 ] = { 'M', 'i', 'k', 'r', 'o', 'E', 0 };
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
fram3_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.
fram3_cfg_setup( &cfg );
FRAM3_MAP_MIKROBUS( cfg, MIKROBUS_1 );
fram3_init( &fram3, &cfg );
}
void application_task ( )
{
char read_data[ 7 ];
uint8_t cnt;
uint8_t status_check;
log_printf( &logger, " - Writing... \r\n" );
Delay_ms( 500 );
status_check = fram3_write_free_access_memory( &fram3, 0x00, &write_data[ 0 ], 7 );
if ( status_check == FRAM3_ERROR )
{
log_printf( &logger, " - ERROR WRITING!!! \r\n" );
for ( ; ; );
}
log_printf( &logger, " - Reading... \r\n" );
Delay_ms( 500 );
status_check = fram3_read_free_access_memory( &fram3, 0x00, &read_data[ 0 ], 7 );
if ( status_check == FRAM3_ERROR )
{
log_printf( &logger, " - ERROR READING!!! \r\n" );
for ( ; ; );
}
for ( cnt = 0; cnt < 7; cnt++ )
{
log_printf( &logger, " %c ", read_data[ cnt ] );
Delay_ms( 100 );
}
log_printf( &logger, " \r\n " );
Delay_ms( 1000 );
log_printf( &logger, "__________________________\r\n " );
Delay_ms( 500 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
