[solved]Problems while building dm6437_demo

I believe the problem here is likely a versioning issue, you are using BIOS 5.31.02 but the DM6437 1.01.00.15 DVSDK including the demo was built around BIOS 5.31.07, I would not be suprised if this difference alone is causing the build failure though it could also be related to other tool versions. You can get updated tool versions from the update advisor available under the help menu of CCS.

I can say that the demo application builds with CCS 3.3.75.5, BIOS 5.31.08, CGT 6.0.8, as I just tested building it now.

Thank you, I was able to build it but waiting to run properly before posting it out.

My problem was in the xdcpaths.mak files, which is corrected now.

BUT, now, when I run the demo or other engine examples, I get codec errors. So the example applications dont run properly now. Now I will try to build them with latest tools and see if they run properly.

SOLVED:

OK, as a newbie, this took a lot of time.

But it seems that the source of the codec errors are using bios_5_31_02 instead of bios_5_31_07 or a later version.

Here is a quick guide for new starters like me: (later I will detail it)

To correct this, check the environment variables, because my CSS version installs bios_5_31_02 defaultly, and sets the related environment variable to this version. To use the a later bios version, first correct this. Then, uninstall bios_5_31_02 to avoid conflictions. Run the component manager from start/all programs/texas instruments/.../ and adjust the Target Content(dsp/bios) to bios_5_31_07.

Rebuild the project and it shall run properly.

Problem Definition:

I am not able to build it with the latest tools beucase I couldn't set the compiler to use bios_5_31_07 instead of bios_5_31_02.

When I rebuild it:

[dm6437_demo.cfg] "C:\dvsdk_1_01_00_15\xdc_2_95_02\xs.exe" xdc.tools.configuro.ccs  --xdcpathsfile="xdcpaths.dat" -pti.platforms.evmDM6437 --tcf -t ti.targets.C64P -c "C:/CCStudio_v3.3/C6000/cgtools" --bios "C:/CCStudio_v3.3/bios_5_31_02" -o "xdcconfig" dm6437_demo.cfg

Info: running XDC configuration using package path:
C:\dvsdk_1_01_00_15\codec_engine_1_20_02\packages
C:\dvsdk_1_01_00_15\codec_engine_1_20_02\examples
C:\dvsdk_1_01_00_15\framework_components_1_20_03\packages
C:\dvsdk_1_01_00_15\xdais_5_21\packages
C:\dvsdk_1_01_00_15\codecs_1_10\packages
C:\dvsdk_1_01_00_15\ndk_1_92_00_22_eval\packages
C:\dvsdk_1_01_00_15\biosutils_1_00_02\packages
C:\dvsdk_1_01_00_15\examples\common\evmDM6437
C:\CCStudio_v3.3\bios_5_31_02\packages
C:\dvsdk_1_01_00_15\xdc_2_95_02\packages

I couldn't set this to bios_5_31_07. How can I do that?

Also it rebuilds the project in this way, but when I run it:

********************************************************
*  Welcome: DM6437 Demo Application 1.30.00
********************************************************
Performing System Initialization...
Performing System Configuration...
Settings: loopback PAL QD1
Performing System Create...
Starting up the Network...
Using MAC Address: 00-0E-99-02-97-81
NDK - Service Status: DHCPC    : Enabled  :          : 000
NDK - Service Status: HTTP     : Enabled  :          : 000
NDK - Service Status: DHCPC    : Enabled  : Running  : 000
Performing System Startup...
000001 Control........... Play loopback
RPCS service is started
System OK
000002 VideoDecode....... ERROR VIDDEC_process(), h264dec  extendedError=0x00000000003 Control........... Stop

I get an error like this. I don't know what to do and I spent a great amount of time on this...

I can see three places you may need to change to get the project to recognize the proper BIOS version:

1. The component manager of CCS under the help menu, this tells CCS what BIOS you want to build with.
2. The xdcpaths.mak file in the root DVSDK directory, this contains a BIOS_INSTALL_DIR variable that has to be set correctly, this tells the xdc tools what BIOS you want to build with.
3. Windows system environment variables, right click on your 'my computer' icon and select properties, than the advanced tab, than the environment variables button, in here you likely have a system variable called BIOS_INSTALL_DIR that should be pointed to the BIOS version you want to build with, this tells anything else that could possibly be referencing BIOS_INSTALL_DIR what version you want to build with.

