Skip to main content

TECH VEDA

Embedded Linux on Edge-AI 23rd Sept 2026 enrollingLinux kernel & Device drivers starts on 24th Oct 2026 enrollingCorporate on-site training - Submit proposal Pick your modulesSharpen your kernel skills: deep dives, drivers, Yocto, CVEs, careers — updated daily. Read the blog →Embedded Linux fast track starts 23rd sept 2026 enrollingEmbedded Linux Mastery track starts 23rd sept 2026 enrollingLinux systems engineering starts 23rd sept 2026 enrolling
✉ info@techveda.org☏ Show number
Login
Enquire now

BSP Tracker  /  SBC Support Status

Which single-board computers still have a future

Development boards grouped by the one thing that decides whether a board can carry a product: how long the kernel underneath still receives upstream security fixes. Re-verified every week against the vendor trees and kernel.org.

Last checked 9 August 202632 boards comparedSource kernel.org + vendor trees

Reading this sheet

Every board is grouped by one date: when the kernel its BSP is based on stops receiving upstream security fixes. That date — not price, connectors or community — bounds how long the board can carry a supported product. Work down from the Longest cover group and stop at the first group that still clears the year you have to ship patches through.

The date is the projected end of life of the kernel.org longterm series the vendor branch is based on — not a vendor longevity figure, which describes chip availability rather than kernel support. Longterm EOLs are the stable maintainers’ current plan and can move, so every row is re-verified weekly against the vendor branch and kernel.org; anything that cannot be confirmed from a primary source is marked unknown rather than guessed.

Raspberry Pi is excluded. It ships a downstream kernel Raspberry Pi maintains on its own schedule, so the upstream fixes-stop date this sheet is keyed on does not apply to it.

Mainline columnmainline mainline drives the SoC; you can ship on it without carrying the vendor treepartial mainline boots the SoC, but named blocks — GPU, VPU, NPU — still need the vendor kernelvendor only no usable mainline support; you are on the vendor branch and its update cadence

Boards, by cover remaining

Grouped by how much upstream cover the kernel behind each board still has, shortest first. Wide screens show every column; narrow screens scroll the table sideways.

