electricity -> behavior pipeline x Swift Embedded Docs

outline.yaml

Hardware Levels, the electricity -> behavior pipe line

- level: Raw Circuit
    - description: custom designed circuit that does one thing.
    - examples: 
      - bistable multi vibrator circuit to preserve toggle status, 
      - some Application Specific Integrated Circuit
    - example_tooling: 
        - software: KiCad 
    - swift embedded documentation covering level:
        - N/A
- level: Programmable Logic Devices
    - description: A step above designing truly custom silicon 
    - examples: A "field-programmable gate array", FPGA
    - example_tooling: 
      - languages: HDL, VHDL, VERILOG
      - software: Quartus, Lattice Radiant, etc. 
    - swift embedded documentation covering level:
        - N/A
- level: Chip Architecture
  - description: the design spec level, not an implementation frequently tooling is available that covers any chip that meets the spec generally. ARM and RISCV are manufacturer independent, but not all are. 
  - examples: ARM, RiscV, 
  - example_tooling: 
    - standard: ARM-CMSIS (Common Microcontroller Software Interface Standard (CMSIS))
    - toolchains: Arm GNU 
    - software: Arm Keil MDK v6
  - swift embedded documentation covering level:
        - No existing architecture driven libraries exist, but assorted examples show examples using different architectures.  
- level: Manufacturer chip implementations
  - description: Actually made processor chips. 
  - examples: 
    - of arm: SAMD21, RP2350, nRF54H20, STM
  - example_tooling:
    - manufacturer supplied IDE
    - open tool chain with manufacture supplied SDK that works with specific chip or chip family. Usually in C, but example code in assembly also provided. 
    - open tool chain with custom "bare metal" implementation ( requires ability to read a data sheet)
  - swift embedded documentation covering level:
    - No chip family driven libraries exist yet, but assorted examples show case working with a variety of processors. 
    - Some of the STM documentation gets close because examples are based on manufacturer dev boards. 
    - 
- level: Protoboards
  - description: buyable boards, vendor of those boards frequently also will supply libraries, SDKs, and other tooling to help make them better.
  - examples: insert some Adafruit, insert some spark fun, some arduino, raspberry pi pico, the actual STM devboard
  - example tooling:
  - swift embedded documentation covering level:
- level: Multi-Board Environments
  - description: Ecosystems that are inclusve of boards from various manufacturers, with different chip sets etc. 
  - examples: Ardunio, Zephyr, Circuit Python
  - example tooling:
  - swift embedded documentation covering level: