How m5stack/m5paper_factorytest works
Project type and purpose
• This is an embedded-firmware project (“M5Paper_FactoryTest”) written in C++/Arduino using PlatformIO.
• It targets the M5Paper e-paper hardware (an ESP32-based device with an e-ink display) and implements a factory-test GUI with multiple screens (“frames”).
File structure
• Top-level files:
• platformio.ini → build/deployment config for PlatformIO
• README.md → project description
• M5Paper_FactoryTest.ino → entry point for Arduino compatibility
• src/
• main.cpp → app entry, system initialization, main loop
• systeminit.* → hardware and peripheral setup (Wi-Fi, display, storage)
• global_setting.* → persistent settings (language, wallpaper, etc.)
• epdgui/ → GUI library: widgets (buttons, switches, textboxes), base classes
• frame/ → screen controllers: each frame_*.cpp/.h implements a test or UI screen
• resources/ → binary resources: fonts, images
• / and lib/ → third-party or shared libraries and headers
• Configuration: .travis.yml, .gitignore, .gitattributes for CI and VCS
README for additional insights
• Sparse README—no architecture drawn, but mentions “PlatformIO Project for M5Paper.”
• The filenames imply a widget/UI layer (epdgui) and a set of “frame” modules each representing a screen in the factory test suite.
Elements
– Clear labels: name each module (systeminit, epdgui, frame_factorytest, etc.)
Final advice
• Persistence: show connection to flash/SPIFFS for settings and resources.