Vision Apps Release Notes

Version: 11.02.00

Introduction
Licensing
Getting Started
Documentation
What's New
Upgrade and Compatibility Information
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 Jacinto 7 platform

To run the demos in vision apps, the companion Processor SDK Linux for Jacinto 7 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]
Surround View Manual Calibration Tool	Instructions for Generating Calibration Binaries	[PDF]
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 and Safe RTOS C7x and R5F and Linux or QNX on A72
- Integrates all major PSDK RTOS and PSDK Linux SW components like TIDL, MMALIB, PDK, OpenVX, OpenGL, C7x algorithms, imaging/sensors, IPC, Linux, TI-RTOS, SPL/uboot.
- Integrates all major HW components like CSI2 camera, eDP/HDMI display, UART, I2C, SD card
Deep Learning demos
- Image Classification demo
- Standalone Semantic Segmentation application
- Standalone Object Detection application
- Auto valet parking (AVP) demo
  - semantic segmentation, Parking spot detect and Vehicle detect algorithms
  - 1 channel, 3 algo mode
  - 3 channel, 3 algo mode (combined network for parking spot and vehicle detect)
  - 3 channel, 5 algo mode - combined network for parking spot and vehicle detect + Three task network for Semantic Segmentation, Motion Segmentation and Depth Estimation (AVP3 demo)
- Front camera demo
  - Camera based
  - 1 channel, combined network for semantic segmentation and object detect
- DKAZE-based Visual Localization application
- Debug support for the ability to debug intermediate layer information from TIDL node
Surround View demos
- 3D surround view using GPU on 4x 2MP 30fps live camera input
- 3D surround view calibration application
- Demo uses GLTF 3D Model.
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 A72
- C7x algorithm offload demo (with DMA acceleration)
CV Demos
- Structure from motion
OpenVX target nodes
- image pre-processing (YUV 2 RGB) nodes for DL demos
- image post-processing and visualization nodes for deep learning, DOF, Stereo demos
- OpenGL nodes for surround view
- Multi-threading support in MSC mosaic node
ECU build support for QNX
- Active power optimization tooling
- Available for Front Camera, SRV and AVP4 Demos.
Profiling, logging and other utility APIs
General stability, performance, documentation improvements
All included MCU tasks are split between MCU2_0 (ETHFW, VPAC HWA) and MCU2_1 (DMPAC HWA), leaving MCU3_0 and MCU3_1 free on main island
Enabled support to get DDR BW per initiator using CtoolsLib on HS-FS Device.
VISS Node Optimizations and performance related bug fixes
- [Optimization] Moved VISS configuration memory to cache write-through region to save 125us of configuration time per camera frame (eliminating cache write-back maintenance operation time)
- [Perf Bug Fix] Removed unnecessary cache invalidate maintenance operation on the VISS configuration memory to save 125us of configuration time per camera frame
- [Perf Bug Fix] Removed redundant cpu copies of DCC tables per camera frame (EdgeEnhancement, gamma tables, raw histogram lut)

Upgrade and Compatibility Information

File	Change description	User application change required	User application recompile required
kernels_j7\include\TI\j7.h	This file is deprecated and removed in this SDK.	YES	YES

The J721S2 SPL powers on only the peripherals required during boot. This is a change from the J721E SPL which powers on additional peripherals beyond what what is used during boot. Therefore, if additional peripherals need to be accessed (e.g., I2C, SPI, GPIO's), they must be powered on prior to access.

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-6386	QoS Settings cause artifacts in DSS M2M output
ADASVISION-6679	[QNX] GCC version of compiler is used in concerto instead of QCC
ADASVISION-6738	[QNX] vx_app_tidl app build broken for debug mode
ADASVISION-6647	MMALIB profile is hardcoded to "release" in linker paths
ADASVISION-6470	Dual Display with both DP ports is failing with Linux+RTOS

Open Defects

ID	Summary
ADASVISION-4923	Single cam error on ports other than port 1 after running multi cam
ADASVISION-5555	SDE disparity artifacts on EVM
ADASVISION-6199	Race Conditions in c7x-mma-tidl and tiadalg builds
ADASVISION-6387	No option to set vpParams->scanFmt in the dss utility from vision_apps
ADASVISION-6451	mailbox queue overflowing while running vx_app_arm_ipc.out
ADASVISION-6453	SRV + AVP demo not working
ADASVISION-6520	Apps killed with Cntrl^C do not do proper cleanup fails on rerun
ADASVISION-6080	Incomplete frame error in multi cam application
ADASVISION-5892	Remove unnecessary files from SafeRTOS build
ADASVISION-5734	App_multi_cam_codec decode framerate drops for more than 2 channels
ADASVISION-6564	Vision app utils: QNX: All thread creation must use default stack instead of global stack
ADASVISION-6809	[SafeRTOS]: Initialize task stack section in system_pre_init API

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