Re: Making Ethernet work on DB1100 (MIPS) ie. "Product Ethernet"
- From: "Doug Cook [MSFT]" <dcook@xxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 10 Mar 2007 22:55:11 -0800
I don't have a copy of the DB1100 BSP handy, I don't know what kind of Ethernet chip it uses, I don't have a copy of your project handy, and I don't have much to go on, so I can only make guesses and suggest how things should work.
You need two things for Ethernet to work:
- Sufficient OS support for Ethernet. This requires SYSGEN_ETHERNET and possibly some other components. This will make the control panel applet available, as well as add a TCP/IP stack and general networking support to the operating system image. Some of these are automatically added. For example, setting SYSGEN_ETHERNET automatically enable SYSGEN_TCPIP. Looking at CE 6.0, if both SYSGEN_CONNMC and SYSGEN_ETHERNET are set and a driver is loaded, you'll get a system tray icon.
- A driver. This will either be from your BSP (usually hardcoded into your BPS's scripts in the case of a built-in BSP-specific ethernet chip) or from the generally available drivers provided with CE (you add a driver based on the type of Ethernet card you have added to your board).
To get a system tray icon, you need three things:
- A loaded Ethernet driver.
- Ethernet support. (SYSGEN_ETHERNET.)
- Network connections UI support (SYSGEN_CONNMC.)
A properly written BSP will automatically include the BSP's built-in ethernet driver if the project includes ethernet support. It generally works like this:
- Ethernet driver is a DLL that is always built, or is built as long as necessary OS support is present. Necessary OS support might come in the form of SYSGEN_DEVICE, SYSGEN_FULLCRT, SYSGEN_ETHERNET, or any number of other prerequisites. You would have to look at the DIRS file or the SOURCES file in the BSP to find out the exact filter (if any). That said, usually the filter is a subset of the filters mentioned below, so this isn't usually a concern.
- Driver DLL is included into your image by your BSP's platform.bib file. The DLL is only included if certain variables are set in the environment -- again, there is a filtering stage. Typically, the driver will be included into your image if both BSP_MYETHERNETCARD=1 and SYSGEN_ETHERNET=1. Often there are additional filters, but this is specific to the BSP. Platform Builder can help you find out what needs to be set to get your driver DLL into the image. Find the driver DLL under your BSP in the catalog view, right-click on it, and select the context menu option that shows "why this driver is excluded" or something to that effect. PB will try to analyze your environment and the platform.bib file and figure out what you can do to make the driver show up in the image. (The analysis isn't perfect, but it is usually helpful.)
- The registry settings that cause your driver to be loaded are specified in the BSP's platform.reg file. Again, the registry settings will be filtered, usually by logic equivalent to the filter for the BIB file.
If your BSP does not have a hardcoded Ethernet chip, you'll need to select one from the available Device Drivers. If a device driver is not available for your Ethernet device, you'll need to get a different Ethernet device or write your own driver.
--
// StdDisclaimer.h
// This posting is provided "AS IS" with no warranties, and confers no rights.
//
"APSFlorida" <APSFlorida@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:6954699B-B497-43DA-9EE3-D430920BF4B8@xxxxxxxxxxxxxxxx
Yes, "SYSGEN_ETHERNET".
How exactly is the connection applet generated, and how does a custom driver
hook in such that it would show up as something available for configuration
under network connections?
"Doug Cook [MSFT]" wrote:
Did you add Ethernet support to your image? (SYSGEN_ETHERNET, or something
like "Wired Local Area Network" in the catalog.)
--
// StdDisclaimer.h
// This posting is provided "AS IS" with no warranties, and confers no
rights.
//
"APSFlorida" <APSFlorida@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3F0DDDEE-1E54-4D45-AB29-66F7CA11AC46@xxxxxxxxxxxxxxxx
>I have a reference board, Ive built and Run Linux on it. That was a
> nightmare...
>
> But the Client want WIN CE 5. AMD provided an image that runs with
> ethernet. It has a connection Icon under network connections when I run
> the
> AMD example NK.bin
>
> When I build an NK.bin I do not have a connection Icon under Network
> connections. What's up
>
> Lastly where are the manuals for using WinCE? I have a 6MB line and > the
> servers are so slow I'm falling asleep between pages. Books on CE 5.0?
>
> Thanks
.
- Follow-Ups:
- Re: Making Ethernet work on DB1100 (MIPS) ie. "Product Ethernet"
- From: APSFlorida
- Re: Making Ethernet work on DB1100 (MIPS) ie. "Product Ethernet"
- References:
- Re: Making Ethernet work on DB1100 (MIPS) ie. "Product Ethernet"
- From: Doug Cook [MSFT]
- Re: Making Ethernet work on DB1100 (MIPS) ie. "Product Ethernet"
- Prev by Date: Re: Appending tens of files into NK image
- Next by Date: Re: WinCE 6.0 / PB6 very slow builds?
- Previous by thread: Re: Making Ethernet work on DB1100 (MIPS) ie. "Product Ethernet"
- Next by thread: Re: Making Ethernet work on DB1100 (MIPS) ie. "Product Ethernet"
- Index(es):
Relevant Pages
|