Re:Re: [ECOS] debug i386 application

[Muna Hummady <muna_hummady at yahoo dot com>]

hello everyone
I'm just could connect the i386 host target to the
redboot target via serial. I also could debug the
example programs via the serial.
When I'm trying to establish connection between the
host and redBoot via ethernet following this
procedure:

1- set the host ip-address to "192.168.0.2"
 
2-  (gdb) target remote 192.168.0.10:9000
     a message appear:
        " no route to host"

3- when i"m booting redboot, appear
   " no network card found"
and when I check the ip_address it appear 0.0.0.0.
(i have in the redboot target PC a built in network
controller and also a intel network card , the
connection failed with both"


I dont know why this happened? because I do the
following during building redboot.bin

1- define the ip_address in the redboot.ecc as shown:

    CYGDAT_REDBOOT_DEFAULT_IP_ADDR  "192, 168, 0, 10"

2- enable CYGSEM_REDBOOT_DEFAULT_NO_BOOTP
   user-value 1

 
 
Did anyone have suggestion??????
                   thanks
                   Muna
  

--- Nick Garnett <nickg@ecoscentric.com> wrote:

> Muna Hummady <muna_hummady@yahoo.com> writes:
> 
> > hello
> > 
> > I want to boot the target i386 PC with the RedBoot
> via
> > a floppy and use GDB to load application image
> into
> > the target PC from the host PC via serial line or
> > ethernet.
> > 
> > As in "Embedded s/w development with eCos" 
> > {it is better to use serial port for RedBoot
> > communicationand allow the application to use
> Ethernet
> > port execlusively} 
> > {RedBoot is able to share the portsit uses for
> > debugging and diagnostics with the eCos
> application}
> > 
> > so I'm trying to do so :
> > 1- First, I'm trying to connect the host target
> (i386)
> > to RedBoot via serial (I have only one serial port
> in
> > my target PC) so I'm enable the following option
> in
> > the redboot.ecc 
> >    CYGNUM_HAL_VIRTUAL_VECTOR_DEBUG_CHANNEL  and
> >    CYGNUM_HAL_VERTUAL_VECTOR_CONSOLE_CANNEL  (both
> to 
> >       port 0)
> 
> You should not need to make any changes to the
> RedBoot configuration.
> The default should do exactly what you want. 
> RedBoot starts listening
> on all channels and only locks onto one when it
> detects activity.
> 
> You could also try downloading the prebuilt binary
> from the website
> and use that.
> 
> > 
> > when I'm using the Hyperterminal to load and run
> the
> > basic1 application, it is done correctly. But i
> > couldnt run any other example program (serial, or
> > twothreads),I'm load them and when I'm run them
> using
> > go it is halted and there are no response.
> > 
> > 
> > I could'nt load and debug any example program
> > following the procedure:
> > 
> > (gdb) set remotebaud 38400
> > (gdb) remote target /dev/ttyS0
> > (gdb) load
> > (gdb) continue
> > when doing continue the target PC is halted and
> there
> > is no response.
> > 
> > could you tell me what is the wrong? 
> 
> If you are using a standard RedBoot then you should
> be able to run
> these programs with no trouble.
> 
> As I have said before, start by running some of the
> standard kernel
> test programs, in particular tm_basic.
> 
> > 
> > 2- please could you tell me how to enable both the
> > ethernet and serial ports to have the
> communication
> > via  serial and loading the application via
> ethernet?
> 
> So long as you have an Intel EtherPro 100 card, the
> standard RedBoot
> should bring the ethernet up. There are also
> configurations for
> RealTek 8139 and Intel i8254x based cards.
> 
> -- 
> Nick Garnett                    eCos Kernel
> Architect
> http://www.ecoscentric.com/     The eCos and RedBoot
> experts
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss