Provide unparalleled data throughput with SST26VF064B and STM32F303RC
Quad the speed, quad the power
Published Aug 25, 2023
Click board™
SQI FLASH Click
Dev. board
Fusion for STM32 v8
Compiler
NECTO Studio
MCU
STM32F303RC
Easily integrate our Serial Quad I/O Flash Memory into existing systems, upgrading storage performance and meeting the demands of modern data-centric applications
A
A
Hardware Overview
How does it work?
SQI FLASH Click is based on the SST26VF064B, a 64 Mbit Serial Quad I/O flash device from Microchip. The chip utilizes a 4-bit multiplexed I/O serial interface to boost performance. The Click is a fast solid-state, non-volatile data storage medium that can be electrically erased and reprogrammed. Operating at 104 MHz, the SST26VF064B enables minimum latency execute-in-place (XIP) capability without code shadowing. Features like high performance and reliability make the SQI Flash click the ideal choice for network appliances, DSL and cable modems, wireless network devices, automotive, and other applications where high-speed, reliable data storage is needed. Further benefits are achieved with its proprietary, high-performance CMOS SuperFlash® technology, which significantly improves performance
and reliability and lowers power consumption. SQI Flash click features a 4-bit I/O interface allowing low-power and high-performance operation. SST26VF064B supports full command-set compatibility with traditional Serial Peripheral Interface (SPI) protocol. System designs using the SQI flash devices occupy less board space and ultimately lower the system costs. The SST26VF064B device is configured as a regular SPI device after the power-on, keeping the backward compatibility with the SPI interface. Once started using the regular SPI interface, the device can be configured to work in the Serial Quad Interface mode by setting the config registers. Several more features on this device are used to protect and manage data, such as the factory-programmed serial ID number, which can not be changed.
This can be used for identification or building various kinds of security devices. On top of the factory serial number, it is possible to define a second custom serial ID number, which can be locked by a protection bit. The device also has several non-volatile memory locations for storing protection/lock bits - so the device won't change the protection status when restarted. 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
Fusion for STM32 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 STMicroelectronics, regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. 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 STM32 v8 provides a fluid and immersive working experience, allowing
access anywhere and under any circumstances at any time. Each part of the Fusion for STM32 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 STM32 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)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
49152
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Fusion for STM32 v8 as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for SQI Flash Click driver.
Key functions:
sqiflash_write_generic- SQI FLASH Writesqiflash_read_generic- SQI FLASH Readsqiflash_global_block_unlock- SQI FLASH Global Block Unlock
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* @file main.c
* @brief SqiFlash Click example
*
* # Description
* This is an example that demonstrates the use of the SQI FLASH Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* SQI FLASH Driver Initialization, initializes the click by setting mikroBUS to
* approprieate logic levels, performing global block unlock and chip erase functions,
* reads manufacturer ID, memory type and device ID and logs it on USB UART terminal.
*
* ## Application Task
* Writing data to click memory and displaying the read data via UART.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "sqiflash.h"
static sqiflash_t sqiflash;
static log_t logger;
uint8_t device_manufac = 0;
uint8_t device_type = 0;
uint8_t device_id = 0;
uint8_t wr_data[ 9 ] = { 'M', 'i', 'k', 'r', 'o', 'E', 13, 10, 0 };
uint8_t rd_data[ 9 ] = { 0 };
uint32_t address = 0x015015ul;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
sqiflash_cfg_t sqiflash_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.
sqiflash_cfg_setup( &sqiflash_cfg );
SQIFLASH_MAP_MIKROBUS( sqiflash_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == sqiflash_init( &sqiflash, &sqiflash_cfg ) )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
Delay_ms ( 300 );
sqiflash_global_block_unlock( &sqiflash );
Delay_ms ( 400 );
sqiflash_chip_erase( &sqiflash );
Delay_ms ( 300 );
device_manufac = sqiflash_device_manufac( &sqiflash );
log_printf( &logger, " Manufacturer ID: 0x%.2X\r\n", ( uint16_t ) device_manufac );
device_type = sqiflash_device_type( &sqiflash );
log_printf( &logger, " Memory Type: 0x%.2X\r\n", ( uint16_t ) device_type );
device_id = sqiflash_device_id( &sqiflash );
log_printf( &logger, " Device ID: 0x%.2X\r\n", ( uint16_t ) device_id );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf( &logger, " Writing data to address: 0x%.6LX\r\n", address );
sqiflash_write_generic( &sqiflash, address, wr_data, 9 );
log_printf( &logger, " Written data: %s", wr_data );
log_printf( &logger, "\r\n Reading data from address: 0x%.6LX\r\n", address );
sqiflash_read_generic( &sqiflash, address, rd_data, 9 );
log_printf( &logger, " Read data: %s", rd_data );
log_printf( &logger, "-------------------------------------\r\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
