Vision Apps Release Notes
Version: 00.05.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 vision, perception demos/applications for J7 Pre-Silicon platform
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] |
What's New
Here are a few of the new features supported in this release:
- [ADASVISION-1803] - Demo: Parking spot detect and Vehicle using CNN - file IO based
- [ADASVISION-1804] - Demo: Motion Segmentation - file IO based
- [ADASVISION-1806] - Integration: Integrate filesystem with MMCSD/eMMC media on TI-RTOS A72
- [ADASVISION-1807] - Integration: Integrate a command line interface (CLI) for demo menu/options
- [ADASVISION-1809] - Integration: Integrate with Linux on A72
- [ADASVISION-1810] - Integration: Integrate TIOVX Linux + TI-RTOS only
- [ADASVISION-1953] - Display Sharing : dedicated task on R5F to marshal display requests / status updates to and from A72 VMs
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 release notes [HTML]
The VLAB version used to validate this package is listed in top level release notes [HTML]
Refer user guide [HTML] for additional instructions to install and setup the dependancies.
Fixed Issues
Not applicable
Known Issues
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