Vision Apps Release Notes
Version: 08.05.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 and R5F and Linux or QNX on A72
- Integrates all major PSDK RTOS and PSDK Linux SW components like TIDL, MMALIB, PDK, OpenVX, ETHFW, OpenGL, C7x 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
- 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 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
- OpenGL nodes for surround view
- Multi-threading support in MSC mosaic node
- 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
- The J784S4 SPL powers on only the peripherals required during boot. This is a change from the J721E SPL which powers on additional peripherals beyond what what is used during boot. Therefore, if additional peripherals need to be accessed (e.g., I2C, SPI, GPIO's), they must be powered on prior to access.
- There is an existing workaround on the DM code to enable power for the DRU4-DRU7. This was a change from the EA1 release which powered this on from the C7X-1.
- There is a known instability with the QNX + SBL boot mode where the kernel will crash upon boot approximately 25% of the time. In order to workaround this issue, you can set the value returned by the board_smp_num_cpu function in the location psdkqa/qnx/src/hardware/startup/boards/j784s4/board_smp.c from 8 to 2 and this issue should no longer be seen
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-5731 | Mutex lock for app_mem_linux memory ops has to be taken before accessing the data structures |
ADASVISION-5710 | gst_init fails to create endpoint if rpmsg_char_init is already called |
ADASVISION-5708 | GTC incorrectly configured/enabled in vision apps, causing corruption |
ADASVISION-5686 | vision_apps appIPCInit incorrectly checks errors from mmap_device_memory |
ADASVISION-5672 | Multiple definition of display size makes it difficult to change output resolution |
ADASVISION-5668 | Number of CPU error boundary check incorrect |
ADASVISION-5662 | vision_apps demo: PC based memory allocation scheme across processes does not enforce exclusion |
ADASVISION-5576 | MCU1-0 IPC sync failing for J7AHP |
ADASVISION-5660 | Code error in appPerfStatsCpuLoadCalc |
ADASVISION-5608 | PC Emulation: DOF visualize is not registered for J721S2/J7AHP |
ADASVISION-5566 | SDE crashes with 12-bit input |
ADASVISION-5375 | Hang observed in 4+ ch multi cam app with LDC on J721S2 |
ADASVISION-5573 | AVP2/AVP3 apps fail on J7AHP due to TIDL models |
Open Defects
ID | Summary |
---|---|
ADASVISION-5733 | App_multi_cam_codec hangs for 2 channels in a few minutes |
ADASVISION-5727 | 2A Node error handling of CPU ID is incorrect |
ADASVISION-5673 | Permission issue can occur when running the vision apps script incorrectly |
ADASVISION-5575 | Graphics bar not rendering properly for all CPU's on J7AHP |
ADASVISION-5555 | SDE disparity artifacts on EVM |
ADASVISION-5399 | VPAC/DMPAC Func clock not enabled for j721s2/j784s4 |
ADASVISION-5065 | OCMC RAM Init fails on MCU2-0 |
ADASVISION-5393 | AVP4 freezes in first second of running on QNX |
ADASVISION-4923 | Frozen frame running OpenVX graphs back to back |
ADASVISION-4799 | Broadcast Mode Unreliable |
ADASVISION-4386 | QNX SBL debug binaries not working on R5F |
ADASVISION-4198 | Partial failure observed for IPC test when MCU1_0 is enabled due to secure mode boot |
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-4978 | Remove PTK Demos from all SDKs | 08.05.00 | 08.05.00 |
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