Expand description
Startup routine and behavior in vexide.
-
User code begins at an assembly routine called
_boot, which sets up the stack section before jumping to a user-provided_startsymbol, which should be your rust entrypoint. -
From there, the Rust entrypoint may call the
startupfunction to finish the startup process by clearing the.bsssection (intended for uninitialized data) and initializing vexide’s heap allocator.
This crate is NOT a crt0 implementation. No global constructors are called.
Modules§
- banner
- vexide startup banner.
Structs§
- Code
Signature - Program Code Signature
- Program
Flags - Program Flags
Enums§
- Program
Owner - The owner (originator) of the user program
- Program
Type - Identifies the type of binary to VEXos.
Functions§
- startup⚠
- Startup Routine