public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Venkatesh" <venkatc@in.ceeyes.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>,
	Venkatesh <venkatc@in.ceeyes.com>,
	ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Facing problem with i82559 driver...
Date: Tue, 06 Aug 2002 05:21:00 -0000	[thread overview]
Message-ID: <200208061051.g76ApuE16174@in.ceeyes.com> (raw)

Hi Andrew,
This is the snapshot which we we observed during debugging thro GDB.
This will be of better help for you.
Please guide us in this process.

Thanks in Advance.
Venkatesh.

******************************************************************

(gdb) b i82559_init
Breakpoint 1 at 0x10d10a: 
file //D/eCOS/packages/devs/eth/intel/i82559/current/src/if_i82559.c,
(gdb) c
Continuing.
intel_i82559_init
[New thread 1]
[Switching to thread 1]

Breakpoint 1, i82559_init (ndp=0x134f40)
    
at //D/eCOS/packages/devs/eth/intel/i82559/current/src/if_i82559.c:1311
1311        sc = (struct eth_drv_sc *)(ndp->device_instance);
(gdb) n
1312        p_i82559 = (struct i82559 *)(sc->driver_private);
(gdb) n
1314        IF_BAD_82559( p_i82559 ) {
(gdb) n
1323        if ( 0 == initialized++ ) {
(gdb) n
1325            if ( ! pci_init_find_82559s() ) {
(gdb) n
pci_init_find_82559s()
Finished cyg_pci_init();
eth0 = 82559
 Wired to HAL vector 43
Found device on bus 0, devfn 0x40:
 Note that board is active. Probed sizes and CPU addresses invalid!
 Vendor    0x8086
 Device    0x1229
 Command   0x0007, Status 0x0290
 Class/Rev 0x02000008
 Header 0x00
 SubVendor 0x8086, Sub ID 0x000c
 BAR[0]    0xe1100000 / probed size 0x00000000 / CPU addr 0xe1100000
 BAR[1]    0x00006401 / probed size 0x00000000 / CPU addr 0x00006400
 BAR[2]    0xe1000000 / probed size 0x00000000 / CPU addr 0xe1000000
 BAR[3]    0x00000000 / probed size 0x00000000 / CPU addr 0x00181f6c
 BAR[4]    0x00000000 / probed size 0x00110232 / CPU addr 0x0001f5c0
 BAR[5]    0x00000000 / probed size 0x0013a9a0 / CPU addr 0x00135f98
 eth0 configured
 memory address = 0xe1100000
 I/O address = 0x00006400
 **** Device enabled for I/O and Memory and Bus Master
1334        if (0 == p_i82559->found)
(gdb) n
1337        p_i82559->mac_addr_ok = 0;
(gdb) n
1339        ioaddr = p_i82559->io_address; // get I/O address for 82559
(gdb) n
1342        os_printf("Init82559 %d @ %x\n82559 Self Test\n",
(gdb) n
Init82559 0 @ 134f40
82559 Self Test
967     {
(gdb) n
975         cyg_drv_interrupt_mask(p_i82559->vector);
(gdb) n
989         return old;
(gdb) n
1349        i82559_reset(p_i82559);
(gdb) n
1352        if ( (selftest = (cyg_uint32)pciwindow_mem_alloc(32) ) == 0)
(gdb) n
1354        p_selftest = (cyg_uint32 *) ((selftest + 15) & ~0xf);
(gdb) n
1355        p_selftest[0] = p_selftest[1] = -1;
(gdb) n
385     {   HAL_WRITE_UINT32( io_address, value );    }
(gdb) n
Remote communication error: Connection reset by peer.

******************************************************************



> On Tue, Aug 06, 2002 at 03:07:54AM -0700, Venkatesh wrote:
> > Dear All,
> > 
> > My configuration is as follows:
> > 
> > eCos: Latest Cvs source
> > Configtool : ecos 2.03
> > Operating system: Windows2000
> > Platform : i386 PC
> > Image download through GDB.
> > 
> > I am trying to execute the "ping_test" example given by eCOS 
sources.  
> > The control is not coming out of the init_all_network_interfaces()  
and 
> > getting struck up after eth_set_mac_address() in if_i82559.c.  The 
> > target is reset upon execuing the line, 
> > OUTL( (VIRT_TO_BUS(p_selftest)) | I82559_SELFTEST, ioaddr + 
SCBPort);
> 
> Im confused about what you say here. 
> 
> It gets stack after eth_set_mac_address(). 
> The target is reset upon executing the self test on the ethernet 
target.
> 
> These are two different things and also different from the output
> trace.
>  
> Which of the three is correct?
> 
> > I request you to please help me to solve the above problem as I am 
> > struggling  with it for the past two weeks.
> 
> If you want some help, you need to give us consistent and useful
> information we can actually work with.
> 
> Where exactly does it get stuck? What happens when its stuck? Does the
> target crash out with a memory error? Does gdb still respond? 
> 
>        Andrew
> 
> -- 
> Before posting, please read the FAQ: 
http://sources.redhat.com/fom/ecos
> and search the list archive: http://sources.redhat.com/ml/ecos-discuss
> 
> 

C.Venkatesh
Ceeyes Software Technologies
Phone No: 7261092/93/94 (1214)
Email_ID:venkatc@in.ceeyes.com

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

             reply	other threads:[~2002-08-06 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06  5:21 Venkatesh [this message]
2002-08-06  5:50 ` Andrew Lunn
  -- strict thread matches above, loose matches on Subject: below --
2002-08-07  4:19 Venkatesh
2002-08-06  5:39 Venkatesh
2002-08-06  4:37 Venkatesh
2002-08-06  4:52 ` Andrew Lunn
2002-08-06  5:16 ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200208061051.g76ApuE16174@in.ceeyes.com \
    --to=venkatc@in.ceeyes.com \
    --cc=andrew.lunn@ascom.ch \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).