• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 1256 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 "killed" on beaglebone

Phillip Norisez
Intellectual 710 points

Other Parts Discussed in Thread: AM3359

I searched a number of different keywords looking for help on this without result, so I decided to post this appeal for help.

I am using a Beaglebone as a development target while our custom board is under design.  I used CCS 5.1.1.00033 to build a Generic CortexA8 Device executable for the HelloWorld project.  I then downloaded the resulting hello.out file to the root directory of my 'bone using tftp (Host as client, 'bone as server).  When I try running the file, all I see on the console is the single word "Killed".  Compiler version TI v4.9.1 producing eabi(ELF).  More info on request.  Help appreciated very much.

  • 0
    Genius 3925 points

    You can install gdb on your target system, then use gdb to debug it.

    For comparison purpose, you can install gcc and the tool chain on the target and build your application there.

  • 0 in reply to Hongfeng Wang
    Intellectual 710 points

    I get the same result from a hello.out built with CCS 5.3.0.00090 as AM3359 [Cortex A] executable on the TI v5.01 compiler.and linker commands from the AM3359.cmd file that came with CCS.

    I am using gdbserver.  When I fire it up I get:

        Process hello.out created; pid = 1579                                          
                                                                                   
        Child terminated with signal = 0x9 (SIGKILL)                                   
        No program to debug.  GDBserver exiting.

    So it is being killed before getting a chance to start.  It seems to me like hello.out is not a compatible executable file.

    I will now try to locate a copy of the toolchain to put on the 'bone. This is going to take a while.

    Meanwhile, the questions:  Am I wasting my time?  Does CCS even support cross development for Beaglebone?

    All I have are free downloads of CCS.  Do I need a paid copy of CSS?

  • 0 in reply to Phillip Norisez
    Genius 3925 points

    as I remember if target arch is wrong, it should give error like "cannot execute binary".

    You can always verify your binary using readelf on your host PC.

    did you enable the -g option when you compile the code?

  • 0 in reply to Hongfeng Wang
    Intellectual 710 points

    Reaqdelf gives no error.

    What is -g option?  I can only manipulate the compiler options that CCS lets me change, and I haven't located it in the list.

  • 0 in reply to Phillip Norisez
    Intellectual 710 points

    CCS, in all its forms, Windows, Linux, 5.1 or 5.3 can't seem to generate a file containing executable code for my Beaglebone.  I don't think it's the kernel either, because the program doesn't work in the Linux sent with the bone either.   

  • 0
    TI__Expert 4245 points

    Hi Phillip,

    Are you using TI compiler to write a hello world program that runs on Linux and you are debugging using gdbserver? I'm not sure that's correct.

    Why don't you use GCC that comes with Linux SDK instead? The TI compiler is probably generating bare metal .out rather than a Linux program i.e eabi whereas Linux is gnueabi. If you are trying bare metal programming i.e without Linux running on the target, then you should be able to load the .out via JTAG and run/debug using CCS itself.

  • 0 in reply to Siddharth Heroor
    Intellectual 710 points

    Thanks, Sid!  That was the hint I needed.  When I reinstalled CCSv5.1.0.00033 using the instructions in http://processors.wiki.ti.com/index.php/Code_Composer_Studio_v5_Users_Guide and built my helloworld it works!

    However, I also received the same messages documented by 's "Linker message when compiling example application" post in the Sitara™ ARM® Microprocessors forum.