Expand description
§MicroRTU SDK
Provides utilities to create wasm blocks for MicroRTU.
§Example
This is a basic example of a block that adds two numbers.
use micrortu_sdk::{BlockPorts, FactoryInput, Shared, StepResult, params, ports, register_block};
use static_cell::StaticCell;
pub struct Counter;
ports! {
#[block_names(counter)]
pub struct Ports {
count: TI13 InOut 1 1,
}
}
params! {
#[block_names(counter)]
pub struct Params {}
}
pub fn factory(_: &FactoryInput) -> Option<&'static mut Counter> {
static COUTNER: StaticCell<Counter> = StaticCell::new();
Some(COUTNER.init(Counter))
}
pub fn init(_: &mut Shared, _: &mut Counter) -> StepResult {
0
}
pub fn step(shared: &mut Shared, _: &mut Counter) -> StepResult {
let ports = Ports::parse(&mut shared.latched_ports[..]);
ports.count.value += 1.;
0
}
register_block!(Counter, counter, factory, init, step);§WASM Binary Layout for Non-Rust builds
If you don’t want to use Rust and micrortu_sdk macros, you can still create
a wasm block for MicroRTU. The binary layout of the wasm blob must be as follows:
To define block block_name, that can be later referenced in MicroRTU
configuration, you need export 3 functions from your final wasm blob.
§Required Exports
§init
init function with signature () -> ().
§SHARED
SHARED symbol, aligned to 8 bytes, and must be valid
for reads and writes for at least 512 bytes.
§COLLECTED_STRINGS
It should be &[u8], which is a pointer to the start and length of the slice.
It should point to all names of the ports and params, concatenated.
name_offset and name_len are relative to this slice.
§factory_{block_name}
factory_{block_name} is a function that will be called to produce a wasm block.
It’s signature should be (i32) -> i32 and code must ensure it follows Rust’s
semantics of that signagure:
for<'a> extern "C" fn(&'a FactoryInput) -> Option<&'static mut BlockName>;Where BlockName is your block’s type.
§init_{block_name}
init_{block_name} is a function that will be called before step. It’s
signature should be (i32, i32) -> i32 and code must ensure it follows Rust’s
semantics of that signagure:
for<'a> extern "C" fn(&'a mut Shared, &'a mut BlockName) -> StepResult;§step_{block_name}
step_{block_name} is a function that will be called to make a “step”. It’s
signature should be (i32, i32) -> i32 and code must ensure it follows Rust’s
semantics of that signature:
for<'a> extern "C" fn(&'a mut Shared, &'a mut BlockName) -> StepResult;§ports_{block_name} and params_{block_name}
There also must be exports for ports and params of type &[BindingDefinition],
which is [i32; 2] in memory - pointer to the start and length of the slice.
§Environment Variables
MICRORTU_BAIL_ON_DUPLICATES - if set, compiler will check for duplicate
port/param definitions, confs and blocks themselves. If not set, last definition
would be used.
Re-exports§
pub use bump_allocator::BumpAllocator;pub use ie_base;pub use ufmt;
Modules§
- bump_
allocator - log
- trap_
err - Helper trait for trapping errors in an iterator.
Macros§
- debug
- error
- finalize
- Macros for generating parser of arguments block requires.
Finalize the build process.
That macro must be called at the end to embed metadata into the binary.
It creates a link section “metadata” with json data of all registered blocks
and exported symbol
COLLECTED_STRINGSwith all strings from the build.BindingDefinition’sname_offsetandname_lenare referencingCOLLECTED_STRINGS. - info
- log
- params
- Macros for generating parser of arguments block requires.
- ports
- Macros for generating parser of arguments block requires.
- register_
block - Macros for generating parser of arguments block requires. Register block. That macro should be called for each block to register it.
- trace
- warn
Structs§
- Binding
Definition - A binding definition.
- Direction
- A direction of a binding.
Meaningful values are
IN,OUT,IN_OUT. All other values are invalid, but safe. - Factory
Input - Shared data between the wasm module and the host.
- IEBuf
- Native
Binding Definition - A
BindingDefinitionfor native (non-wasm) blocks. - Shared
- Shared data between the wasm module and the host.
Enums§
- Parse
Error - Erorrs that can occur while parsing genarated ports from
Shared, written byMicroRTU. Indicates misconfiguration ofMicroRTUor a bug inports!macro orMicroRTUfirmware.
Constants§
- BINDINGS_
BYTES_ CAP - IN
- Represents an input binding.
- IN_OUT
- Represents an input-output binding.
- OUT
- Represents an output binding.
- REQUIRED
Traits§
Functions§
Type Aliases§
- Step
Result - The result of a step.
0means success, anything else is an error. Implementation could also trap, but it’s not recommended. Any error would be logged.
Derive Macros§
- Config
- Macros for generating parser of arguments block requires.
Derive macro for
Configtrait. If block requires some configuration, it should be derived fromConfigtrait. It requires type to beAsBytesandFromBytes. Firmware will pass slice of bytes and you should be able to callfrom_bytesmethod on it to get the configuration. For C code you should be able to cast a pointer to your struct.