vmu.h

Go to the documentation of this file.

/* KallistiOS ##version##
 
   dc/maple/vmu.h
   Copyright (C) 2000-2002 Jordan DeLong, Megan Potter
   Copyright (C) 2008 Donald Haase
   Copyright (C) 2023 Andy Barajas
   Copyright (C) 2023, 2025 Falco Girgis
 
*/
 
/** \file    dc/maple/vmu.h
    \brief   Definitions for using the VMU device.
    \ingroup vmu
 
    This file provides an API around the various Maple function
    types (LCD, MEMCARD, CLOCK) provided by the Visual Memory Unit. 
    Each API can also be used independently for devices which aren't
    VMUs, such as using MEMCARD functionality with a standard memory
    card that lacks a screen or buzzer.
 
    \author Jordan DeLong
    \author Megan Potter
    \author Donald Haase
    \author Falco Girgis
*/
 
#ifndef __DC_MAPLE_VMU_H
#define __DC_MAPLE_VMU_H
 
#include <sys/cdefs.h>
__BEGIN_DECLS
 
#include <arch/types.h>
#include <dc/maple.h>
#include <kos/regfield.h>
 
#include <stdint.h>
#include <time.h>
 
/** \defgroup vmu Visual Memory Unit
    \brief    VMU/VMS Maple Peripheral API
    \ingroup  peripherals
 
    The Sega Dreamcast's Visual Memory Unit (VMU) 
    is an 8-Bit gaming device which, when plugged into 
    the controller, communicates with the Dreamcast 
    as a Maple peripheral. 
 
                Visual Memory Unit
                 _________________
                /                 \
                |   @ Dreamcast   |
                |   ___________   |                  
                |  |           |  |                 
                |  |           |  |                 
                |  |           |  |            
                |  |           |  |  
        Sleep   |  |___________|  |   Mode 
          ------|---------\    /--|-------  
                |   |¯|   *   *   |
             /--|-|¯   ¯| /¯\ /¯\_|____     
            /   |  ¯|_|¯  \_/ \_/ |    \
           |    |          |      |    B
         D-pad  \__________|______/  
                           |
                           A
 
    As a Maple peripheral, the VMU implements the 
    following functions:
    - <b>MEMCARD</b>: Storage device used for saving and 
                      loading game files.
    - <b>LCD</b>:     Secondary LCD display on which additional
                      information may be presented to the player.
    - <b>CLOCK</b>:   A device which maintains the current date 
                      and time, provides at least one buzzer for
                      playing tones, and also has buttons used 
                      for input.
 
    Each Maple function has a corresponding set of C functions
    providing a high-level API around its functionality.
 
*/
/** \defgroup vmu_settings Settings
    \brief    Customizable configuration data 
    \ingroup  vmu 
    
    This module provides a high-level abstraction around various 
    features and settings which can be modified on the VMU. Many
    of these operations are provided by the Dreamcast's BIOS when
    a VMU has been formatted.
*/
 
/** \brief   Get the status of a VMUs extra 41 blocks
    \ingroup vmu_settings
 
    This function checks if the extra 41 blocks of a VMU have been
    enabled.
 
    \param  dev             The device to check the status of.
 
    \retval 1               On success: extra blocks are enabled
    \retval 0               On success: extra blocks are disabled
    \retval -1              On failure
*/
int vmu_has_241_blocks(maple_device_t *dev);
 
/** \brief   Enable the extra 41 blocks of a VMU
    \ingroup vmu_settings
 
    This function enables/disables the extra 41 blocks of a specific VMU.
 
    \warning    Enabling the extra blocks of a VMU may render it unusable
                for a very few commercial games.
 
    \param  dev             The device to enable/disable 41 blocks.
    \param  enable          Values other than 0 enables. Equal to 0 disables.
 
    \retval 0               On success
    \retval -1              On failure
*/
int vmu_toggle_241_blocks(maple_device_t *dev, int enable);
 
/** \brief   Enable custom color of a VMU
    \ingroup vmu_settings
 
    This function enables/disables the custom color of a specific VMU. 
    This color is only displayed in the Dreamcast's file manager.
 
    \param  dev             The device to enable/disable custom color.
    \param  enable          Values other than 0 enables. Equal to 0 disables.
 
    \retval 0               On success
    \retval -1              On failure
 
    \sa vmu_set_custom_color
*/
int vmu_use_custom_color(maple_device_t *dev, int enable);
 
