Spectrolab's High-Efficiency Solar Cells and CICs

Advancing Space Missions with Spectrolab's High-Efficiency Solar Cells and CICs

As space exploration pushes the boundaries of human achievement, the need for reliable, high-performance solar power solutions is paramount. Spectrolab, a leader in the field of photovoltaic technology, offers a range of GaInP/GaAs/Ge lattice-matched triple-junction (3J) solar cells. These cells are not only designed to meet but exceed the rigorous demands of various space missions, from Low Earth Orbit (LEO) to deep space missions. Below, we explore the advanced technical features and performance metrics of Spectrolab’s solar cells and Cell-Interconnect-Coverglass (CIC) assemblies.

Overview of Spectrolab’s Solar Cell Technologies

Spectrolab’s portfolio includes a variety of solar cells tailored for specific mission profiles, each offering distinct benefits in terms of efficiency, radiation tolerance, and thermal management.

XTE Family of Cells: Pioneering Efficiency and Durability

XTE-SF (Standard Fluence)

Efficiency: The XTE-SF solar cell offers an impressive BOL efficiency of 32.2%, maintaining 27.9% EOL efficiency after significant radiation exposure. [View Datasheet]
Thermal Characteristics: It operates approximately 2°C cooler than other space-grade solar cells, reducing thermal stress and extending operational life.
Applications: Suitable for both LEO and GEO missions, these cells are available in multiple sizes up to 85 cm².

XTE-HF (High Fluence)

Efficiency: The XTE-HF cell provides a BOL efficiency of 32.1%, retaining 23.7% efficiency after exposure to high radiation levels. [View Datasheet]
Radiation Tolerance: Designed for missions with high radiation exposure, such as MEO missions.
Size Options: Available in a range of sizes to fit different satellite power system designs.

XTE-LILT (Low Intensity Low Temperature)

Efficiency: This cell excels under low light and low-temperature conditions, with 31.6% BOL efficiency at 1 AU and 37% at 5.5 AU. [View Datasheet]
Low-Temperature Operation: Ideal for deep space missions, particularly those beyond Mars.
Mission Suitability: Optimized for regions with reduced solar intensity and extreme cold.

XTJ Prime and Legacy Cells: Proven Space Performance

XTJ Prime

Efficiency: The XTJ Prime series offers a BOL efficiency of 30.7% and retains 26.7% efficiency at EOL after significant radiation exposure. [View Datasheet]
Structural Integrity: Features the heritage upright lattice-matched triple junction structure, known for its robustness in space environments.
Temperature Coefficients: Engineered to operate cooler than other space-grade solar cells, reducing thermal degradation.

UTJ and XTJ Legacy Cells

UTJ Cells: Delivering up to 28.3% efficiency, these cells are known for their radiation tolerance and are available in various sizes. [View UTJ Datasheet]
XTJ Cells: The XTJ cells offer a BOL efficiency of up to 29.5% and are available in CIC assemblies, simplifying satellite integration. [View XTJ Datasheet]

Spectrolab’s CIC Assemblies: Seamless Integration for Space Missions

Spectrolab’s CIC assemblies are meticulously designed to facilitate the integration of solar cells into satellite systems, offering enhanced reliability and performance.

Key Features

Space-Qualified Coverglass: Coverglass options range from 3 mils to 30 mils in thickness, with various coatings available.
Bypass Diodes and Interconnects: These assemblies include discrete Si bypass diodes and welded interconnects for robust electrical connections.
Customizable Configurations: Available in multiple configurations, from bare cells to fully integrated assemblies on solar panels. [View Datasheet]

Conclusion

Spectrolab continues to set the standard in space solar power solutions with its innovative range of high-efficiency solar cells and CIC assemblies. Whether your mission is in LEO, GEO, or deep space, Spectrolab offers products that provide unparalleled efficiency, durability, and reliability. As the demands of space exploration evolve, Spectrolab remains at the forefront, ready to support the next generation of space missions with its advanced photovoltaic technology.

For more information on Spectrolab’s products, visit Spectrolab's website.

OreSat public repositories and batch clone

OreSat Repositories

