Re: CE 6.0 Networking Problems
- From: "Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam DOT com>
- Date: Tue, 22 Jul 2008 13:07:38 -0700
If you're running KITL over Ethernet, when you're running KITL, the hardware
interface is completely different than from the real driver (no interrupts
used, generally).
Paul T.
"George M." <GeorgeM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A311494D-2E8E-49B8-ADF1-106682110A46@xxxxxxxxxxxxxxxx
Yes, usually it does.
I thought I had that squared away, as it works fine with the bootloader
version of the driver and also with KITL when running a RAM image from PB.
But perhaps something is still not quite right with the interrupts.
The real driver is an NDIS driver and maybe more interrupt investigation
is
needed.
--
Thanks,
George
"Paul G. Tobey [eMVP]" wrote:
Intermittent things in the network almost always point to interrupts...
Paul T.
"George M." <GeorgeM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A5BE9836-829F-46BF-98AB-14501FF6A171@xxxxxxxxxxxxxxxx
Hello,
I've found some new observations.
On occasion, when I ping my device from my development PC, I do get a
reply
from the target. It doesn't happen often but it has responded.
Also, if I'm pinging from my PC, and then go to my target and ping my
host
PC, then on my host PC I consistently get a reply from the target until
the
target is done pinging my host PC.
Perhaps it's a timing issue in the driver? Maybe, as you pointed out,
my
interrupt isn't quite set up correctly yet?
Any other insights would be appreciated.
--
Thanks,
George
"Paul G. Tobey [eMVP]" wrote:
Just for quick grins, make sure that there is no firewall running on
your
PC. As you say, the address appears fine, as long as the subnet masks
on
each device are correct; I would guess 255.255.255.0.
The most-likely cause that I can think of is a problem with the
Ethernet
driver. It could be that interrupts aren't working right for some
reason
(you've got them configured for 'edge' sensitivity, but the controller
doesn't work that way, etc.) It could also be a problem with the
registry
settings for the driver (maybe the register stride is something other
than
1, but you haven't set a registry option that tells the driver that).
I
would expect these basic sorts of things to be weeded out by being
able
to
ping outward to the PC, though. The next thing would be to build a
debug
image, with the full debug messages, and see what the messages from
the
driver, and the system, might tell you about what's going on.
Paul T.
"George M." <GeorgeM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE105AEE-B5CD-4AFA-916C-28A9A81734D9@xxxxxxxxxxxxxxxx
Thank you for the reply. My apologies, I failed to provide some
valuable
information.
This is a retail image running the real driver and executing out of
NOR
flash, KITL is not being used.
Also, the IP address does seem valid. My development machine is
10.7.236.14
and my target gets 10.7.236.13. So to me that means it's a valid
address.
The Ethernet card I'm using is SMSC 9118 (LAN9217 family).
Hope that helps. Any other information I can provide let me know.
--
Thanks,
George
"Paul G. Tobey [eMVP]" wrote:
Is the IP address it's getting *valid*? If you're on a firewalled
network
(there's a firewall between you and the Internet), tell us your
development
PC IP address and the one that the device is getting (since they're
not
externally accessible to us anyway).
This is a debug image running VMini over KITL? Or it's a retail
image
running the real driver for your Ethernet card? What type of
Ethernet
card
is it?
Paul T.
"George M." <GeorgeM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F7779CD4-4DFB-4C0B-B6E1-A570CE473C6D@xxxxxxxxxxxxxxxx
Hi,
I am having problems connecting my custom target device, running
a
Freescale
i.MX31 platform with CE 6.0.
Right now I am simply trying to ping my device but am not having
any
success. I'm also trying to reach the internet with the IE
browser
but
that
is not working either.
It appears that my device can talk to the DHCP server correctly,
as
it
obtains an IP address. And I can ping my development machine
from
my
target
successfully, i.e. receive a reply. But when I ping my target
from
my
development machine my target does not respond.
Also, on the IE browser on my target I see that it is connected
on
the
"Local intranet" as is displayed on the bottom ride side of the
browser
pane.
So something appears to perhaps be blocking it? I do not have
the
'Firewall' catalog item included in my image, so I don't think
it's
the
firewall on the target unless there is some other security
feature I
am
not
aware of.
Can anyone help please? What catalog items are needed in the
image
to
be
able to browse the internet, ping the target, connect to it, etc.
I've
tried
to provide useful information but I can provide more. I could
also
list
all
the network related items I've included in my image if that's
helpful.
--
Thanks,
George
.
- References:
- Re: CE 6.0 Networking Problems
- From: Paul G. Tobey [eMVP]
- Re: CE 6.0 Networking Problems
- From: George M.
- Re: CE 6.0 Networking Problems
- From: Paul G. Tobey [eMVP]
- Re: CE 6.0 Networking Problems
- From: George M.
- Re: CE 6.0 Networking Problems
- From: Paul G. Tobey [eMVP]
- Re: CE 6.0 Networking Problems
- From: George M.
- Re: CE 6.0 Networking Problems
- Prev by Date: Re: CE 6.0 Networking Problems
- Next by Date: Re: less than 1 Mb in g_oalAddressTable
- Previous by thread: Re: CE 6.0 Networking Problems
- Next by thread: require input on CoCreateGuid functionality for a kernel mode driver
- Index(es):
Relevant Pages
|
