SPRAD48 July   2022 DRA829J , DRA829J-Q1 , DRA829V , DRA829V-Q1 , TDA4VM , TDA4VM-Q1

 

  1.   Abstract
  2.   Trademarks
  3. 1 Introduction
  4. 2 Summary of Changes
  5. 3 Procedure to Apply the Changes
    1. 3.1 Do Not Skip Any of These Steps
    2. 3.2 Patch Information
  6. 4 Build Instructions
    1. 4.1 PSDKRA Build Instructions
    2. 4.2 PSDKLA Build Instructions
  7. 5 Demo Applications
    1. 5.1 Basic OpenVX Kernels
    2. 5.2 Capture - Display UseCase
      1. 5.2.1 Steps to Enable Demo
    3. 5.3 Single Camera VPAC Application Demo
      1. 5.3.1 Steps to Enable Demo
    4. 5.4 Multi Camera VPAC Application Demo
      1. 5.4.1 Steps to Enable Demo
  8. 6 Run Instructions
  9. 7 Basic Demo Applications
  10. 8 Single Camera VPAC Application Demo
  11. 9 Multi Camera VPAC Application Demo
  12. 10Limitations

10 Limitations

SI Number Limitations Description
1 File system access is not available in R5 As FatFS is not integrated with RTOS, file system is not accessible here
2 DCC cannot be updated on the fly DCC should be loaded initially, then perform the build
3 IPC failed between A72 and R5F Currently, A72 as a target is not supported on OpenVX host as R5 due to various reasons. One reason would be that the IPC portID of A72 should be known by R5. In order to do that, below workaround is proposed.
Workaround : Before beginning the demo, an IPC message with payload "0xDEAD0000" is sent from A72 to R5 in order for R5 to retrieve the portID of A72
4 Memory allocation for A72 targets The Memory allocated by the R5 is not known by A72 in order to convert it into virtual memory and provide a file descriptor