Imaging Release Notes
Version: 10.00.00
Contents
- Introduction
- Licensing
- Getting Started
- Documentation
- What's New
- Upgrade and Compatibility Information
- Device Support
- Supported Image Sensors PSDK RTOS
- Supported Image Sensors EdgeAI
- Supported Image Sensors by Third Party
- Validation Information
- Fixed Issues
- Change Requests
- Known Issues
- Technical Support
- Package Versioning
Introduction
The Imaging package consists of the Texas Instruments OpenVX conformant implementation for J7 EVM and AM6xA EVM platforms
Licensing
The licensing information of this library, as well as any third-party components included which are made available under a number of other open-source licenses are enumerated as part of the manifest. A complete manifest along with export control information is detailed here [HTML].
Getting Started
The Imaging User Guide [HTML] provides the documentation and references necessary to begin development on TI's platforms using Imaging.
Documentation
Refer to following documentation for further details:
Imaging documentation
| Imaging User Guide for J7 and AM6xA | Build instructions, additional information related to J7 and AM6xA platform | [HTML] |
| Software Manifest | Licenses, terms of use | [HTML] |
Tuning Guides and FAQs
| ISP Tuning Guide for J7/TDA4 | Work flow of tuning the ISP related to J7/TDA4 platform | [HTML] |
| ISP Tuning Guide for AM6xA | Work flow of tuning the ISP related to AM6xA platform | [HTML] |
| Tuning Tool Request Form | Tuning Tool Request Form | [LINK] |
Reports
| Static Analysis Report | C and C++ Taxonomy Report | [XLSX] |
| Bidirectional Traceability Report | Mapping of requirements to test cases | [XLSX] |
| Test Reports | Conformance test reports, TI platform test reports | [XLSX] |
What's New
Here is a list of the new feature(s) supported in this release:
- [SENSOR DRIVER] IMX390 RCM broadcast mode is enabled by default for multi-cam
- [SENSOR DRIVER] OV2312 support for QNX + RTOS
- [VISS] GLBCE context save restore for multi-cam enabled on J722S & AM62A
- [VISS] Support for simultaneous RGB and IR outputs on J722S
- [MSC] Enables YUV420 dual channel processing on each thread of MSC on VPAC3 and VPAC3L devices
- [MSC] Enables simultaneous processing of two plane inputs (such as luma-chroma, luma-luma planes) with different bit-depths and formats on a single thread of MSC on VPAC3 and VPAC3L devices
- [LDC] Enables simultaneous processing of two plane inputs (such as luma-chroma, luma-luma planes) with different storage formats on LDC on VPAC3 and VPAC3L devices
- [MSC] Enables YUV422I input processing on MSC on VPAC3 and VPAC3L devices
- [MSC] Enables arbitrary bit conversions, such as 10-bit to 8-bit conversion by left shifting 2 bits on MSC
Upgrade and Compatibility Information
No updates!
Device Support
| SoC | HOST (OS) | Target (OS) | Test Plaform |
| J7 | x86_64 (Linux) | A72 (Linux) | J721E/J721S2/J722S/J784S4 EVM + Fusion board Revision 1C and 2. Older Fusion boards are not supported. |
| AM6xA | x86_64 (Linux) | A53 (Linux) | AM62A EVM |
Supported Image Sensors PSDK RTOS
| Image Sensor | Max Instances | Supported Platform | Module | Ordering Info |
| IMX390 | 8 Note: j784s4 + Fusion2 can support up to 12 |
J721E/J721S2/J722S/J784S4 EVMs | D3RCM-IMX390-953 | D3RCM-IMX390-953 |
| AR0233 | 1 | J721E/J721S2/J784S4 EVMs | MARS (MARS1-TI953-GEVK, MARS1-AR0233ATSCS-GEVB) | Please contact OnSemi |
| AR0820 | 1 | J721E/J721S2/J784S4 EVMs | LI-AR0820-FPDLINKIII | LI-AR0820-FPDLINKIII |
| GW5200-AR0233 YUV422 | 1 | J721E/J721S2/J784S4 EVMs | LI-GW5200-AR0233 | LI-GW5200-AR0233 |
| IMX390 DesignCore® Discovery Series (55° HFOV, 100° HFOV, 174° HFOV) | 4 | J721E/J721S2/J784S4 EVMs + Fusion1 | IMX390 DesignCore® Discovery Series | IMX390 DesignCore® Discovery Series |
| OV2312 | 1 | SK-AM62A Board + QNX only | LI-OV2312-FPDLINKIII-LED-110H | LI-OV2312-FPDLINKIII-LED-110H |
Supported Image Sensors EdgeAI
Only DCC XML and binary configuration files are provided in Imaging for the sensors listed below. V4L2 Sensor drivers are provided by Processor SDK Linux.
Supported Image Sensors by Third Party
The listed sensors are supported by third-parties.
| Image Sensor | Max Instances | Module | Ordering Info |
| IMX623 | 1 | Sony module w/ SR1069A Lens | Please contact Sony for SDK 8.1 driver Registration flow | Developer World (sony.com) |
Validation Information
This release was built and validated using the following tools:
Build Tools (included in Processor SDK RTOS):
- ARM R5F Code Generation Tools version: Same as Processor SDK RTOS
Dependencies (included in Processor SDK RTOS):
- TIOVX version: Same as Processor SDK RTOS
- VXLIB version: Same as Processor SDK RTOS
- Processor SDK RTOS version: 10.00.00
Fixed Issues
| ID | Summary |
|---|---|
| ISS-498 | Some IMX390 Camera Modules output corrupted images in Multi Cam app on j784s4 + Fusion2 |
| ADASVISION-6276 | Fcp_EeConfig.lut is of type int32_t instead of int16_t |
| ISS-288 | AR0820 Camera does not work with Fusion-2 board |
| ISS-486 | [MSC-PMD]: The max downscaling factor is limited to 2, which under-utilizing MSC HW |
| ISS-549 | GLBCE ctx save/restore is not enabled for J722S |
| ISS-551 | [J722S] AR0233 has error log, but streams okay |
| ISS-558 | AR0820 does not work on j722s-evm Linux and QNX + RTOS |
| ISS-561 | iss_sensors.c have misleading variable and function names and print statements |
| ISS-562 | Sensor Driver - Function names are unclear and lack comments |
| ISS-563 | Sensor Driver - code is repetitive and can be refactored for improved readability and re-usability |
| ISS-568 | MSC dual channel processing on each thread |
| ISS-569 | LDC validate function shall ensure stride alignment corresponds to IP-defined requirements |
| ISS-570 | [VPAC-MSC]: YUV422I format support in MSC |
| ISS-571 | J722S: IMX390 Disco fails to initialize |
| ISS-572 | H3A data alignment is wrong |
| ISS-574 | j722s: 7 and 8 cameras do fail to start with multi-cam |
| ISS-575 | SDK shall support sensor broadcast mode as default sensor mode |
| ISS-578 | Typo in python script for DCC profile creation |
| ISS-585 | Software support for 10-to-8-bit conversion in VPAC MSC |
| ISS-586 | [VHWA-MSC]: Support for dual channel with different bit depth |
| ISS-588 | [VHWA-LDC]: Support for dual channel with different bit depth |
| ISS-589 | [LDC] Incorrect Condition Check for Multi-Plane and Single-Plane Formats in Output Images |
| ISS-599 | [VPAC-MSC]: YUV422I format support in MSC PC emulation |
Change Requests
- Scope In - None.
- Scope Out - None.
- Scope Modifications
- Support for multiple difference camera configuration/CFA in VPAC moved to 10.1
Known Issues
| ID | Summary |
|---|---|
| ADASVISION-4923 | Single cam error on ports other than port 1 after running multi cam |
| ADASVISION-5774 | Glitches seen on stereo app for J784S4 with safertos |
| ADASVISION-6080 | Multi Cam application capture error |
| ADASVISION-6315 | [J722S/J7AEN] DOF: Display2 with PipeID 1 fails to create |
| ISS-474 | Interpolation method should be configurable from Imaging for VPAC3L |
| ISS-515 | H3A data mismatch on RGB-IR outputs of J7AEN |
| ISS-552 | [VISS Node]: Incorrect mux selection for HV + MV pipeline |
| ISS-606 | Switching between IMX390 RCM and IMX390 Disco single-cam app results in error |
| ISS-610 | Camera auto detection failed on Fusion-1 port-1 in single-cam app |
| ISS-611 | Sensor register read and write fails for EdgeAI J721E-SK board |
| ISS-614 | AEN + Fusion2 + IMX728 Power issues |
Technical Support
For technical support and additional assistance, contact E2E Forum
Package Versioning
Each package version is composed of 4 period-delimited numbers - represented here by the letters M, m, p and b [M.m.p.b]. The table below provides a descriptive reference regarding package version numbering.
| Digit | Meaning | Description |
|---|---|---|
| 1 (M=Major) | Major revision | Incremented when the new version is substantially different from the previous For example, a new module added or an existing module's algorithm significantly altered. |
| 2 (m=minor) | Minor revision | Incremented when the new version has changed but not in a major way. For example, some minor changes in the API or feature set. |
| 3 (p=patch) | Patch number | Incremented for all other source code changes. This include any packaging support code. |
| 4 (b=build) | Build number | Incremented for each release delivery to CM. Reset for any change to M, m or p |
Copyright 2024, Texas Instruments Incorporated