Flash 13 Click
Flash 13 Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.
Click Library
- Author : Stefan Filipovic
- Date : Mar 2025.
- Type : SPI type
Software Support
Example Description
This example demonstrates the use of Flash 13 Click board by writing specified data to the memory and reading it back.
Example Libraries
- MikroSDK.Board
- MikroSDK.Log
- Click.Flash13
Example Key Functions
- flash13_cfg_setup This function initializes Click configuration structure to initial values.
void flash13_cfg_setup(flash13_cfg_t *cfg)
Flash 13 configuration object setup function.
Flash 13 Click configuration object.
Definition flash13.h:222
- flash13_init This function initializes all necessary pins and peripherals used for this Click board.
err_t flash13_init(flash13_t *ctx, flash13_cfg_t *cfg)
Flash 13 initialization function.
Flash 13 Click context object.
Definition flash13.h:205
- flash13_erase_memory This function erases the selected amount of memory which contains the selected address.
err_t flash13_erase_memory(flash13_t *ctx, uint8_t erase_cmd, uint32_t address)
Flash 13 erase memory function.
- flash13_memory_write This function writes a desired number of data bytes starting from the selected memory address.
err_t flash13_memory_write(flash13_t *ctx, uint32_t address, uint8_t *data_in, uint32_t len)
Flash 13 memory write function.
- flash13_memory_read This function reads a desired number of data bytes starting from the selected memory address.
err_t flash13_memory_read(flash13_t *ctx, uint32_t address, uint8_t *data_out, uint32_t len)
Flash 13 memory read function.
Application Init
Initializes the driver and checks the communication by reading and verifying the device ID.
{
log_cfg_t log_cfg;
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
if ( SPI_MASTER_ERROR ==
flash13_init( &flash13, &flash13_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
{
log_error( &logger, " Check communication." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
@ FLASH13_ERROR
Definition flash13.h:247
#define FLASH13_MAP_MIKROBUS(cfg, mikrobus)
MikroBUS pin mapping.
Definition flash13.h:189
err_t flash13_check_communication(flash13_t *ctx)
Flash 13 check communication function.
void application_init(void)
Definition main.c:34
Application Task
Writes a desired number of bytes to the memory and then verifies if it is written correctly by reading from the same memory location and displaying the memory content on the USB UART. The whole 4KB sector of memory that contains the STARTING_ADDRESS will be erased before writing data.
{
uint8_t data_buf[ 128 ] = { 0 };
log_printf ( &logger,
" Memory address: 0x%.6LX\r\n", ( uint32_t )
STARTING_ADDRESS );
{
log_printf ( &logger, " Erase memory block (4KB)\r\n" );
}
{
log_printf ( &logger, " Write data: %s\r\n", data_buf );
Delay_ms ( 100 );
}
memset ( data_buf, 0, sizeof ( data_buf ) );
{
log_printf ( &logger, " Read data: %s\r\n\n", data_buf );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
log_printf ( &logger,
" Memory address: 0x%.6LX\r\n", ( uint32_t )
STARTING_ADDRESS );
{
log_printf ( &logger, " Erase memory block (4KB)\r\n" );
}
{
log_printf ( &logger, " Write data: %s\r\n", data_buf );
Delay_ms ( 100 );
}
memset ( data_buf, 0, sizeof ( data_buf ) );
{
log_printf ( &logger, " Read data: %s\r\n\n", data_buf );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
}
@ FLASH13_OK
Definition flash13.h:246
#define FLASH13_CMD_SECTOR_ERASE_4KB
Definition flash13.h:100
void application_task(void)
Definition main.c:70
#define DEMO_TEXT_MESSAGE_2
Definition main.c:28
#define DEMO_TEXT_MESSAGE_1
Definition main.c:27
#define STARTING_ADDRESS
Definition main.c:29
Application Output
This Click board can be interfaced and monitored in two ways:
- Application Output - Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
- UART Terminal - Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Additional Notes and Information
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.