How arm-software/cmsis-driver works
Main Components
• CMSIS-Driver Core API: At the center of the architecture, visually emphasize that every driver implements the CMSIS-Driver API. This is your “contract” for the implementations.
• Driver Modules: Group the driver implementations by function. Create separate components for:
• Ethernet Drivers (MAC and PHY) – Represent each of the submodules (e.g., ETH_KSZ8851SNL, ETH_LAN91C111, ETH_LAN9220) and the PHY drivers (e.g., PHY_DP83848, PHY_KSZ8061RNB, etc.).
• Flash Drivers – List the different flash implementations (AM29x800BB, AT45DB641E, and so on).
• I2C – The I2C_MultiSlave driver which wraps underlying implementations.
• NAND – The NAND_MemBus driver.
• SPI – The SPI_MultiSlave driver.
• WiFi Drivers – Cover the various WiFi driver modules (DA16200, ISM43362, ESP32, ESP8266, WizFi360) along with their firmware handling.
• Shield Layers – Modules that are specific to Arduino Uno WiFi shield implementations (such as Inventek ISMART43362-E, Sparkfun DA16200, Sparkfun ESP8266, and WizNet WizFi360-EVB).
Relationships and Interactions
• If desired, show an outer "integration layer" where these drivers can be used by other application layers (or middleware) on an MCU. Though the pack is hardware abstraction, it might be useful to note that external software (or drivers in the CMSIS pack) will consume these modules.
Architectural Patterns & Design Principles
• Abstraction via the CMSIS-Driver API: Emphasize that these separate modules abstract the hardware routines.
• Reusability: The provision of “template files” and configuration directories (such as those in the Config folder) hint at a design which encourages reusability and easy adaptation for different MCU targets.
Relevant Technologies and Framework Details
• Configuration Files: Include a separate element representing configuration (e.g., the Config folder with I2C_MultiSlave_Config.h, NAND_MemBus_Config.h, and SPI_MultiSlave_Config.h). This indicates that drivers can be tailored per target hardware.
• Version Control/CI Aspects: Although they are peripheral to the architecture, you might include “CI/CD Workflows” (from the .github folder) as external support systems if a high-level overview is desired.