EmbeddedRelated.com
Forums
Memfault State of IoT Report

msp-gdb message?

Started by Martin May 19, 2006
Hi,

does anybody know what this gdb error message means?

This GDB was configured as "--host=i686-pc-cygwin
--target=msp430"..."/home/tst/LCD/test_1": not in executable format:
File format not recognized



Thanks in advance,
Martin.

On 2006-05-19, Martin <uid09012_ti@martin-collins.de> wrote:
> Hi, > > does anybody know what this gdb error message means? > > This GDB was configured as "--host=i686-pc-cygwin > --target=msp430"..."/home/tst/LCD/test_1": not in executable format: > File format not recognized
Please post the complete gdb session (including the command you used to start gdb). Also post the contents of .gdbinit (or whatever it's called on Cygwin systems). Don't attempt to re-type stuff: cut/paste it into the posting without changing anything (including line breaks). -- Grant Edwards grante Yow! The SAME WAVE keeps at coming in and COLLAPSING visi.com like a rayon MUU-MUU...
Hi,

I invoked gdb with:

msp430-gdb test_1

And gdb outputs this:

This GDB was configured as "--host=i686-pc-cygwin
--target=msp430"..."/home/tst/LCD/test_1": not in executable format:
File format not recognized

I've seen that this message doesn't come when msp-gcc is invoked with
the option "-mmcu=msp430x1121" instead of "-mmcu=msp430x449" to compile
and link test_1 in the commandline:

msp430-gcc main.c -o test_1.elf  -mmcu=msp430x449 -O2 -Wall -g

Thanks for any help,
Martin.

Martin wrote:
> > I invoked gdb with: > > msp430-gdb test_1 > > And gdb outputs this: > > This GDB was configured as "--host=i686-pc-cygwin > --target=msp430"..."/home/tst/LCD/test_1": not in executable format: > File format not recognized > > I've seen that this message doesn't come when msp-gcc is invoked with > the option "-mmcu=msp430x1121" instead of "-mmcu=msp430x449" to compile > and link test_1 in the commandline: > > msp430-gcc main.c -o test_1.elf -mmcu=msp430x449 -O2 -Wall -g
I'm not familiar with gdb (i'm a fan of 'printk' at kernel level and background monitoring at embedded level), but it seems to me that you are dealing with different files: 'test_1.elf' for compiler/linker output and 'test_1' for debugger input. May be you should double check which files you are actually using. Regards, Bodo

Memfault State of IoT Report