Vision Apps Release Notes

Version: 06.02.00

Contents

  1. Introduction
  2. Licensing
  3. Getting Started
  4. Documentation
  5. What's New
  6. Upgrade and Compatibility Information
  7. Device Support
  8. Validation Information
  9. Fixed Issues
  10. Known Issues
  11. Technical Support
  12. 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 Automotive SDK for Jacinto 7 also needs to be downloaded separately.


Licensing

Refer to Processor SDK RTOS Automotive 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


Upgrade and Compatibility Information

Not applicable. Early adopter release.


Device Support

Refer Processor SDK RTOS Automotive release notes [HTML]

Validation Information

The tools used to validate this package are listed in top level user guide [HTML]


Fixed Issues

ID Description Module Affected Versions Affected Platforms
ADASVISION-2442 SRV demos: Car model rendering is incorrect 3D SRV demo 01.00.00 J721E
ADASVISION-2576 PTK demos: Fusion demo stops with error prints from GPU after running for some time PTK Demos 01.00.00 J721E
ADASVISION-2575 PTK demos: Camera SFM output does not detect occupied and free space correctly PTK Demos 01.00.00 J721E
ADASVISION-2592 Multi Cam App : Back to Back Test Fails, hangs during sensor init Multi Cam demo 01.00.00 J721E
ADASVISION-2597 Stereo demos: Visualization in stereo demo needs improvements to fix false colors Stereo demo 01.00.00 J721E
ADASVISION-2600 Stereo demos: Stereo demo fails to run in PC Emulation Mode Stereo demo 01.00.00 PC Emulation


Known Issues

ID Description Module Reported in Release Affected Platforms Occurrence Workaround in this release
ADASVISION-3994 CSI-RX: 8 camera multicam loopback application fails CSI-RX TIOVX Node 06.02.00 J721E Always None. The 8 camera application works fine with driver example. Suspects this to be an vision apps application code issue
ADASVISION-3995 CSI-RX Node Split mode 8-channel capture is failing CSI-RX TIOVX Node 06.02.00 J721E Always This feature is not yet validated. This feature enables to have independent graphs for each of the CSI-RX node instances. Work around is run all 8-channels with same FPS from the two CSI-RX instances from the same graph
ADASVISION-2556 SRV demos: GPU Crash during SRV long run test 3D SRV demo 01.00.00 J721E Sometimes Seen in long run tests sometimes
ADASVISION-2501 TIDL AVP demo: SW Mosaic performance node is higher than expected due to scalar co-effs programmed for each channel each window DL Demos 01.00.00 J721E Always Need to program scalar co-effs only if there is change in scaling ratio
ADASVISION-2476 Singe/Multi Cam demos: I2C failures seen while setting exposure parameters for IMX390 sensor single camera, multi camera, 3D SRV demos 00.09.01 J721E Sometimes None
ADASVISION-2344 Utils: UDMA init error intermittently on C7x when running in Linux+RTOS mode utils 00.09.00 J721E Sometimes Disable overlap check during UDMA init. Overlap check disabled by default in vision_apps
ADASVISION-2565 Demos: apps do not exit gracefully on doing a Ctrl-C All demos/applications 01.00.00 J721E Always Stop apps gracefully using menu option 'x' else reboot board
ADASVISION-2577 OpenVX tutorial: SetNodeTarget Error in vx_tutorial_graph_user_kernel_pytiovx OpenVX tutorial 01.00.00 J721E Always This is false error print and can be ignored
ADASVISION-2599 Utils: HWA load measurement for MSC reports 50% lower performance since Chroma plane is not considered in calculation single cam demo, AVP demo 01.00.00 J721E Always Multiply the reported MP/s by a factor of 1.5x for these demos


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 2019, Texas Instruments Incorporated