Vision Apps Release Notes

Version: 07.00.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 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 Description Module Affected Versions Affected Platforms
ADASVISION-4104 IMX390 30 FPS sensor init takes 40 seconds per camera in release mode Sensor framework SDK_J7_06_02_00 J7-EVM
ADASVISION-4097 Remote Device: Incorrect scope of Task Params Remote Device SDK_J7_06_02_00 J7-EVM
ADASVISION-4094 vxMapImagePatch takes around 1ms to map 0.5MB image on Linux Utils SDK_J7_06_02_00 J7-EVM
ADASVISION-4079 Python tool to update memory requires update for the dtb files Tools SDK_J7_06_02_00 J7-EVM
ADASVISION-4072 NFS boot error loading mcu_2_1 Boot SDK_J7_06_02_00 J7-EVM
ADASVISION-4064 Vision Apps includes a "make rtos_sdk" option which is no longer supported Build SDK_J7_06_02_00 J7-EVM
ADASVISION-4048 MSC Mosaic node should be using mem type DMA, not mem type HOST Kernels SDK_J7_06_02_00 J7-EVM
ADASVISION-4040 Frame drops in 3 camera, 60 fps demo Camera Apps SDK_J7_06_02_00 J7-EVM
ADASVISION-4025 QNX : AppLogGetTimeInUsec gives incorrect timing value Utils SDK_J7_06_02_00 J7-EVM
ADASVISION-4024 QNX : SRV application has segfault when run for 3+ hours SRV Algos SDK_J7_06_02_00 J7-EVM
ADASVISION-4022 Image PreProcessing node does not work for non-aligned pitch Kernels SDK_J7_06_02_00 J7-EVM
ADASVISION-4018 QNX : GUI enablement causes SRV performance degradation SRV Algos SDK_J7_06_02_00 J7-EVM
ADASVISION-4017 QNX: Performance statistics failing Utils SDK_J7_06_02_00 J7-EVM
ADASVISION-4011 QNX : Some of the Open VX conformance test fails TIOVX SDK_J7_06_02_00 J7-EVM
ADASVISION-4010 QNX : Multi Cam App hangs Camera Apps SDK_J7_06_02_00 J7-EVM
ADASVISION-4003 QNX : SRV App has corrupted output SRV Algos SDK_J7_06_02_00 J7-EVM
ADASVISION-3994 CSI-RX: 8 camera multicam loopback application fails CSI-RX TIOVX Node SDK_J7_06_02_00 J7-EVM
ADASVISION-3920 QNX : TIDL AVP2 demo hangs when run with release binary DL Demos SDK_J7_06_02_00 J7-EVM
ADASVISION-3859 QNX: DOF App hangs when built for QNX DOF Demos SDK_J7_06_01_01 J7-EVM
ADASVISION-3834 QNX: App Log Sync not functional Utils SDK_J7_06_01_01 J7-EVM
ADASVISION-3828 Capture should support the hot pluging of the cameras CSI-RX TIOVX Node SDK_J7_01_00_00_00 J7-EVM
ADASVISION-2619 Add format validation for mosaic node Kernels SDK_J7_06_02_00 J7-EVM
ADASVISION-2599 Utils: HWA load measurement for MSC reports 50% lower performance since Chroma plane is not considered in calculation Utils SDK_J7_01_00_00_00 J7-EVM
ADASVISION-2577 OpenVX tutorial: SetNodeTarget Error in vx_tutorial_graph_user_kernel_pytiovx OpenVX Tutorial SDK_J7_01_00_00_00 J7-EVM
ADASVISION-2565 Demos: apps should exit gracefully on doing a Ctrl-C Demos SDK_J7_01_00_00_00 J7-EVM
ADASVISION-2556 SRV demos: GPU Crash during SRV long run test SRV Algos SDK_J7_01_00_00_00 J7-EVM
ADASVISION-2476 Singe/Multi Cam demos: I2C failures seen while setting exposure parameters for IMX390 sensor Sensor framework SDK_J7_00_09_01_00 J7-EVM


Known Issues

ID Description Module Reported in Release Affected Platforms Occurrence Workaround in this release
ADASVISION-4202 QNX: DSS underflow observed when using SBL boot flow and running AVP+SRV demo SBL Boot SDK_J7_07_00_00 J7-EVM Always This occurs is observed when there is high DDR traffic, which is the case in the AVP+SRV demo. The DSS underflow issue is working in the SPL boot flow. A patch will be provided post-release to fix this issue in SBL.
ADASVISION-4199 HDMI Display error with ethernet firmware Ethernet firmware and display SDK_J7_07_00_00 J7-EVM Always HDMI display mode is not enabled with ethernet firmware. eDP mode must be used
ADASVISION-4198 Partial failure observed for IPC test when MCU1_0 is enabled IPC SDK_J7_07_00_00 J7-EVM Always None
ADASVISION-4196 Surround view crash occasionally observed SRV Algos SDK_J7_07_00_00 J7-EVM Rarely None
ADASVISION-4188 eDP to HDMI adaptors are disabled due to ethfw integration issue Display SDK_J7_07_00_00 J7-EVM Always None. eDP to HDMI adaptors cannot be used.
ADASVISION-4187 OpenGL mosaic app fails for Linux Sample kernels SDK_J7_07_00_00 J7-EVM Always Generated output for Linux is invalid
ADASVISION-4150 app_multi_cam output corrupted when run for 4 ch @ 30fps CSI-RX TIOVX Node SDK_J7_07_00_00 J7-EVM Rarely This error occurs primarily when broadcast mode is enabled. Therefore, broadcast mode has been disabled for this release
ADASVISION-4135 app_multi_cam performance drop observed when 8 cameras are enabled CSI-RX TIOVX Node SDK_J7_07_00_00 J7-EVM Always None. The multi cam app will reach full performance in a future release.
ADASVISION-4115 Stereo demos cannot display graphics and outputs properly Stereo demos SDK_J7_07_00_00 J7-EVM Sometimes None
ADASVISION-4099 CSI-RX Node Split mode 8-channel capture is failing CSI-RX TIOVX Node SDK_J7_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 within the same capture node from the same graph
ADASVISION-4080 QNX: SRV File I/O segfault sometimes observed SRV Algos SDK_J7_07_00_00 J7-EVM Sometimes None
ADASVISION-3958 Output resolution is fixed to 1080p in all Basic Demos Display SDK_J7_06_02_00 J7-EVM Always Output resolution must be manually modified in order to set it to a different value
ADASVISION-3954 SFM OG map and Valet parking demo crashes with DOF enabled DL Demos SDK_J7_01_00_00_00 J7-EVM Always None
ADASVISION-2682 Support for Embedded data (0x12) from sensor CSI-RX TIOVX Node SDK_J7_06_02_00 J7-EVM Always None. Support for this feature will be added in future releases.
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-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


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