/** \brief   Set custom color of a VMU
    \ingroup vmu_settings
 
    This function sets the custom color of a specific VMU. This color is only
    displayed in the Dreamcast's file manager. This function also enables the 
    use of the custom color. Otherwise it wouldn't show up.
 
    \param  dev             The device to change the color of.
    \param  red             The red component. 0-255
    \param  green           The green component. 0-255
    \param  blue            The blue component. 0-255
    \param  alpha           The alpha component. 0-255; 100-255 Recommended
 
    \retval 0               On success
    \retval -1              On failure
 
    \sa vmu_get_custom_color, vmu_use_custom_color
*/
int vmu_set_custom_color(maple_device_t *dev, uint8_t red, uint8_t green, uint8_t blue, uint8_t alpha);
 
/** \brief   Get custom color of a VMU
    \ingroup vmu_settings
 
    This function gets the custom color of a specific VMU. This color is only
    displayed in the Dreamcast's file manager. This function also returns whether
    the custom color is currently enabled.
 
    \param  dev             The device to change the color of.
    \param  red             The red component. 0-255
    \param  green           The green component. 0-255
    \param  blue            The blue component. 0-255
    \param  alpha           The alpha component. 0-255; 100-255 Recommended
 
    \retval 1               On success: custom color is enabled
    \retval 0               On success: custom color is disabled
    \retval -1              On failure
 
    \sa vmu_set_custom_color, vmu_use_custom_color
*/
int vmu_get_custom_color(maple_device_t *dev, uint8_t *red, uint8_t *green, uint8_t *blue, uint8_t *alpha);
 
/** \brief   Set icon shape of a VMU
    \ingroup vmu_settings
 
    This function sets the icon shape of a specific VMU. The icon shape is a
    VMU icon that is displayed on the LCD screen while navigating the Dreamcast
    BIOS menu and is the GUI representation of the VMU in the menu's file manager.
    The Dreamcast BIOS provides a set of 124 icons to choose from.
 
    \note
    When a custom file named "ICONDATA_VMS" is present on a VMU, it overrides this
    icon by providing custom icons for both the DC BIOS menu and the VMU's LCD screen.
 
    \param  dev             The device to change the icon shape of.
    \param  icon_shape      One of the values found in \ref vmu_icons.
 
    \retval 0               On success
    \retval -1              On failure
 
    \sa vmu_icons, vmu_get_icon_shape
*/
int vmu_set_icon_shape(maple_device_t *dev, uint8_t icon_shape);
 
/** \brief   Get icon shape of a VMU
    \ingroup vmu_settings
 
    This function gets the icon shape of a specific VMU. The icon shape is a
    VMU icon that is displayed on the LCD screen while navigating the Dreamcast
    BIOS menu and is the GUI representation of the VMU in the menu's file manager.
    The Dreamcast BIOS provides a set of 124 icons to choose from.
 
    \note
    When a custom file named "ICONDATA_VMS" is present on a VMU, it overrides this
    icon by providing custom icons for both the DC BIOS menu and the VMU's LCD screen.
 
    \param  dev             The device to change the icon shape of.
    \param  icon_shape      One of the values found in \ref vmu_icons.
 
    \retval 0               On success
    \retval -1              On failure
 
    \sa vmu_icons, vmu_set_icon_shape
*/
int vmu_get_icon_shape(maple_device_t *dev, uint8_t *icon_shape);
 
/** \defgroup maple_lcd LCD Function
    \brief API for features of the LCD Maple Function
    \ingroup  vmu
 
    The LCD Maple function is for exposing a secondary LCD screen
    that gets attached to a controller, which can be used to display
    additional game information, or information you only want visible
    to a single player. 
*/
 
/**
    \brief   Pixel width of a standard VMU screen
    \ingroup maple_lcd
*/
#define VMU_SCREEN_WIDTH    48
 
/**
    \brief Pixel height of a standard VMU screen
    \ingroup maple_lcd
*/
#define VMU_SCREEN_HEIGHT   32
 
/** \brief   Display a 1bpp bitmap on a VMU screen.
    \ingroup maple_lcd
 
    This function sends a raw bitmap to a VMU to display on its screen. This
    bitmap is 1bpp, and is 48x32 in size.
 
    \param  dev             The device to draw to.
    \param  bitmap          The bitmap to show.
 
    \retval MAPLE_EOK       On success.
    \retval MAPLE_EAGAIN    If the command couldn't be sent. Try again later.
    \retval MAPLE_ETIMEOUT  If the command timed out while blocking.
 
    \sa vmu_draw_lcd_rotated, vmu_draw_lcd_xbm, vmu_set_icon
*/
int vmu_draw_lcd(maple_device_t *dev, const void *bitmap);
 
