With our SRAM memory, you can trust in data integrity and fast access for critical operations
A
A
Hardware Overview
How does it work?
SRAM 3 Click is based on the ANV32AA1WDK66, a serial non-volatile SRAM with double memory architecture and SPI serial interface organized as 128k words of 8 bits each from Anvo-System Dresden. This memory has a silicon-oxide-nitride-oxide-silicon (SONOS) flash storage element included with each memory cell. In the case of an unforeseeable operating voltage drop below a defined value, the SONOS technology enables non-volatile data storage in less than 15ms. An integrated Power Down functionality of the SRAM 3 Click with a standby current of less than 1µA ensures low power consumption, with recovery time from Power-Down Mode typically of 60µs. This ANV32AA1WDK66 possesses unique safety features, such as Checksum Protected Memory Accesses (Secure READ and Secure WRITE instructions) and Time Monitoring that ensures a
high degree of reliability of this Click board™. Corrupt data cannot overwrite existing memory content; even valid data would not overwrite on a corrupted address. The SRAM 3 Click also provides some distinctive advantages of SRAMs, such as fast access times and unlimited write/read endurance. SRAM 3 Click incorporates an additional IC, the TXB0108PWR, an 8-bit bidirectional voltage level translator from Texas Instruments. This allows the Click board™ to be used with a much more extensive range of MCUs. At the same time, the TXB0108PWR protects the ANV32AA1WDK66 from the Electrostatic Discharges (ESD) up to ±15 kV, making SRAM 3 Click a very reliable embedded storage solution. The ANV32AA1WDK66 communicates with MCU using the standard SPI serial interface that supports modes 0 and 3 with a maximum
frequency of 66 MHz. It also possesses an additional HOLD function routed at the PWM pin of the mikroBUS™ socket labeled as HLD. This pin is used with the CS pin to select the device. When the device is selected, and a serial sequence is underway, an HLD pin can pause the serial communication with the host device 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 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The
board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,
and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
32
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
4096
You complete me!
Accessories
Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.
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 SRAM 3 Click driver.
Key functions:
sram3_enable_write
- This function is for enabling writing to memory, status register or user serial.sram3_disable_write
- Function for disabling writing to memory, status register or user serial.sram3_protect_memory
- Function which secures part of memory from writing.
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 SRAM3 Click example
*
* # Description
* This is an example that shows the use of SRAM memory, using SRAM 3 click. SRAM 3 click is based on ANV32AA1W,
* and ANV32AA1W is a 1Mb serial SRAM with a non-volatile SONOS storage element included with each memory cell,
* organized as 128k words of 8 bits each. The devices are accessed by a high speed SPI-compatible bus.
* Specifically in this example, we used the high-speed SPI communication characteristics to write data to a specific
* registration address and read it.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization SPI module, logger initalization and click initialization.
*
* ## Application Task
* First, we write the data to the registry address 0x00, and then we read the data from 0x00 address.
*
* @author Jelena Milosavljevic
*
*/
#include "board.h"
#include "log.h"
#include "sram3.h"
static sram3_t sram3;
static log_t logger;
uint8_t buf[10] = { 'M','i','k','r','o','E', 0 };
void application_init ( void ) {
log_cfg_t log_cfg; /**< Logger config object. */
sram3_cfg_t sram3_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.
sram3_cfg_setup( &sram3_cfg );
SRAM3_MAP_MIKROBUS( sram3_cfg, MIKROBUS_1 );
err_t init_flag = sram3_init( &sram3, &sram3_cfg );
if ( SPI_MASTER_ERROR == init_flag ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_info( &logger, " Application Task " );
sram3_release_hold( &sram3 );
Delay_ms( 100 );
}
void application_task ( void ) {
char buff_out[ 10 ] = { 0 };
log_printf( &logger, "Writing [ %s ] to memory...\r\n", buf );
sram3_enable_write( &sram3 );
sram3_write( &sram3, 0x00, &buf[0], 6 );
Delay_ms( 100 );
sram3_read( &sram3, 0x00, &buff_out[0], 6 );
Delay_ms( 100 );
log_printf( &logger, "Data read from memory: %s \r\n", buff_out );
log_printf( &logger, "---------------------------------------------\r\n" );
Delay_ms( 2000 );
}
void main ( void ) {
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END