Vision Apps Release Notes
Version: 09.00.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 and Safe 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
- Multi channel codec demo utilizing CSI2RX + VISS + LDC + MSC + Display with Linux and QNX running on A72
- C7x algorithm offload demo (with DMA acceleration)
- 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
No upgrade and compatibility changes since previous 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-5914 | psdk_rtos/scripts/board_env.sh has wrong image name |
| ADASVISION-5893 | Removal about information about PyTorch based training script for DKAZE |
| ADASVISION-5880 | PSDK RTOS - ADDON package mySecureSW request link does not exist |
| ADASVISION-5878 | [Documentation] [J784s4] - The Multi cam demo is not updated regarding the changes of object split array |
| ADASVISION-5877 | Documentation: SafeRTOS documentation with PDK reference is broken |
| ADASVISION-5789 | vx_app_load_test provides a lower load when given 100% load as input |
| ADASVISION-5763 | MCU2_0 startups much more slower if its OS is SafeRTOS |
Open Defects
| ID | Summary |
|---|---|
| ADASVISION-5990 | Single Cam application not running in PC emulation mode |
| ADASVISION-5986 | NFS steps mentioned in Vision Apps User guide not working |
| ADASVISION-5967 | 9+ Channel Camera Capture to Encode on J784S4 not Supported |
| ADASVISION-5955 | eDP to HDMI adaptors are failing |
| ADASVISION-5918 | Codec app compiler warnings with GCC 11.3 |
| ADASVISION-5892 | Remove unnecessary files from SafeRTOS build |
| ADASVISION-5849 | [J784s4] Graph hangs in delete callback of tidl node in C7x when multiple graphs are created and deleted |
| ADASVISION-5798 | HDMI display from infotainment board not rendering image |
| ADASVISION-5788 | L2_MEM shows 100% unused when tidl_od demo is run |
| ADASVISION-5774 | Glitches seen on stereo app for J784S4 with safertos |
| ADASVISION-5758 | Enable en_out_ldc_write cause freeze in Multi Cam Demo |
| ADASVISION-5734 | App_multi_cam_codec decode framerate drops for more than 2 channels |
| ADASVISION-5732 | eDP to HDMI adaptors failing on J721S2 QNX builds with SBL boot app |
| ADASVISION-5726 | CPU is hitting 100% when using gst-launch for both encode and decode using appsink, appsrc |
| ADASVISION-5673 | Permission issue can occur when running the vision apps script incorrectly |
| ADASVISION-5669 | SCIserver should use UART logs instead of appLogPrintf |
| ADASVISION-5575 | Graphics bar not rendering properly for all CPU's on J7AHP |
| ADASVISION-5555 | SDE disparity artifacts on EVM |
| ADASVISION-5393 | AVP4 freezes in first second of running |
| ADASVISION-5100 | Peak DDR BW numbers seem too high for some demos |
| ADASVISION-5034 | [Doc]: Details about 8-channels/camera usecase |
| ADASVISION-4924 | EtherCAT Slave Demo is not working |
| ADASVISION-4923 | Single cam error on ports other than port 1 after running multi cam |
| ADASVISION-4386 | QNX SBL debug binaries not working on R5F |
| ADASVISION-4196 | SRV crash occasionally observed |
| ADASVISION-4080 | QNX: SRV File I/O failing with specific car model |
| ADASVISION-4039 | Frame drops in 8 camera, 30 fps demo |
Known Issues
| ID | Summary | Workaround |
|---|---|---|
| ADASVISION-5060 | Long duration run of vision apps tidl object detection demo hangs at high usage of A72 | 1. Ask customers to have TI review board design 2. Determine if sample has gone through full TMS production testing from die ID. Ask die ID using: devmem2 0x43000020 – for die id 0 devmem2 0x43000024 – for die id 1 devmem2 0x43000028 – for die id 2 devmem2 0x4300002C – for die id 3 Send die ID to TI. |
| ADASVISION-4345 | SteamFIFO overflow observed in long run > 6hrs when using D3 IMX390 CM cameras | Upgrade to D3 IMX390 RCM cameras |
| ADASVISION-4199 | HDMI Display error with ethernet firmware |
Change Requests
| ID | Headline | Original Fix Version | New Fix Version |
|---|---|---|---|
| JACINTOREQ-5018 | De-scope BAM enablement on J7 from 8.6 | 08.06.00 | 09.01.00 |
| JACINTOREQ-6636 | Descope of few TIDL 9.0 MRs | 09.00.00 | DESCOPE |
| JACINTOREQ-5374 | Descope Orphaned FR's for J721E, J721S2, and J784S4 on QNX | 08.06.00 | DESCOPE |
| JACINTOREQ-6510 | QoS Scope Modify CR w.r.t AEN PPR and SDK restructuring | 09.00.00 | PSDK_9.x |
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