* [ECOS] Configure Network Support for eCos
@ 2005-08-19 21:16 Ruchika Singh
2005-08-20 9:39 ` Andrew Lunn
0 siblings, 1 reply; 7+ messages in thread
From: Ruchika Singh @ 2005-08-19 21:16 UTC (permalink / raw)
To: ecos-discuss
Hi All:
I am using BRH evaluation board by ADI Engg, it runs an older eCos
version,(downloaded April 02)
I am trying to configure network support for the same.
I addedd packages :
CYGPKG_NET
CYGPKG_IO_ETH_DRIVERS
CYGPKG_IO_FILEIO
configured option CYGHWR_NET_DRIVER_ETH1_ADDRS to statically assign IP,
provide netmask, gateway,server ip etc.
When I run server_test.c i get following output:
0x11bb8 in ?? ()
Loading section .rom_vectors, size 0x40 lma 0xc0020000
Loading section .text, size 0x430a0 lma 0xc0020040
Loading section .rodata, size 0x1d60 lma 0xc00630e0
Loading section .data, size 0x2418 lma 0xc0064e40
Start address 0xc0020040 , load size 291416
Transfer rate: 40900 bits/sec, 300 bytes/write.
Scanning PCI bus for an Ethernet device. Please Wait.
Start SERVER test
BOOTP[eth0] op: REPLY
htype: Ethernet
hlen: 6
hops: 0
xid: 0x0
secs: 0
flags: 0x0
hw_addr: ff:ff:ff:ff:ff:ff
client IP: 192.168.1.2
my IP: 192.168.1.2
server IP: 192.168.1.101
gateway IP: 192.168.1.1
options:
subnet mask: 255.255.255.0
IP broadcast: 192.168.1.255
gateway: 192.168.1.1
SIOCSIFADDR: Device not configured
BOOTP/DHCP failed on eth1
SIOCSIFADDR: Device not configured
BOOTP/DHCP failed on eth2
SIOCSIFADDR: Device not configured
Network initialization failed for eth0
I am not sure what causes initialization to fail for eth0.
What configuration option I might be missing? Where do I specify hw_address??
I'll appreciate any inputs.
Thanks
-R.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ECOS] Configure Network Support for eCos
2005-08-19 21:16 [ECOS] Configure Network Support for eCos Ruchika Singh
@ 2005-08-20 9:39 ` Andrew Lunn
2005-08-29 2:53 ` Ruchika Singh
0 siblings, 1 reply; 7+ messages in thread
From: Andrew Lunn @ 2005-08-20 9:39 UTC (permalink / raw)
To: Ruchika Singh; +Cc: ecos-discuss
On Fri, Aug 19, 2005 at 09:16:04PM -0000, Ruchika Singh wrote:
>
> Hi All:
>
> I am using BRH evaluation board by ADI Engg, it runs an older eCos
> version,(downloaded April 02)
Rather old. I suggest you try to upgrade to anoncvs is possible.
> I am trying to configure network support for the same.
> I addedd packages :
> CYGPKG_NET
> CYGPKG_IO_ETH_DRIVERS
> CYGPKG_IO_FILEIO
Rather than add packages its better to use the net template...
ecosconfig new foobar net
> configured option CYGHWR_NET_DRIVER_ETH1_ADDRS to statically assign IP,
> provide netmask, gateway,server ip etc.
> When I run server_test.c i get following output:
>
> 0x11bb8 in ?? ()
> Loading section .rom_vectors, size 0x40 lma 0xc0020000
> Loading section .text, size 0x430a0 lma 0xc0020040
> Loading section .rodata, size 0x1d60 lma 0xc00630e0
> Loading section .data, size 0x2418 lma 0xc0064e40
> Start address 0xc0020040 , load size 291416
> Transfer rate: 40900 bits/sec, 300 bytes/write.
> Scanning PCI bus for an Ethernet device. Please Wait.
> Start SERVER test
> BOOTP[eth0] op: REPLY
> htype: Ethernet
> hlen: 6
> hops: 0
> xid: 0x0
> secs: 0
> flags: 0x0
> hw_addr: ff:ff:ff:ff:ff:ff
> client IP: 192.168.1.2
> my IP: 192.168.1.2
> server IP: 192.168.1.101
> gateway IP: 192.168.1.1
> options:
> subnet mask: 255.255.255.0
> IP broadcast: 192.168.1.255
> gateway: 192.168.1.1
> SIOCSIFADDR: Device not configured
> BOOTP/DHCP failed on eth1
> SIOCSIFADDR: Device not configured
> BOOTP/DHCP failed on eth2
> SIOCSIFADDR: Device not configured
> Network initialization failed for eth0
>
> I am not sure what causes initialization to fail for eth0.
> What configuration option I might be missing? Where do I specify hw_address??
That will depend on your ethernet device driver. Read the source code.y
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ECOS] Configure Network Support for eCos
2005-08-20 9:39 ` Andrew Lunn
@ 2005-08-29 2:53 ` Ruchika Singh
2005-08-29 7:06 ` Ruchika Singh
2005-08-29 7:22 ` Ruchika Singh
0 siblings, 2 replies; 7+ messages in thread
From: Ruchika Singh @ 2005-08-29 2:53 UTC (permalink / raw)
To: Andrew Lunn; +Cc: ecos-discuss
Hi:
I am still trying to work out the network configuration.
I have updated to the latest eCos version, put the problem still remains.
My hardware platform is not directly supported by eCos. Its a BRH board by
ADI Engg, that addeded their own support for brh on eCos/Redboot source code.
They claim only however, Redboot's support for Networking, not paticularly
for eCos applications that would run on board.
So, I have this basic questions:
1. If anyone has used eCos on brh board, with networking support?
2. I am wondering if ethernet driver support for eCos applications and
Redboot could be different? Perhaps my hadware only has driver support for
redboot.?( and hence eCos application can't find MAC address etc when
Redboot is able to find it) I am not sure if the two are different though.
If yes, any insight/pointers into how I can modify it to support eCos
applications as well?
I am a newbie to eCos. I would really appreciate any insights into this
problem..have been stuck for a while!
Thanks
-R.
Andrew Lunn <andrew@lunn.ch> said:
> On Fri, Aug 19, 2005 at 09:16:04PM -0000, Ruchika Singh wrote:
> >
> > Hi All:
> >
> > I am using BRH evaluation board by ADI Engg, it runs an older eCos
> > version,(downloaded April 02)
>
> Rather old. I suggest you try to upgrade to anoncvs is possible.
>
> > I am trying to configure network support for the same.
> > I addedd packages :
> > CYGPKG_NET
> > CYGPKG_IO_ETH_DRIVERS
> > CYGPKG_IO_FILEIO
>
> Rather than add packages its better to use the net template...
>
> ecosconfig new foobar net
>
> > configured option CYGHWR_NET_DRIVER_ETH1_ADDRS to statically assign IP,
> > provide netmask, gateway,server ip etc.
> > When I run server_test.c i get following output:
> >
> > 0x11bb8 in ?? ()
> > Loading section .rom_vectors, size 0x40 lma 0xc0020000
> > Loading section .text, size 0x430a0 lma 0xc0020040
> > Loading section .rodata, size 0x1d60 lma 0xc00630e0
> > Loading section .data, size 0x2418 lma 0xc0064e40
> > Start address 0xc0020040 , load size 291416
> > Transfer rate: 40900 bits/sec, 300 bytes/write.
> > Scanning PCI bus for an Ethernet device. Please Wait.
> > Start SERVER test
> > BOOTP[eth0] op: REPLY
> > htype: Ethernet
> > hlen: 6
> > hops: 0
> > xid: 0x0
> > secs: 0
> > flags: 0x0
> > hw_addr: ff:ff:ff:ff:ff:ff
> > client IP: 192.168.1.2
> > my IP: 192.168.1.2
> > server IP: 192.168.1.101
> > gateway IP: 192.168.1.1
> > options:
> > subnet mask: 255.255.255.0
> > IP broadcast: 192.168.1.255
> > gateway: 192.168.1.1
> > SIOCSIFADDR: Device not configured
> > BOOTP/DHCP failed on eth1
> > SIOCSIFADDR: Device not configured
> > BOOTP/DHCP failed on eth2
> > SIOCSIFADDR: Device not configured
> > Network initialization failed for eth0
> >
> > I am not sure what causes initialization to fail for eth0.
> > What configuration option I might be missing? Where do I specify
hw_address??
>
> That will depend on your ethernet device driver. Read the source code.y
>
> 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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ECOS] Configure Network Support for eCos
2005-08-29 2:53 ` Ruchika Singh
@ 2005-08-29 7:06 ` Ruchika Singh
2005-08-29 7:22 ` Ruchika Singh
1 sibling, 0 replies; 7+ messages in thread
From: Ruchika Singh @ 2005-08-29 7:06 UTC (permalink / raw)
To: ecos-discuss
Hi:
I realized that the low-level drivers are shared by eCos supported TCP/IP
stack and Redboot.
My eCos application now correctly picks the MAC address from EEPROM connected
to i82559 device on my target. However, network initalization still fails. I
have attached output with driver debug option enabled. It seems to go over the
low-level driver fine, what happens when a call to high-level driver is made?
As I mentioned my hardware platform does not support eCos, but does support
Redboot. I want to know how the high level driver support for the two is
different. I am not sure about this but am guessing that perhaps things go
wrong as high -level driver support for eCos app doesn't exist.
I would appreciate any insights into this.
Thanks
-R.
Init device 'i82559_enet1'
intel_i82559_init
pci_init_find_82559s()
Scanning PCI bus for an Ethernet device. Please Wait.
Finished cyg_pci_init();
eth0 = 82559
Wired to HAL vector 34
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach () dFound device on bus
0, devfn 0x08:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c000000 / probed size 0x00000000 / CPU addr 0x0c000000
BAR[1] 0x0a000001 / probed size 0x00000000 / CPU addr 0x0a000000
BAR[2] 0x0c020000 / probed size 0x00000000 / CPU addr 0x0c020000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth0 configured
memory address = 0x0c000000
I/O address = 0x0a000000
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d **** Device enabled
for I/O and Memory and Bus Master
eth1 = 82559
Wired to HAL vector 35
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach () dFound device on bus
0, devfn 0x10:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c040000 / probed size 0x00000000 / CPU addr 0x0c040000
BAR[1] 0x0a000041 / probed size 0x00000000 / CPU addr 0x0a000040
BAR[2] 0x0c060000 / probed size 0x00000000 / CPU addr 0x0c060000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth0 configured
memory address = 0x0c000000
I/O address = 0x0a000000
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d **** Device enabled
for I/O and Memory and Bus Master
eth1 = 82559
Wired to HAL vector 35
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach () dFound device on bus
0, devfn 0x10:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c040000 / probed size 0x00000000 / CPU addr 0x0c040000
BAR[1] 0x0a000041 / probed size 0x00000000 / CPU addr 0x0a000040
BAR[2] 0x0c060000 / probed size 0x00000000 / CPU addr 0x0c060000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth1 configured
memory address = 0x0c040000
I/O address = 0x0a000040
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d **** Device enabled
for I/O and Memory and Bus Master
eth2 not found
Init82559 0 @ c00bd400
82559 Self Test
TRACE: intr.cxx [ 607] void Cyg_Interrupt::mask_interrupt ()
rTRACE: intr.cxx [ 607] void
Cyg_Interrupt::mask_interrupt () )TRACE: intr.cxx
[ 617] void Cyg_Interrupt::mask_interrupt ()
dTRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d General self-test:
passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (DBD8681D).
eeprom data bits 6 (ioaddr a00000e)
Valid EEPROM checksum
Set MAC Address = 00 08 A2 00 03 A2 (ok 1)
i82559_init: MAC Address = 00 08 A2 00 03 A2
TRACE: memmove.cxx [ 73] __memmove()
rTRACE: memmove.cxx [ 73] __memmove()
)TRACE: memmove.cxx [ 100]
__memmove() 4TRACE:
memmove.cxx [ 73] __memmove()
rTRACE: memmove.cxx [ 73] __memmove()
.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ECOS] Configure Network Support for eCos
2005-08-29 2:53 ` Ruchika Singh
2005-08-29 7:06 ` Ruchika Singh
@ 2005-08-29 7:22 ` Ruchika Singh
1 sibling, 0 replies; 7+ messages in thread
From: Ruchika Singh @ 2005-08-29 7:22 UTC (permalink / raw)
To: ecos-discuss
Hi:
I realized that the low-level drivers are shared by eCos supported TCP/IP
stack and Redboot.
My eCos application now correctly picks the MAC address from EEPROM connected
to i82559 device on my target. However, network initalization still fails. I
have attached output with driver debug option enabled. It seems to go over the
low-level driver fine, what happens when a call to high-level driver is made?
As I mentioned my hardware platform does not support eCos, but does support
Redboot. I want to know how the high level driver support for the two is
different. I am not sure about this but am guessing that perhaps things go
wrong as high -level driver support for eCos app doesn't exist.
I would appreciate any insights into this.
Thanks
-R.
Init device 'i82559_enet1'
intel_i82559_init
pci_init_find_82559s()
Scanning PCI bus for an Ethernet device. Please Wait.
Finished cyg_pci_init();
eth0 = 82559
Wired to HAL vector 34
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach () dFound device on bus
0, devfn 0x08:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c000000 / probed size 0x00000000 / CPU addr 0x0c000000
BAR[1] 0x0a000001 / probed size 0x00000000 / CPU addr 0x0a000000
BAR[2] 0x0c020000 / probed size 0x00000000 / CPU addr 0x0c020000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth0 configured
memory address = 0x0c000000
I/O address = 0x0a000000
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d **** Device enabled
for I/O and Memory and Bus Master
eth1 = 82559
Wired to HAL vector 35
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach () dFound device on bus
0, devfn 0x10:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c040000 / probed size 0x00000000 / CPU addr 0x0c040000
BAR[1] 0x0a000041 / probed size 0x00000000 / CPU addr 0x0a000040
BAR[2] 0x0c060000 / probed size 0x00000000 / CPU addr 0x0c060000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth0 configured
memory address = 0x0c000000
I/O address = 0x0a000000
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d **** Device enabled
for I/O and Memory and Bus Master
eth1 = 82559
Wired to HAL vector 35
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach () dFound device on bus
0, devfn 0x10:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c040000 / probed size 0x00000000 / CPU addr 0x0c040000
BAR[1] 0x0a000041 / probed size 0x00000000 / CPU addr 0x0a000040
BAR[2] 0x0c060000 / probed size 0x00000000 / CPU addr 0x0c060000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth1 configured
memory address = 0x0c040000
I/O address = 0x0a000040
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d **** Device enabled
for I/O and Memory and Bus Master
eth2 not found
Init82559 0 @ c00bd400
82559 Self Test
TRACE: intr.cxx [ 607] void Cyg_Interrupt::mask_interrupt ()
rTRACE: intr.cxx [ 607] void
Cyg_Interrupt::mask_interrupt () )TRACE: intr.cxx
[ 617] void Cyg_Interrupt::mask_interrupt ()
dTRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d General self-test:
passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (DBD8681D).
eeprom data bits 6 (ioaddr a00000e)
Valid EEPROM checksum
Set MAC Address = 00 08 A2 00 03 A2 (ok 1)
i82559_init: MAC Address = 00 08 A2 00 03 A2
TRACE: memmove.cxx [ 73] __memmove()
rTRACE: memmove.cxx [ 73] __memmove()
)TRACE: memmove.cxx [ 100]
__memmove() 4TRACE:
memmove.cxx [ 73] __memmove()
rTRACE: memmove.cxx [ 73] __memmove()
.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ECOS] Configure Network Support for eCos
@ 2005-08-30 13:04 Ruchika Singh
0 siblings, 0 replies; 7+ messages in thread
From: Ruchika Singh @ 2005-08-30 13:04 UTC (permalink / raw)
To: ecos-discuss
Hi:
Can anyone pl let me know what kind of high -level ethernet driver support
needs to be provided by a target for eCos application with TCP/IP stack.
Are there any kind of additional interface implementations/code that would
be added to support networking in eCos application, assuming networking
support is already available for Redboot on the target.
Thanks a lot!
-R.
Hi:
I realized that the low-level drivers are shared by eCos supported TCP/IP
stack and Redboot.
My eCos application now correctly picks the MAC address from EEPROM connected
to i82559 device on my target. However, network initalization still fails. I
have attached output with driver debug option enabled. It seems to go over
the
low-level driver fine, what happens when a call to high-level driver is made?
As I mentioned my hardware platform does not support eCos, but does support
Redboot. I want to know how the high level driver support for the two is
different. I am not sure about this but am guessing that perhaps things go
wrong as high -level driver support for eCos app doesn't exist.
I would appreciate any insights into this.
Thanks
-R.
----------------------------------------------------------------
Init device 'i82559_enet1'
intel_i82559_init
pci_init_find_82559s()
Scanning PCI bus for an Ethernet device. Please Wait.
Finished cyg_pci_init();
eth0 = 82559
Wired to HAL vector 34
TRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt ()
)TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach ()
dFound device on bus
0, devfn 0x08:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c000000 / probed size 0x00000000 / CPU addr 0x0c000000
BAR[1] 0x0a000001 / probed size 0x00000000 / CPU addr 0x0a000000
BAR[2] 0x0c020000 / probed size 0x00000000 / CPU addr 0x0c020000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth0 configured
memory address = 0x0c000000
I/O address = 0x0a000000
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt ()
**** Device enabled for I/O and Memory and Bus Master
eth1 = 82559
Wired to HAL vector 35
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE:
intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach ()
Found device on bus
0, devfn 0x10:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c040000 / probed size 0x00000000 / CPU addr 0x0c040000
BAR[1] 0x0a000041 / probed size 0x00000000 / CPU addr 0x0a000040
BAR[2] 0x0c060000 / probed size 0x00000000 / CPU addr 0x0c060000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth0 configured
memory address = 0x0c000000
I/O address = 0x0a000000
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d
**** Device enabled for I/O and Memory and Bus Master
eth1 = 82559
Wired to HAL vector 35
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE:
intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach ()
Found device on bus 0, devfn 0x10:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c040000 / probed size 0x00000000 / CPU addr 0x0c040000
BAR[1] 0x0a000041 / probed size 0x00000000 / CPU addr 0x0a000040
BAR[2] 0x0c060000 / probed size 0x00000000 / CPU addr 0x0c060000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth1 configured
memory address = 0x0c040000
I/O address = 0x0a000040
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d
**** Device enabled for I/O and Memory and Bus Master
eth2 not found
Init82559 0 @ c00bd400
82559 Self Test
TRACE: intr.cxx [ 607] void Cyg_Interrupt::mask_interrupt ()
rTRACE: intr.cxx [ 607] void
Cyg_Interrupt::mask_interrupt () )TRACE: intr.cxx
[ 617] void Cyg_Interrupt::mask_interrupt ()
dTRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d
General self-test:passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (DBD8681D).
eeprom data bits 6 (ioaddr a00000e)
Valid EEPROM checksum
Set MAC Address = 00 08 A2 00 03 A2 (ok 1)
i82559_init: MAC Address = 00 08 A2 00 03 A2
TRACE: memmove.cxx [ 73] __memmove()
rTRACE: memmove.cxx [ 73] __memmove()
)TRACE: memmove.cxx [ 100]
__memmove() 4TRACE:
memmove.cxx [ 73] __memmove()
rTRACE: memmove.cxx [ 73] __memmove()
//some more trace comments...
device init failed
Init device 'i82559_enet2'
intel_i82559_init
Init82559 1 @ c00bd410.....so on
Thanks
-R.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ECOS] Configure Network Support for eCos
@ 2005-08-29 7:56 Ruchika Singh
0 siblings, 0 replies; 7+ messages in thread
From: Ruchika Singh @ 2005-08-29 7:56 UTC (permalink / raw)
To: ecos-discuss
the previous email missed the last part of output(initialization fails) ;
here it is..after the mail..
Hi:
I realized that the low-level drivers are shared by eCos supported TCP/IP
stack and Redboot.
My eCos application now correctly picks the MAC address from EEPROM connected
to i82559 device on my target. However, network initalization still fails. I
have attached output with driver debug option enabled. It seems to go over the
low-level driver fine, what happens when a call to high-level driver is made?
As I mentioned my hardware platform does not support eCos, but does support
Redboot. I want to know how the high level driver support for the two is
different. I am not sure about this but am guessing that perhaps things go
wrong as high -level driver support for eCos app doesn't exist.
I would appreciate any insights into this.
Thanks
-R.
----------------------------------------------------------------
Init device 'i82559_enet1'
intel_i82559_init
pci_init_find_82559s()
Scanning PCI bus for an Ethernet device. Please Wait.
Finished cyg_pci_init();
eth0 = 82559
Wired to HAL vector 34
TRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt ()
)TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach ()
dFound device on bus
0, devfn 0x08:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c000000 / probed size 0x00000000 / CPU addr 0x0c000000
BAR[1] 0x0a000001 / probed size 0x00000000 / CPU addr 0x0a000000
BAR[2] 0x0c020000 / probed size 0x00000000 / CPU addr 0x0c020000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth0 configured
memory address = 0x0c000000
I/O address = 0x0a000000
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt ()
**** Device enabled for I/O and Memory and Bus Master
eth1 = 82559
Wired to HAL vector 35
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach ()
Found device on bus
0, devfn 0x10:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c040000 / probed size 0x00000000 / CPU addr 0x0c040000
BAR[1] 0x0a000041 / probed size 0x00000000 / CPU addr 0x0a000040
BAR[2] 0x0c060000 / probed size 0x00000000 / CPU addr 0x0c060000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth0 configured
memory address = 0x0c000000
I/O address = 0x0a000000
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d
**** Device enabled for I/O and Memory and Bus Master
eth1 = 82559
Wired to HAL vector 35
TRACE: intr.cxx [ 77] Cyg_Interrupt::Cyg_Interrupt ()
rTRACE: intr.cxx [ 77]
Cyg_Interrupt::Cyg_Interrupt () )TRACE: intr.cxx
[ 100] Cyg_Interrupt::Cyg_Interrupt ()
dTRACE: intr.cxx [ 386] void Cyg_Interrupt::attach ()
rTRACE: intr.cxx [ 447] void
Cyg_Interrupt::attach ()
Found device on bus 0, devfn 0x10:
Note that board is active. Probed sizes and CPU addresses invalid!
Vendor 0x8086
Device 0x1209
Command 0x0007, Status 0x0290
Class/Rev 0x02000009
Header 0x00
SubVendor 0x0000, Sub ID 0x0000
BAR[0] 0x0c040000 / probed size 0x00000000 / CPU addr 0x0c040000
BAR[1] 0x0a000041 / probed size 0x00000000 / CPU addr 0x0a000040
BAR[2] 0x0c060000 / probed size 0x00000000 / CPU addr 0x0c060000
BAR[3] 0x00000000 / probed size 0x00000000 / CPU addr 0x00000000
BAR[4] 0x00000000 / probed size 0xc002e280 / CPU addr 0x00000000
BAR[5] 0x00000000 / probed size 0xc002d584 / CPU addr 0x00000000
eth1 configured
memory address = 0x0c040000
I/O address = 0x0a000040
TRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d
**** Device enabled for I/O and Memory and Bus Master
eth2 not found
Init82559 0 @ c00bd400
82559 Self Test
TRACE: intr.cxx [ 607] void Cyg_Interrupt::mask_interrupt ()
rTRACE: intr.cxx [ 607] void
Cyg_Interrupt::mask_interrupt () )TRACE: intr.cxx
[ 617] void Cyg_Interrupt::mask_interrupt ()
dTRACE: intr.cxx [ 626] void Cyg_Interrupt::unmask_interrupt ()
rTRACE: intr.cxx [ 635] void
Cyg_Interrupt::unmask_interrupt () d
General self-test:passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (DBD8681D).
eeprom data bits 6 (ioaddr a00000e)
Valid EEPROM checksum
Set MAC Address = 00 08 A2 00 03 A2 (ok 1)
i82559_init: MAC Address = 00 08 A2 00 03 A2
TRACE: memmove.cxx [ 73] __memmove()
rTRACE: memmove.cxx [ 73] __memmove()
)TRACE: memmove.cxx [ 100]
__memmove() 4TRACE:
memmove.cxx [ 73] __memmove()
rTRACE: memmove.cxx [ 73] __memmove()
//some more trace comments...
device init failed
Init device 'i82559_enet2'
intel_i82559_init
Init82559 1 @ c00bd410.....so on
Thanks
-R.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2005-08-30 12:25 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-08-19 21:16 [ECOS] Configure Network Support for eCos Ruchika Singh
2005-08-20 9:39 ` Andrew Lunn
2005-08-29 2:53 ` Ruchika Singh
2005-08-29 7:06 ` Ruchika Singh
2005-08-29 7:22 ` Ruchika Singh
2005-08-29 7:56 Ruchika Singh
2005-08-30 13:04 Ruchika Singh
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).