Bring up an LX2160

Where this stands

SpaceOS does not run on the LX2160A today. No target profile ships for it, and the platform source lists the board under “Not currently supported” in its support matrix (docs/support-matrix.md).

The board was demonstrated under the OSIP T1 programme at the minimal integration level. That is programme history, and the code does not carry it: LX2160, Layerscape and DPAA2 name nothing in the platform source, and no shipped profile declares a packet-processing accelerator.

The vendor build and flash steps below are NXP’s and they work. The SpaceOS half does not exist, so this page stops where Linux boots.

The NXP LX2160A (Layerscape family) is a 16-core ARM Cortex-A72 system-on-chip with built-in packet-processing accelerators (DPAA2, NXP’s Data Path Acceleration Architecture). Those accelerators suit high-throughput CCSDS framing on the bus interface. It is intended as a daemon install in the target matrix, with the vendor board support package keeping the boot path and Solo5/KVM carrying unikernel workloads.

Before you start, get the board’s network settings and management credentials from its operator.

Use NXP LSDK 21.08, NXP’s Layerscape software development kit. Validate any later board support package release on the board before you rely on it.

Hardware topology

The LX2160A platform exposes:

• 16× Arm Cortex-A72 cores at up to 2.2 GHz.
• DPAA2 packet-processing accelerators.
• Up to 100 Gbps Ethernet over the chip’s serializer/deserializer lanes, plus DDR4 memory. Multiple PCIe Gen 4 lanes attach accelerators.

Two boot modes are common during bring-up:

• NOR / QSPI boot. The production path, with firmware flashed in place.
• SD-card boot. The development path, where the SD card carries the U-Boot payload and the Linux root filesystem.

Build a Linux image

Start from the vendor board support package and build the image:

1. Source the LSDK environment.
2. Configure for the LX2160A reference board (RDB or variant).
3. Enable KVM and the relevant DPAA2 driver set. Size the contiguous memory area the kernel reserves for devices; cma=900M is a working starting point.
4. Build a wic disk image or a tar.gz root filesystem.

SpaceOS ships no target overlay for this board, so the kernel configuration above is yours to make.

Flash and boot

Halt the platform, move the SD card to the build host, and flash the image:

sudo dd if=lsdk-lx2160a-sdimage.wic of=/dev/<sd-card-device> \
  conv=fsync status=progress bs=4M

Warning: double-check the target device. sudo dmesg | grep <your-sd-device> names the right one. Never run dd against a mounted partition.

Re-insert the SD card into the platform and power-cycle.

Verify the substrate

After Linux is up, log in over the serial console and confirm the board has what the substrate needs:

ls /dev/kvm                # KVM enabled
cat /proc/device-tree/compatible   # board identity
cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq

With KVM and the target devices present, the board has what a SpaceOS daemon install would require.

This is where the page stops today. There is no LX2160A target profile to name, so there is no space target connect command to run against this board. Prove the workload on the Raspberry Pi CM5, which is a supported target.

For power cycling and serial-console access, follow the steps your bench operator supplies.