oresat-c3-hardware: Repository for the hardware design of OreSat's C3 subsystem.
oresat-c3-software: Software repository for OreSat's C3 subsystem.
oresat-configs: Configuration files and settings for the OreSat project.
oresat-olaf: Repository for the OLAF subsystem used in OreSat.
oresat-firmware: Firmware repository for various OreSat components.
oresat-adcs-software: Software related to Attitude Determination and Control System (ADCS) for OreSat.
oresat-linux: Repository for managing Linux distributions and configurations used in OreSat.
oresat-helmholtz: Helmholtz coil simulation and design repository for OreSat.
oresat-solar-simulator-hardware: Hardware design for the solar simulator in OreSat.
oresat-simulator: Simulation environment and tools for testing OreSat components.
oresat-ax5043-driver: Driver code for the AX5043 RF transceiver used in OreSat.
oresat-live-handheld-ground-station: Code and designs for a handheld ground station for OreSat's live operations.
oresat-kicad: KiCad design files for various OreSat components.
oresat-c3-watchdog: Watchdog timer code for OreSat's C3 subsystem.
oresat-flatsat: Repository for the flat-sat testing platform for OreSat.
oresat-vpn: VPN configurations and management for secure OreSat communications.
oresat-battery-testing: Battery testing procedures and data for OreSat.
oresat-solar-simulator-software: Software for the solar simulator used in OreSat testing.
oresat-cfc-software: Software repository for the CFC (Control Flight Computer) in OreSat.
oresat-star-tracker-software: Software related to the star tracker system for OreSat.
oresat-prucam-ar013x: Driver and interface code for the AR013X camera in OreSat's PRUCAM system.
oresat-gps-software: GPS software and utilities for OreSat.
oresat-gps-hardware: Hardware design for the GPS subsystem in OreSat.
oresat-diode-test-card: Test card designs for diodes used in OreSat.
oresat-dxwifi-software: Software for the DXWiFi communication module in OreSat.
oresat-adcs-hardware: Hardware repository for the ADCS (Attitude Determination and Control System) in OreSat.
oresat-prucam-pirt1280: Interface and driver code for the PIRT1280 camera in OreSat's PRUCAM system.
oresat-endcaps: Design files for the endcaps used in the OreSat structure.
oresat-end-cards: End card design and documentation for OreSat.
libbpe: A utility library for binary protocol encoding used in OreSat.
oresat-c3-hardware: Duplicate entry for the hardware design of OreSat's C3 subsystem.
COTS-Star-Tracker: Repository for a commercial off-the-shelf star tracker system used in OreSat.
CANopen-monitor: CANopen protocol monitoring tools for OreSat.
oresat-proto-card: Prototype card designs for testing OreSat components.
getting-started: Guides and documentation for getting started with OreSat development.
oresat-zephyr: Zephyr RTOS configuration and code for OreSat.
oresat-cfc-hardware: Hardware design files for the Control Flight Computer (CFC) in OreSat.
oresat-lost: Code and utilities for tracking and recovering lost OreSat modules.
oresat-software-docs: Documentation for various software components of OreSat.
oresat-batteries: Battery design and testing for OreSat.
oresat-tpane: T-Pane hardware and software designs for OreSat.
oresat-live-software: Software for live operations and telemetry of OreSat.
oresat-libdxwifi: A library for managing DXWiFi communications in OreSat.
oresat-pi-gen: Raspberry Pi generation tools and configurations for OreSat.
oresat-thermal: Thermal design and management for OreSat components.
oresat-backplane: Backplane design and integration for OreSat systems.
eds-utils: Utilities for embedded development and simulation in OreSat.
oresat-structure: Structural design files and documentation for OreSat.
oresat-linux-manager: Tools for managing Linux distributions on OreSat modules.
oresat-linux-updater: Automated update tools for Linux systems in OreSat.
oresat-testing: Testing scripts and utilities for OreSat hardware and software.
oresat-decoders: Decoders for various data formats used in OreSat telemetry.
OpenCCSDS: Open source implementation of the CCSDS protocol for OreSat.
oresat-flatsat-landing-pages: Landing pages and documentation for OreSat's flat-sat configuration.
oresat-c3-rf: RF subsystem design and software for OreSat's C3 module.
oresat-eagle-libraries: Eagle CAD libraries for use in OreSat PCB design.
u-boot: U-Boot bootloader configuration for OreSat's embedded systems.
jekyll-includes: Jekyll includes and templates for OreSat's documentation website.
oresat-firmware-deprecated: Deprecated firmware files and archives for OreSat.
field-of-view: Field of view simulations and calculations for OreSat's sensors.
low-gain-radio: Low-gain radio communication designs for OreSat.
system-controller: System controller code and interfaces for OreSat.
toolchain: Toolchain and development tools for OreSat's software development.
stm32f411xx-rs: Rust support for STM32F411 microcontrollers used in OreSat.
stm32f446xx-rs: Rust support for STM32F446 microcontrollers used in OreSat.
syscon-rs: Rust-based system controller code for OreSat.
devsat: Development satellite platform and tools for OreSat.
mini-oresat: Design files and code for a miniaturized version of OreSat.
semtech-dev-board: Development board designs and drivers for Semtech components in OreSat.
oresat-fec-library: Forward error correction library used in OreSat communications.
2017-2018-deployable-antenna-capstone: Capstone project for deployable antenna designs in OreSat.
oresat-live-mini-oresat: Live telemetry and control software for the mini-OreSat module.
oresat-acs-firmware: Firmware for the Attitude Control System (ACS) in OreSat.
oresat-imu: Inertial Measurement Unit (IMU) integration and software for OreSat.
jekyll-layouts: Jekyll layout files for OreSat's documentation site.
reaction-wheels: Design and control software for reaction wheels in OreSat.
oresat-magnetorquer: Magnetorquer design and control software for OreSat's attitude control.
oresat-design: General design files and documentation for the OreSat project.
oresat-paws: Software and hardware design for OreSat's PAWS subsystem.
oresat-antenna: Antenna design and testing for OreSat's communication systems.
project-optimization: Optimization tools and methods for OreSat project development.
oresat-star-tracker-hardware: Hardware design for the star tracker system in OreSat.

