/
2025.2

2025.2

1. Release Notes

1.1 Steps to Generate ISP Example Design and Build Software Components

Generate ISP Example Design: Begin by generating the ISP Vivado example design, according to the steps outlined in the PG432 ISP Product Guide.

Generate Yocto-based Linux Artifacts: Follow the instructions provided in the Linux section to Yocto EDF Build and Image Generation Guide.

ISP Firmware Preparation: You can either use the pre-built ISP firmware binary from the generated root filesystem (rootfs) or generate the ISP firmware by following the steps detailed on the ISP Firmware [2025.2].

1.2 ISP IP/Driver Features

The following table describes the list of ISP features, input/output formats, maximum resolutions, and output paths supported as part of the 2025.2 release.

I/O Type 

Driver (2025.2)

I/P Formats

 

O/P Formats
(GStreamer Terminology)

No of I/P Streams

Input Type

Max Resolution

Memory/Live Input

Output Path

Format

Media-ctl Name

 

MIMO

 NON-MCM

gbrg,
grbg,
rggb,
bg10,
gb10,
ba10,
rg10,
bg12,
gb12,
ba12,
rg12

BGRG8,
GRBG8, RGGB8, SBGGR10, SGBRG10, SBGGR10, SRGGB10, SBGGR12, SGBRG12, SBGGR12, SRGGB12

NV16,
NV12,
YUY2,
GRAY8,
RGB

1

File input

1920x1080

Memory

Primary Path

LIMO

NON-MCM

rg12

SRGGB12

NV16, NV12, YUY2, RGB.

1 stream per ISP (4 total ISP Instances)

3 MP/8 MP/5 MP

1920x1080 / 3840x2160

Live

Primary Path and Secondary Path

MCM

rg12

SRGGB12

NV16, NV12, YUY2, RGB.

4 streams on single ISP instance

3 MP/8 MP

1920x1080/3840x2160

Live

Primary Path and Secondary Path

LILO

NON-MCM

rg12

SRGGB12

NV16, NV12,
RGB.

1 stream per ISP (2 total ISP Instances)

3 MP/8 MP

1920x1080/
3840x2160

Live

Primary Path (RGB)/Secondary path (IR)

For information related to baremetal, refer to Baremetal Driver Features.

1.3 Newly Added Features in ISP Stack

  • VISP BareMetal

    • Example APU BareMetal driver support for LIMO, LILO, and MIMO configuration

  • Sensor Support

    • RGB-IR sensor (5 MP) supports Legacy and AB modes.

    • Added support for Sony 3 MP and 8 MP sensors.

  • Firmware and Architecture

    • Multiple ISP firmware instances run in AMP mode.

    • Firmware loads to every core via Remoteproc from APUs Linux.

    • APU supports bare-metal code to run and control ISP firmware.

    • A single Vitis project builds all RPU firmware 6/7/8/9.

  • MCM Configuration

    • MCM supports ISP tiles with 4+1 and 3+2 configurations within an ISP tile.

  • ISP Firmware Functional Safety

    • Integrated and enabled ISP Software FuSa AoUs in RPU Firmware from APU Linux drivers.

  • Performance

    • An end-to-end pipeline with an 8 MP (3840x2160) sensor achieves up to 15 fps (MCM) and 30 fps (Non-MCM) per stream.

    • In Non-MCM mode, six sensors validate on all ISP tiles.

  • Linux Drivers

    • v4l2 controls support is added in LIMO and LILO drivers.

1.4 Known Issues

  • AMP Mode

    • The Mailbox driver is providing intermittent prints of No message in shared memory for rpu_id X

  • Source elements connected to the VISP node in the device tree are not included in the media pipeline, therefore they must be removed from the device tree and the VISP source node must be updated.

  • Compatibility Issue: ISP capture → DP display pipeline does not work for NV12 format due to buffer alignment issues.

  • MIMO Driver:

    • Does not run work with RPU8 and RPU9.

    • ISP can produce corrupted output frames. This issue is observed when the CMA node with address 0x500_0000_0000 is present in the DTS, even though the ISP driver does not use this node for any allocations.
      Work-around: As ISP driver does not allocate from this region, commenting the 0x500_0000_0000 CMA region resolves the issue.

  • LILO Driver:

    • The OBA PPC value is not updated dynamically by the LILO Linux driver; it is fixed at 4 PPC.

    • OBA programming calls in the RPU overwrite OBA registers on TILE0 when programming OBA for TILE1 or TILE2. Because of this, in multi-tile designs only RGB888 is supported (the default OBA configuration). In single-tile designs, either RGB888 and NV16 or NV12 alone are supported. (NV12 support is added in the driver but not validated with the design.)

    • When running both the primary output (MP) and the secondary output (SP) simultaneously, closing the primary output (MP) pipeline will invoke ISP stream off thus also stop the secondary stream (SP).

  • ISP Tuning

    • Image flickering will be observed in stream when 2A is enabled, due to 2A algorithm issues.

  • Baremetal Driver

    • Observing noise in MIMO mode

    • Resolutions above 1920×1080 are not supported.

    • Frame rate (FPS) is fixed at 30.

    • In LILO SP self-path configurations, the buffer address might appear as 0x0 in the dump command.

1.5 Bug Fixes

  • MCM is validated with up to five sensors at 30 fps.

  • Resolved closing pipeline in the MCM use case that caused hangs on other pipelines of the same ISP instance.

  • Memory In Memory Out (MIMO) pipeline with fake sink works.

  • Core dump issue on closing media-server is resolved.

  • Kernel crash when unloading overlay is resolved.

1.6 Limitations

  • 3 ISP Tiles can support maximum 15 sensors but due to existing XylonFMC + VEK385 board pin limitations, currently, only 6 streams are supported.

  • On a VEK385 board, Xylon FMC supports only 3 MIPI interfaces.

  • Use only the shared Tuning files, custom tuning Parameters cannot be supported.

  • Tuning tool is not supported.