EDIT: It sounds like you already found the problem, I am glad to hear that your codec errors were resolved with a newer BIOS version.

I have problems similar to those described by Elric. I have changed the bios version to BIOS 5.31.07 in both, the code composer and Windows environmental variables. This did not seem to have an effect.

A) Identifiers are "unidentified".

I will look in the xdcpaths.mak file and see if I can fix this.

B) I get the error message:

[dm6437_demo.cfg] "C:\dvsdk_1_01_00_15\xdc_2_95_02\xs.exe" xdc.tools.configuro.ccs  --xdcpathsfile="xdcpaths.dat" -pti.platforms.evmDM6437 --tcf -t ti.targets.C64P -c "C:/CCStudio_v3.3/C6000/cgtools" --bios "C:/CCStudio_v3.3/bios_5_31_07" -o "xdcconfig" dm6437_demo.cfg
js: "./xdc/xdc.tci", line 314: org.mozilla.javascript.Undefined@182da3d: no property named 'xdc.tools.configuro.ccs'
    "C:/dvsdk_1_01_00_15/xdc_2_95_02/packages/xdc/xs.js", line 132

I can't seem to find what is wrong here. Could please you advise about how to fix this one?

Fixed A)

The compiler.opt and xdcpaths.mak files had xdc_2_94_01 directory in their path instead of xdc_2_95_02.

Still have problem B).

BogdanDzyubak said:

B) I get the error message:

[dm6437_demo.cfg] "C:\dvsdk_1_01_00_15\xdc_2_95_02\xs.exe" xdc.tools.configuro.ccs  --xdcpathsfile="xdcpaths.dat" -pti.platforms.evmDM6437 --tcf -t ti.targets.C64P -c "C:/CCStudio_v3.3/C6000/cgtools" --bios "C:/CCStudio_v3.3/bios_5_31_07" -o "xdcconfig" dm6437_demo.cfg
js: "./xdc/xdc.tci", line 314: org.mozilla.javascript.Undefined@182da3d: no property named 'xdc.tools.configuro.ccs'
    "C:/dvsdk_1_01_00_15/xdc_2_95_02/packages/xdc/xs.js", line 132

I have not seen that particular error message come up myself, but I suspect that it is also some pathing issue, perhaps something got changed while you were trying to fix the first issue? That particular package it is seeking should exist within C:\dvsdk_1_01_00_15\xdc_2_95_02\packages\xdc\tools\configuro\ccs which it should be able to find if there are no bad paths.

I think I didnt get an error message like this too. If you are sure that every path is corrected in the project files, you may check your enviromental variables by right clicking My Computer and going to Properties/Advance. If there is a same named enviromental variable with one in your project files, and the paths are different, it may be a problem since the Windows enviromental variables have higher priority than in your files.

Fixed the error. It was a result of a me making an earlier mistake of copying a file into a directory instead of rewriting the path.

I was able to build the project successfully. Now, I am trying to compile. CCS is looking for libraries in the /lib directory. I am using Windows so that directory does not exist. What is the best way to fix this problem?

Also, I have the error with some files  not being able to find evmdm6437.h I initially solved it by adding the correct path to compeler.opt. This is a system generated file, however. Is there a better way to do this?

Thank you for your help so far! I appologize for my lack of experience with this.

For your library issue, you should be able to show the linker where your libraries are within the Project -> Build Options -> Linker Tab -> Libraries Category, here you can specify library search paths allowing you to direct the linker to where it should find libraries.

As to the header file you should be able to fix this also with the same menu, Project -> Build Options -> Compiler Tab -> Preprocessor Category, this has an include search path option where you can define folders that hold header files.

Hello!

I have a problem with running the demos with the PC Host Application.

When I'm  trying to start the host-side demo application and run the run.bat file from C:\dvsdk_1_xx_xx_xx\dm6437_demo_x_xx_xx\hostapp directory and click the Discovery button to find the IP adress of the EVM board,there occur a error: could not locate any DM6437EVM demo-running targets on the network.

I would like to know how I can correct this error?

