Hi Robert,
 
Thanks for the reply.
 
I believe it only has one NIC:
Board is something like this
http://www.embeddedplanet.com/products/ep8260.asp
 
Our old BSP's build file for the board clearly says 0x20 for the NIC interrupt.
I've asked the customer to verify the PHY #...
 
Thanks !
 
Dave

________________________________

From: Robert Craig [mailto:community-noreply@qnx.com]
Sent: Mon 1/19/2009 6:38 PM
To: drivers-networking
Subject: RE: ep8260 6.4.0 - no receive packets



Hi Dave:

So... Either the interrupt isn't firing OR the PHY that you think that you're connected to isn't the one that you're 
actually connected to.  Are there multiple interfaces on the board?  Did this BSP work on the same hardware with 6.3.2?

   Robert.

-----Original Message-----
From: Dave Bott [mailto:community-noreply@qnx.com]
Sent: Mon 1/19/2009 7:27 PM
To: drivers-networking
Subject: ep8260 6.4.0 - no receive packets

Customer has migrated Embedded Planet 8260 BSP to 6.4.0
Using io-net driver with shim, things come up and appear to start, but nicinfo shows no packets received...

Here are sloginfo, pidin info, ifconfig and nicinfo output. IRQ 0x20 appears to be the required one.

Suggestions welcome !

Dave

EP8260_MAC=0010EC007E65
EP8260_IP1=10.1.0.112
io-pkt-v4 -dppc8260-ep channel=1,mac=EP8260_MAC,verbose -vvvvvvvvvv
waitfor /dev/socket
ifconfig en0 $EP8260_IP1

Here's what's in my slog:

Jan 01 00:30:41    5    14     0 tcpip starting
Jan 01 00:30:41    3    14     0 Unable to attach to pci server: No such
file or
 directory
Jan 01 00:30:41    3    14     0 Using pseudo random generator.  See
"random" op
tion
Jan 01 00:30:41    5    10     0 PPC 8260
Jan 01 00:30:41    5    10     0 Vendor .............. 0x0
Jan 01 00:30:41    5    10     0 Device .............. 0x0
Jan 01 00:30:41    5    10     0 Revision ............ 0x0
Jan 01 00:30:41    5    10     0 Interrupt ........... 0x20
Jan 01 00:30:41    5    10     0 MAC address ......... 0010ec 007e65
Jan 01 00:30:41    5    10     0 devn-ppc8260: MII transceiver found at
address
0.
Jan 01 00:30:41    5    14     0 io-pkt shim
Jan 01 00:30:41    5    14     0 Vendor .............. 0x0
Jan 01 00:30:41    5    14     0 Device .............. 0x0
Jan 01 00:30:41    5    14     0 Revision ............ 0x0
Jan 01 00:30:41    5    14     0 MAC address ......... 0010ec 007e65
Jan 01 00:30:44    5    10     0 devn-ppc8260: link up (100 MBPS Full
Duplex)
Jan 01 00:33:12    5    10     0 devn-ppc8260: shutdown1()
Jan 01 00:33:12    5    10     0 devn-ppc8260: shutdown2()
Jan 01 00:34:04    5    14     0 tcpip starting


# ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet 127.0.0.1 netmask 0xff000000
en0: flags=80008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,SHIM> mtu
1500
        address: 00:10:ec:00:7e:65
        inet 10.1.0.112 netmask 0xff000000 broadcast 10.255.255.255


# pidin irqs
     pid tid name
       1   1 c/boot/procnto-600
                0       0x80000000    0 -P- @0x57398:0x0
       1   2 c/boot/procnto-600
       1   3 c/boot/procnto-600
       1   4 c/boot/procnto-600
       1   5 c/boot/procnto-600
       1   6 c/boot/procnto-600
       1   7 c/boot/procnto-600
       1   8 c/boot/procnto-600
       1   9 c/boot/procnto-600
       1  10 c/boot/procnto-600
       1  11 c/boot/procnto-600
       1  12 c/boot/procnto-600
       2   1 ot/devc-serppc8260
       2   2 ot/devc-serppc8260
                1              0x4 26080 --- =INTR
       3   1 proc/boot/slogger
       4   1 proc/boot/pipe
       4   2 proc/boot/pipe
       4   3 proc/boot/pipe
       4   4 proc/boot/pipe
       4   5 proc/boot/pipe
    8198   1 proc/boot/devf-ppc
    8198   3 proc/boot/devf-ppc
    8198   4 proc/boot/devf-ppc
  159753   1 bin/devc-pty
  172042   1 bin/mqueue
  217093   1 proc/boot/ksh
  729099   1 bin/inetd
 1474567   1...

So, the problem is solved, but not sure why...

The customer tried a channel # of 3 instead of 1, and it burst into life.

No idea why - ppc8260.c doesn't even have a switch case for 3...

Happy Happy Joy Joy !

Cheers

Dave

Andrew Boyd wrote:
>
> Generally, no rx packets is usually caused by
> the interrupt not firing.  However, I did notice
> this in ths sloginfo:
>
> > Jan 01 00:33:12    5    10     0 devn-ppc8260: shutdown1()
> > Jan 01 00:33:12    5    10     0 devn-ppc8260: shutdown2()
>
> which I am not sure I understand.
>
> --
> aboyd
>
>
> _______________________________________________
> Networking Drivers
> http://community.qnx.com/sf/go/post20372
>


-- 
Dave Bott (dbott@qnx.com)	Field Applications Engineer 
QNX Software Systems, Inc.	Voice: 408-879-7230 
900 E. Hamilton Ave #100	Fax:408-879-7221 
Campbell CA 95008		Cell:408 391-3535

Join Foundry27 <http://community.qnx.com>;  - the new QNX developer forum.