EveApps is a set of applications based on Eve Series chip (FT80X, FT81X, BT815/6, BT817/8) for users to refer to. It contains 28 demo application and 11 sample application. They are all written in ANSI C code and full source code is enclosed.

• Demo application is for demo purpose and fair complex, which is closed to real-life project.
• Sample application is for the tutorial purpose which is simpler and easier to understand each display list or command.

For beginners, please always start from SampleApp project at first.

All the applications here depend on a set of common files under "common" folder. Each application has one subfolder "project" which contains the project file used to build it up from toolchain. For FT4222/MPSSE or Eve Emulator platform, the project file is for Microsoft Visual Studio 2019 IDE. For FT90X/FT930 platform, the project is for Eclipse IDE from Bridgetek.

Users are assumed to be familiar with the programming guide and data sheet of Eve Series chips.

Please note that some of the applications are developed for certain Eve Series chips or host platforms (see "Support platforms").

Requires the Pico toolchain https://github.com/ndabas/pico-setup-windows to be installed.

Pico-SDK version 1.3.0 is required

The following steps will build for Raspberry Pi Pico. Replace X:\source\eve_apps with your EveApps repository path.

Launch the Developer Command Prompt for VS

cd X:\source\EveApps
mkdir build
cd build
cmake -G "NMake Makefiles" -DEVE_APPS_PLATFORM=RP2040 -DEVE_APPS_GRAPHICS=[EVE graphics] ..
nmake [Project name]

# [EVE graphics] can be EVE or module name, such as BT817, BT815, VM800B35A_BK ...
# [Project name] is the folder name of a subfolder inside DemoApps or SampleApp
# example: nmake AudioPlayback

Display resolution is set via EVE_APPS_DISPLAY, example: cmake -G "NMake Makefiles" -DEVE_APPS_DISPLAY=WXGA By default, WVGA is set

EVE graphics is set via EVE_APPS_GRAPHICS, example: cmake -G "NMake Makefiles" -DEVE_APPS_GRAPHICS=BT815 By default, MULTI is set

Way 1: Open EveApps_Emulator.sln or EveApps_MSVC.sln, press F5 to build and run

Way 2: Use Cmake:

#Launch the Developer Command Prompt for VS
cd X:\source\EveApps
mkdir build
cd build
cmake -G "NMake Makefiles" -DEVE_APPS_PLATFORM=FT4222 -DEVE_APPS_GRAPHICS=[EVE graphics] ..
nmake [Project name]

# [EVE graphics] can be EVE or module name, such as BT817, BT815, VM800B35A_BK ...
# [Project name] is the folder name of a subfolder inside DemoApps or SampleApp
# example: nmake AudioPlayback

Way 1: Import FT9XX's project inside foler "FT9XX" of any project into FT9XX toolchain. Build and run using GUI.

Way 2: Use Cmake: Correct location of "FT9XX_TOOLCHAIN" inside EveApps/CMakelist.txt at first.

cd X:\source\EveApps
mkdir build
cd build
cmake -G "MinGW Makefiles" -DEVE_APPS_PLATFORM=[FT9XX module name] -DEVE_APPS_GRAPHICS=[EVE graphics] ..
nmake [Project name]

# [EVE graphics] can be EVE or module name, such as BT817, BT815, VM800B35A_BK ...
# [FT9XX module name] can be MM900EV3A, MM930LITE ... etc
# [Project name] is the folder name of a subfolder inside DemoApps or SampleApp
# example: nmake AudioPlayback

Brief overview of symbol naming styles used.

Functions and local variables inside functions are in camelCase, for example copyToBuffer.

Public variables inside structures, and other global variables, are in PascalCase, for example WriteIndex.

Global functions, and functions used across C files within the libray, are prefixed with the namespace in all-caps, and the filename, class or other identifying module in PascalCase, for example EVE_CoCmd_. A global function will end up as EVE_CoCmd_copyToBuffer, a global variable will end up as EVE_CoCmd_WriteIndex, this helps in disambiguating variable and function names. Global functions and variables that are globally applicable may simply be prefixed with EVE_, for example EVE_initialize.

Static functions (used within a single file) don't need a prefix, just the bare name. Static variables should have an s_ prefix for clarity, but should be avoided where possible.

Structure names are in PascalCase and preceeded by the EVE_ prefix, for example EVE_ConfigParameters.

