Validation Information

This release has dependency on GCC, and on C66x/C7x compiler. Please refer top level sdk documentation to know exact version of these dependencies.

Build Commands for Library building on Linux Machine

• Pre built library of each API is provided with release. But in case if user wants to build it again then run “make <algorithm_name>_lib” from top level <PSDK_ROOT>/tiadalg/ folder.This will generate required library at <PSDK_ROOT>/tiadalg/lib/.
  • E.g. "make tiadalg_dof_plane_seperation_lib". This will build the required library for DOF plane seperation algorithm and it will be available at <PSDK_ROOT>/tiadalg/lib/.
  • E.g. "make tiadalg_structure_from_motion_lib". This will build the required library for structure from motion algorithm.
  • Run "make tiadalg_libs" to build all algorithm libraries. Alternativly "make all" also does the same job.
  • Run "make scrub" to clean everything. It is recommended to clean everything before start building the library.
  • Please check the various dependent tools path at <PSDK_ROOT>/tiadalg/makerules/config.mk.

Build Commands for Executable building on Linux Machine

• Executable for APIs are not provided with release. User need to run “make <algorithm_name>” from top level <PSDK_ROOT>/tiadalg/ folder. This will generate required executable at <PSDK_ROOT>/tiadalg/out/
  • E.g. "make tiadalg_dof_plane_seperation" will build the C66x executable for DOF plane seperation algorithm. This is BIOS independent executable, which can be tested on standalone CCS.
  • For structure from motion algorithm BIOS independent executable is not supported. Hence to build BIOS based executable, execute following command "make final_install" from <PSDK_ROOT>/tiadalg/tiadalg_structure_from_motion/test folder. This will generate required executable at <PSDK_ROOT>/tiadalg/out/. This executable can be tested on standalone CCS.

Run Instructions

• Connect c7x_1 or C66x DSP and load the specific executable present at <PSDK_ROOT>/tiadalg/out/.
• For floating point algorithm ( e.g. strucuture from motion), debug vs release output can slightly differ because of floating point operations reordering. It may even differ on target vs PC.
• File read and write to hdd are slow through JTAG. This is the case in structure from motion executable running on CCS. At the end of frame processing output data is written in hdd at location <PSDK_ROOT>tiadalg/data/structure_from_motion/output which may take 4-5 minutes per frame.
• Algorithms may use static input and outputs to speed up standlone execution. Please refer specific test application file for more details.

Host emulation building

• Add "TARGET_PLATFORM=PC" to any make command to build the host emulation library or executable
• Host emulation is not supported for BIOS based build. Hence to build host emulation executable for structure from motion algorithm, use BIOS independent mode. I.e. use command "make tiadalg_structure_from_motion TARGET_PALTFORM=PC" from <PSDK_ROOT>/tiadalg folder

Misc. Information

• Libraries are by default built with release mode. To build it in debug add TARGET_BUILD=debug in compile command.
• Executable are by default built with debug mode. To build it in release mode add TARGET_BUILD=debug in compile command.
• In host emulation build incremental build is not supported if any header file is changed. Hence complete clean is needed before build. This restriction is not there for target build.
• tiadalg_structure_from_motion is the only C7x component, rest other are C66x component.