Achieve the perfect balance of speed, efficiency, and data density with MB85AS8MT and TM4C1299KCZAD
Say goodbye to lag with ReRAM's lightning-fast speed
Published Oct 18, 2023
Click board™
ReRAM 2 Click
Dev. board
Fusion for Tiva v8
Compiler
NECTO Studio
MCU
TM4C1299KCZAD
Enhance your data storage capabilities with ReRAM, the innovative solution that's redefining how we store and access information
A
A
Hardware Overview
How does it work?
ReRAM 2 Click is based on the MB85AS8MT, a highly reliable 8Mbit resistive random-access memory (ReRAM) organized as 1,048,576 words of 8 bits from Fujitsu Semiconductor. It uses the resistance-variable memory process and silicon-gate CMOS process technologies to form nonvolatile memory cells. The MB85AS8MT specifies 1.000.000 endurance cycles with data retention of a minimum of 10 years, which gives the MB85AS8MT the capability to handle unlimited reads/writes to the memory. One prominent feature of the MB85AS8MT is an extremely small average current, despite its large density, for reading operations of 0.15mA at an operating frequency of 5MHz, which is only 5% of
large-density EEPROM devices. This feature enables minimal power consumption when in applications with frequent data-read operations. Besides higher write endurance, it has faster write speeds than EEPROM and flash memory, while its electric specifications, such as commands and timings, are compatible with EEPROM products. The ReRAM 2 Click communicates with MCU through a standard SPI interface that enables high clock speeds up to 10MHz, supporting the two most common SPI modes, SPI Mode 0 and 3. An additional feature of this Click board™ represents the configurable Write Protection function labeled as WP routed on the PWM pin of the mikroBUS™ socket. The WP pin protects the entire memory
and all registers from write operations and must be set to a low logic state to inhibit all the write operations. All memory and register write are prohibited when this pin is low, and the address counter is not incremented. Besides, the ReRAM 2 Click also has an additional HOLD pin, routed to the RST pin of the mikroBUS™ socket labeled as HO, to interrupt a serial operation without aborting it. 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 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)
512
Silicon Vendor
Texas Instruments
Pin count
212
RAM (Bytes)
262144
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 Tiva 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 ReRAM 2 Click driver.
Key functions:
reram2_read_device_id- ReRAM 2 read device ID function.reram2_write_memory- ReRAM 2 write memory function.reram2_read_memory- ReRAM 2 read memory function.
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 ReRAM2 Click example
*
* # Description
* This library contains API for ReRAM 2 Click driver.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes SPI driver and log UART.
* After driver initialization the app set default settings,
* performs device wake-up, check Device ID,
* set Write Enable Latch command and write demo_data string ( mikroE ),
* starting from the selected memory_addr ( 1234 ).
*
* ## Application Task
* This is an example that demonstrates the use of the ReRAM 2 Click board™.
* In this example, we read and display a data string, which we have previously written to memory,
* starting from the selected memory_addr ( 1234 ).
* Results are being sent to the Usart Terminal where you can track their changes.
*
* @author Nenad Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "reram2.h"
static reram2_t reram2;
static log_t logger;
static char demo_data[ 9 ] = { 'm', 'i', 'k', 'r', 'o', 'E', 13 ,10 , 0 };
static uint32_t memory_addr;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
reram2_cfg_t reram2_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.
reram2_cfg_setup( &reram2_cfg );
RERAM2_MAP_MIKROBUS( reram2_cfg, MIKROBUS_1 );
if ( SPI_MASTER_ERROR == reram2_init( &reram2, &reram2_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( RERAM2_ERROR == reram2_default_cfg ( &reram2 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
reram2_wake_up( &reram2 );
Delay_ms( 100 );
if ( RERAM2_ERROR == reram2_check_device_id( &reram2 ) )
{
log_error( &logger, " Communication Error. " );
log_info( &logger, " Please, run program again... " );
for( ; ; );
}
reram2_send_command( &reram2, RERAM2_CMD_WREN );
Delay_ms( 100 );
log_info( &logger, " Application Task " );
memory_addr = 1234;
log_printf( &logger, "\r\n Write data : %s", demo_data );
reram2_write_memory( &reram2, memory_addr, &demo_data[ 0 ], 9 );
log_printf( &logger, "-----------------------\r\n" );
Delay_ms( 1000 );
}
void application_task ( void )
{
static char rx_data[ 9 ] = { 0 };
reram2_read_memory( &reram2, memory_addr, &rx_data[ 0 ], 9 );
log_printf( &logger, " Read data : %s", rx_data );
log_printf( &logger, "-----------------------\r\n" );
Delay_ms( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
