Sorry, my mistake... Forget about what I wrote, the gdbserver is working fine.
Now another question: I have to give a port number and also the hostname IP address. That's what I did (and as already said, works fine). This is the output of the gdbserver running on FoxBoard: gdbserver 192.168.123.140:2345 i2c Process i2c created; pid = 140 Listening on port 2345 192.168.123.140 is the IP address of the PC running Linux in a VMware session, 2345 is just "a" port number I gave. So far, so good, I would think... Now I'm having DDD up and running, using the gdb-cris debugger, not the standard gdb (started as follows: "ddd --debugger gdb-cris &"). What are the next steps to take? How can I instruct DDD to start my app on the FoxBoard? What about the port number? Best rgds, --Geert --- In [email protected], "Geert Vancompernolle" <[EMAIL PROTECTED]> wrote: > > Hi Kirby et al, > > I've put my first steps in FoxBoard debug land. I compiled the I2C > example of John (Phrozen SDK), located in /apps/i2c and when starting > up the gdbserver on the FoxBoard like this: > > gdbserver 192.168.123.140:2345 ./i2c > > I get the following error: > > gdbserver 192.168.123.140:2345 ./i2c > Process ./i2c created; pid = 6604 > Cannot exec ./i2c: Exec format error. > > Child exited with retcode = 7f > Listening on port 2345 > > Whether I'm using ./i2c or i2c, that doesn't make any difference... > > Any idea why I get this error? > > If I look using the "file" command, I don't see any abnormal problems: > > file i2c > > i2c: ELF 32-bit LSB executable, version 1 (SYSV), for GNU/Linux 2.4.5, > dynamically linked (uses shared libs), for GNU/Linux 2.4.5, not stripped > > Best rgds, > > --Geert >