Clone All Repositories

for repo in \
    oresat/oresat-c3-hardware \
    oresat/oresat-c3-software \
    oresat/oresat-configs \
    oresat/oresat-olaf \
    oresat/oresat-firmware \
    oresat/oresat-adcs-software \
    oresat/oresat-linux \
    oresat/oresat-helmholtz \
    oresat/oresat-solar-simulator-hardware \
    oresat/oresat-simulator \
    oresat/oresat-ax5043-driver \
    oresat/oresat-live-handheld-ground-station \
    oresat/oresat-kicad \
    oresat/oresat-c3-watchdog \
    oresat/oresat-flatsat \
    oresat/oresat-vpn \
    oresat/oresat-battery-testing \
    oresat/oresat-solar-simulator-software \
    oresat/oresat-cfc-software \
    oresat/oresat-star-tracker-software \
    oresat/oresat-prucam-ar013x \
    oresat/oresat-gps-software \
    oresat/oresat-gps-hardware \
    oresat/oresat-diode-test-card \
    oresat/oresat-dxwifi-software \
    oresat/oresat-adcs-hardware \
    oresat/oresat-prucam-pirt1280 \
    oresat/oresat-endcaps \
    oresat/oresat-end-cards \
    oresat/libbpe \
    oresat/COTS-Star-Tracker \
    oresat/CANopen-monitor \
    oresat/oresat-proto-card \
    oresat/getting-started \
    oresat/oresat-zephyr \
    oresat/oresat-cfc-hardware \
    oresat/oresat-lost \
    oresat/oresat-software-docs \
    oresat/oresat-batteries \
    oresat/oresat-tpane \
    oresat/oresat-live-software \
    oresat/oresat-libdxwifi \
    oresat/oresat-pi-gen \
    oresat/oresat-thermal \
    oresat/oresat-backplane \
    oresat/eds-utils \
    oresat/oresat-structure \
    oresat/oresat-linux-manager \
    oresat/oresat-linux-updater \
    oresat/oresat-testing \
    oresat/oresat-decoders \
    oresat/OpenCCSDS \
    oresat/oresat-flatsat-landing-pages \
    oresat/oresat-c3-rf \
    oresat/oresat-eagle-libraries \
    oresat/u-boot \
    oresat/jekyll-includes \
    oresat/oresat-firmware-deprecated \
    oresat/field-of-view \
    oresat/low-gain-radio \
    oresat/system-controller \
    oresat/toolchain \
    oresat/stm32f411xx-rs \
    oresat/stm32f446xx-rs \
    oresat/syscon-rs \
    oresat/devsat \
    oresat/mini-oresat \
    oresat/semtech-dev-board \
    oresat/oresat-fec-library \
    oresat/2017-2018-deployable-antenna-capstone \
    oresat/oresat-live-mini-oresat \
    oresat/oresat-acs-firmware \
    oresat/oresat-imu \
    oresat/jekyll-layouts \
    oresat/reaction-wheels \
    oresat/oresat-magnetorquer \
    oresat/oresat-design \
    oresat/oresat-paws \
    oresat/oresat-antenna \
    oresat/project-optimization \
    oresat/oresat-star-tracker-hardware; do git clone https://github.com/$repo; done

