Vision Apps Release Notes
Version: 01.00.00
Contents
- Introduction
- Licensing
- Getting Started
- Documentation
- What's New
- Upgrade and Compatibility Information
- Device Support
- Validation Information
- Fixed Issues
- Known Issues
- 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 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- OpenVX based demos for ADAS, Vision, deep learning applications
- TI-RTOS on C7x, C6x, R5F and Linux on A72
- Integrates all major PSDKRA and PSDKLA SW components like TIDL, MMALIB, PDK, OpenVX, OpenGL, video codec, C6x algorithms, imaging/sensors, IPC, Linux, TI-RTOS, SPL/uboot.
- Integrates all major HW components like CSI2 camera, eDP/HDMI display, UART, I2C, ethernet, SD card
- Deep learning demos
- Image Classification demo
- Auto valet parking (AVP) demo
- semantic segmentation, Parking spot detect and Vehicle detect algorithms
- 1 channel, 3 algo @ 56 fps mode
- 3 channel, 3 algo @ 28 fps mode (combined network for parking spot and vehicle detect)
- Surround view demos
- 3D surround view using GPU on 4x 2MP 30fps live camera input
- 3D surround view calibration application
- ADAS/Vision demos
- Dense optical flow (DOF) demo
- Stereo disparity engine demo
- Single and multi camera CSI2RX + VISS + LDC + MSC + Display demo
- C7x algorithm offload demo
- Perception Toolkit (PTK) Demos
- Camera based SFM and occupancy grid mapping using Dense optical flow HW engine
- Radar and lidar occupancy grid mapping
- Camera SFM, radar, lidar fusion for occupancy grid mapping
- 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
- lidar, radar, camera SFM nodes for PTK demos
- OpenGL nodes for surround view
- Profiling, logging and other utility APIs
- General stability, performance, documentation improvements
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-2341 | AVP app hangs when running long duration with 3 Algos, 3 channel | AVP demo | 0.9.1 | J721e |
ADASVISION-2499 | DDR bandwidth shows 100% in long run but resets after running statistics | All demos | 0.9.1 | J721e |
ADASVISION-2340 | AVP app hangs on first frame when running TIDL with 3 Algos, 3 channel | AVP demo | 0.9.1 | J721e |
ADASVISION-2502 | A72 load not getting updated | All demos | 0.9.1 | J721e |
ADASVISION-2505 | The C7x is showing a load on the SRV application | SRV demos | 0.9.1 | J721e |
Known Issues
ID | Description | Module | Reported in Release | Affected Platforms | Occurrence | Workaround in this release |
---|---|---|---|---|---|---|
ADASVISION-2556 | SRV demos: GPU Crash during SRV long run test | 3D SRV demo | 01.00.00 | J721E | Seen in long run tests sometimes | None |
ADASVISION-2575 | PTK demos: Camera SFM output does not detect occupied and free space correctly | PTK Demos | 01.00.00 | J721E | Always | None |
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-2442 | SRV demos: Car model rendering is incorrect. This is car model issue and not a SW issue. | 3D SRV demo | 01.00.00 | J721E | Always | None |
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-2576 | PTK demos: Fusion demo stops with error prints from GPU after running for some time | PTK Demos | 01.00.00 | J721E | Always | None |
ADASVISION-2592 | Multi Cam App : Back to Back Test Fails, hangs during sensor init | Multi Cam demo | 01.00.00 | J721E | Sometimes | None |
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-2597 | Stereo demos: Visualization in stereo demo needs improvements to fix false colors | Stereo demo | 01.00.00 | J721E | Always | Potentially a input sequence and/or visualization issue. SDE node and driver output matches C model as expected |
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 |
ADASVISION-2600 | Stereo demos: Stereo demo fails to run in PC Emulation Mode | Stereo demo | 01.00.00 | PC Emulation | Always | None |
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