Re: About EBOOT and WIN CE Image?(EP9302)
- From: "John Lee" <jinhualee@xxxxxxx>
- Date: 20 Sep 2006 23:23:21 -0700
Michel Verhagen (eMVP) wrote:
Do you have a DHCP server on your network? It looks like eboot can't
connect to a DHCP server. If you are using CEPC HW, you can use loadcepc
to set a static IP instead of a dynamic (DHCP supplied) one.
Michel Verhagen,
I am sure there is a DHCP server on our network.
After that,I try to download a old version EBOOT and OS IMAGE to my
newly hardware platform,it is not successful yet. And the HyperTerminal
show message as below.The old version OS IMAGE can download to my old
hardware platform smoothly.Moreover,there is no differece between my
newly hardware platform and the old one but the size.
I suspect RAM(K4S561632E),FLASH(E28F128JA),or ETHERNET(CS8952T) is
wrong.
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
Microsoft Windows CE Ethernet Bootloader Common Library Version 1.0
Built Sep 20
2006 16:49:51
Copyright (c) 2000-2001 Microsoft Corporation
============================================================
EP931x Windows CE Ethernet Bootloader
(Built on Sep 20 2006 16:49:56)
============================================================
Downloading BIN file using Ethernet.
EEINFO: SPI Device Not detected.
CS8950DMAInit: dwPhysicalAddr = 0x10000, dwVirtualAddr= 0x10000 dwSize
= 0x3000
0
Card Type = CS8950, Address =
CS8950Init: pbBaseAddress = 0x80010000
CS8950Init: pChip = 0x5FA40, pChip->pData = 0x5EFA0
CS8950: Speed = 100 Mbs, Duplex = Full.
System ready!
Preparing for download...
INFO: Using device name: 'EDB93014660'
InitDHCP():: Calling ProcessDHCP()
ProcessDHCP()::DHCP_INIT
Got Response from DHCP server, IP address: 192.168.101.18
ProcessDHCP()::DHCP IP Address Resolved as 192.168.101.18, netmask:
255.255.255.
0
Lease time: 8640000 seconds
Got Response from DHCP server, IP address: 192.168.101.18
No ARP response in 2 seconds, assuming ownership of 192.168.101.18
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Locked Down Link 1
Src IP 192.168.101.18 Port 0800 Dest IP 192.168.101.118 Port 042F
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp
Erasing flash blocks: start Addr = 0x60000000 length = 0xB671B0
(It is reset itself here.)//John Lee
Microsoft Windows CE Ethernet Bootloader Common Library Version 1.0
Built Sep 20
2006 16:49:51
Copyright (c) 2000-2001 Microsoft Corporation
============================================================
EP931x Windows CE Ethernet Bootloader
(Built on Sep 20 2006 16:49:56)
============================================================
Downloading BIN file using Ethernet.
EEINFO: SPI Device Not detected.
CS8950DMAInit: dwPhysicalAddr = 0x10000, dwVirtualAddr= 0x10000 dwSize
= 0x3000
0
Card Type = CS8950, Address = 0x80010000.
CS8950Init: pbBaseAddress = 0x80010000
CS8950Init: pChip = 0x5FA40,
CS8950: Speed = 100 Mbs, Duplex = Full.
System ready!
Preparing for download...
INFO: Using device name: 'EDB93014660'
InitDHCP():: Calling ProcessDHCP()
ProcessDHCP()::DHCP_INIT
Got Response from DHCP server, IP address: 192.168.101.18
ProcessDHCP()::DHCP IP Address Resolved as 192.168.101.18, netmask:
255.255.255.0
Lease time: 8640000 seconds
Got Response from DHCP server, IP address: 192.168.101.18
No ARP response in 2 seconds, assuming ownership of 192.168.101.18
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
TFTP link[0]: State:0, DestAddr.wPort: 0, SrcAddr.wPort: 0
TFTP link[1]: State:0, DestAddr.wPort: 0, SrcAddr.wPort: 0
TftpReceiver, port: 0x00000008, wkp: 0x0000D403
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
TFTP link[0]: State:0, DestAddr.wPort: 0, SrcAddr.wPort: 0
TFTP link[1]: State:0, DestAddr.wPort: 0, SrcAddr.wPort: 0
TftpReceiver, port: 0x00000008, wkp: 0x0000D403
Sent BOOTME to 255.255.255.255
.
- Follow-Ups:
- Re: About EBOOT and WIN CE Image?(EP9302)
- From: John Lee
- Re: About EBOOT and WIN CE Image?(EP9302)
- References:
- About EBOOT and WIN CE Image?(EP9302)
- From: John Lee
- Re: About EBOOT and WIN CE Image?(EP9302)
- From: Michel Verhagen (eMVP)
- About EBOOT and WIN CE Image?(EP9302)
- Prev by Date: Re: Kernel Debugging problem
- Next by Date: Re: Deteremining system idle time (from mouse/keybaord input without system hooks)
- Previous by thread: Re: About EBOOT and WIN CE Image?(EP9302)
- Next by thread: Re: About EBOOT and WIN CE Image?(EP9302)
- Index(es):
Relevant Pages
|