| LX2160A Family | |
| |
| LX2160A, SystemReady certified systems, Ex: Solidrun Honeycomb/clearfog family | |
| Processing | |
| Manufacturer | NXP + Solidrun |
| Architecture | AArch64 |
| CPU | ARM Cortex-A72 |
| Extensions | No known extensions |
| Memory | 1GB - 64GB |
| VPU | Various |
| Connectivity | |
| Audio | Various |
| Network | Various |
| Storage | Various |
| Support | |
| Supported release(s) | Fedora 32+ |
| Website | https://www.solid-run.com/embedded-networking/nxp-lx2160a-family/ |
LX2160A Family
Based on NXP’s Layerscape LX2160A. The platform has 16 Arm Cortex A72's, SODIMM Slots, SATA, USB3, PCIe, and 10/40/100G networking.
For the most part, the machine behaves like a standard SystemReady machine with UEFI+ACPI. The normal Fedora install and administration guides should be used. Yet, some of the machines ship without UEFI installed, and the high-speed (DPAA2) networking requires some additional nonstandard configuration.
Kernel features status and overview
Brief overview of the kernel status
Bootloader/firmware status and overview
The system should be provisioned with a recent UEFI firmware image from https://images.solid-run.com/LX2k/lx2160a_uefi Choose the correct firmware based on whether it will be flashed to the SPI or SD and matches the installed RAM speed.
The solidrun pages have details on how to assure the correct firmware is installed, but for SD the process is approximatly:
- Download the image
- decompress it with xzdec,
- dd it to a raw sd card like: dd if=lx2160acex7_2200_700_2400_8_5_2.img of=/dev/sdX where sdX is the SD card.
- Plug the SD card into the board.
- Make sure firmware boot source switches are set off-ON-ON-ON-ON-off.
Other details
On the first boot of the installer, it may be required to add arm-smmu.disable_bypass=0 to the grub/kernel command line. That will then propagate to the installed system and remain over upgrades.
- To manage the SFP+ ports please install the "restool" package.
- To auto-enable the SFP+ ports, it may be necessary to add a udev rule to /etc/udev/rules.d. For example, a file named fsl_mc_bus.rules containing:
ACTION=="add", SUBSYSTEM=="fsl-mc", ENV{DEVTYPE}=="fsl_mc_bus_dpmac", RUN+="/usr/bin/flock /usr/bin/ls-addni -c '(PATH=/usr/bin /usr/bin/ls-addni %k)'