Re: [ECOS] Facing problem with i82559 driver...

Re: [ECOS] Facing problem with i82559 driver...

[Venkatesh]

Hi Gary,
Thanks for your immediate response.
We are using Redboot PC as our target.
Our Redboot PC has a static IP address say..10.1.4.179.
Thro' BOOTP server, we are getting another IP say..10.1.4.180.
Now, BOOTP server is sending the IP but, Redboot is not receiving.
and hence the snapshot of the output pasted in the previous mail.
Please help me in this regard.

Venkatesh.

> On Tue, 2002-08-06 at 04:07, 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.
> > 
> 
> How are you connecting to GDB?  If it's by the network, you must 
somehow
> arrange that RedBoot and your eCos application use different IP 
> addresses or the whole process will fail.
> 
> > 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);
> > 
> > I request you to please help me to solve the above problem as I am 
> > struggling  with it for the past two weeks.
> 
> Relax - don't forget that this forum is *volunteer*, and your access 
to 
> eCos is free.  If you want more immediate/direct help, contract for 
it.
> 
> 
> 
> 
> -- 
> 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

Re: [ECOS] Facing problem with i82559 driver...

[Venkatesh]

Hi Andrew Lunn,

Thanks for your valuable comments and continued help.
With what you have said, I have downloaded the image onto the Redboot 
PC through serial and then tested and debugged the image through 
network using GDB.  It is not working if we download and debug the 
image through network.

Now it's working fine thro serial and our desperation ended at last.

Thanks and Regards,
Venkatesh.



Date: 8/6/2002 14:50:10 +0200
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Venkatesh <venkatc@in.ceeyes.com>
CC: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Facing problem with i82559 driver...  All headers  
On Tue, Aug 06, 2002 at 03:51:56AM -0700, Venkatesh wrote:
> 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.

Connection reset by peer. i.e. your board. You have just
re-initialised the ethernet device the gdb stub is using to talk to
gdb. Thats why you lost the connection. There are parts of eCos you
cannot debug using gdb.  If you use the serial port for gdb you can
then debug the network code. Don't try to debug the serial port
thought!

       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

Re: [ECOS] Facing problem with i82559 driver...

[Andrew Lunn]

On Tue, Aug 06, 2002 at 03:51:56AM -0700, Venkatesh wrote:
> 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.

Connection reset by peer. i.e. your board. You have just
re-initialised the ethernet device the gdb stub is using to talk to
gdb. Thats why you lost the connection. There are parts of eCos you
cannot debug using gdb.  If you use the serial port for gdb you can
then debug the network code. Don't try to debug the serial port
thought!

        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

Re: [ECOS] Facing problem with i82559 driver...

[Venkatesh]

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

Re: [ECOS] Facing problem with i82559 driver...

[Gary Thomas]

On Tue, 2002-08-06 at 04:07, 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.
> 

How are you connecting to GDB?  If it's by the network, you must somehow
arrange that RedBoot and your eCos application use different IP 
addresses or the whole process will fail.

> 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);
> 
> I request you to please help me to solve the above problem as I am 
> struggling  with it for the past two weeks.

Relax - don't forget that this forum is *volunteer*, and your access to 
eCos is free.  If you want more immediate/direct help, contract for it.




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

Re: [ECOS] Facing problem with i82559 driver...

[Andrew Lunn]

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

[ECOS] Facing problem with i82559 driver...

[Venkatesh]

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);

I request you to please help me to solve the above problem as I am 
struggling  with it for the past two weeks.

The snapshot of the output is pasted below:

Thanks in Advance,
Venkatesh.


________________________________________________________________________
Snapshot of the output 
________________________________________________________________________
intel_i82559_init
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 0x0013d180
 BAR[4]    0x00000000 / probed size 0x0010fbee / CPU addr 0x0013d270
 BAR[5]    0x00000000 / probed size 0x00138ac0 / CPU addr 0x00136068
 eth0 configuredESH //d/ecos/examples
 memory address = 0xe1100000
 I/O address = 0x00006400
 **** Device enabled for I/O and Memory and Bus Master
Init82559 0 @ 135060
82559 Self Test
  General self-test: passed.
  Serial sub-system self-test: passed.
  Internal registers self-test: passed.
  ROM checksum self-test: passed (04F4518B).
eeprom data bits 6 (ioaddr 640e)
Valid EEPROM checksum
Set MAC Address = 00 02 B3 20 05 34 (ok 1)
i82559_init: MAC Address = 00 02 B3 20 05 34
________________________________________________________________________


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