This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/TDA2PXEVM: Data visualization HDMI output

Part Number: TDA2PXEVM
Other Parts Discussed in Thread: SYSBIOS

Tool/software: TI-RTOS

I am using Processor SDK Vision 3.3.0.0 and the apps demo with configuration tda2px_evm_bios_radar, which uses the radar_read_fft_write use-case. That use-case includes GrpxSrc->Display_Grpx. I thought that link was intended to display diagnostic information via HDMI, so I set DATA_VIS_INCLUDE=yes in the tda2px_evm_bios_radar/cfg.mk config file so I could try it out. However, I have never been able to see any HDMI output, though UART and TCP/IP is working. Can you provide more information about the purpose of the GrpxSrc link and how to utilize it, plus what needs to be done to enable HDMI output?

Thanks.

  • Hi,

    DATA_VIS_INCLUDE=yes in config will include the feature in GrpxSrc Link.
    However, you also need to enable "dataVisDataBwDisplayEnable" in the createPrm of GrpxSrc to see the visualization on display.
    In your use case, you can add something like this.
    pUcObj->GrpxSrcPrm.dataVisDataBwDisplayEnable=1;

    Regards,
    Stanley
  • It appears that dataVisDataBwDisplayEnable should already be set:
    grpxSrcLink.h: GrpxSrcLink_CreateParams_Init() sets it to TRUE if DATA_VIS_INCLUDE is defined. This is called by:
    chains_radarfilereadfftwrite_ResetLinkPrms()
    chains_radarfilereadfftwrite_Create()
    Chains_radarreadfftwrite()
    Chains_radarMain()
    Chains_main()
    However, I see -DDATA_VIS_INCLUDE is set in gmake output, yet when I set a breakpoint inside GrpxSrcLink_CreateParams_Init(), hovering over DATA_VIS_INCLUDE gives an error:
    'Computing hover expression' has encountered a problem. An internal error occurred during: "Computing hover expression".
    Details: An internal error occurred during: "Computing hover expression".
    java.lang.NullPointerException
    Stepping through the code, it appears to set Enable to False, as if DATA_VIS_INCLUDE is not actually defined.

    I created a CCS project by importing an existing makefile that includes the entire Processor SDK distribution, and let CCS index all the code. Does the index play a role when debugging, or does the debugger go by symbols that it loads when uploading code to the target? The debugger greys out code based on #defines, but I'm not sure if I should trust that. I used a script to create a file of #defines matching compiler options I saw on gmake output so the indexer would know which sections were valid when browsing through the code.

    I tried adding ($info) commands to print _CLAGS within rules_m4.mk, but ran into snags due to some special characters contained within _CFLAGS. Instead, I did gmake without the -s option and looked at the -D compiler parameters. Is there an easy way to get a list of what was actually # defined (may be core-dependent too I suppose)? I also considered adding diagnostics to the showconfig target, but it is more complicated since _CFLAGS is defined in a child makefile and vision_SDK_CFLAGS doesn't appear to include everything.
  • If CCS Debugger greys out the code, that means that piece of code is not compiled. It goes by the executable you loaded in CCS.

    If you give the below command from ~\vision_sdk\build, it will list all the configurations.
    >gmake showconfig
    You can check if DATA_VIS_INCLUDE=yes is listed.
    If yes, that means the code was not recompiled or recompiled but not linked into the library.
    In any case, a clean build will make sure everything is updated.

    Regards,
    Stanley
  • DATA_VIS_INCLUDE=yes is set and indicated by gmake showconfig. I have done a clean build, but still do not see HDMI output under any circumstances. I believe that the radar_read_fft_write usecase should have display output. Any other ideas of what I should try?

    I am looking at the HDMI output directly on the TDA2Px EVM board, not the one on a small daughter card with 2 USB connectors.

    Is there another example that should produce display output with easily satisfied prerequisites?
  • Did you follow the steps provided in ProcessorSDKRadar_UserGuide.pdf to run radar_read_fft_write use case?
    Please first try to build without any change to make sure everything works.
    You should see radar 2D FFT heatmap output on HDMI Display.
  • Yes, I followed the steps in ProcessorSDKRadar_UserGuide.pdf for the radar_read_fft_write use case. I did a clean build, and ran the network_tx and network_rx tools on Windows using TFDTP. However, I do not see any HDMI output whatsoever from either of the HDMI connectors on the board. Any ideas what else to try? Are there any other demos that should exercise the HDMI output and run on the TDA2Px EVM?

  • Could you try Processor SDK Vision instead? www.ti.com/.../processor-sdk-vision

    In Vision SDK, you can build "tda2px_evm_bios_all" config.

    It includes a use case null_src_display. It is under Miscellaneous Test menu option.

    You will find menu option "3: NullSrc (YUV) + Display and Null".

    This use case will display TI logo on TV via HDMI output. You should plug in to the connector on the main board, not on the daughter card with other usb connectors.

  • Thanks for the suggestion. I have been using Vision instead of Radar even though I am using Radar use-cases, since I ran into a build error on Radar that did not occur on Vision, and mostly they appear to be the same. Any pitfalls expected from doing that?

    I tried to build apps under Vision using the tda2px_evm_bios_all config as you said. However, I ran into a build error that I could not immediately resolve. I verified the file exists in the directory C:\ti\PROCESSOR_SDK_VISION_03_03_00_00\vision_sdk\apps\src\rtos\alg_plugins\common. But something about the build process seems to make the file have 0 length or remove it altogether. I guess it must be autogenerated somehow. I tried restoring it from a backup copy but the subsequent build still fails the same way. Any suggestions? Here is the related build output and error:

    # Compiling tda2px-evm:arp32_1:release:app_alg_plugins: common/sample_vcop_array_add_uns_short_kernel.k
    fatal error: cannot open file
       "common/sample_vcop_array_add_uns_short_kernel.c"

    >> Compilation failure
    gmake[5]: *** [c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_all/obj/app_alg_plugins/tda2px-evm/arp32/release/sample_vcop_array_add_uns_short_kernel.oearp32F] Error 1
    gmake[4]: *** [arp32_1] Error 2
    gmake[3]: *** [libs] Error 2
    gmake[2]: *** [app_alg_plugins] Error 2
    gmake[1]: *** [apps] Error 2
    gmake: *** [vision_sdk] Error 2

  • It is okay to use Vision SDK and it supports Radar as well.

    "common/sample_vcop_array_add_uns_short_kernel.c" is not included in the build. Only "common/sample_vcop_array_add_uns_short_kernel.k" should be compiled.
    It looks like there might be something wrong with your build environment.

    If you are building in Windows, could you make sure xdctools path is in the top of the PATH?
    We haven seen wrong version of build utility getting called instead of the ones from xdctools path.
  • I am running Windows 10 and my path has xdctools as the first item: Path=C:\ti\PROCESSOR_SDK_VISION_03_03_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;...

    What are *.k files used for and how do they differ from C?

    The only reference to common/sample_vcop_array_add_uns_short_kernel.c I found in a search of all the project files was quoted in a #line directive, within the file of the same name. I would not think the filename in a #line statement would directive would actually be looked up, but rather just used for reference.
    #line 78 "common/sample_vcop_array_add_uns_short_kernel.c"
  • The source files to be compiled are defined in ~/vision_sdk/apps/src/rtos/alg_plugins/common/SRC_FILES.MK and it does not have "common/sample_vcop_array_add_uns_short_kernel.c".

    *.k file is Kernel-C language source file used for EVE Vector Core programming. It is compiled using ARP32 compiler.
  • Are you saying I should add common/sample_vcop_array_add_uns_short_kernel.c to the makefile you mentioned? I haven't modified this file and presumably this example has been tested successfully so I don't see why it should need editing.

    Thanks.

  • No. I meant to indicate that "common/sample_vcop_array_add_uns_short_kernel.c" is not part of the build so you should not see any build error because of that file.

    You can also find more details about the build system in ~/vision_sdk/docs/FeatureSpecificUserGuides/VisionSDK_UserGuide_BuildSystem.pdf

    And, yes, the build and use case should work out-of-box.

  • Nonetheless, I do see that error. What do you recommend to resolve the issue?

  • Could you share some more info as the followings?
    - The complete PATH setting from your build window
    - The output of "gmake showconfig"
    - The complete build log (using "gmake" command without "-s -j" option) after deleting "binaries" folder under ~/vision_sdk

  • Here are the requested items. I see there is a warning that more processors are included than necessary (I didn't change the defaults). Is that an issue?

    Path=C:\ti\PROCESSOR_SDK_VISION_03_03_00_00\ti_components\os_tools\windows\xdctools_3_32_01_22_core;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\NXP\S32DS_Power_v1.2\utils\MinGW\msys\1.0\bin

    The MinGW directory is not really needed but defines ls for directory listings.

    For some reason, if I run "gmake -s clean", it hangs, but "gmake clean" works (but with more verbose output).

    gmake -s showconfig output:

    gmake -C c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/apps/configs -f build_makeconfig.mk showconfig
    gmake[1]: Entering directory `c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/apps/configs'
    #
    # Build Config is [ tda2px_evm_bios_all ]
    # Build Config file is @ c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/configs/tda2px_evm_bios_all/cfg.mk
    # Build Config .h file is @ c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/links_fw/include/config/apps/tda2px_evm_bios_all/system_cfg.h
    # Build CPUs is @ ipu1_0 ipu1_1 ipu2 a15_0 dsp1 dsp2 eve1 eve2
    #
    # CPUs included in application,
    # PROC_IPU1_0_INCLUDE=yes
    # PROC_IPU1_1_INCLUDE=yes
    # PROC_IPU2_INCLUDE=yes
    # PROC_DSP1_INCLUDE=yes
    # PROC_DSP2_INCLUDE=yes
    # PROC_EVE1_INCLUDE=yes
    # PROC_EVE2_INCLUDE=yes
    # PROC_EVE3_INCLUDE=no
    # PROC_EVE4_INCLUDE=no
    # PROC_A15_0_INCLUDE=yes
    #
    # Platform config,
    # VSDK_BOARD_TYPE=TDA2PX_EVM [options: TDA2XX_EVM TDA2EX_EVM TDA3XX_EVM TDA3XX_RVP TDA2XX_RVP]
    # PLATFORM=tda2px-evm
    # DUAL_A15_SMP_BIOS=no
    # DDR_MEM=DDR_MEM_512M [options: DDR_MEM_128M DDR_MEM_512M DDR_MEM_1024M]
    # NDK_PROC_TO_USE=a15_0 [options: a15_0 ipu1_0 ipu1_1 ipu2 none]
    # NSP_TFDTP_INCLUDE=no [options: yes no]
    # TDA2EX_ETHSRV_BOARD=no [options: yes no]
    # FATFS_PROC_TO_USE=ipu1_0 [options: ipu1_0 none]
    # RADAR_BOARD=none [options: TDA3XX_AR12_ALPS TDA3XX_AR12_VIB_DAB_BOOSTER TDA3XX_RADAR_RVP none]
    #
    # Build config,
    # BUILD_OS=Windows_NT [options: Windows_NT Linux]
    # BUILD_DEPENDENCY_ALWAYS=no
    # BUILD_ALGORITHMS=no
    # BUILD_INFOADAS=no
    # PROFILE=release [options: debug release]
    # KW_BUILD=no
    # CPLUSPLUS_BUILD=no
    # IPU_PRIMARY_CORE=ipu1_0 [options: ipu1_0 ipu2]
    # IPU_SECONDARY_CORE=ipu2 [options: ipu1_0 ipu2]
    # A15_TARGET_OS=Bios [options: Bios Linux Qnx]
    # BSP_STW_PACKAGE_SELECT=all [options: all vps-iss-dss-only vps-vip-vpe]
    #
    # Safety Module config,
    # RTI_INCLUDE=no
    # ECC_FFI_INCLUDE=no
    # DCC_ESM_INCLUDE=no
    #
    # Video Module config,
    # IVAHD_INCLUDE=yes
    # VPE_INCLUDE=yes
    # CAL_INCLUDE=yes
    # ISS_INCLUDE=yes
    # ISS_ENABLE_DEBUG_TAPS=no
    # WDR_LDC_INCLUDE=no
    # DSS_INCLUDE=yes
    #
    # Open Compute config,
    # OPENCL_INCLUDE=no
    # TARGET_ROOTDIR=c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/ari_app/src/rtos/opencl
    # ENABLE_OPENCV=no
    # ENABLE_OPENCV_TESTS=no
    # OPENVX_INCLUDE=no
    #
    # Log config,
    # ENABLE_UART_LOG=yes
    # ENABLE_NETWORK_LOG=no
    # ENABLE_CCS_LOG=no
    # CIO_REDIRECT=yes
    #
    # IPC config,
    # WORKQ_INCLUDE=no
    # IPC_LIB_INCLUDE=no
    #
    # Surround View config,
    # SRV_FAST_BOOT_INCLUDE=no
    #
    # Other Module config,
    # AVB_INCLUDE=no
    # DCAN_INCLUDE=no
    # RADAR_INCLUDE=no
    # CPU_IDLE_ENABLED=yes
    # FAST_BOOT_INCLUDE=no
    # DATA_VIS_INCLUDE=no
    # HS_DEVICE=no
    # ULTRASONIC_INCLUDE=no
    #
    # Linux config,
    # DEFAULT_UBOOT_CONFIG=dra7xx_evm_vision_config
    # DEFAULT_KERNEL_CONFIG=ti_sdk_dra7x_release_defconfig
    # DEFAULT_DTB=dra7-evm-infoadas.dtb
    # CMEM_INCLUDE=no
    # IPUMM_INCLUDE=no
    # IPU1_EVELOADER_INCLUDE=no
    # ROBUST_RVC_INCLUDE=no
    # BUILD_ADAM_CAR=no
    #
    # Alg plugins included in build,
    # ALG_autocalibration ALG_clr ALG_deWarp ALG_dmaSwMs ALG_vpeSwMs ALG_edgedetection ALG_framecopy ALG_lanedetection ALG_objectdetection ALG_safe_framecopy ALG_sceneobstruction ALG_sfm ALG_sparseopticalflow ALG_subframecopy ALG_surroundview ALG_iss_aewb
    #
    # Use-cases included in build,
    # UC_iss_capture_isp_simcop_display UC_iss_mult_capture_isp_2d_3d_sv_tda3x UC_iss_mult_capture_isp_dewarp_3dsv_tda3xx UC_iss_mult_capture_isp_simcop_sv_tda3xx UC_iss_multi_inst_capture_display UC_srv_calibration UC_lvds_vip_multi_cam_view UC_lvds_vip_sv_standalone UC_network_rx_tx UC_null_src_dec_display UC_null_src_display UC_saveDisFrame UC_vip_single_cam_analytics2 UC_vip_single_cam_edge_detection UC_vip_single_cam_frame_copy UC_vip_single_cam_frame_copy_safety UC_vip_single_cam_lane_detection UC_vip_single_cam_object_detection2 UC_vip_single_cam_sfm UC_vip_single_cam_sparse_optical_flow UC_vip_single_cam_subframe_copy UC_vip_single_cam_tlr UC_vip_single_cam_view UC_vip_single_cam_view_encdec
    #
    # vision_sdk_CFLAGS = -DTDA2PX_BUILD -DTDA2XX_FAMILY_BUILD -DSOC_TDA2PX -DPLATFORM_EVM_SI -D_DRA7xx -D_SC_VER_1_16 -D__sysbios__ -DTDA2XX_512MB_DDR -DUTILS_ASSERT_ENABLE -DFVID2_BACKWARD_COMPATIBLE -DUSE_STD_ASSERT -DTRACE_ENABLE -DASSERT_ENABLE -DENABLE_UART_LOG -D_GNU_SOURCE -DBOARD_TYPE_TDA2PX_EVM -DIPU_PRIMARY_CORE_IPU1 -DIPU_SECONDARY_CORE_IPU2
    #
    gmake -s -fbuild_makeconfig.mk check_cpu_include
    gmake[2]: Entering directory `c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/apps/configs'
    #
    # CPUs that are NOT required but included in config [ tda2px_evm_bios_all ],
    #
    # WARNING: IPU1_1 can be excluded from application
    # WARNING: IPU2 can be excluded from application
    # WARNING: EVE2 can be excluded from application
    #
    # CPUs that are required but not included in config [ tda2px_evm_bios_all ],
    #
    #
    # Edit c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/configs/tda2px_evm_bios_all/cfg.mk to include or exclude CPUs in an application
    #
    gmake[2]: Leaving directory `c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/apps/configs'
    gmake[1]: Leaving directory `c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/apps/configs'

    gmake_depend.txt

    gmake.txt

    stderror output:

    c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/rtos/makerules/rules_66.mk:181: target `c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_all/obj/app_alg_plugins/tda2px-evm/66/release/GAlignLUT_tda3xx.oe66' given more than once in the same rule.
    c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/rtos/makerules/rules_66.mk:181: target `c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_all/obj/app_alg_plugins/tda2px-evm/66/release/GAlignExt_tda3xx.oe66' given more than once in the same rule.
    c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/rtos/makerules/rules_66.mk:181: target `c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_all/obj/app_alg_plugins/tda2px-evm/66/release/GAlignLUT_tda3xx.oe66' given more than once in the same rule.
    c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/build/rtos/makerules/rules_66.mk:181: target `c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_all/obj/app_alg_plugins/tda2px-evm/66/release/GAlignExt_tda3xx.oe66' given more than once in the same rule.
    fatal error: cannot open file
       "common/sample_vcop_array_add_uns_short_kernel.c"
    gmake[5]: *** [c:/ti/PROCESSOR_SDK_VISION_03_03_00_00/vision_sdk/binaries/apps/tda2px_evm_bios_all/obj/app_alg_plugins/tda2px-evm/arp32/release/sample_vcop_array_add_uns_short_kernel.oearp32F] Error 1
    gmake[4]: *** [arp32_1] Error 2
    gmake[3]: *** [libs] Error 2
    gmake[2]: *** [app_alg_plugins] Error 2
    gmake[1]: *** [apps] Error 2
    gmake: *** [vision_sdk] Error 2

  • Could you share what is in ~\vision_sdk\apps\src\rtos\alg_plugins\common\SRC_FILES.MK?
  • Could you also check the folder permission for ~\vision_sdk\apps\src\rtos\alg_plugins\common\?
    sample_vcop_array_add_uns_short_kernel.c is generated from ARP32 compiler when it compiles sample_vcop_array_add_uns_short_kernel.k.
    Maybe the folder permission is not allowing the compiler to open and write the file.
  • Here is the contents of the file SRC_FILES.mk:



    SRCDIR += common/

    SRCS_COMMON += alg_ivision.c

    SRCS_c66xdsp_1 +=

    SRCS_c66xdsp_2 +=

    SRCS_arp32_1 +=

    SRCS_arp32_2 +=

    SRCS_arp32_3 +=

    SRCS_arp32_4 +=

    SRCS_a15_0 +=  

    SRCS_ASM_a15_0 +=  sample_a15.asm

    SRCS_CPP_COMMON += sample.cpp

    SRCS_K_arp32_1 += sample_vcop_array_add_uns_short_kernel.k

    Authenticated Users have read/write permission to the folder. However, the folder itself is marked as Read-only for some reason. Perhaps because I added it to a local Git repository? Other folders are marked read-only too, yet I'm not having trouble with other builds.

  • Did you checkout the folder from Git so compiler can create/write a file?
    We typically don't generate file in other source folders. The build artifacts go to the binaries folder.
  • I turned off read-only for all contents of the TI folders using the Windows folder property dialog. Now the build worked without reported errors.

    However, the example is not running as expected. No menus are displayed after I select 2: MISC Tests. It just shows the following:

    [IPU1-0]  Vision SDK Usecases,
    [IPU1-0]  --------------------
    [IPU1-0]
    [IPU1-0]  1: RADAR Usecases
    [IPU1-0]  2: MISC Tests
    [IPU1-0]
    [IPU1-0]  s: System Settings
    [IPU1-0]
    [IPU1-0]  x: Exit
    [IPU1-0]
    [IPU1-0]  Enter Choice:
    [IPU1-0]
    [IPU1-0]     86.795613 s:
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Unit Test ... Start !!!
    [IPU1-0]     86.795613 s:
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Create Done !!!
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Run Started for [EVE1] !!!
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Run Done (Total time = 0 usec, Per iteration time = 0 usec)!!!
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Run Started for [DSP1] !!!
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Run Done (Total time = 0 usec, Per iteration time = 0 usec)!!!
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Run Started for [IPU1-0] !!!
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Run Done (Total time = 0 usec, Per iteration time = 0 usec)!!!
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Run Started for [IPU1-1] !!!
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Run Done (Total time = 0 usec, Per iteration time = 0 usec)!!!
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Delete Done !!!
    [IPU1-0]     86.795613 s:
    [IPU1-0]     86.795613 s:  SYSTEM: WORKQ: Unit Test ... DONE !!!
    [IPU1-0]     86.795613 s:
    [IPU1-0]     86.795613 s:  Current System Settings,
    [IPU1-0]     86.795613 s:  ========================
    [IPU1-0]     86.795613 s:  Display Type   : HDMI 1920x1080 @ 60fps
    [IPU1-0]     86.795613 s:  My IP address  : 192.168.1.200
    [IPU1-0]     86.795613 s:
    [IPU1-0]     86.795613 s:  ============
    [IPU1-0]     86.795613 s:  Usecase Menu
    [IPU1-0]     86.795613 s:  ============
    [IPU1-0]     86.795613 s:

    When building, I set Rules.make to apps and tda2px_evm_bios_all, and ran the following build steps:

    gmake clear

    gmake makeconfig // Is this necessary?

    gmake -s -j depend

    gmake -s -j

    Anything else I'm missing?

    Thanks.

  • It looks like you are building from Processor SDK Radar, not Processor SDK Vision.

    If you look at the ~/apps/src/rtos/radar/src/common/chains_main_bios_radar.c, this is the menu you are seeing and "MISC Tests" is for WORKQ unit test as shown in the log.

    For Vision SDK 3.04 release, you should get the menu from ~/apps/src/rtos/common/chains_main_bios_vision.c and "a: Miscellaneous test's" -> "3: NullSrc (YUV) + Display and Null".
  • I am definitely using the Vision build directory for path and build, as I normally do when working on radar features also. Is there another radar-related configuration setting I may be overlooking to get the vision demo to work?

    Thanks.

  • This only happens if "RADAR_INCLUDE=yes" is set in the cfg.mk under the ~/vision_sdk/apps/configs/tda2px_evm_bios_all.
  • That does not appear to be the case. The showconfig output I posted previously in this thread (7/25) indicates RADAR_INCLUDE=no. Any other ideas I should try?

    Thanks.

  • You can add something to each source file mentioned earlier to purposely generate compilation errors.

    This will tell you for sure which file is getting compiled.

    Another thing you can try is to DELETE the "binaries" folder completely, not just "clean" build.

    This way it will remove all the ".dep" folders and build again from scratch.