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.

DM6437 EVP hosapp not run

Other Parts Discussed in Thread: TMS320DM6437, DEMOAPP-DM6437, CCSTUDIO

Hi. I have got DM6437 DVDP and I have some problems: I probe demo6437_demo program (executed on start) and I can’t connect hostapp with device. I know the device is running because audio line in is on audio line out (with SW4-3 down). The 4 LEDs are off (even DS1, with both SW7 position). “Getting started Guide” document describes that DS2 LED might be ON when the IPstack is ready. By default, demo is configurated in DHCP mode, so I connect board to a router whit DHCP activated, and through my computer host (where I try to connect with “hostapp”). I check connections in router and I find 192.168.1.105 to client host “dm6437evm9def” and 192.168.1.106 for the host. I think all is correct, by it happens three troubles: 1. I can’t do ping from host to board (from 192.168.1.106 to 192.168.1.105) 2. LED DS2 is off 3. hostapp can’t connect to board (both button “discover” and connect to 192.168.1.105 )

Please, could you help me?. I’m very frustrated.

  • Hello Pablo,

    Could you tell me which version of DVSDK you are running?  I am running with DVSDK_1_01_00_15 and it is working just like the starting guide.  Do you run the Demo start from Sect. 3.3 of the starting guide?  You might also need to check your ethernet connection.  My PC and the EVM are connecting to the same Ethernet switch.  You can download the DVSDK I was using from here: http://processors.wiki.ti.com/index.php/TMS320DM6437_DaVinci_Technology_One-Day_Workshop.

    Regards,

    Viet

     

  • Hi.

    Thanks for your response. I use the same version of yours (DVSDK_1_01_00_15, I think is the same like workshop you mention), I use Code composer 3.3 (it's in purchased CD) and I follow the steps in 3.3 point of User Guide. I have other considerations:

    • I can't recompile the project (just I receive from CCS a message that XDC/std.h is not found, and when I compile the project,  compilation fails). To avoid loosing my dm6437_demo objet file in this fail (CCS erases .out files when I rebuild the project...) and can load it in board, I made a copy before the compilation attempt. I search for info about this problem, and I found a lot of people with problems like mine. I don't check them deeply, but I think is due for dependencies/conflicts with different versions of CCS 3.3 package and demo6437 package...Maybe you know what would it be...For this problem, I can't, at the moment, change DHCP ip in device for static IP, and for that , I need a router with DHCP assignament.
    • I have dm6437_demo_1_30_00.
    • I checked that board works, with test examples installed with the package (I don't check ethernet test, because I need loopback connector, but others works fine)
    • I use a virtual Machine XP on SP host machine (all CCS & EVM SW packages are installed here on VM) with ethernet interface in bridge mode, but I think this shouldn't be a problem (I check my host, my VM host and device are in the same subnet/LAN, through DHCP statics in router. Moreover, I can make ping from VM to host)

    Well, I don't know what to do...

     

     

  • Hello Pablo,

    I have the CCS v3.3 with SR12.  If you don't have it, you can download and install from ti.com.

    I am using the same dm6437_demo_1_30_00 like yours.  I attached the host app executable that I was using for you to verify your setup.  If it ran Ok, then there is something wrong with your ethernet setup.  I do not use VM ware, just window XP prof.

    The std.h is in C:\dvsdk_1_01_00_15\xdc_2_95_02\packages\xdc.

    Regards,

    Viet

    dm6437_demo.out
  • Hi.

    Thanks.  I knew this file (std.h) is in that path, but is strange that message (a popup appears  in CCS opening dm6430_demo_1_30_00 project, saying "Cannot find xdc/std.h") without compiling. After compiling, compiler says fails in opening this file too. I suppose it's necesary change something in some paths or files to associate this file with the path that you say. I checked I have too in this path...

    I will check your .out, but is strange that router shows IP associated to device and led DS2 on board is OFF (I don't know if must be ON when the IP is asigned, I understand through User guide that it should be ON ). I send you my client .out (I use file on Debug directory!!) and maybe you can check if works fine on your board...

    Bufff...

    Thanks a lot, I'm very pleased for your tips and responses3755.dm6437_demo.zip

  • Well. I check some posts and I find some possibilities to fix my problem.

    I had two installation for BIOS (5.31.02 & 5.31.07), and demo6437 compiles with 07. For that, I desintalled 02 version and changed enviroment variable to 07 version in my host.

    I checked  "component manager"  in CCS3.3 ( 3.3.38.2), and associated BIOS 5.31.07. The information is Code generation v6.0.8 Board revision 0.0.0 , target revision 0.0.0, adn correct BIOS

    I checked in "C:\dvsdk_1_01_00_15" two xdc files: C:\dvsdk_1_01_00_15: xdcpaths (mak file) and xdcpaths_evmDM6437 (data file) (I don't know what to do now, and I don't know how this files affect the CCS enviromentment. )

    I realized that in xdcpaths there was incorrect path for XDC_PATH entry XDC_INSTALL_DIR   := $(DAVINCI6437_INSTALL_DIR)/xdc_2_91_02 and I had xdc_2_95_02, for that I changed it.

    The problem is present yet, the enviroment don't find std file.

    I will be pleased for your tips...

     

     

     

     

  • Hello Pablo,

    It must be your setup because I can run your built demo and it works perfect.

    Regards,

    Viet

  • Ups!

    Well., thanks for your probes and response.

    Do you know what changes should I make in my IDE?

    How do you have your environment configurated?

     

    Thanks a lot

  • Finally I could compiled it!!!

    But, I  load .out program (in Debug directory) and it's not working fine: there is no image in ouput and if I put break point in first line of void main, never reaches that!

    (...)

    int main(int argc, char *argv[]) {

      int status = 0;

      /* init the codec engine runtime */
      CERuntime_init();   <----- HERE
    (...)

     

    Does anyone know what it happens? Maybe project is different that in flash is loaded...

    Thanks a lot

  • Pablo,

    It seems to be a CCS setup problem so I am moving this issue to CCS support for help.

    Regards,

    Viet

  • Finally I could compiled it!!!

    But, I  load .out program (in Debug directory) and it's not working fine: there is no image in ouput and if I put break point in first line of void main, never reaches that!

    (...)

    int main(int argc, char *argv[]) {

      int status = 0;

      /* init the codec engine runtime */
      CERuntime_init();   <----- HERE
    (...)

     

    Does anyone know what it happens? Maybe project is different that in flash is loaded...

    Thanks a lot

  • Pablo,

    Which CCS version are you using?  If it is not v3.3 with SP12, can you upgrade it so we can compare apple to apple here?

    Regards,

    Viet

  • I use CCS 3.3.38.2 updated (checked from available updates TI site).I use DM6437

    I have a lot of problems with every projects using BIOS/PSP. I can't debug this projects, and I have doubts programs are executing correctly. Only test examples(included in CCS/boards/DM6437 folder) work.

    I followed steps in "C6000 Embedded Design Workshop Using BIOS" (all files downloaded) and I could create a project with BIOS to process audio-in and give it on output. In this case, I can debug. I understand GUI and utilities/tools.

    But I need processing video from one camera and give it in output DAC (this workshop uses audio codec only). I found "Accessing_Pixels_In_A_Frame_1_03"  based in "video_preview" doing that, but I can't debug.  I recompile "video_preview" and there's no troubles, I load it and it runs (CCS tells me "running"), but I can't  "go to main", stopping in breakpoints (SW/HW). I see video camera in output,  but I think the program loaded in flash (default program) is executing and not RAM downloaded program ...

    I think examples/samples in dm6437 folder (dvsdk_1_01_00_15) doesn't work. PSP examples in same folder don't work too.

    How can I resolve this problems?? have anyone programs/tutorial to doing video processing with BIOS/PSP??

    Thanks a lot!

  • Pablo,

    Please try to run from CCS with the attached video_preview.out to see if you get any video output.  I am using NTSC composite input to DM6437 from DVD output and S-Video DM6437 output to the TV and it works great.

    Regards,

    Viet

    video_preview.out
  • Hello!

    Welle, finally I found the solution thanks to  "Sankaranarayanan B" in DSPRelated Forum. I resolved my problems: I should changing GEL file, downloaded from Digital Spectrum web, and then, all projects ran fine.

    Thanks a lot!

  • Pablo,

    Thank you very much for your feedback.  I don't recall to use any GEL file when I run the example.  Could you post the link of the GEL file you use in case other customer has the same problem?

    Thanks,

    Viet

  • Yes, of course. The link with GEL file it works fine in my EVM is:

     

    http://c6000.spectrumdigital.com/evmdm6437/reve/files/evmdm6437.gel

  • Hi again.

    I try to use new version "demoapp-dm6437" downloaded from "http://focus.ti.com/docs/toolsw/folders/print/demoapp-dm6437.html#Technical%20Documents", but when I compile it I have this error:

    js: "C:/dvsdk_1_01_00_15/xdc_2_95_02/packages/xdc/cfg/Main.xs", line 170: exception from uncaught JavaScript throw: Error: incompatible use of package 'ti.rtdx': imported ti.rtdx [2,0,0,5,0], ti.bios.utils was built with ti.rtdx [], ti.bios.log.support was built with ti.rtdx [], ti.bios.log.ndk was built with ti.rtdx []; incompatible use of package 'xdc.bld': imported xdc.bld [1,0,0,0,1183011756898], ti.rtdx was built with xdc.bld [1, 0, 1], ti.pmi was built with xdc.bld [1, 0, 1], ti.pscl was built with xdc.bld [1, 0, 1], ti.bios was built with xdc.bld [1, 0, 1]; incompatible use of package 'xdc': imported xdc [1,1,0,0,1183011749422], ti.rtdx was built with xdc [1, 1, 1, 0], ti.pmi was built with xdc [1, 1, 1, 0], ti.pscl was built with xdc [1, 1, 1, 0], ti.bios was built with xdc [1, 1, 1, 0]
    Adding the following line to your configuration script:
        environment['xdc.cfg.check.fatal'] = 'false';
    converts this incompatibility error into a warning. Please, check the documentation for the package xdc.cfg for more information.
        "C:/dvsdk_1_01_00_15/xdc_2_95_02/packages/xdc/xs.js", line 137
    gmake.exe: *** [package/cfg/dm6437_demo_x64P.c] Error 1
    gmake.exe: *** [package/cfg/dm6437_demo_x64P.c] Deleting file `package/cfg/dm6437_demo_x64Pcfg.cmd'
    gmake.exe: *** [package/cfg/dm6437_demo_x64P.c] Deleting file `package/cfg/dm6437_demo_x64Pcfg_c.c'
    gmake.exe: *** [package/cfg/dm6437_demo_x64P.c] Deleting file `package/cfg/dm6437_demo_x64Pcfg.s62'

    *************************
    Configuration step failed.
    *************************

    Explanation:
    -----------
    A configuration script threw an exception (error).
    Please look at the highlighted script name and line number above to determine what could be the cause of error.


    Please review the above information carefully to correct this configuration error.


    I don't know how documentation check and what is the problem. Anyone could me help??

    Thanks a lot.

  • Again,after resolving a lot of problem with version SW, I compile this new version...

  • Hi Pablo,

     plz post the link  , where u got the solution .

  • You have to check all paths are correct: check XDC configuration (for example, at the building begining). This paths that work fine in my machine are:

    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_07\packages
    C:\dvsdk_1_01_00_15\xdc_2_95_02\packages

    For that, you must have installed CCS3.3, dvsdk_1_01_15 (version attached with EVM6437 sw kit) and BIOS 5_31_07 (you can update with component manager in CCS3.3)

    I hope you could resolve the problems...

     

    By