Follows the same style as EVE Hal.

Application code generally omits any namespace prefix, since it's not necessary. Varies between apps.

Older code, preceeded by either a FT_ or Ft_ prefix, uses a mixture of PascalCase and Upper_Snake_Case.

📂 EveApps
    ├───common                  
    │   ├───application      | Application's common functions and fatfs library
    │   ├───eve_flash        | Blob binary for flash programming
    │   └───eve_hal          | Hardware abstraction layer to bridge different platforms
    │                        
    ├───DemoApps
    │    ├───CircleView      | Image viewer demo
    │    ├───EvChargePoint   | Electric charging station demo
    │    ├───FlashBitbang    | Reading flash content in low-level mode
    │    ├───Gauges          | Gauges demo
    │    ├───Gradient        | Color gradient demo
    │    ├───Graph           | Graph demo
    │    ├───HDPictureViewer | 4K image viewing demo
    │    ├───Imageviewer     | Image viewer demo
    │    ├───Imageviewer2    | Image viewer demo
    │    ├───Instrument      | Instrument demo
    │    ├───Jackpot         | Jackpot game demo
    │    ├───Keyboard        | Keyboard demo
    │    ├───Lift            | Lift demo
    │    ├───Lift2           | Lift with video background demo
    │    ├───Mainmenu        | Main menu demo
    │    ├───MediaPlayer     | Manage and play media content on hard disk/SD card
    │    ├───Metaballs       | Balls demo
    │    ├───Meter           | Meter demo 
    │    ├───Refrigerator    | Refrigerator demo
    │    ├───RotaryDial      | Rotary dial demo
    │    ├───RunningBar      | Street light moving demo 
    │    ├───Signals         | Wave signals demo
    │    ├───Signature       | Signature demo
    │    ├───Sketch          | Sketch demo
    │    ├───Unicode         | Unicode demo
    │    ├───UnicodeRuntime  | Unicode demo with runtime determined characters
    │    ├───WashingMachine  | Washing machine UI demo
    │    
    ├───SampleApp
    │    ├───Animation       | Sample usage of animation 
    │    ├───Bitmap          | Sample usage of bitmap 
    │    ├───Flash           | Sample usage of flash 
    │    ├───Font            | Sample usage of font 
    │    ├───Power           | Sample usage of power control
    │    ├───Primitives      | Sample usage of drawing primitives
    │    ├───Touch           | Sample usage of touch
    │    ├───Utility         | Sample usage of helper utilities
    │    ├───Video           | Sample usage of video playback
    │    ├───Widget          | Sample for default widgets
    │            
    ├───Tools/EveApps_Configure  | An .NET GUI tool to help user select hardware quicly

Note:

• For Eve registers and commands/instructions definition, user can find it at the file common/eve_hal/EVE_GpuDef.h and common/eve_hal/Eve_CoCmd.h.
• For Eve Emulator, it is for windows platform only and located at common/eve_hal/Bin/Simulation and common/eve_hal/Hdr
• For flash blob file used to access the eve connected flash chip, user can find it at common/eve_flash.

For SD card access, EveApps using FatFs library version R0.14a from http://elm-chan.org/fsw/ff/00index_e.html.

License: BSD (http://elm-chan.org/fsw/ff/doc/appnote.html#license)

FatFs library is locate at folder common/application/fatfs.

This version is v1.5.1-rc1

v1.5.1-rc1
  - Fix Cmake compile error
  - Fix issue: No sound when start Sound project
v1.5.0-rc1
  - Update FatFS library in common/application/fatfs to R0.14b
  - Add DemoApp.snl and SampleApp.snl to build all the demo projects and sampleApp project in one batch
  - Update4d Cmakelist.txt to build every project in one shot for FT90X/Win32/RP2040 platform 
  - Break the SampleApp into 11 smaller projects
v1.4.0-rc3:
    - Fix minor issue: DemoGauges's UI broken on LCD WXGA
v1.4.0-rc2
    - Fix QSPI connection issue of MM930LITE and MM817EV
    - Code clean up and minor bug fix     
v1.4.0-rc1
    - Add 28 demo application and 1 sample application
    - Add Pico RP2040 platform support
    - Trigger the system reset (at bootup) for some platform which has no Power Down pin toggled (such as GD3X)