SRAM's combination of speed and power efficiency makes it an essential component in the world of modern electronics
A
A
Hardware Overview
How does it work?
SRAM 4 Click is based on the CY14B512Q, a 512Kbit nvSRAM memory organized as 64K words of 8 bits each from Infineon. The nvSRAM specifies one million endurance cycles for nonvolatile cells with data retention of a minimum of 20 years. All the reads and writes to nvSRAM happen to the SRAM, which gives nvSRAM the unique capability to handle infinite writes to the memory. The embedded nonvolatile elements incorporate the QuantumTrap technology, making this Click board™ an ideal choice for secure data storage, creating the world’s most reliable nonvolatile memory. The CY14B512Q communicates with MCU through a standard SPI interface that enables very high clock speeds up to 40MHz with zero cycle
delay read and write cycles. It also supports the two most common modes, SPI Mode 0 and 3, and 104 MHz SPI access speed with special instructions for the read operation. Besides, the SRAM 4 Click also has an additional HOLD signal, routed to the PWM pin of the mikroBUS™ socket labeled as HLD, used to suspend the serial communication without resetting the serial sequence. The CY14B512Q uses the standard SPI opcodes for memory access. In addition to the general SPI instructions for reading and writing, also provide four special instructions: STORE, RECALL, AutoStore Disable, and AutoStore Enable. The significant benefit of this memory over serial EEPROMs is that all reads and writes to nvSRAM
are performed at the speed of the SPI bus with zero cycle delay. Therefore, no wait time is required after any of the memory accesses. Only the STORE and RECALL operations need finite time to complete, and all memory accesses are inhibited during this time. 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 STM32L073RZ 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
![default](https://dbp-cdn.mikroe.com/catalog/mcus/resources/STM32L073RZ.jpg)
Architecture
ARM Cortex-M0
MCU Memory (KB)
192
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
20480
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
![SRAM 4 Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee79090-c5f4-6e06-8cf6-0242ac120009/schematic.webp)
Step by step
Project assembly
Track your results in real time
Application Output
After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.
![Application Output Step 1](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed554e-d80f-6694-8cb9-02420a000272/AP-Step1.jpg)
After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.
![Application Output Step 3](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-3c0f-6800-a19f-02420a000272/AP-Step3.jpg)
Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.
![Application Output Step 4](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-d4d0-6b20-a348-02420a000272/AP-Step4.jpg)
Software Support
Library Description
This library contains API for SRAM 4 Click driver.
Key functions:
sram4_memory_read
- Read data from memory.sram4_memory_write
- Write data to memory.sram4_generic_command
- Command writing 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 main.c
* @brief SRAM4 Click example
*
* # Description
* This example application showcases ability of device
* ability to manipulate with memory( writing and reading data ).
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of communication modules(SPI, UART) and additional
* pins. Reads ID and checks if it matches with SRAM4_DEVICE_ID to
* check communication. Then clears protection from memory access.
*
* ## Application Task
* Writes 3 times to memory with length of data offset in memory address.
* Then reads 2 times first 2 data written should be read in one read,
* and 3rd write should be read separately.
*
* @author Luka FIlipovic
*
*/
#include "board.h"
#include "log.h"
#include "sram4.h"
static sram4_t sram4;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
sram4_cfg_t sram4_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.
sram4_cfg_setup( &sram4_cfg );
SRAM4_MAP_MIKROBUS( sram4_cfg, MIKROBUS_1 );
err_t init_flag = sram4_init( &sram4, &sram4_cfg );
if ( SPI_MASTER_ERROR == init_flag )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
if ( sram4_default_cfg ( &sram4 ) )
{
log_error( &logger, " Default configuration. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
char read_buf[ 100 ] = { 0 };
char click_name[ ] = "SRAM 4";
char company_name[ ] = "MikroE";
char product_name[ ] = " Click board";
static const uint16_t START_ADR = 0x0001;
uint16_t mem_adr = START_ADR;
//Write Data
sram4_memory_write( &sram4, mem_adr, click_name, strlen( click_name ) );
mem_adr += strlen( click_name );
sram4_memory_write( &sram4, mem_adr, product_name, strlen( product_name ) );
mem_adr += strlen( product_name );
sram4_memory_write( &sram4, mem_adr, company_name, strlen( company_name ) );
//Read Data
mem_adr = START_ADR;
sram4_memory_read( &sram4, mem_adr, read_buf, strlen( click_name ) + strlen( product_name ) );
log_printf( &logger, " > Read Data from 0x%.4X memory address: %s\r\n", mem_adr, read_buf );
memset( read_buf, 0, strlen( read_buf ) );
mem_adr += strlen(click_name) + strlen( product_name );
sram4_memory_read( &sram4, mem_adr, read_buf, strlen( company_name ) );
log_printf( &logger, " > Read Data from 0x%.4X memory address: %s\r\n", mem_adr, read_buf );
log_printf( &logger, "**********************************************************************\r\n" );
Delay_ms( 3000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END