Vision Apps Release Notes
Version: 08.01.00
Contents
- Introduction
- Licensing
- Getting Started
- Documentation
- What's New
- Upgrade and Compatibility Information
- Device Support
- Validation Information
- Fixed Issues
- Open Defects
- Known Issues
- Change Requests
- 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 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- OpenVX based demos for ADAS, Vision, deep learning applications
- Free RTOS on C7x, C6x on R5F and Linux or QNX on A72
- Integrates all major PSDK RTOS and PSDK Linux SW components like TIDL, MMALIB, PDK, OpenVX, ETHFW, OpenGL, 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
- File based
- Camera based
- Standalone Semantic Segmentation application
- File based
- Camera based
- Standalone Object Detection application
- File based
- Camera based
- Auto valet parking (AVP) demo
- semantic segmentation, Parking spot detect and Vehicle detect algorithms
- 1 channel, 3 algo mode
- 3 channel, 3 algo mode (combined network for parking spot and vehicle detect)
- 3 channel, 5 algo mode - combined network for parking spot and vehicle detect + Three task network for Semantic Segmentation, Motion Segmentation and Depth Estimation (AVP3 demo)
- DKAZE-based Visual Localization application
- Debug support for the ability to debug intermediate layer information from TIDL node
- Surround View demos
- 3D surround view using GPU on 4x 2MP 30fps live camera input
- 3D surround view calibration application
- 3D Surround view + AVP2 demo running simultaneously
- 3D surround view using GPU on 4x 2MP 30fps live camera input
- 3 channel, 3 algo mode (combined network for parking spot and vehicle detect)
- 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 (with DMA acceleration)
- 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
- CV Demos
- Structure from motion
- 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
- Multi-threading support in MSC mosaic node
- Block based processing example kernel on C66x using UDMA/DRU
- Profiling, logging and other utility APIs
- General stability, performance, documentation improvements
- All included MCU tasks are split between MCU2_0 (ETHFW, VPAC HWA) and MCU2_1 (DMPAC HWA), leaving MCU3_0 and MCU3_1 free on main island
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-5069 | hex number to show registered sensor drivers |
| ADASVISION-5068 | Duplicate log in single cam app in PSDKR v8.0 |
| ADASVISION-5044 | Multi cam app error with enable_error_detection flag |
| ADASVISION-5028 | appSplitVpacDcc() is incorrectly checking for allocated buffers |
| ADASVISION-5014 | IPC resource table should use RPMSG_VRING_ADDR_ANY |
| ADASVISION-4992 | Remote Device: RPMessage heap is sized wrong and is causing heap corruption of Rx messages |
| ADASVISION-4980 | IPC Utils: RPMessage heap is sized wrong and is causing heap corruption of Rx messages |
| ADASVISION-4927 | CPU Load values in free RTOS is inconsistent |
| ADASVISION-4926 | QNX: Ipc Init fail when invoking twice appCommonInit() in a process |
| ADASVISION-4911 | C7x L2RAM heap size incorrect |
| ADASVISION-4906 | Python tool for updating memory map does not generate free RTOS files |
| ADASVISION-4777 | DOF app output differs between release vs debug on PC mode |
| ADASVISION-4776 | SFM apps output differs for each run on PC mode |
| ADASVISION-4874 | 8-camera use case fails with FreeRTOS |
| ADASVISION-5103 | Random hang at vxWaitGraph for MCU2_0 based OpenVX nodes |
| ADASVISION-5116 | QNX7: PSDK QNX 8.1 Build Error With Imaging Libraries |
Open Defects
| ID | Summary |
|---|---|
| ADASVISION-5100 | Peak DDR BW numbers seem too high for some demos |
| ADASVISION-5060 | Long duration run of vision apps tidl object detection demo hangs at high usage of A72 |
| ADASVISION-5039 | TIDL preemption test fails when TIDL logs are used |
| ADASVISION-4925 | Bandwidth performance values in certain applications are incorrect |
| ADASVISION-4923 | Frozen frame running OpenVX graphs back to back |
| ADASVISION-4876 | Performance degradation observed on some vision apps demos |
| ADASVISION-4873 | [IMGPreProcNode]: BT601 limited range CSC coefficients causes clipping |
| ADASVISION-4864 | Instability in heterogeneous camera |
| ADASVISION-4799 | QNX: SRV Broadcast Mode Unreliable |
| 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 | QNX SBL debug binaries not working on R5F |
| 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 | QNX: SRV File I/O failing |
| 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-1540 | J7ES Flex connect scope change | 08.00.00 | 08.01.00 |
| JACINTOREQ-1465 | Descope Windows build/installer for J7ES RTOS SDK | 08.00.00 | Descoped |
| JACINTOREQ-1444 | Vision apps firmware inclusion in yocto build | 08.00.00 | Descoped |
| JACINTOREQ-1244 | Descope RTOS-Based Codecs and OpenVX codec nodes | 08.00.00 | Descoped |
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