CEPC stuck at DHCP

Hi all,

I tried to create a CEPC platform based on an old Pentium 3 PC with a 3Com
3c90x Ethernet interface. I had used the CEPCBOOT.144 utility to create the
boot diskette. The PC was booted up with the default
config.sys/autoexec.bat options. The ethernet interface was correctly
identified by loadcepc as a 3Com 3c90x ethernet interface but eboot.bin
failed in trying to obtain an IP address via DHCP with the message:

ProcessDHCP()::DHCP_INIT

I sniffed the ethernet interface to verify that the CEPC was not sending out
any packets at all.

I had also tried to assign a static IP address to see if the CEPC would
contact my development machine with BOOTME requests. Again, I did not
detect any packets coming from the CEPC.

Does anyone know what could be the problem?

K
Thu May 26 02:57:08 CDT 2005

It seems that the EBoot could *not* drive your 3com NIC properly.
Do you try to use some other NIC, maybe RealTek 8139 a cheaper but more
popular one for Windows CE developing??

"Soh Kok Hong" <kokhong.soh@avnet.com> ¼¶¼g©ó¶l¥ó·s»D:eL6VfTbYFHA.796@TK2MSFTNGP09.phx.gbl...
> Hi all,
>
> I tried to create a CEPC platform based on an old Pentium 3 PC with a 3Com
> 3c90x Ethernet interface. I had used the CEPCBOOT.144 utility to create
> the
> boot diskette. The PC was booted up with the default
> config.sys/autoexec.bat options. The ethernet interface was correctly
> identified by loadcepc as a 3Com 3c90x ethernet interface but eboot.bin
> failed in trying to obtain an IP address via DHCP with the message:
>
> ProcessDHCP()::DHCP_INIT
>
> I sniffed the ethernet interface to verify that the CEPC was not sending
> out
> any packets at all.
>
> I had also tried to assign a static IP address to see if the CEPC would
> contact my development machine with BOOTME requests. Again, I did not
> detect any packets coming from the CEPC.
>
> Does anyone know what could be the problem?
>
>
>

winfresh
Thu May 26 05:17:01 CDT 2005

i think u need to remove the USB driver from ur catalog.
It gives problem for CEPC download.

"Soh Kok Hong" wrote:

> Hi all,
>
> I tried to create a CEPC platform based on an old Pentium 3 PC with a 3Com
> 3c90x Ethernet interface. I had used the CEPCBOOT.144 utility to create the
> boot diskette. The PC was booted up with the default
> config.sys/autoexec.bat options. The ethernet interface was correctly
> identified by loadcepc as a 3Com 3c90x ethernet interface but eboot.bin
> failed in trying to obtain an IP address via DHCP with the message:
>
> ProcessDHCP()::DHCP_INIT
>
> I sniffed the ethernet interface to verify that the CEPC was not sending out
> any packets at all.
>
> I had also tried to assign a static IP address to see if the CEPC would
> contact my development machine with BOOTME requests. Again, I did not
> detect any packets coming from the CEPC.
>
> Does anyone know what could be the problem?
>
>
>
>

Soh
Fri May 27 01:41:16 CDT 2005

I tried removing USB-related items from the catalog, disable USB in the BIOS
and switching to a RTL8139D-based PCI ethernet card. But the problem is
still there.


"winfresh" <winfresh@discussions.microsoft.com> wrote in message
news:90AE3707-1A11-46B8-BE63-235C255FB551@microsoft.com...
> i think u need to remove the USB driver from ur catalog.
> It gives problem for CEPC download.
>
> "Soh Kok Hong" wrote:
>
> > Hi all,
> >
> > I tried to create a CEPC platform based on an old Pentium 3 PC with a
3Com
> > 3c90x Ethernet interface. I had used the CEPCBOOT.144 utility to create
the
> > boot diskette. The PC was booted up with the default
> > config.sys/autoexec.bat options. The ethernet interface was correctly
> > identified by loadcepc as a 3Com 3c90x ethernet interface but eboot.bin
> > failed in trying to obtain an IP address via DHCP with the message:
> >
> > ProcessDHCP()::DHCP_INIT
> >
> > I sniffed the ethernet interface to verify that the CEPC was not sending
out
> > any packets at all.
> >
> > I had also tried to assign a static IP address to see if the CEPC would
> > contact my development machine with BOOTME requests. Again, I did not
> > detect any packets coming from the CEPC.
> >
> > Does anyone know what could be the problem?
> >
> >
> >
> >

Soh
Mon May 30 00:50:34 CDT 2005

Found the problem. I had tried both the built-in 3C920 Ethernet interface
and Realtek 8139D PCI ethernet cards and the had both failed to transmit a
single packet. The reason is that these chips use PCI Bus Mastering to
transfer the packet data from memory to the chip internal FIFO. The
bootloader code that was provided my M$FT did not enable the bus mastering
capabilities of these devices.

To fix the problem, I had to go into my system bios to force the PCI bus
master enable for the appropriate PCI slot. Ideally, this problem should be
fixed in the boot loader code. Does anyone know exactly where to fix this
problem in the boot loader code?

"Soh Kok Hong" <kokhong.soh@avnet.com> wrote in message
news:eL6VfTbYFHA.796@TK2MSFTNGP09.phx.gbl...
> Hi all,
>
> I tried to create a CEPC platform based on an old Pentium 3 PC with a 3Com
> 3c90x Ethernet interface. I had used the CEPCBOOT.144 utility to create
the
> boot diskette. The PC was booted up with the default
> config.sys/autoexec.bat options. The ethernet interface was correctly
> identified by loadcepc as a 3Com 3c90x ethernet interface but eboot.bin
> failed in trying to obtain an IP address via DHCP with the message:
>
> ProcessDHCP()::DHCP_INIT
>
> I sniffed the ethernet interface to verify that the CEPC was not sending
out
> any packets at all.
>
> I had also tried to assign a static IP address to see if the CEPC would
> contact my development machine with BOOTME requests. Again, I did not
> detect any packets coming from the CEPC.
>
> Does anyone know what could be the problem?
>
>
>