/** \brief   Display a 1bpp bitmap on a VMU screen.
    \ingroup maple_lcd
 
    This function sends a raw bitmap to a VMU to display on its screen. This
    bitmap is 1bpp, and is 48x32 in size. This function is equivalent to
    vmu_draw_lcd(), but the image is rotated 180° so that the first byte of the
    bitmap corresponds to the top-left corner, instead of the bottom-right one.
 
    \warning    This function is optimized by an assembly routine which operates
                on 32 bits at a time. As such, the given bitmap must be 4-byte
                aligned.
 
    \param  dev             The device to draw to.
    \param  bitmap          The bitmap to show.
    \retval MAPLE_EOK       On success.
    \retval MAPLE_EAGAIN    If the command couldn't be sent. Try again later.
    \retval MAPLE_ETIMEOUT  If the command timed out while blocking.
 
    \sa vmu_draw_lcd, vmu_draw_lcd_xbm, vmu_set_icon
*/
int vmu_draw_lcd_rotated(maple_device_t *dev, const void *bitmap);
 
/** \brief   Display a Xwindows XBM image on a VMU screen.
    \ingroup maple_lcd
 
    This function takes in a Xwindows XBM, converts it to a raw bitmap, and sends 
    it to a VMU to display on its screen. This XBM image is 48x32 in size.
 
    \param  dev             The device to draw to.
    \param  vmu_icon        The icon to set.
 
    \retval MAPLE_EOK       On success.
    \retval MAPLE_EAGAIN    If the command couldn't be sent. Try again later.
    \retval MAPLE_ETIMEOUT  If the command timed out while blocking.
 
    \sa vmu_draw_lcd, vmu_set_icon
*/
int vmu_draw_lcd_xbm(maple_device_t *dev, const char *vmu_icon);
 
/** \brief   Display a Xwindows XBM on all VMUs.
    \ingroup maple_lcd
 
    This function takes in a Xwindows XBM and displays the image on all VMUs.
 
    \note
    This is a convenience function for vmu_draw_lcd() to broadcast across all VMUs.
 
    \todo
    Prevent this routine from broadcasting to rear VMUs.
 
    \param  vmu_icon        The icon to set.
 
    \sa vmu_draw_lcd_xbm
*/
void vmu_set_icon(const char *vmu_icon);
 
/** \defgroup maple_memcard Memory Card Function
    \brief    API for features of the Memory Card Maple Function
    \ingroup  vmu
 
    The Memory Card Maple function is for exposing a low-level,
    block-based API that allows you to read from and write to
    random blocks within the memory card's filesystem.
 
    \note
    A standard memory card has a block size of 512 bytes; however,
    the block size is a configurable parameter in the "root" block,
    which can be queried to cover supporting homebrew memory
    cards with larger block sizes.
 
    \warning
    You should never use these functions directly, unless you 
    <i>really</i> know what you're doing, as you can easily corrupt
    the filesystem by writing incorrect data. Instead, you should
    favor the high-level filesystem API found in vmufs.h, or just
    use the native C standard filesystem API within the virtual 
    `/vmu/` root directory to operate on VMU data. 
*/
 
/** \brief   Read a block from a memory card.
    \ingroup maple_memcard
 
    This function performs a low-level raw block read from a memory card.
 
    \param  dev             The device to read from.
    \param  blocknum        The block number to read.
    \param  buffer          The buffer to read into (512 bytes).
 
    \retval MAPLE_EOK       On success.
    \retval MAPLE_ETIMEOUT  If the command timed out while blocking.
    \retval MAPLE_EFAIL     On errors other than timeout.
 
    \sa vmu_block_write
*/
int vmu_block_read(maple_device_t *dev, uint16_t blocknum, uint8_t *buffer);
 
/** \brief   Write a block to a memory card.
    \ingroup maple_memcard
 
    This function performs a low-level raw block write to a memory card.
 
    \param  dev             The device to write to.
    \param  blocknum        The block number to write.
    \param  buffer          The buffer to write from (512 bytes).
 
    \retval MAPLE_EOK       On success.
    \retval MAPLE_ETIMEOUT  If the command timed out while blocking.
    \retval MAPLE_EFAIL     On errors other than timeout.
 
    \sa vmu_block_read
*/
int vmu_block_write(maple_device_t *dev, uint16_t blocknum, const uint8_t *buffer);
 