Thank you!

How well the discovery capability works depends on your local network configuration, if your board and the PC are connected to a corporate network it is possible that they are blocking the messages that are necessary for the automatic discovery to work, if they are both connected to a local switch and router (dhcp server) than it should generally work. One example of discovery not working that I have seen is if the host is on a WiFi connection and the target board is connected to the network via cable, not to say this setup would never work but it did not for me (I believe this has to do with WiFi in my setup being on a different subnet).

Even if the discovery does not work it is still possible to run the demo however, it just means that you need to find the IP address of the board through alternate means. In particular if you load the demo from CCS as opposed to booting it from flash in a stand alone situation than you can see the IP address on the standard output messages coming from the board within CCS allowing you to manually configure the host application with the proper board IP. An alternative and tricker method would be to look at your DHCP server (router) status and see what IP address it assigned to the board, though this may or may not be possible depending on your network.

I used the Ethernet cable to connect  the EVM's Ethernet connector to the PC  workstation to enable the host-side part of the demo application (according to Getting Started Guid that I received with the DVDP.)

So the board and the PC are directly connected by the Ethernet cable.It is correctly or I have to use a switch?

Thank you!

The direct connection will only work if you use a cross over cable or your PC has an autodetecting interface, and your PC is running a DHCP server or the board is configured for a static IP. Out of the box the board will be configured for DHCP so to have it work with the host application it needs a DHCP server, the typical way of meeting this requirement is to have both the board and the host PC on the same local network with a regular broadband router, or even potentially a corporate network.

You can use a static IP and a direct PC connection by modifying app_main.c to have "static" in place of "dhcp" around line 372, as well as potentially adjusting the rest of the network information (change the IP address and such). With the change in place just rebuild the demo and load it to the board.

I agree this is a limitation of the getting started guide, as it makes no mention of the network configuration required to get the demo to work properly.

Hello,

I have the same problem with sth.h and I donn't know how to correct xdcpath.mak.Can you help me with this?

Thank you,

Eve M

I'm trying now to buil the project  dm6437_demo.pjt  but it finds a lot of undefined symbols during the build as shown below. I suspect some file(s) containing those symbols definitions are missing. Where should those symbols be defined?

"undefined                        first referenced
 symbol                              in file
---------                        ----------------
_VPBEMD_FXNS                     C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\package\cfg\dm6437_demo_x64Pcfg.o64P
_llTimerTick                     C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\package\cfg\dm6437_demo_x64Pcfg.o64P
_EVMDM6437_EDMA_AIC33_FXNS       C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\package\cfg\dm6437_demo_x64Pcfg.o64P
_NDK_hookInit                    C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\package\cfg\dm6437_demo_x64Pcfg.o64P
_RSZMD_FXNS                      C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\package\cfg\dm6437_demo_x64Pcfg.o64P
_VPFEMD_FXNS                     C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\package\cfg\dm6437_demo_x64Pcfg.o64P
_EVMDM6437_EDMA_AIC33_init0      C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\package\cfg\dm6437_demo_x64Pcfg.o64P
_I2CMD_FXNS                      C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\package\cfg\dm6437_demo_x64Pcfg.o64P
_NDK_hookCreate                  C:\dvsdk_1_01_00_15\dm6437_demo_1_30_00\xdcconfig\package\cfg\dm6437_demo_x64Pcfg.o64P
_PSP_VPFE_TVP5146_Close          C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_block_video_input.obj
_PSP_VPFE_TVP5146_Open           C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_block_video_input.obj
_PSP_VPFE_TVP5146_Control        C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_block_video_input.obj
_fdClose                         C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_socket                          C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_fdOpenSession                   C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_recv                            C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_send                            C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_listen                          C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_accept                          C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_fdError                         C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_bind                            C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_fdCloseSession                  C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_setsockopt                      C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ipc_nw.obj
_edma3init                       C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_main.obj
_inet_addr                       C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_CfgNew                          C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_mmCopy                          C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
__oscfg                          C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_DaemonFree                      C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_CfgFree                         C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_NC_NetStart                     C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_NC_SystemOpen                   C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_DaemonNew                       C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_recvncfree                      C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_sendto                          C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_mmZeroInit                      C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_NC_SystemClose                  C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_CfgAddEntry                     C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_recvncfrom                      C:\\dvsdk_1_01_00_15\\dm6437_demo_1_30_00\\Debug\\app_ndk.obj
_efs_createfile                  C:\dvsdk_1_01_00_15\biosutils_1_00_02\packages\ti\bios\log\ndk\lib\logservercgi.a64P
_CONTENT_TYPE_APPLET             C:\dvsdk_1_01_00_15\biosutils_1_00_02\packages\ti\bios\log\ndk\lib\logservercgi.a64P
_httpSendClientStr               C:\dvsdk_1_01_00_15\biosutils_1_00_02\packages\ti\bios\log\ndk\lib\logservercgi.a64P
_httpSendStatusLine              C:\dvsdk_1_01_00_15\biosutils_1_00_02\packages\ti\bios\log\ndk\lib\logservercgi.a64P
_efs_destroyfile                 C:\dvsdk_1_01_00_15\biosutils_1_00_02\packages\ti\bios\log\ndk\lib\logservercgi.a64P
_CRLF                            C:\dvsdk_1_01_00_15\biosutils_1_00_02\packages\ti\bios\log\ndk\lib\logservercgi.a64P
_CONTENT_TYPE_HTML               C:\dvsdk_1_01_00_15\biosutils_1_00_02\packages\ti\bios\log\ndk\lib\logservercgi.a64P
>>   error: symbol referencing errors - './Debug/dm6437_demo.out' not built

