Vision Apps Release Notes
Version: 11.02.01
Contents
- Introduction
- Licensing
- Getting Started
- Documentation
- What's New
- Device Support
- Validation Information
- Fixed Issues
- Open Defects
- Technical Support
- Package Versioning
Introduction
The Vision Apps package consists of ADAS, vision, deep learning, perception demos/applications for J722S platform
To run the demos in vision apps, the companion PROCESSOR-SDK-LINUX-J722S also needs to be downloaded separately.
Licensing
Refer to Processor SDK RTOS manifest at top level [HTML]
Getting Started
The Vision Apps User Guide [HTML] provides the documentation and references necessary to begin development on TI's platforms using Vision Apps.
Documentation
Refer to following documentation for further details:
| Vision Apps User Guide | Build instructions, API Guide | [HTML] |
| Release Notes Archive | Previous release notes | [FOLDER] |
What's New
New features in this release are highlighted in bold- OpenVX based demos for ADAS, Vision, deep learning applications
- Free RTOS on C7x and R5F and Linux or QNX on A53
- Integrates all major PSDK RTOS and PSDK Linux SW components like TIDL, MMALIB, MCU-PLUS-SDK, OpenVX, C7x algorithms, imaging/sensors, IPC, Linux, Free-RTOS, SPL/uboot.
- Integrates all major HW components like CSI2 camera, HDMI display, UART, I2C, SD card
- Deep Learning demos
- Image Classification demo
- File based
- Camera based
- Standalone Object Detection application
- File based
- Camera based
- Front camera demo
- Camera based
- Debug support for the ability to debug intermediate layer information from TIDL node
- Image Classification demo
- ADAS/Vision demos
- Dense optical flow (DOF) demo
- Stereo disparity engine demo
- Single and multi camera CSI2RX + VISS + LDC + MSC + Display demo
- Multi channel codec demo utilizing CSI2RX + VISS + LDC + MSC + Display with Linux and QNX running on A53
- Edge AI TIOVX apps
- Multi-channel, Multi-instance TIDL based OpenVx demos
- Works with RTOS based capture and display OpenVx nodes
- Works with V4L2 based elements like H.264/H.265 encoder/decoder without buffer copies
- Easy to use config file to construct multi-input, multi-network, multi-output graphs
- Profiling, logging and other utility APIs like CTOOLS for on-chip profiling and debugging
- SDK now supports SAFERTOS enablement on J722S, providing safety-certified RTOS capabilities for functional safety applications
- SDK now supports ETHFW (Ethernet firmware) on MCU2_0 for J722S, enabling advanced Ethernet connectivity and communication features
Device Support
Refer Processor SDK RTOS release notes [HTML]
Validation Information
The tools used to validate this package are listed in top level user guide [HTML]
Fixed Issues
| ID | Summary |
|---|---|
| ADASVISION-6809 | [SafeRTOS/FREERTOS]: Initialize task stack section in system_pre_init API |
| ADASVISION-7276 | J7*: MULTI-CAM-CODEC DECODER Only App fails |
| ADASVISION-6932 | Add: SBL linux build flow support in SDK for freertos/safertos mmcsd boot mode |
| ADASVISION-6992 | [J722S/J7AEN]: SRV demo docs and run scripts missing |
Open Defects
| ID | Summary |
|---|---|
| ADASVISION-6451 | mailbox queue overflowing while running vx_app_arm_ipc.out |
| ADASVISION-6473 | Multi-cam codec app fails on QNX |
| ADASVISION-6520 | [J722S/J7AEN] DOF: Display2 with PipeID 1 fails to create |
| ADASVISION-6564 | Vision app utils: qnx: All thread creation must use default stack instead of global stack |
| ADASVISION-6621 | Memory map tool does not update sysconfig files if addresses change |
| ADASVISION-7165 | Single and Multi cam have intermittent back to back failure with Fusion2 |
| ADASVISION-6564 | Vision app utils: qnx: All thread creation must use default stack instead of global stack |
| ADASVISION-6705 | [QNX] Check the usage of archiver and fix with standard qcc way |
Technical Support
For technical support and additional assistance, contact local TI Field Application Engineer
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 2020, Texas Instruments Incorporated