Vision Apps Release Notes

Version: 08.05.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. Open Defects
  11. Known Issues
  12. Change Requests
  13. Technical Support
  14. 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


Upgrade and Compatibility Information


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-5731 Mutex lock for app_mem_linux memory ops has to be taken before accessing the data structures
ADASVISION-5710 gst_init fails to create endpoint if rpmsg_char_init is already called
ADASVISION-5708 GTC incorrectly configured/enabled in vision apps, causing corruption
ADASVISION-5686 vision_apps appIPCInit incorrectly checks errors from mmap_device_memory
ADASVISION-5672 Multiple definition of display size makes it difficult to change output resolution
ADASVISION-5668 Number of CPU error boundary check incorrect
ADASVISION-5662 vision_apps demo: PC based memory allocation scheme across processes does not enforce exclusion
ADASVISION-5576 MCU1-0 IPC sync failing for J7AHP
ADASVISION-5660 Code error in appPerfStatsCpuLoadCalc
ADASVISION-5608 PC Emulation: DOF visualize is not registered for J721S2/J7AHP
ADASVISION-5566 SDE crashes with 12-bit input
ADASVISION-5375 Hang observed in 4+ ch multi cam app with LDC on J721S2
ADASVISION-5573 AVP2/AVP3 apps fail on J7AHP due to TIDL models

Open Defects

ID Summary
ADASVISION-5733 App_multi_cam_codec hangs for 2 channels in a few minutes
ADASVISION-5727 2A Node error handling of CPU ID is incorrect
ADASVISION-5673 Permission issue can occur when running the vision apps script incorrectly
ADASVISION-5575 Graphics bar not rendering properly for all CPU's on J7AHP
ADASVISION-5555 SDE disparity artifacts on EVM
ADASVISION-5399 VPAC/DMPAC Func clock not enabled for j721s2/j784s4
ADASVISION-5065 OCMC RAM Init fails on MCU2-0
ADASVISION-5393 AVP4 freezes in first second of running on QNX
ADASVISION-4923 Frozen frame running OpenVX graphs back to back
ADASVISION-4799 Broadcast Mode Unreliable
ADASVISION-4386 QNX SBL debug binaries not working on R5F
ADASVISION-4198 Partial failure observed for IPC test when MCU1_0 is enabled due to secure mode boot
ADASVISION-4039 Frame drops in 8 camera, 30 fps demo


Known Issues

ID Summary Workaround
ADASVISION-4345 SteamFIFO overflow observed in long run > 6hrs when using D3 IMX390 CM cameras Upgrade to D3 IMX390 RCM cameras

Change Requests

ID Headline Original Fix Version New Fix Version
JACINTOREQ-4978 Remove PTK Demos from all SDKs 08.05.00 08.05.00


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