Modular File System Platform

Why This Platform Is Strong

The design removes customer-specific #if/#else branches from application code. File system selection and parameters are configured via JSON; a generator script produces headers before build.

• Single API contract — Developers always use the same fs* functions
• Configuration-driven — Customer selects backend via activeFsName
• Tested units — New FS is developed and tested externally; added via config
• Hardware independence — read/prog/erase/sync callbacks injected from JSON via flashHwFunc

Quick Startup Flow

• #include "Midd_FS/fs_port.h"
• FS_HARDWARE_INIT(error)
• fsInit()
• fsOpenFile, fsReadFile, fsWriteFile

The application is isolated from backend changes. Customer and platform details are pushed into generated headers.

Include Chain Animation

A single include resolves automatically to customer-specific headers and the active FS port.

Generator Pipeline Animation

From JSON input to generated headers — the generator script pipeline.

System Flow Diagram

flowchart LR
  J[fs_config.json] --> G[generate_fs_port_config.py]
  G --> C[cus_fs_port_config.h]
  G --> F[FS_Port_Config.h]
  A[fs_port.h] --> F
  F --> C
  C --> H["fs_port_xx.h"]
  H --> I[FS_HARDWARE_INIT]
  I --> M[fsInit]
  M --> O["fs API"]

Benefits Summary