VHWA Introduction
Contents
- Introduction
- Licensing
- Documentation
- What's New
- Fixed Issues
- Known Issues
- VHWA Test Application
- Technical Support
- Package Versioning
- Trainings
Introduction
The Vision Hardware Accelerator (VHWA) provides the logic to interface for MSC, NF, LDC, VISS, DOF and SDE accelerators. This is VHWA FVID2 driver documentation.
Licensing
Documentation
| VHWA Static Analysis Report | Static Analysis Report | [XLSX] |
| VHWA Driver API Guide | API Guide | [HTML] |
| VHWA Standalone applications performance | Performance Statistics | [XLSX] |
| VHWA Test Report | Test Report | [Zipped File] |
| VHWA Bidirectional Traceability Reports | Jacinto Bi_Di Report | [XLSX] |
What's New
Here is a list of the new feature(s) supported in this release:
- VHWA (VPAC and DMPAC) low-level drivers (VISS, MSC, LDC, NF, DOF, SDE) on VPAC3 devices are ready for ASIL-B safety certification. CSP package will be made available upon request.
- [VISS] The VISS low-level driver now supports FCP histogram readback on FCP1 and FCP2 for VPAC3 devices.
- [VISS] The HTS limiter feature for VISS is now available on VPAC3 devices.
- [VISS] The VISS low-level driver now supports RAW histogram readback on VPAC3 devices.
- [VISS] H3A Autofocus feature is now supported on VPAC3 devices.
- [VISS] GLBCE WDR mode configuration is now supported on VPAC3 devices.
- [VISS] The FCP block now supports RGB LUT and YUV Saturation LUT configuration for FCP1 and FCP2 on VPAC3 devices.
Fixed Issues
No new issues fixed as part of this release for VPAC3 devices.
Known Issues
| ID | Summary |
|---|---|
| PDK-12683 | Chroma only output is not correct from Human Vision Pipeline when machine vision is enabled. |
| PDK-12681 | Incorrect access of luma and chroma channel in luma only and chroma only mode causes corruption. |
| PDK-13247 | AEWB output incorrect for VISS for Three Frame Merge with two YUV420, saturation and AEWB output |
| PDK-12860 | [VHWA-VISS]: Error check missing while setting VISS module specific configuration |
| - | [VHWA]: DPC stats enable MMR is not configurable from VHWA VPAC3L. |
| - | [VHWA]: DCC live tuning for AWB is not working properly on AM62A |
| - | [VHWA]: GLBCE context save and restore requires validation using low level driver test case for J722S and AM62A |
| - | [DMPAC]: DOF and SDE performance numbers are not meeting expectation on J722S; DOF 1MP performance number is not meeting expectation on J784S4 |
| - | [VPAC]: AF output incorrect for VISS for Three Frame Merge with two YUV420, saturation and AF output |
Application Examples
| VHWA Module | Test Application | Supported Platform | Supported Cores |
|---|---|---|---|
| VISS | baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos baremetal |
J721S2, J721E, J784S4, J742S2, J722S |
mcu2_0, mcu2_0, mcu2_0, mcu4_0, mcu2_0, mcu4_0, main_r5 |
| LDC | baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos baremetal |
J721S2, J721E, J784S4, J742S2, J722S |
mcu2_0, mcu2_0, mcu2_0, mcu4_0, mcu2_0, mcu4_0, main_r5 |
| MSC | baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos baremetal |
J721S2, J721E, J784S4, J742S2, J722S |
mcu2_0, mcu2_0, mcu2_0, mcu4_0, mcu2_0, mcu4_0, main_r5 |
| DOF | baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos baremetal |
J721S2, J721E, J784S4, J742S2, J722S |
mcu2_1, mcu2_1, mcu2_1, mcu2_1, main_r5 |
| SDE | baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos, safertos baremetal, freertos baremetal |
J721S2, J721E, J784S4, J742S2, J722S |
mcu2_1, mcu2_1, mcu2_1, mcu2_1, main_r5 |
Steps to run VHWA test applications:
For VPAC1 and VPAC3 devices
cd pdk/packages/ti/drv/vhwa/
make help
VHWA example build
make vhwa_msc_baremetal_testapp BOARD=j721s2_evm SOC=j721s2 CORE=mcu2_0 BUILD_PROFILE=debug
For VPAC3L devices:
Navigate to mcu_plus_sdk path
make DEVICE=j722s gen-buildfiles
cd test/unity/
make -f makefile.j722s.r5f.ti-arm-clang
cd ../../
make -s -f makefile.j722s all DEVICE=j722s PROFILE=release
make -C source/drivers/vhwa -f makefile.j722s.main-r5fss0-0.ti-arm-clang PROFILE=release
make -C source/drivers/vhwa/examples/vhwa_viss_test/j722s-evm/main-r5fss0-0_nortos/ti-arm-clang/ PROFILE=release
Technical Support
For technical support and additional assistance, contact E2E Forum
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 |
Trainings
| VHWA Overview | VHWA Modules and SW Overview | [PPTX] |
[PDF] |
Copyright 2024, Texas Instruments Incorporated