Skip to main content

LEON SPARC BSP for VxWorks 6.9: Port, Features, and Deployment

·704 words·4 mins
VxWorks Leon Sparc BSP RTOS Embedded Systems Aerospace Hal
Table of Contents

LEON SPARC BSP for VxWorks 6.9: Port, Features, and Deployment

For aerospace, defense, and other high-reliability domains, combining a radiation-tolerant processor architecture with a deterministic RTOS is a common requirement. A complete LEON SPARC port (HAL) and Board Support Package (BSP) for VxWorks 6.9.4.12 provides a production-ready foundation for such systems, enabling real-time workloads on flight-proven hardware.

This solution targets developers who need full control over low-level integration while maintaining the stability and tooling ecosystem of VxWorks.

🚀 Overview
#

The package delivers a full SPARC-based HAL and LEON BSP suite for VxWorks 6.9.4.12, covering both generic and board-specific configurations.

Key Characteristics
#

  • Full source code availability for HAL and BSP layers
  • Pre-integrated drivers for on-chip peripherals
  • Example projects for rapid bring-up
  • Support for both Linux and Windows host environments

Licensing Constraints
#

  • Requires a Wind River GPP 6.9 source license with VxWorks 6.9.4.12
  • Limited compatibility with PNE (basic build only)
  • Automotive and other variants are not supported

This setup ensures full feature availability within the standard GPP toolchain and ecosystem.

🧩 Architecture and Processor Coverage
#

The port is designed to span multiple generations of LEON processors, enabling reuse across legacy and modern designs.

Supported Architectures
#

  • LEON2
  • LEON3
  • LEON4

BSP Availability
#

  • Generic LEON BSP for early-stage bring-up
  • Dedicated BSPs for:
    • GR740
    • GR712RC
    • UT699
    • UT700
    • LEON4-N2X

This layered approach allows teams to start generic and progressively specialize for target hardware.

⚙️ Core Features
#

Architecture Capabilities
#

  • MMU and non-MMU configurations
  • SMP (Symmetric Multiprocessing) support
  • FPU and non-FPU system compatibility
  • GCC 4.9 toolchain integration

Peripheral Driver Support
#

  • Core I/O: UART, Timer, Interrupt Controller
  • Networking: LAN9C111 (10/100), GRETH (10/100/1000)
  • SpaceWire: GRSPW
  • CAN: OCCAN (non-DMA), GRCAN (DMA)
  • MIL-STD-1553: GR1553B (BC/RT/BM), B1553BRM (basic)
  • USB: GRUSBHC (1.1/2.0 Host)
  • I2C: I2CMST
  • PCI: GRPCI2, GRPCI, PCIF, AT697

Tooling and Validation
#

  • Workbench 3.3 integration
  • Scopetools support for tracing and performance analysis
  • VxTestV2 for validation
  • RAM and ROM image generation
  • Basic AMP support

These features cover the full development lifecycle from bring-up to validation.

🛠️ Deployment Workflow
#

A structured deployment process ensures predictable bring-up and integration.

1. Prerequisites
#

  • VxWorks 6.9.4.12 GPP source license
  • Host system: Linux or Windows (Windows 10 recommended)
  • Workbench 3.3 installed
  • GCC 4.9 cross-toolchain
  • Target hardware with JTAG/debug probe (e.g., GRMON-compatible)

2. Installation
#

  • Extract the package to a clean directory
  • Follow the provided installation manual
  • Integrate HAL and BSP into the VxWorks source tree
  • Configure environment variables or setup scripts
  • Build and verify using example projects

3. BSP Configuration
#

  • Begin with the generic LEON BSP
  • Transition to a board-specific BSP for production

Typical customization points:

  • Memory map and clock configuration
  • Peripheral enablement
  • Build-time feature flags:
    • INCLUDE_MMU
    • INCLUDE_SMP
    • INCLUDE_FPU
    • Driver-specific options (e.g., INCLUDE_GRETH, INCLUDE_GRSPW)

Low-level files such as config.h, sysLib.c, and romInit.s are central to board adaptation.

4. Image Build
#

Using Workbench or CLI:

make -C <bsp_dir> TOOL=gnu CPU=SPARC
  • Build RAM image (vxWorks) for development
  • Build ROM image (vxWorks_rom) for deployment
  • Configure SMP parameters for multicore targets

5. Target Deployment
#

Supported loading methods:

  • JTAG (RAM image): Fast iteration during development
  • Flash/ROM: Persistent standalone boot
  • Network boot (TFTP): Supported via Ethernet drivers

Example workflow using GRMON:

  1. Connect JTAG probe
  2. Load image: grmon -u -x -e vxWorks
  3. Execute: run
  4. Monitor output via UART console

6. Debugging and Validation
#

  • Source-level debugging via Workbench
  • Performance tracing with Scopetools
  • Functional validation using VxTestV2
  • Console monitoring via UART or network

This stage is critical for verifying timing, driver behavior, and system stability.

7. Production Readiness
#

  • Enable compiler optimizations
  • Strip debug symbols
  • Generate final ROM/flash images
  • Perform full integration testing
  • Validate under environmental constraints (e.g., radiation, thermal)

Source access enables custom driver development and hardware-specific tuning.

🎯 Target Use Cases
#

This solution is particularly suited for:

  • Satellite and spacecraft avionics
  • Launch vehicle control systems
  • Defense and mission-critical platforms
  • Radiation-hardened embedded systems

The combination of LEON SPARC and VxWorks provides deterministic performance under extreme conditions.

🔚 Conclusion
#

The LEON SPARC BSP for VxWorks 6.9.4.12 offers a mature and extensible platform for high-reliability embedded systems. With full architectural support, comprehensive drivers, and a clear deployment path, it significantly reduces integration effort while maintaining flexibility.

For teams operating in safety-critical and space-grade environments, this port provides a solid baseline to accelerate development without compromising system integrity.

Related

Running VxWorks 6.9 on Zynq-7000: BSP Setup and Boot Guide
·1338 words·7 mins
VxWorks Zynq-7000 ARM Embedded Systems BSP
VxWorks Platforms 3.8: Architecture, Features, and RTOS Capabilities
·754 words·4 mins
VxWorks RTOS Embedded Systems SMP AMP Wind River Real-Time OS Middleware Network Stack
Using Emacs With VxWorks
·631 words·3 mins
VxWorks Emacs