espforge-devices

Create a no_std device wrapper in espforge_devices generic over the embedded-hal bus type, register it with a Cargo feature, then write a builder plugin in espforge_devices_builder that parses YAML config and generates initialization code. Finish with a YAML example and app.rs.

Define a Deserialize config struct using DeviceRef<ComponentRef> or DeviceRef<PinRef>, derive DevicePlugin with name, features, and config attributes, then implement validate_config, resolve_dependencies, and generate_code returning GeneratedCode via the codegen() helper.

Yes, espforge devices are built on embedded-hal v1 traits such as I2c and SpiDevice. The included check_crate.sh and findcrates.sh scripts query crates.io to verify a candidate crate depends on embedded-hal version 1.x before integration.

The runtime device crate espforge_devices is compiled no_std for ESP32, so std:: paths are forbidden. Replace them with core:: equivalents, or use alloc:: types like String and Vec after adding extern crate alloc.

quote! cannot interpolate struct field access like #ctx.instance_name directly. Bind the value to a local identifier first using format_ident!("{}", ctx.instance_name), then interpolate that identifier inside the quote! block.

If the upstream driver constructor accepts a DelayNs parameter, pass *delay in the builder init block since esp-hal Delay is Copy. If delay is only needed per read call, pass &mut delay from app code instead of storing it in the device.