Device Emulator
Emulate device profiles before hardware exists.
Overview
What Device Emulator is
Research into executing builds against a defined device profile, so behaviour on a target is observable long before that hardware exists.
Architecture position
Where this sits in the stack.
Portable and vendor-independent by construction: standard interfaces and open targets, so software moves across the ecosystem rather than binding to one platform.
RVStack architecture, 7 layers from top to bottom: 01 Application, 02 Development toolchain, 03 Portable runtime, 04 Operating layer, 05 RISC-V architecture, 06 Device profile, 07 Deployment target.
- ApplicationGames, tools and software targeting the Aevornix platform..aev project format
- Development toolchainCompiler, linker, debugger, SDK and build systems.ELFDWARF
- Portable runtimeExecution services shared across supported RISC-V targets.
- Operating layerSystem services, permissions, storage, networking and application lifecycle.POSIX-style system interfaces
- RISC-V architecturefoundationThe open instruction-set foundation beneath the software stack.RV64GCRVA23
- Device profileDefined hardware capabilities used for emulation and compatibility testing.
- Deployment targetPhysical devices, virtual environments, cloud targets and certified platforms.linux-riscv64
What a profile has to describe
- Instruction-set extensions
- Memory budget
- Graphics capability
- Input devices and schemes
- Storage allowance
- Performance envelope
Development
Where the work stands.
Objectives and dependencies. Dates appear only where a specific verifiable event backs them.
Active(1)
Device emulator
PrototypeExecute builds against a defined device profile so target behaviour is observable before hardware exists.
- Depends on
- Device profile definitions