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

DM8168 DVR RDK

tkCheng
Intellectual 810 points

Hi All.

I am working on DM8168 DVR RDK from udworks. I would like to know is there a better way to achieve the following during development:

1. Restart the DVR RDK application without reboot the whole unit - to avoid wasting time waiting unit reboot and speed up development.

2. Besides using printf to get the status, any there a better way that enable me to steps through the application during debugging? Is XDS-560 JTAG emulator helpful in this case?

Thank you very much.

Best regards,

Cheng

  • 0
    TI__Expert 7765 points

    Cheng,

    For #1,

    If your changes are only on A8 you can exit the DVR RDK application by pressing 'e' and tarnsfer only updated .out to targetfs and re-run the application. This applies if the application gracefully exits. If your A8 application gets  stuck in execution  you can try ctrl + c to come to prompt after that you can choose to reload m3 and rerun your application with changes. Remember you can save your build time also by building specifically only for A8 using make -s dvr_rdk_linux, similarly it applies for m3 side changes make -s dvr_rdk_bios.

    If your changes are only on m3 you need not restart entire system. you have to exit A8 side app by above methods and then run unload.sh followed by load.sh This will load your updated m3 binaries from target fs.

    For #2,

    XDS-560 JTAG will help you debugging only with m3/dsp side code. You can connect m3s/dsp after you execute load.sh in you running sequence. For A8 side debug you can use prints and gdb.

    Regards,

    Yogesh.

     

  • 0 in reply to Yogesh Marathe
    Intellectual 810 points

    Hi Yogesh,

    Question 1:

    I believe the 'e' command is apply on McFw demo that is describe in document DM81xx DVR RDK Demo Guide. But the application I refer to is the DVR RDK application with full DVR functionality (GUI, storage and playback function etc) as describe in document DM8168 DVR RDK Application and GUI Guide. Is the above method still apply on this applications?

    Qustion 2:

    For the GUI application, is there any guide I can use to remotely debugging the application using gdb? Any guide/document that I can refer to import the whole DVR RDK on A8 into eclipse to ease my development and debugging.

    Best regards,

    Cheng

  • 0 in reply to tkCheng
    TI__Expert 7765 points

    Cheng,

    For #1, In case of GUI based application I guess ctrl+c should still work, I agree 'e' applies only to demo but once you get to the prompt you should be able to reload and rerun the app without rebooting.

    For #2, you can telnet to board and then use gdb or you can modify scripts to run programs in background by appending '&' to commands in initial scripts (init.sh and load.sh) . We have not tried that but it should work. ip address you can get from the boot log when you start the board in case if you want to telnet. There is no user guide specifcally for gdb and eclipse usage for DVR RDK.

    Regards,

    Yogesh.