Installing and Setting Up ChibiOS

ChibiOS is a compact, fast, and reliable real-time operating system (RTOS) designed for embedded systems. It is particularly well-suited for microcontrollers, including those based on ARM Cortex-M architectures such as the Cortex-M0. This guide will walk you through the steps to install and set up ChibiOS for development.

Step 1: Download ChibiOS

To get started, you need to download the ChibiOS source code. You can download it from the ChibiOS official website or the ChibiOS GitHub repository. You can either clone the repository using Git or download the source as a ZIP file.

        git clone https://github.com/ChibiOS/ChibiOS.git

Step 2: Set Up the Development Environment

To develop with ChibiOS, you need to set up a suitable development environment. Here's how to do it:

1. Install a Toolchain

If you are targeting Cortex-M0, you will need an ARM GCC toolchain. You can download it from ARM’s official website or use the package manager for your OS.

For example, on Ubuntu, you can install it using:

        sudo apt-get install gcc-arm-none-eabi

Alternatively, you can use other IDEs like Keil uVision, IAR Embedded Workbench, or STM32CubeIDE, which come with built-in support for ARM microcontrollers.

2. Install Make (if using command line)

On Linux and macOS, make is usually pre-installed. On Windows, you can install make through tools like MinGW or use a shell environment like Git Bash or Cygwin.

Step 3: Configure ChibiOS for Your Microcontroller

Next, you need to configure ChibiOS to work with your specific microcontroller.

1. Select a Board Support Package (BSP)

ChibiOS includes BSPs for many development boards and microcontrollers. Navigate to the os/hal/boards directory in the ChibiOS source code to find a suitable BSP.

If your board or microcontroller is not directly supported, you may need to create a custom BSP by modifying existing ones.

2. Configure ChibiOS

Modify the configuration files (chconf.h, halconf.h, mcuconf.h) according to your microcontroller and application requirements. These files are usually found in the os/rt/ and os/hal/ directories.

Step 4: Build a Sample Project

ChibiOS includes several demo projects that you can use as a starting point.

1. Navigate to a Demo Project

Navigate to the directory of a demo project that matches your microcontroller.

        cd ChibiOS/demos/ARMCM0-STM32F0xx-NUCLEO-F030R8

2. Build the Project

Use the provided Makefile to build the project.

        make

This command compiles the ChibiOS kernel, the HAL, and the application code into a binary file that you can flash onto your microcontroller.

Step 5: Flash the Binary to Your Microcontroller

Once you have built the project, the next step is to flash the binary onto your microcontroller.

1. Connect Your Programmer/Debugger

Connect your development board to your computer using a programmer/debugger like ST-Link, J-Link, or CMSIS-DAP.

2. Flash the Binary

Use the programmer’s software or a command-line tool like st-flash for ST-Link or JLinkExe for J-Link to flash the compiled binary onto your microcontroller.

        st-flash write build/ch.bin 0x08000000

Adjust the command based on your toolchain and microcontroller’s memory address.

Step 6: Debug and Test

Use your IDE or debugging tools to debug the application, monitor the real-time behavior of the RTOS, and ensure everything works as expected.

By following these steps, you should have ChibiOS installed, configured, and running on your Cortex-M0 microcontroller.

STAR-DUNDEEE Installation

To install and set up a STAR-Dundee SpaceWire interface on a Linux system, you need to follow several steps, including obtaining the necessary software and drivers, installing the hardware, and configuring the system. Here is a general guide to help you through the process:

1. Obtain the Necessary Software and Drivers

Visit STAR-Dundee's Website:
- Go to the STAR-Dundee website and navigate to the Downloads section.
- Download the appropriate drivers and software for your specific SpaceWire interface and operating system.
Register or Contact Support:
- You might need to register or contact STAR-Dundee support to get access to certain downloads.

2. Install the Hardware

Connect the Hardware:
- Connect your STAR-Dundee SpaceWire interface to your computer using the provided cables.
- Ensure the hardware is properly seated and securely connected.

3. Install the Drivers

Extract the Downloaded Package:
- Extract the contents of the downloaded driver package to a known location.
Install Required Dependencies:
- You may need to install additional dependencies. Use your package manager to install the necessary packages. For example, on Debian-based systems:
```
sudo apt-get update
sudo apt-get install build-essential linux-headers-$(uname -r)
```
Build and Install the Driver:
- Navigate to the extracted driver directory and follow the installation instructions provided in the README or INSTALL file. Typically, this involves running make and make install commands:
```
cd /path/to/extracted/driver
make
sudo make install
```
Load the Driver:
- Load the driver module using modprobe or insmod:
```
sudo modprobe star-spacewire
```

4. Verify the Installation

Check Device Nodes:
- Verify that the device nodes are created, typically under /dev/. For example:
```
ls /dev/star-spacewire*
```
Check Kernel Logs:
- Check the kernel logs to ensure the driver is loaded correctly:
```
dmesg | grep spacewire
```

5. Configure and Test

Run Example Applications:
- STAR-Dundee often provides example applications or tests to verify the installation. Run these applications to ensure your setup is working correctly.
Write Your Application:
- Once verified, you can start writing your applications using the STAR-Dundee API. Refer to the documentation and example code provided in the downloaded package.

Example Code to Communicate Using SpaceWire

Here’s an example in Python that assumes you have the necessary Python bindings for the STAR-Dundee SpaceWire API:


import star_dundee

def initialize_spacewire(port):
    # Initialize SpaceWire interface
    interface = star_dundee.SpaceWireInterface(port)
    interface.open()
    return interface

def send_data(interface, data):
    # Send data over SpaceWire
    interface.write(data)
    print(f"Data sent: {data}")

def receive_data(interface, length):
    # Receive data over SpaceWire
    data = interface.read(length)
    print(f"Data received: {data}")
    return data

def main():
    port = "/dev/star-spacewire0"  # Example port
    data_to_send = b"Hello, SpaceWire!"
    
    # Initialize SpaceWire interface
    interface = initialize_spacewire(port)
    
    try:
        # Send data
        send_data(interface, data_to_send)
        
        # Receive data (assuming the same length for simplicity)
        received_data = receive_data(interface, len(data_to_send))
        
    finally:
        # Close the SpaceWire interface
        interface.close()

if __name__ == "__main__":
    main()

Real-Time OS/Frameworks for High-Reliability Applications

RTEMS (Real-Time Executive for Multiprocessor Systems)

Description: A free real-time operating system (RTOS) for embedded systems.

Use Cases: Aerospace, military, industrial control systems, and other high-reliability applications.

NASA Core Flight System (cFS)

Description: A portable, platform-independent framework for developing flight software applications.

Use Cases: NASA spacecraft and missions, supporting modularity and reusability in software development.

VxWorks

Description: A real-time operating system developed by Wind River Systems.

Use Cases: Aerospace, defence, automotive, medical devices, and industrial equipment for real-time performance and reliability.

FreeRTOS

Description: An open-source real-time operating system kernel for embedded devices.

Use Cases: Widely used in various industries, including aerospace, for implementing real-time applications on microcontrollers.

TTEthernet (Time-Triggered Ethernet)

Description: An extension of standard Ethernet designed to provide deterministic and fault-tolerant communication.

Use Cases: Aerospace, automotive, and industrial applications requiring high reliability and precise timing.

Implementing SpaceWire in a Real-Time Linux Environment

SpaceWire is a high-speed communication network designed for real-time data handling and communication between spacecraft subsystems. Implementing SpaceWire in a Real-Time Linux environment involves specific options and considerations to ensure optimal performance and reliability.

1. SpaceWire Interface Cards

STAR-Dundee

STAR-Dundee offers a range of SpaceWire interface cards compatible with Linux, including real-time Linux. Their drivers and APIs support various real-time operations, making them a popular choice for aerospace applications.

4Links

4Links provides SpaceWire interfaces that can be integrated with Linux systems. They offer support for real-time applications through custom drivers, ensuring that your SpaceWire communication remains reliable and efficient.

2. Real-Time Linux Distributions

PREEMPT_RT Patch

The PREEMPT_RT patch can be applied to your Linux kernel to achieve real-time capabilities. This patch enhances the kernel's preemption capabilities, making it suitable for real-time applications, including SpaceWire.

