[ECOS] i386 platform !
Sun Nov 14 17:33:00 GMT 2004
My configuration is described on several mails, I'm going to summarize a little bit:
Target: STPC (i386)
Ethernet Chip: i82559
Gdb link: Ethernet (no serial available)
Host: WinXP, cygwin
I'm sure the network configuration is working fine because this image:
is working fine (gdb connect and I can download and debug an application)
David, the configuration you sent to me is not working with my configuration.
I guess the problem comes from my host. I suspect the XP firewall (gdb.exe is allowed and port 9000 is open but...).
On my configuration gdb starts working fine (see log below) and stops after few packets. Does gdb use another port when the connection is established?
Did gdb debug method changed from the time the image above has been build and today that may explain the behavior on my configuration?
I'm going to test a clean host version on a non firewalled OS (my XP does have a group policy for security) to see if I can connect.
De : Jason Thomas [mailto:email@example.com]
Envoyé : Sunday, November 14, 2004 08:42
À : Gary Thomas
Cc : Jean-François Mullet; Andrew Lunn; firstname.lastname@example.org
Objet : RE: [ECOS] i386 platform !
Are you certain a driver apropriate to your ethernet card is built into
your image of redboot? I had to get a driver specific to my AMD LancePCI
chip. Can you ping the device remotely? Or ping anything from it?
On Fri, 12 Nov 2004, Gary Thomas wrote:
> On Fri, 2004-11-12 at 15:36, Jean-François Mullet wrote:
> > Hi Andrew,
> > I can build an image without any problem; I just cannot connect to it with gdb.
> > I've tested eCos versions (randomly) from two years ago till the last version
> > on CVS and I've never been able to connect with gdb.
> > Sometimes the toolchain is not compatible with the eCos source code (compilation
> > options...) but the error is obvious and an update is easy and fast.
> Are you sure you have communication between your host and the target
> board? e.g. you should be able to connect to the target via a serial
> connection using something like minicom (Linux) or hyperterm (Windows).
> Set the baud rate, etc. You should get the RedBoot prompt. Then to
> test the GDB connection, try typing this: $g#67 You won't see anything
> get echoed, but you should see some characters come back on the
> terminal. If that works, you should be able to get into gdb.
> Once you know the basic communication is working, try this:
> * run GDB on the host
> (gdb) set remotebaud 38400
> (gdb) set remotedebug 1
> (gdb) tar rem /dev/ttyS0 (on Linux)
> (gdb) tar rem com1 (on Windows)
> Let us know if this doesn't help.
> > It would be nice to know on which platform people are using eCos.
> > It seems that x86 is not the most used according the number of
> > relative questions on the mailing list.
> Indeed - the x86 is not really an embedded platform :-) Most eCos
> platforms are based on PowerPC, ARM or MIPS embedded processors.
> > JF
> > -----Message d'origine-----
> > De : Andrew Lunn [mailto:email@example.com]
> > Envoyé : Friday, November 12, 2004 16:01
> > À : Jean-François Mullet
> > Cc : firstname.lastname@example.org
> > Objet : Re: [ECOS] i386 platform !
> > On Fri, Nov 12, 2004 at 02:45:30PM +0100, Jean-Fran?ois Mullet wrote:
> > > Hi,
> > >
> > > I'm trying to setup a redboot image to accept remote gdb debug on
> > > i386 target (which is supposed to be really easy !).
> > >
> > > The only working configuration have been able to use is the prebuild
> > > version actually in CVS which is more than 2 years old.
> > >
> > > Any other prebuild version or any version I can build whatever the
> > > ecos, cygwin and toolchain version I'm using is not accepting gdb
> > > remote connection.
> > How are you building it. I just built one:
> > lunn@londo:~/eCos/work2$ ecosconfig new pc redboot
> > U CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
> > U CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK, new inferred value 0
> > lunn@londo:~/eCos/work2$ ecosconfig import ../anoncvs-clean/packages/hal/i386/pc/current/misc/redboot_FLOPPY.ecm
> > U CYGHWR_HAL_I386_FPU_SWITCH_LAZY, new inferred value 0
> > lunn@londo:~/eCos/work2$ ecosconfig tree
> > lunn@londo:~/eCos/work2$ make -s
> > headers finished
> > /home/lunn/eCos/anoncvs-clean/packages/devs/eth/intel/i82559/current/src/if_i82559.c: In function `i82559_start':
> > /home/lunn/eCos/anoncvs-clean/packages/devs/eth/intel/i82559/current/src/if_i82559.c:1664: warning: implicit declaration of function `memset'
> > /home/lunn/eCos/anoncvs-clean/packages/devs/eth/intel/i82559/current/src/if_i82559.c: In function `i82559_recv':
> > /home/lunn/eCos/anoncvs-clean/packages/devs/eth/intel/i82559/current/src/if_i82559.c:2135: warning: implicit declaration of function `memcpy'
> > /home/lunn/eCos/anoncvs-clean/packages/devs/eth/intel/i82559/current/src/if_i82559.c: At top level:
> > /home/lunn/eCos/anoncvs-clean/packages/devs/eth/intel/i82559/current/src/if_i82559.c:2712: warning: `eth_dsr' defined but not used
> > /home/lunn/eCos/anoncvs-clean/packages/hal/common/current/src/hal_stub.c: In function `handle_exception_cleanup':
> > /home/lunn/eCos/anoncvs-clean/packages/hal/common/current/src/hal_stub.c:457: warning: comparison between pointer and integer
> > /home/lunn/eCos/anoncvs-clean/packages/redboot/current/src/fs/disk.c: In function `find_dos_partitions':
> > /home/lunn/eCos/anoncvs-clean/packages/redboot/current/src/fs/disk.c:94: warning: unused variable `tmp'
> > build finished
> > I don't have an i386 board to test it with, but it seems to compile OK
> > except for some warnings.
> > Andrew
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
More information about the Ecos-discuss