• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 378 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.

where is the demo code be place? and how does it start when power the EVM?

david ding
Prodigy 10 points

Hi all,

I am a new for DM355. I have a EVM and go through all of the samples on the getting started guide. Now I want to write my application by studying the demo code with the EVM.

As you all know, when the EVM is powered, the video output is a remote graph on the TV. My question are:

(1) Where do I find the source code?

(2)How does the Linux start the code when it powers on?

Best regards,

David

  • 0
    Prodigy 220 points

    There should be a demo folder where ever you extracted the DVSDK. This has some very useful demos. Though I am not sure if the factory boot runs any of those examples. By default, the Davinci boots from flash. The demo program is probably started by a script file in /etc/init.d/ on the flash file system, but you shouldn't concern yourself with that.

    TI's recommended development environment is to setup an NFS drive on a normal Linux machine (Instructions on how to do this are in the getting started guide, spruf73). When you build your program you copy it into the NFS folder. Then you just SSH into your Davinci and run your program from the command line.

     

  • 0
    TI__Mastermind 37340 points

    David,

    1) After you install the DVSDK (assumming DVSDK 1.30.00.40), the demos are under

    dvsdk_1_30_00_40/demos/dm355

    In particular, the source code that outputs the menu controlled by RCU is the "interface" demo

    2) there is a script under /etc/init.d/ (I believe is called 'dvevm') that calls on 'loadmodules.sh' and runs the 'interface' demo.  This scripts is only found in the file system found on the HDD, which is why you see the menu when you boot from the HDD; you could theoretically put the same script in the NFS mount filesystem as well.

    3) Finally, as Chris suggested, during the development phase, you want to work on your more powerful host machine and use TFTP (for kernel changes) and NFS (for user application changes) to quickly change and test your source code.  Only after you got really close to the final software do you want to transition to flashing new kernel/file system onto hardware boards itself (much slower process to test).