Whether it's in networking, embedded systems, or consumer electronics, SRAM memory solutions drive performance to new heights
A
A
Hardware Overview
How does it work?
SRAM Click is based on the 23LC1024, a highly reliable 1Mbit Serial SRAM designed to interface directly with Microchip's Serial Peripheral Interface (SPI). The 23LC1024 is organized as 128k words of 8 bits each and provides fast access alongside infinite read and write cycles to the memory array. The embedded nonvolatile elements incorporate the CMOS technology, making this Click board™ an ideal choice for secure data storage, creating the world's most reliable nonvolatile memory. The serial SRAM has three modes of operation, byte, page, and sequential, which are chosen by setting bits in the MODE register. In Byte mode, the R/W operations are limited to only one byte,
while in Page mode, R/W operations are limited to within the addressed page. The last Sequential mode allows the entire array to be written to and read from. The 23LC1024 communicates with MCU through a standard SPI interface that enables very high clock speeds up to 20MHz with zero cycle delay read and write cycles. It may also interface with MCUs that do not have a built-in SPI port by using discrete I/O lines programmed properly in firmware to match the SPI protocol. In addition, the 23LC1024 can operate in SDI and SQI modes. In the SDI mode, the SI and SO data lines are bidirectional, allowing the transfer of two bits per clock pulse, while in the SQI mode, two additional
data lines enable the transfer of four bits per clock pulse. The SRAM Click also has an additional HOLD signal, routed to the RST pin of the mikroBUS™ socket labeled as HLD, used to suspend the serial communication without resetting the serial sequence. This Click board™ can operate with both 3.3V and 5V logic voltage levels selected via the PWR 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
Fusion for TIVA v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different 32-bit ARM® Cortex®-M based MCUs from Texas Instruments, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over a WiFi network. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for TIVA v8 provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances at any time. Each part of the Fusion for TIVA v8 development board contains the components necessary for the most efficient operation of the same board. An advanced integrated CODEGRIP programmer/debugger module offers many valuable programming/debugging options, including support for JTAG, SWD, and SWO Trace (Single Wire Output)), and seamless integration with the Mikroe software environment. Besides, it also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector.
Communication options such as USB-UART, USB HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet is also included. In addition, it also has the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options for the TFT board line of products and character-based LCD. Fusion for TIVA v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Type
8th Generation
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
Texas Instruments
Pin count
128
RAM (Bytes)
262144
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via UART Mode
1. Once the code example is loaded, pressing the "FLASH" button initiates the build process, and programs it on the created setup.
2. After the programming is completed, click on the Tools icon in the upper-right panel, and select the UART Terminal.
3. After opening the UART Terminal tab, first check the baud rate setting in the Options menu (default is 115200). If this parameter is correct, activate the terminal by clicking the "CONNECT" button.
4. Now terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
Software Support
Library Description
This library contains API for SRAM Click driver.
Key functions:
sram_write_byte
- Function write the 8-bit data to the target 24-bit register address of 23LC1024sram_read_byte
- Function read the 8-bit data to the target 24-bit register address of 23LC1024
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 Sram Click example
*
* # Description
* SRAM Click presents additional 1Mbit SRAM memory that can be added to device.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Application Init performs Logger and Click initialization.
*
* ## Application Task
* SRAM Click communicates with register via SPI protocol by write data to and read data from 23LC1024 Serial RAM device.
* Results are being sent to the UART where you can track their changes.
* All data logs on USB UART for aproximetly every 1 sec.
*
* \author Mihajlo Djordjevic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "sram.h"
char send_buffer[ 17 ] = { 'm', 'i', 'k', 'r', 'o', 'E', 'l', 'e', 'k', 't', 'r', 'o', 'n', 'i', 'k', 'a', ' ' };
char mem_data[ 17 ];
uint8_t n_cnt;
// ------------------------------------------------------------------ VARIABLES
static sram_t sram;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
sram_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 );
Delay_ms ( 100 );
log_info( &logger, "---- Application Init ----" );
// Click initialization.
sram_cfg_setup( &cfg );
SRAM_MAP_MIKROBUS( cfg, MIKROBUS_1 );
sram_init( &sram, &cfg );
log_printf( &logger, "--------------------------\r\n" );
log_printf( &logger, " ------ SRAM Click ----- \r\n" );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms ( 1000 );
}
void application_task ( void )
{
log_printf( &logger, " Writing text :\r\n" );
for ( n_cnt = 0; n_cnt < 16; n_cnt++ )
{
sram_write_byte( &sram, n_cnt, send_buffer[ n_cnt ] );
Delay_ms ( 100 );
log_printf( &logger, "%c", send_buffer[ n_cnt ] );
mem_data[ n_cnt ] = sram_read_byte( &sram, n_cnt );
}
log_printf( &logger, "\r\n" );
log_printf( &logger, " Read text :\r\n" );
for ( n_cnt = 0; n_cnt < 16; n_cnt++ )
{
mem_data[ n_cnt ] = sram_read_byte( &sram, n_cnt );
Delay_ms ( 100 );
log_printf( &logger, "%c", mem_data[ n_cnt ] );
}
log_printf( &logger, "\r\n" );
log_printf( &logger, "--------------------------\r\n" );
Delay_ms ( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END