BoardFixes stopMainlineKernelSoCArchYocto layer
Losing cover within twelve months3Enough runway for a bring-up or an evaluation, not for a product that has to be supported past the date.
Avaota A1 (SBC)Dec 20264 mo leftpartial5.15Allwinner T507 / T527Allwinnerarm64meta-sunxi
Forlinx OKT507-CDec 20264 mo leftpartial5.15Allwinner T507 / T527Allwinnerarm64meta-sunxi
MYIR MYD-LT527Dec 20264 mo leftpartial5.15Allwinner T507 / T527Allwinnerarm64meta-sunxi
Covered for another year or two7Workable for a product with a short life, or one you plan to move to mainline before the date.
Firefly ITX-3588JDec 202716 mo leftpartial6.1Rockchip RK3588 / RK3588SRockchiparm64meta-rockchip
Forlinx OK3588-CDec 202716 mo leftpartial6.1Rockchip RK3588 / RK3588SRockchiparm64meta-rockchip
Radxa ROCK 5BDec 202716 mo leftpartial6.1Rockchip RK3588 / RK3588SRockchiparm64meta-rockchip
STM32MP157C-EV1Dec 202716 mo leftmainline6.6ST STM32MP1 (STM32MP157)STMicroelectronicsarmmeta-st-stm32mp
STM32MP157F-DK2Dec 202716 mo leftmainline6.6ST STM32MP1 (STM32MP157)STMicroelectronicsarmmeta-st-stm32mp
STM32MP257F-DKDec 202716 mo leftpartial6.6ST STM32MP2 (STM32MP257)STMicroelectronicsarm64meta-st-stm32mp
STM32MP257F-EV1Dec 202716 mo leftpartial6.6ST STM32MP2 (STM32MP257)STMicroelectronicsarm64meta-st-stm32mp
Longest cover available20The kernel behind these has the most runway left, and is where a product with a long support obligation should start.
Banana Pi BPI-M2S (SBC)Dec 202828 mo leftpartial6.12Amlogic A311D (G12B)Amlogicarm64meta-meson
BeagleBone BlackDec 202828 mo leftmainline6.18TI AM335x (Sitara)Texas Instrumentsarmmeta-ti
i.MX 6ULL EVKDec 202828 mo leftmainline6.18NXP i.MX6ULLNXParmmeta-imx
i.MX 8M Plus EVKDec 202828 mo leftpartial6.18NXP i.MX8M PlusNXParm64meta-imx
i.MX 93 EVKDec 202828 mo leftmainline6.18NXP i.MX93NXParm64meta-imx
J721EXSOMXEVMDec 202828 mo leftvendor only6.18TI J721E / TDA4VMTexas Instrumentsarm64meta-ti
Khadas VIM3 (SBC)Dec 202828 mo leftpartial6.12Amlogic A311D (G12B)Amlogicarm64meta-meson
Kria KV260 Vision AI Starter KitDec 202828 mo leftmainline6.18AMD Zynq UltraScale+ MPSoCAMD (Xilinx)arm64meta-xilinx
Lantronix Open-Q 6490CS SOM dev kitDec 202828 mo leftpartial6.18Qualcomm QCS6490 (RB3 Gen 2)Qualcommarm64meta-qcom
MYIR MYD-YG2LXDec 202828 mo leftpartial6.12Renesas RZ/G2L (R9A07G044)Renesasarm64meta-renesas
Qualcomm RB3 Gen 2 Development KitDec 202828 mo leftpartial6.18Qualcomm QCS6490 (RB3 Gen 2)Qualcommarm64meta-qcom
Radxa ZERO 2 Pro (SBC)Dec 202828 mo leftpartial6.12Amlogic A311D (G12B)Amlogicarm64meta-meson
RZ/G2L Evaluation Board Kit (SMARC)Dec 202828 mo leftpartial6.12Renesas RZ/G2L (R9A07G044)Renesasarm64meta-renesas
SAMA7G54-EK (EV21H18A)Dec 202828 mo leftmainline6.18Microchip SAMA7G5 (SAMA7G54)Microchiparmmeta-atmel
SK-AM62A-LPDec 202828 mo leftpartial6.18TI AM62A (AM62A7)Texas Instrumentsarm64meta-ti
SK-AM62BDec 202828 mo leftmainline6.18TI AM62x (AM625)Texas Instrumentsarm64meta-ti
SK-TDA4VMDec 202828 mo leftvendor only6.18TI J721E / TDA4VMTexas Instrumentsarm64meta-ti
TI AM335x starter kitDec 202828 mo leftmainline6.18TI AM335x (Sitara)Texas Instrumentsarmmeta-ti
ZCU102Dec 202828 mo leftmainline6.18AMD Zynq UltraScale+ MPSoCAMD (Xilinx)arm64meta-xilinx
ZCU104Dec 202828 mo leftmainline6.18AMD Zynq UltraScale+ MPSoCAMD (Xilinx)arm64meta-xilinx
Not established2No date could be confirmed from a primary source. Recorded as unknown rather than guessed.
Jetson AGX Orin Developer Kit—not establishedvendor only6.8NVIDIA Jetson Orin (Tegra234)NVIDIAarm64meta-tegra (community, OE4T)
Jetson Orin Nano Developer Kit—not establishedvendor only6.8NVIDIA Jetson Orin (Tegra234)NVIDIAarm64meta-tegra (community, OE4T)
Building a shortlist? Keep the boards whose Fixes stop date clears the year your product must still receive security patches, then prefer mainline rows — they move to new kernels without waiting for the vendor. Break the remaining ties on price, connectors and community.

What to do about it

Every SoC listed here has a date. After that date the kernel the BSP is based on receives no further security fixes from upstream, and maintaining it becomes the product team’s responsibility.

There are three options:

  1. Backport the fixes yourself. Your team maintains a kernel that nobody else maintains: tracking each CVE, applying the patch to a tree that has diverged from upstream, and testing the result, for as long as the product ships.
  2. Move to the vendor’s newer BSP. This gives you a few more years of upstream fixes, and it costs a second bring-up: a new kernel, your patches forward-ported, drivers re-validated, and the product re-tested.
  3. Move to mainline. Whether mainline is an option depends on the SoC. Each record lists which blocks mainline supports and which it does not. It is the only option that does not have to be repeated when the next vendor kernel reaches end of life.

All three are engineering work, and all three are work we do: reading vendor kernel trees, checking what mainline actually supports, and moving products from one to the other. This page is built from the same work.

Embedded Linux engineering →Talk to us about your BSP

Get the updates

An email when a kernel series reaches end of life, a board row changes, or a layer picks up a release branch. Nothing else.

RSS