The most likely difference to look into is that RedBoot polls
the device whereas eCos expects it to generate interrupts.
The flow shown below indicates that the eCos driver is being
somewhat successful talking to the device (do you ever see any
packets come out?), but that since there were no interrupts,
no incoming packets were processed.
On Thu, 2002-06-20 at 01:42, Vladimir Sterjantov wrote:
Novice in eCos, and any help will be greatly appreciated.
Problem:
- target: pc,
Network card Intel EtherExpress 100 Pro, chip 82558B
- host: linux at i386
Both RedBoot and ping_test (OpenBSD stack used, template "net") built from
eCos CVS sources, downloaded 11 jun 2002.
Target PC boots from RedBoot floppy, without network support, but with
support of debugging via serial line.
82559 driver compiled with DEBUG_82559 turned on.
Now run ping_test and see output:
# gdb -nw ping_test
........SKIPPED....................................................
i82559_start 0 flg 47 Link = Down, 10 Mbps, Half Duplex
PING server 172.16.200.90
Tx 0 13af40: 1 sg's, 42 bytes, KEY 156800
Tx 0 13af40: Starting Engines: KEY 156800 TxCB 1bb26c
TxDone 0 13af40: KEY 156800 TxCB 1bb26c
recvfrom: Operation timed out --- Problem.
.........
Any network test don't works too.
May be difference between 82558 and 82559 not solved in network driver?
Thanks,
Vladimir