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

Can't run executable on OMAP-L138 target

Jimbo
Intellectual 805 points
Other Parts Discussed in Thread: OMAPL138, OMAP-L138

Hi all,

I've got an eXperimeter dev board with the provided Linux kernel build, with both Kernel and NFS running from the Linux host over tftp.  I've gone through the steps for establishing a connection between host and target, and setting up the DVSDK, as described in the OMAPL138 Software Developers Guide.  However I run into problems when I try to run a hello world application on the target.  I can run the executable on the host, in the directory that is mapped to the target, and get the expected message.  When I try to do the same thing on the target itself, I get the following error message.

:line 1: syntax error: "(" unexpected

This looks like a compile time error - any idea what's going on here?

Thanks,

Jimbo

  • 0
    TI__Guru 64500 points

    You mentioned you were able to run the hello world application on your host and get expected output to STDOUT?  Then when you copy this executable to the OMAP-L138 target filesystem and try to run it on the OMAP-L138, you get an error message?

    My first thought is that the hello world has been compiled with the host machine (likely x86 instruction set) and will not run on an ARM926 target.  I don't know if that is the source of the syntax error message, but the fact that the executable runs fine when invoked by your host machine is a red flag for me.

    You need to make sure that when you compile the hello world application, you are using the ARM cross compile tools.

  • 0 in reply to BrandonAzbell
    Intellectual 805 points

    Thanks, that seems like a plausible explanation.  I'll try and get the provided IDE working.

  • 0 in reply to Jimbo
    Intellectual 805 points

    Okay, it's working now.  There was a problem in my make file, and it wasn't picking up the make file in the DVSDK.  Thank you!