/** \defgroup maple_clock Clock Function
    \brief    API for features of the Clock Maple Function
    \ingroup  vmu
 
    The Clock Maple function provides a high-level API for the 
    following functionality:
        - buzzer tone generation
        - date/time management
        - input/button status
*/
 
/** \name Buzzer
    \brief Methods for tone generation.
    @{
*/
 
/** \brief   Make a VMU beep (low-level).
    \ingroup maple_clock
 
    This function sends a raw beep to a VMU, causing the speaker to emit a tone
    noise.
 
    \note
    See http://dcemulation.org/phpBB/viewtopic.php?f=29&t=97048 for the
    original information about beeping.
 
    \warning
    This function is submitting raw, encoded values to the VMU. For a more
    user-friendly API built around generating simple tones, see vmu_beep_waveform().
 
    \param  dev             The device to attempt to beep.
    \param  beep            The tone to generate. Byte values are as follows:
                                1. period of square wave 1
                                2. duty cycle of square wave 1
                                3. period of square wave 2 (ignored by
                                   standard mono VMUs)
                                4. duty cycle of square wave 2 (ignored by
                                   standard mono VMUs) 
 
    \retval MAPLE_EOK       On success.
    \retval MAPLE_EAGAIN    If the command couldn't be sent. Try again later.
    \retval MAPLE_ETIMEOUT  If the command timed out while blocking.
 
    \sa vmu_beep_waveform
*/
int vmu_beep_raw(maple_device_t *dev, uint32_t beep);
 
/** \brief   Play VMU Buzzer tone.
    \ingroup maple_clock
 
    Sends two different square waves to generate tone(s) on the VMU. Each
    waveform is configured as shown by the following diagram. On a standard
    VMU, there is only one piezoelectric buzzer, so waveform 2 is ignored; 
    however, the parameters do support dual-channel stereo in case such a 
    VMU ever does come along. 
 
                               Period
                       +---------------------+
                       |                     |
        HIGH __________            __________
                       |          |          |          |
                       |          |          |          |
                       |__________|          |__________|
        LOW
                                  |          |
                                  +----------+
                                   Duty Cycle
        
                             WAVEFORM
 
    To stop an active tone, one can simply generate a flat wave, such as by 
    submitting both values as 0s.
 
    \warning
    Any submitted waveform which has a duty cycle of greater than or equal to 
    its period will result in an invalid waveform being generated and is 
    going to mute or end the tone.
 
    \note
    Note that there are no units given for the waveform, so any 3rd party VMU 
    is free to use any base clock rate, potentially resulting in different 
    frequencies (or tones) being generated for the same parameters on different 
    devices.
 
    \note
    On the VMU-side, this tone is generated using the VMU's Timer1 peripheral
    as a pulse generator, which is then fed into its piezoelectric buzzer. The 
    calculated range of the standard VMU, given its 6MHz CF clock running with a 
    divisor of 6 is driving the Timer1 counter, is approximately 3.9KHz-500Khz;
    however, due to physical characteristics of the buzzer, not every frequency
    can be produced at a decent volume, so it's recommended that you test your
    values, using the KOS example found at `/examples/dreamcast/vmu/beep`.
 
    \param  dev                 The VMU device to play the tone on
    \param  period1             The period or total interval of the first waveform
    \param  duty_cycle1         The duty cycle or active interval of the first waveform 
    \param  period2             The period or total interval of the second waveform
                                (ignored by standard first-party VMUs).
    \param  duty_cycle2         The duty cycle or active interval of the second waveform
                                (ignored by standard first-party VMUs).
 
    \retval MAPLE_EOK           On success.
    \retval MAPLE_EAGAIN        If the command couldn't be sent. Try again later.
    \retval MAPLE_ETIMEOUT      If the command timed out while blocking.
*/
int vmu_beep_waveform(maple_device_t *dev, uint8_t period1, uint8_t duty_cycle1, uint8_t period2, uint8_t duty_cycle2);
 
/** @} */
 
/** \name Date/Time
    \brief Methods for managing date and time.
    @{
*/
 
/** \brief  Set the date and time on the VMU.
    \ingroup maple_clock
 
    This function sets the VMU's date and time values to
    the given standard C Unix timestamp.
 
    \param  dev             The device to write to.
    \param  unix            Seconds since Unix epoch
 
    \retval MAPLE_EOK       On success.
    \retval MAPLE_ETIMEOUT  If the command timed out while blocking.
    \retval MAPLE_EFAIL     On errors other than timeout.
 
    \sa vmu_get_datetime
*/
int vmu_set_datetime(maple_device_t *dev, time_t unix);
 
