• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 53 subscribers
  • Views 830 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.

hello world got the "killed" response and exited.

Michael Yu2
Prodigy 90 points

hi,

 I used  CCS v5_4 to prepare a "hello world" running on dm8168 evm. I got the "killed" response.

 I have no emulators. So I tried to build the "hello world" and then run the a.out via NFS.

 I booted the board from the SD card and  mounted the Debug directory, Lastly run  /home/root/bb/a.out.

The source codes are:

---------------------------

#include <stdio.h>

void main()

{

    puts("hello world\n");

}

-----------------------------

The followings  are the screenshot on  the evm side and the screenshots of the settings in the hello world project.

 

 

 Can anyone help me? Thanks a lot !

Michael

 

 

 

 

  • 0 in reply to desouza
    Prodigy 90 points

    Rafael,

     

    I want to produce an output executable (Hello World)  running on the ARM(Cortex-A8) side of the DM816x evm target.

     

    Now I have installed the CCS v5.4 and the Codesourcery g++ Lite 2009q1-203 on the Ubuntu host. And thank you very much for your providing of the threads above.

     

    After the reading, I have two questions:

    1. which tool (or tools) among the above should  be used to acomplish my goal? (CCS?, Codesourcery?, or both of them?)

    2. If the answer of #1 is 'both of them' , do I have to do things like the thread http://processors.wiki.ti.com/index.php/GCC_-_Create_a_project talking about?

     (but replacing the ccsv4 by ccs v5.4)

     

    Michael

     

  • 0 in reply to Michael Yu2
    Prodigy 90 points

    Hello ,

    Can anyone know the answers of the above questions and tell me? Forgive my poor English... thanks a lot !!

    Best Regards,

    Michael

  • 0 in reply to Michael Yu2
    TI__Guru**** 171819 points

    Michael,

    1. To compile, build your project and debug it using GDB you only need Codesourcery Lite - however, you will have to be skilled in using the command line options for the compiler, as well as be well versed in the GDB commands to debug it. In this particular case CCS is a helper: it is a nice graphical front-end to manage your project, project options, multiple source files, compile/assemble/link the code and debug it using the debugger interface with multiple views of the target. In other words: Codesourcery (or another GNU Compiler Collection tool) is mandatory and CCS is optional.

    2. Yes for creating a project (although there is an updated version of this page here). For debugging, you can check the section Run mode debug of this other page.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 90 points

    Hi, Rafael,

         Thank you very much for your clear explaination.

          I compiled a hello.c by  command-line instruction  "arm-none-linux-gnueabi-gcc hello.c<enter>". And I succeeded in running the resulting executable on the DM8168 EVM target.

         Later, I plugged-in the Codesourcery.into Eclipse.  Creat a "hello world"  C/C++ project in CCS 5.4.  Compiled it  once again. But stuck at the compiling error: bad value (cortex-m4) for -mcpu= switch 

         I do not know how to solve it.

      Best Regargs,

      Michael

     

     

  • 0 in reply to Michael Yu2
    TI__Guru**** 171819 points

    Michael,

    Wow, I wasn't aware that Linux supported Cortex M4 devices, but a quick internet search brought me up to speed (how quickly things evolve...)

    In this case, the 2009q1-203 release does not support cortex-m4 devices (I don't think any commercial device existed in 2009), therefore you will need an updated release of these tools.

    To quickly verify the supported options for the target specifications, simply run

    host@user$ arm-none-linux-gnueabi-gcc --target-help

    Regards,

    Rafael