TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (405 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (133 codes)
  5. Bugz Bensce (97 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (141427 times)
  2. FAT32 Library (74284 times)
  3. Network Ethernet Library (58813 times)
  4. USB Device Library (48899 times)
  5. Network WiFi Library (44678 times)
  6. FT800 Library (44198 times)
  7. GSM click (30933 times)
  8. mikroSDK (29784 times)
  9. PID Library (27391 times)
  10. microSD click (27313 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
mikroSDK Library

SRAM 4 Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.16

mikroSDK Library: 2.0.0.0

Category: SRAM

Downloaded: 378 times

Not followed.

License: MIT license  

SRAM 4 Click is a compact add-on board that contains highly reliable nonvolatile memory. This board features the CY14B512Q, a 512Kbit SRAM with a nonvolatile element in each memory cell from Cypress Semiconductor, now part of Infineon.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "SRAM 4 Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "SRAM 4 Click" changes.

Do you want to report abuse regarding "SRAM 4 Click".

  • Information
  • Comments (0)

mikroSDK Library Blog


SRAM 4 Click

SRAM 4 Click is a compact add-on board that contains highly reliable nonvolatile memory. This board features the CY14B512Q, a 512Kbit SRAM with a nonvolatile element in each memory cell from Cypress Semiconductor, now part of Infineon.

sram_4_click.png

Click Product page


Click library

  • Author : Luka FIlipovic
  • Date : Aug 2021.
  • Type : SPI type

Software Support

We provide a library for the SRAM4 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Library Description

This library contains API for SRAM4 Click driver.

Standard key functions :

  • sram4_cfg_setup Config Object Initialization function.

    void sram4_cfg_setup ( sram4_cfg_t *cfg );
  • sram4_init Initialization function.

    err_t sram4_init ( sram4_t *ctx, sram4_cfg_t *cfg );
  • sram4_default_cfg Click Default Configuration function.

    err_t sram4_default_cfg ( sram4_t *ctx );

Example key functions :

  • sram4_memory_read Read data from memory.

    err_t sram4_memory_read ( sram4_t *ctx, uint16_t memory_adr, uint8_t *read_data, uint8_t read_len );
  • sram4_memory_write Write data to memory.

    err_t sram4_memory_write ( sram4_t *ctx, uint16_t memory_adr, uint8_t *write_data, uint8_t write_len );
  • sram4_generic_command Command writing function.

    err_t sram4_generic_command ( sram4_t *ctx, uint8_t cmd );

Example Description

This example application showcases ability of device ability to manipulate with memory( writing and reading data ).

The demo application is composed of two sections :

Application Init

Initialization of communication modules(SPI, UART) and additional pins. Reads ID and checks if it matches with SRAM4_DEVICE_ID to check communication. Then clears protection from memory access.


void application_init ( void )
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    sram4_cfg_t sram4_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.
    sram4_cfg_setup( &sram4_cfg );
    SRAM4_MAP_MIKROBUS( sram4_cfg, MIKROBUS_1 );
    err_t init_flag  = sram4_init( &sram4, &sram4_cfg );
    if ( SPI_MASTER_ERROR == init_flag )
    {
        log_error( &logger, " Application Init Error. " );
        log_info( &logger, " Please, run program again... " );
        for ( ; ; );
    }

    if ( sram4_default_cfg ( &sram4 ) )
    {
        log_error( &logger, " Default configuration. " );
        log_info( &logger, " Please, run program again... " );
        for ( ; ; );
    }

    log_info( &logger, " Application Task " );
}

Application Task

Writes 3 times to memory with length of data offset in memory addres. Then reads 2 times first 2 data written should be read in one read, and 3rd write should be read separately.


void application_task ( void )
{
    char read_buf[ 100 ] = { 0 };
    char click_name[ ] = "SRAM 4";
    char company_name[ ] = "MikroE";
    char product_name[ ] = " Click board";
    static const uint16_t START_ADR = 0x0001;
    uint16_t mem_adr = START_ADR;

    //Write Data
    sram4_memory_write( &sram4, mem_adr, click_name, strlen( click_name ) );
    mem_adr += strlen( click_name );
    sram4_memory_write( &sram4, mem_adr, product_name, strlen( product_name ) );
    mem_adr += strlen( product_name );
    sram4_memory_write( &sram4, mem_adr, company_name, strlen( company_name ) );

    //Read Data
    mem_adr = START_ADR;
    sram4_memory_read( &sram4, mem_adr, read_buf, strlen( click_name ) + strlen( product_name ) );
    log_printf( &logger, " > Read Data from 0x%.4X memory address: %s\r\n", mem_adr, read_buf );
    memset( read_buf, 0, strlen( read_buf ) );
    mem_adr += strlen(click_name) + strlen( product_name );
    sram4_memory_read( &sram4, mem_adr, read_buf, strlen( company_name ) );
    log_printf( &logger, " > Read Data from 0x%.4X memory address: %s\r\n", mem_adr, read_buf );
    log_printf( &logger, "**********************************************************************\r\n" );

    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
    Delay_ms ( 1000 );
}

The full application code, and ready to use projects can be installed directly from NECTO Studio Package Manager(recommended way), downloaded from our LibStock™ or found on Mikroe github account.

Other Mikroe Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.SRAM4

Additional notes and informations

Depending on the development board you are using, you may need USB UART Click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all MikroElektronika compilers, or any other terminal application of your choice, can be used to read the message.


ALSO FROM THIS AUTHOR

Semper Flash click

5

The Semper Flash Click is a Click board which features the S25HS512T, a perfect solution for the mass storage option in various embedded applications.

[Learn More]

DC Motor 17 Click

0

DC Motor 17 Click is a compact add-on board that contains a brushed DC motor driver. This board features the TC78H660FTG, a dual H Bridge driver for one or two brushed motors that incorporate a DMOS with low on-resistance in output transistors from Toshiba Semiconductor. This IC is a PWM controlled constant-current drive with supply voltages from 2.5V to 16V and 2A of output current. It features a sense-resistor less current control architecture and VCC regulator for the internal circuit. Also offers multi-error detect functions with error detection flag output function. This Click board™ is suitable for driving DC motors, controlling the direction of the rotation, as well as brake and regulate the motor current.

[Learn More]

Accel 2 click

5

Accel 2 click carries ST’s LIS3DSH IC, a low-power factory-calibrated three-axis accelerometer which embeds a FIFO buffer and two programmable state machines. The board communicates with the target board MCU through either SPI (CS#, SCK, SDO, SDI) or I2C (SCL, SDA) interfaces.

[Learn More]