/** \brief   Get the date and time on the VMU.
    \ingroup maple_clock
 
    This function gets the VMU's date and time values
    as a single standard C Unix timestamp.
 
    \note
    This is the VMU equivalent of calling `time(unix)`.
 
    \param  dev             The device to write to.
    \param  unix            Seconds since Unix epoch (set to -1 upon failure)
 
    \retval MAPLE_EOK       On success.
    \retval MAPLE_ETIMEOUT  If the command timed out while blocking.
    \retval MAPLE_EFAIL     On errors other than timeout.
 
    \sa vmu_set_datetime
*/
int vmu_get_datetime(maple_device_t *dev, time_t *unix);
 
/** @} */
 
/** \defgroup vmu_buttons VMU Buttons
    \brief    VMU button masks
    \ingroup  maple_clock
 
    VMU's button state/cond masks, same as capability masks
 
    \note
    The MODE and SLEEP button states are not pollable on
    a standard VMU.
 
    @{
*/
 
#define VMU_DPAD_UP    BIT(0)   /**< Up Dpad button on the VMU */
#define VMU_DPAD_DOWN  BIT(1)   /**< Down Dpad button on the VMU */
#define VMU_DPAD_LEFT  BIT(2)   /**< Left Dpad button on the VMU */
#define VMU_DPAD_RIGHT BIT(3)   /**< Right Dpad button on the VMU */
#define VMU_A          BIT(4)   /**< 'A' button on the VMU */
#define VMU_B          BIT(5)   /**< 'B' button on the VMU */
#define VMU_MODE       BIT(6)   /**< Mode button on the VMU */
#define VMU_SLEEP      BIT(7)   /**< Sleep button on the VMU */
 
/** \brief Represents the combined state of all VMU buttons.
 
    Button states values:
    - `0`: Released
    - `1`: Pressed
 
    \note
    The Dpad buttons are automatically reoriented for you depending on
    which direction the VMU is facing in a particular type of controller.
 */
typedef union vmu_buttons {
    uint8_t raw;                /**< Combined button state mask */
    struct {
        uint8_t dpad_up:    1;  /**< Dpad Up button state */
        uint8_t dpad_down:  1;  /**< Dpad Down button state */
        uint8_t dpad_left:  1;  /**< Dpad Left button state */
        uint8_t dpad_right: 1;  /**< Dpad Right button state */
        uint8_t a:          1;  /**< 'A' button state */
        uint8_t b:          1;  /**< 'B' button state */
        uint8_t mode:       1;  /**< Mode button state */
        uint8_t sleep:      1;  /**< Sleep button state */
    };
} vmu_buttons_t;
 
/** "Civilized" structure containing VMU's current state.
 
    \note
    Don't forget that if you want valid button state information, you must
    enable polling for it in the driver with vmu_set_buttons_enabled()!
*/
typedef struct vmu_state {
    struct {
        vmu_buttons_t current;  /**< Button states from the current frame */
        vmu_buttons_t previous; /**< Button states from the previous frame */
    } buttons;                  /**< Latest two frames of button state data */
} vmu_state_t;
 
/** @} */
 
/** \name Input
    \brief Methods for polling button states.
    @{
*/
 
/** \brief   Enable/Disable polling for VMU input
    \ingroup maple_clock
 
    This function is used to either enable or disable polling the
    VMU buttons' states for input each frame.
 
    \note
    These buttons are not usually accessible to the player; however,
    several devices, such as the ASCII pad, the arcade pad, and
    the Retro Fighters controller leave the VMU partially exposed,
    so that these buttons remain accessible, allowing them to be used
    as extended controller inputs.
 
    \note
    Polling for VMU input is disabled by default to reduce unnecessary
    Maple BUS traffic.
 
    \sa vmu_get_buttons_enabled
*/
void vmu_set_buttons_enabled(int enable);
 
/** \brief   Check whether polling for VMU input has been enabled
    \ingroup maple_clock
 
    This function is used to check whether per-frame polling of
    the VMU's button states has been enabled in the driver.
 
    \note
    Polling for VMU input is disabled by default to reduce unnecessary
    Maple BUS traffic.
 
    \sa vmu_set_buttons_enabled
*/
int vmu_get_buttons_enabled(void);
 
/** @} */
 
/** \cond */
/* Init / Shutdown -- Managed internally by KOS */
void vmu_init(void);
void vmu_shutdown(void);
/** \endcond */
 
__END_DECLS
 
#endif  /* __DC_MAPLE_VMU_H */