• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 381 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Question about vc3 demo.

Jongpil Won
Intellectual 595 points

Hi, I'm using 8168 EVM + Video Conference Daughter board.

I have a general question.

In pre-build package for VC daughter board(sdk_05_00_00_11), there are vc3 binary and two *.xem3 files.

(vc3_m3video.xem3, vc3_m3vpss.xem3 and vc3_a8host_debug.xv5T)

What is the role of *.xem3 files during executing vc3_a8host_debug.xv5t file?

Another question is below.

In that SDK, there are source code for these pre-built package.

I modified make file only for matching developming enviroment, and then run "make vc3" to build two xem3 files and execution file for vc3.

vc3_a8host_debug.xv5T is OK.

But vc3_m3vpss.xem3 and vc3_m3video.xem3 are not built. Instead of them, I can see 4 files.

vc3_m3video_whole_program_debug.xem3
vc3_m3video_whole_program_debug.xem3.map
vc3_m3vpss_whole_program_debug.xem3
vc3_m3vpss_whole_program_debug.xem3.map

I can't run vc3 demo with *.xem3 files which have _whole_program_debug_ .

How can I solve it?

 

Thanks.

Regards,

Jongpil

 

  • 0
    TI__Intellectual 1915 points

    Jongpil,

    The xem3 files are the executables (firmware) for the Media Controllers (M3 cores) in DM8168. vc3_m3video.xem3 is the executable for Video-M3 and vc3_m3vpss.xem3 is the executable for VPSS-M3. There are 2 builds supported in vc3, namely debug and whole_program_debug. The M3 executables are generated accordingly. Debug build, as the name suggests is primarily for debug, whereas the whole_program_debug build generates optimized executables for M3. In the pre-built package, the executbales have been renamed to vc3_m3video.xem3 and vc3_m3vpss.xem3 from their original names vc3_m3video_whole_program_debug.xem3 and vc3_m3vpss_whole_program_debug.xem3.

    In sdk 5.0.0.11, the A8 executable vc3_a8host_debug.xv5T loads the firmware (M3 executables or binaries) on the M3 cores. It therefore assumes that the M3 firmware file names are vc3_m3video.xem3 and vc3_m3vpss.xem3. This assumption is made in the file vc3\src\app_cfg.h as shown below:

    #define DOMX_CORE_SLAVECORE_M3VIDEO_EXEC_NAME   "vc3_m3video.xem3"
    #define DOMX_CORE_SLAVECORE_M3VPSS_EXEC_NAME    "vc3_m3vpss.xem3"

    Therefore, you can rename the generated xem3 files vc3_m3video_whole_program_debug.xem3 and vc3_m3vpss_whole_program_debug.xem3 to vc3_m3video.xem3 and vc3_m3vpss.xem3 and use these to run the vc3 example.

    Having said this, please note that SDK 5.0.0.11 is a April 2011 release and there are updated versions of SDK (EZSDK) available - the latest being 5.3.1.15 (December 2011). I would recommend migrating to this version. The source code for vc3 is available in the form of an Overlay Installer that can be accessed provided you have the requisite NDA in place

    Regards,

    Anirban


     

  • 0 in reply to Anirban Sengupta
    Intellectual 595 points

    Anirban,

    Thanks for your reply.

    As you mention, I'll update my SDK to the newest version.

    Before to do that, I need some confirmation.

    I know that the lastest SDK version(5.3.1.15) doesn't have hdmi driver for capture and vc3 source code.

    So, I need to contact my local FAE to get the vc3 source code and HDMI drivers for capture. To do that, I need some NDA. Am I right?

     

    Thanks.

    Jongpil.

     

  • 0 in reply to Jongpil Won
    TI__Intellectual 1915 points

    Jongpil,

    Yes. That is right.

    Regards,

    Anirban

  • 0 in reply to Anirban Sengupta
    Intellectual 595 points

    Anirban,

    Thanks for your confirmation.

    I'll contact with my local FAE.

    Regards,

    Jongpil