>> Compilation failure

Build Complete,
  2 Errors, 0 Warnings, 0 Remarks."

Can you help me with this?

Thank you!

            Eve

These undefined symbol errors most likely mean that there is some path incorrect in your project such that it cannot find the libraries that contain these symbols, in particular you probably need to ensure it can find the libraries in C:\dvsdk_1_01_00_15\ndk_1_92_00_22_eval\packages\ti\ndk\lib and C:\dvsdk_1_01_00_15\psp_1_00_02_00\pspdrivers\lib\DM6437\Release which look to be the libraries that contain these. There may be errors prior to the listing you show here that may shed more light on why this would be happening, off the top of my head I would suspect either an environment variable with a path is incorrect or your xdcpaths.mak has an incorrect path in it.

Can you tell me what changes did you made to the xdcpaths.mak in order to make it work?

 There are some incorrect paths in xdcpaths.mak ,for example :

CE_INSTALL_DIR    := $(DAVINCI6437_INSTALL_DIR)/codec_engine_1_20

instead CE_INSTALL_DIR    := $(DAVINCI6437_INSTALL_DIR)/codec_engine_1_20_02

and others errors like this one.

I have a problem when I'm trying to run the demo application in preview mode:

it must simply  captures video/audio from the input video/audio device and sends it to the display/speaker.

The video works,but audio doesn't.

For encode+decode loopback mode I have the same problem,but in decode from file mode the speaker works.

There is any problem with the speaker and the microphone,they can not work simultaneous?

Can you tell me how can I correct this?

Thank you!

Eve

Hi all,

I am having a similar problem, I have connect the board and  the PC via a Dlink router and I configured the IP address of the board to be static (IP: 192.168.1.100) I also set static IP for the PC (IP: 192.168.1.200) but I did not work.

I changed the setting of the IP to be dynamic (dhcp) and I made the PC IP automatic but still does not work.

I tried also connecting the board directly to the PC in both case still nothing work. .............

I don't know what is wrong .......... and the Getting started guide TI mentioned nothing about this seeming it simple connection.

I hope somebody has answer to my quires 

Hi all,

I am having a similar problem, I have connect the board and  the PC via a Dlink router and I configured the IP address of the board to be static (IP: 192.168.1.100) I also set static IP for the PC (IP: 192.168.1.200) but I did not work.

I changed the setting of the IP to be dynamic (dhcp) and I made the PC IP automatic but still does not work.

I tried also connecting the board directly to the PC in both case still nothing work. .............

I don't know what is wrong .......... and the Getting started guide TI mentioned nothing about this seeming it simple connection.

I hope somebody has answer to my quires

Please, I wrote a new post related with your explanations. Could you take a look??

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/99/t/190175.aspx

Thanks a lot