Vision Apps Release Notes

Version: 07.03.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. Technical Support
  13. 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

Not applicable. Early adopter release.


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-4680 VisionApps: QNX: Remove the use of _NTO_TCTL_IO_PRIV in ThreadCtl calls
ADASVISION-4653 psdk_rtos: setup script uses sudo command even when passing –skip_sudo
ADASVISION-4578 DMPAC (SDE/DOF) performance stat has some issues
ADASVISION-4547 Open Klocwork bugs remaining in 7.2 SDK
ADASVISION-4150 CSI output corrupted when run for 4 ch @ 30fps or 1ch @60fps
ADASVISION-2344 Utils: UDMA init error intermittently on C7x when running in Linux+RTOS mode


Open Defects

ID Summary
ADASVISION-4583 C6x Memory Leak in TIDL Demos
ADASVISION-4577 PTK SFM/Valet parking demos throw error
ADASVISION-4422 PTK SFM/Valet parking demo throw rpmsg error when terminated by Ctrl+C
ADASVISION-4412 Performance measurement incorrect for display node
ADASVISION-4411 Performance measurement incorrect for capture node
ADASVISION-4386 Exception in IPC on R5's with QNX SBL debug binaries
ADASVISION-4199 HDMI Display error with ethernet firmware
ADASVISION-4198 Partial failure observed for IPC test when MCU1_0 is enabled due to secure mode boot
ADASVISION-4196 SRV crash occasionally observed
ADASVISION-4080 SRV File I/O is failing
ADASVISION-4039 Frame drops in 8 camera, 30 fps demo
ADASVISION-4570 Open Klocwork bugs in video codec library


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


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