Achieve the perfect balance of speed, efficiency, and data density with MB85AS8MT and PIC32MZ1024EFH064
Say goodbye to lag with ReRAM's lightning-fast speed
Published Oct 18, 2023
Click board™
ReRAM 2 Click
Dev Board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
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
PIC32MZ Clicker is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit PIC32MZ microcontroller with FPU from Microchip, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access anywhere and under
any circumstances. Each part of the PIC32MZ Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the PIC32MZ Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for PIC, dsPIC, or PIC32 programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB Micro-B connection can provide up to 500mA of current, which is more than enough to operate all onboard
and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. PIC32MZ Clicker is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping 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
Architecture
PIC32
MCU Memory (KB)
1024
Silicon Vendor
Microchip
Pin count
64
RAM (Bytes)
524288
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 PIC32MZ clicker 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 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
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 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
