Experience seamless multitasking and quick data processing with 23LC1024 and PIC18F57Q43
Highly reliable nonvolatile memory
Published Feb 13, 2024
Click board™
SRAM Click
Dev Board
Curiosity Nano with PIC18F57Q43
Compiler
NECTO Studio
MCU
PIC18F57Q43
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
PIC18F57Q43 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate microcontrollers within the PIC18-Q43 family. Central to its design is the inclusion of the powerful PIC18F57Q43 microcontroller (MCU), offering advanced functionalities and robust performance. Key features of this evaluation kit include a yellow user LED and a responsive
mechanical user switch, providing seamless interaction and testing. The provision for a 32.768kHz crystal footprint ensures precision timing capabilities. With an onboard debugger boasting a green power and status LED, programming and debugging become intuitive and efficient. Further enhancing its utility is the Virtual serial port (CDC) and a debug GPIO channel (DGI
GPIO), offering extensive connectivity options. Powered via USB, this kit boasts an adjustable target voltage feature facilitated by the MIC5353 LDO regulator, ensuring stable operation with an output voltage ranging from 1.8V to 5.1V, with a maximum output current of 500mA, subject to ambient temperature and voltage constraints.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
48
RAM (Bytes)
8196
You complete me!
Accessories
Curiosity Nano Base for Click boards is a versatile hardware extension platform created to streamline the integration between Curiosity Nano kits and extension boards, tailored explicitly for the mikroBUS™-standardized Click boards and Xplained Pro extension boards. This innovative base board (shield) offers seamless connectivity and expansion possibilities, simplifying experimentation and development. Key features include USB power compatibility from the Curiosity Nano kit, alongside an alternative external power input option for enhanced flexibility. The onboard Li-Ion/LiPo charger and management circuit ensure smooth operation for battery-powered applications, simplifying usage and management. Moreover, the base incorporates a fixed 3.3V PSU dedicated to target and mikroBUS™ power rails, alongside a fixed 5.0V boost converter catering to 5V power rails of mikroBUS™ sockets, providing stable power delivery for various connected devices.
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 Curiosity Nano with PIC18F57Q43 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 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
