Nexus platform documentation¶
Complete one task using the current reusable C11 platform. Product applications, scheduling policy, private PCB data and recovery policy belong in external consumer repositories. Source documentation, executed software evidence and physical board qualification remain separate.
The current implementation uses generated typed factories and immutable C interface faces. Factory lookup returns an existing static object; ordinary I/O goes directly through its operations table. Startup does not start a scheduler.
- Tutorials
- Task guides
- Obtain the exact source and pinned dependencies
- Configure a product and make I/O progress
- Add a reviewed Board package
- Add a SoC, provider or reusable component
- Wait correctly and shut down an explicit owner
- Migrate legacy configuration and interface access
- Measure resources and prepare hardware acceptance
- Reference
- Architecture explanations
- How the platform is assembled and executed
- Typed factory, static instances and polymorphic faces
- Borrow, completion and observer lifetime
- RTC and LPTIM: separate time domains and retained requests
- GPIO pin states: explicit images under one retained lease
- Source-adjacent contracts
- Core contracts
- CPU-local primitives
- Typed I/O contracts and shared mechanisms
- Optional OS adapters
- Optional common components
- SoC packages and private providers
- Reusable IP implementations
- Reviewed Board facts
- Status and evidence
- Support scope and platform selection
- Nexus 0.1.0 Source SDK developer preview
- Software verification, source identity and evidence
- Documentation-system implementation and formal acceptance
- HIL and physical-board status
- Original ledgers, exit conditions and derived views
- Iteration directions and admission conditions
- Maintaining Nexus
- Maintained design contracts
- Current design and execution ledgers
- Finite ADC sequences with explicit integer frames
- CPU, atomics and runtime assembly contracts
- Build system maintenance contract
- CAN FD with fixed physical RAM and explicit request ownership
- Classic CAN mechanisms and integration boundaries
- Explicit clock leases and shallow sleep
- Developer experience and provider iteration
- Nexus complete documentation-system improvement checklist
- Nexus documentation content and diagram standards
- Nexus documentation-system architecture and delivery plan
- Nexus documentation page templates
- Next-generation platform engineering handbook
- Raw Ethernet MAC, MDIO and DP83848
- Ethernet frame loans and the MAC hardware clock
- Finite I2S2 slave TX on STM32F407
- Fault observation and retained responsibility
- H743 Flash maintenance from a private RAM execution pod
- H743 V-only high-clock profile
- Explicit I2C bus recovery
- Bounded I3C controller core
- Integration, resource assembly and source-SDK contract
- I/O evolution: static resources and explicit data contracts
- Mapped storage, AMP, image handoff, RTC and frame boundaries
- Bounded I/O lifecycle property matrix
- I/O observations, capacity and retained recovery
- Mainstream MCU adaptation and feedback
- Multiple controller ownership
- Independent finite UART and SPI DMA controllers
- Nexus next-generation platform: design from first principles
- Official drivers and provider iteration
- OS backend integration
- OS execution and lifecycle contract
- Selected provider assembly gate
- Finite PWM and ADC windows with one hardware owner
- Exact selected-mode HIL preparation
- SoC execution budgets
- SoC refinement and physical acceptance
- Source versions, factory generations and dependency maintenance
- Stack observations and owner lifecycle endurance
- STM32G474RET6 / MB1367 selected peripheral platform
- ThreadX configuration and integration
- Reviewed shallow tickless timebase
- Optional timer capture and complementary PWM
- U575 single-tuple LPTIM1 LPBAM across Stop2
- U575 MPU-v2 scalar GPIO WRITE authority
- U575 retained elapsed-time domain
- U575 finite SRAM4 copy across Stop2
- U575 dual-world GPIO reference contract
- Finite USART1 GPDMA TX on STM32U575
- UART receive DMA, duplex DMA and electrical adaptation
- Bounded UART hardware FIFO bytes
- USB FS device packet ownership and integration boundaries
- Kernel-invoked user I/O admission
- Recorded delivery evidence
- Current platform delivery
- Current system architecture
- Build system execution record
- Derived capabilities and integration matrix
- Cortex-M software support and platform-integration boundaries
- Selected I/O and clock extension delivery
- External-project migration
- Next iterations and team execution
- OS delivery scope and verification
- Software candidates and physical qualification
- Security scanning and lifecycle boundaries
- SoC extension verification
- SoC refinement execution record
- Exact support scope
- Current evidence and acceptance boundaries