Xenomai

Xenomai is a real-time development framework that works with the Linux kernel to provide a real-time interface. It can be used with SpaceWire to achieve deterministic behavior, essential for real-time data handling in space applications.

3. Drivers and Libraries

Open Source Drivers

Some open-source drivers are available for SpaceWire devices. These drivers may need modifications to ensure real-time performance with PREEMPT_RT or Xenomai.

Vendor-Specific Drivers

Utilize drivers provided by SpaceWire hardware vendors. These drivers are typically optimized for the hardware and may include real-time support or require minimal modification.

4. Protocol Stacks and Middleware

RMAP (Remote Memory Access Protocol)

Middleware and protocol stacks for RMAP can be integrated into a real-time Linux system to handle SpaceWire communication more effectively.

CCSDS (Consultative Committee for Space Data Systems)

Protocol stacks compliant with CCSDS can manage real-time SpaceWire data, ensuring reliable communication and data integrity.

5. Development Tools

SpaceWire Routers and Switches

Devices like routers and switches from vendors like STAR-Dundee can facilitate the management of multiple SpaceWire nodes in real-time applications.

SpaceWire Test and Development Kits

Vendors often include tools for testing and developing SpaceWire systems in real-time environments. These kits are essential for validating the performance and reliability of your SpaceWire setup.

6. Configuration and Optimization

CPU Affinity and Isolation

Configure CPU affinity and isolate CPUs for real-time tasks to ensure that SpaceWire processing is not interrupted by non-real-time tasks.

Kernel Tuning

Tune kernel parameters for real-time performance, such as scheduling policies and interrupt handling, to optimize your system for SpaceWire communication.

Example Setup

To set up a SpaceWire system in a Real-Time Linux environment, you can follow these steps:

Install Real-Time Linux Kernel: Patch and compile the Linux kernel with PREEMPT_RT. Learn how to apply the PREEMPT_RT patch.
Install SpaceWire Interface: Connect and install the drivers for your SpaceWire interface card (e.g., STAR-Dundee).
Configure Real-Time Settings: Adjust real-time settings, such as CPU isolation and priority scheduling.
Develop/Integrate SpaceWire Application: Write or integrate your application using the provided API and libraries to handle SpaceWire communication.
Test and Validate: Use development kits and tools to test the real-time performance and ensure that the SpaceWire communication meets the required timing constraints.

By leveraging these options and tools, you can effectively implement and manage SpaceWire communication in a Real-Time Linux environment.

For more detailed information on each step and additional resources, visit the following links:

Feel free to reach out if you have any questions or need further assistance with your SpaceWire implementation!

Basic Cubesat components

Example Integration of a CubeSat with GNSS capabilities

An example integration of these building blocks could look like this:

Structure and Deployment: A 1U, 2U, or 3U CubeSat frame with deployable solar panels and antennas.
Power: Solar panels connected to a power distribution unit that charges the battery pack.
Command & Data Handling: A central command and control unit managing the CubeSat’s operations and interfacing with the GNSS receiver.
Communication: A transceiver connected to a deployable antenna for ground communication.
GNSS: A GNSS receiver module connected to a GNSS antenna mounted on the CubeSat frame.
ADCS: Sensors and actuators integrated with the OBC for attitude determination and control.
Thermal Control: Coatings and heaters ensure components stay within operational temperatures.
Software: Embedded flight software on the OBC handling mission operations and GNSS data processing.
Payload: GNSS receiver providing real-time position and timing data for navigation and experiments.

Top View:

Side View:

Command & Data Handling

Command and data handling should be selected to comply with the form factor expected.

For example, a 1U form factor CubeSat is a small satellite with dimensions of 10 cm x 10 cm x 10 cm and a mass of up to 1.33 kg. It's the basic building block of the CubeSat standard, and its small size and standardized form make it popular for educational, research, and technology demonstration missions. Here's a breakdown of the key components and subsystems for a 1U CubeSat, especially one incorporating GNSS capabilities.

The other factor is the computation power and the power rating. It is a tradeoff between speed and power usage. FPGAs are usually a good choice, especially when equipped with a System on Chip (SoC).

RTEMS

We want to install RTEMS on our Linux LXDE Desktop (kernel 4.5) that has kernel Ubuntu 16.04.1 LTS.

it was needed to install curl.