Boost the efficiency and speed of your design with FRAM memory technology
A
A
Hardware Overview
How does it work?
Excelon-Ultra Click is based on the CY15B116QSN, a high-performance 16-Mbit nonvolatile memory employing an advanced Infineon ferroelectric process. The memory array is logically organized as 2,097,152 × 8 bits and is accessed using an industry-standard serial peripheral interface (SPI) bus. The CY15B116QSN combines a 16-Mbit F-RAM with the high-speed Quad SPI SDR and DDR interfaces, enhancing FRAM technology's nonvolatile write capability. The key differences between the CY15B116QSN and a serial flash are the FRAM's superior write performance, high endurance, and lower power consumption. The CY15B116QSN is ideal for nonvolatile memory applications requiring frequent or rapid writes. Examples range from data collection, where the number of write cycles may be critical, to demanding industrial controls, where the long
write time of serial Flash can cause data loss. Excelon-Ultra Click communicates with MCU using an industry-standard SPI interface supporting the two most common modes, SPI Mode 0 and 3, with a maximum frequency 108MHz. Data is written to the memory array immediately after each byte is successfully transferred to the device. The following bus cycle can commence without the need for data polling. It supports 1e14 read/write cycles, or 100 million times more write cycles than EEPROM. In addition, the CY15B116QSN offers substantial write endurance compared to other nonvolatile memories. Furthermore, this Click board™ provides additional hardware-controlled functions. The configurable Write Protection function routed on the PWM pin of the mikroBUS™ socket protects all registers (including status and
configuration) from write operations when the SRWD bit (SR1[7]) is set to '1'. The WP pin must be held high to inhibit all the write operations to registers. When this pin is high, all memory and register writes are prohibited, and the address counter is not incremented. Also, it has a Reset feature routed to the RST pin on the mikroBUS™ socket, which, with a low logic level, puts the CY15B116QSN into a Reset state and, with a high level, operates the module normally. 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 STM32F091RC 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
Architecture
ARM Cortex-M0
MCU Memory (KB)
256
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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
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 Excelon-Ultra Click driver.
Key functions:
excelonultra_write_data_to_memory
- Write data starting from specified memory addressexcelonultra_read_data_from_memory
- Read data starting from specified memory addressexcelonultra_clear_data_from_memory
-Clears data starting from specified memory address
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 ExcelonUltra Click example
*
* # Description
* This example is showcase of device and it's library abillity.
* In this example is shown device ID, ability to manipulate with memory.
* After default configuration device IDs are logged. After that application
* Writes data to memory, reads data from memory, clears data from memory and
* checks if data is cleard by reading that same memory address.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes MCU modules for communication used in this application (UART, SPI).
* Calls default configuration that resets device, reads IDs, and enables writing to
* memory and sets all RAM memory to be free for conrol.
*
* ## Application Task
* Write data to memory, read data from memory. After that clears that memory address,
* and checks if it's cleared by reading data. On every iteration of the fucntion
* writing data is changed between "MikroE" and "Excelon-Ultra Click"
*
* @author Luka Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "excelonultra.h"
#define MIKROE_DATA "MikroE"
#define CLICK_DATA "Excelon-Ultra Click"
static excelonultra_t excelonultra;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
excelonultra_cfg_t excelonultra_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.
excelonultra_cfg_setup( &excelonultra_cfg );
EXCELONULTRA_MAP_MIKROBUS( excelonultra_cfg, MIKROBUS_1 );
err_t init_flag = excelonultra_init( &excelonultra, &excelonultra_cfg );
if ( init_flag == SPI_MASTER_ERROR )
{
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
excelonultra_default_cfg ( &excelonultra );
log_printf( &logger, " > Manufacturer ID: 0x%.4X\r\n", excelonultra.manufacturer_id );
log_printf( &logger, " > Product ID: 0x%.4X\r\n", excelonultra.product_id );
log_printf( &logger, " > Density ID: 0x%.2X\r\n", excelonultra.density_id );
log_printf( &logger, " > Die Rev: 0x%.2X\r\n", excelonultra.die_rev );
log_printf( &logger, " > Unique ID: 0x%.2X" , excelonultra.unique_id[ 7 ] );
log_printf( &logger, "%.2X" , excelonultra.unique_id[ 6 ] );
log_printf( &logger, "%.2X" , excelonultra.unique_id[ 5 ] );
log_printf( &logger, "%.2X" , excelonultra.unique_id[ 4 ] );
log_printf( &logger, "%.2X" , excelonultra.unique_id[ 3 ] );
log_printf( &logger, "%.2X" , excelonultra.unique_id[ 2 ] );
log_printf( &logger, "%.2X" , excelonultra.unique_id[ 1 ] );
log_printf( &logger, "%.2X\r\n" , excelonultra.unique_id[ 0 ] );
Delay_ms( 1000 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
static uint32_t memory_address = 0x00000055;
static uint8_t data_selection = 1;
static uint8_t write_len;
char to_write[ 50 ] = { 0 };
char read_from[ 50 ] = { 0 };
if (data_selection)
{
strcpy( to_write, MIKROE_DATA );
data_selection = !data_selection;
}
else
{
strcpy( to_write, CLICK_DATA );
data_selection = !data_selection;
}
write_len = strlen( to_write );
log_printf( &logger, " > Writing data to memory: %s\r\n", to_write );
excelonultra_write_data_to_memory( &excelonultra, memory_address, to_write, write_len );
Delay_ms( 500 );
excelonultra_read_data_from_memory( &excelonultra, memory_address, read_from, write_len );
log_printf( &logger, " > Read data from memory: %s\r\n", read_from );
Delay_ms( 500 );
log_printf( &logger, " > Clearing data from memory\r\n" );
excelonultra_clear_data_from_memory( &excelonultra, memory_address, write_len );
Delay_ms( 500 );
excelonultra_read_data_from_memory( &excelonultra, memory_address, read_from, write_len );
log_printf( &logger, " > Read data from memory: %s\r\n", read_from );
log_printf( &logger, "***********************************\r\n" );
Delay_ms( 500 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:FRAM