@mithi: "I am developing a BSP for a handheld device around a samsung ARM processor. I 
have got the EBOOT running till the point that it is broadcasting the BOOTME 
packets and in response expecting to receive the response packets through 
TFTP protocol.
I am able to detect the device in platform builder 5, as I am able to see 
the device ID in menu Target->connectivity options 
->Download->ethernet->settings.
After I select the device in platform builder and try to attach to device 
using option Target->Attach Device, I don't seem to be able to connect to 
target device, basically the corresponding dialog box just doesn't show any 
progress.
Basic issue I am seeing is that on target, there is no UDP packets received 
diretly addressed to the device. It's capturing lots of packets which are 
broadcasted or multicasted across the LAN.
This issue is coming even if I assign static IP address to target. I have 
tried even connecting the host PC and target directly using a cross cable 
also.
I am using LAN91C111 ethernet card.
Please suggest what could be the issue. I had assumed that since I am using 
standard WinCE code for this area(LAN91C driver and TFTP,DHCP protocols), it 
should all have worked pretty smoothly."
    @mithi: "Thanks for quick response. I think I have tried most of below suggestions.
I checked the IP traffic from my host PC to target and I am seeing host PC 
is sending multicast as well as Unicast packets to my target.
On Target side, I am seeing lots of multicast packets sent by my PC and  
other machines on the network, but never ever the unicast packet is received 
on target! The receive side must be working fine as I have tested that it 
gets dynamic IP address through DHCP process.
I have disabled the interrupts and system is basically working in polled 
mode only.
- mithi
<quote>"
    @pspacetobeynospam: "Check the Ethernet address of the device.  It sounds possible to be some 
dummy or just uninitialized value (0xffffffffffff).
Paul T.
"mithi" <email_address> wrote in message 
news:<email_address>
<quote>"
    @mithi: "I had manually supplied the MAC address of the device. Without a valid Mac 
address I don't think it will get a valid IP address through DHCP.
<quote>"
    @mocliamtoh: ""Without a valid Mac address I don't think it will get a valid IP address 
through DHCP."
Not always true - not all DHCP servers are equal.
Ensure that your MAC address filter matches the MAC address that you are 
using on the wire.
Verify that you do not have the multicast bit set in the MAC address, that 
is the lowest order bit in the highest byte.
Be careful with endians! 01-00-00-00-00-00 has the multicast bit set.
Geoff
. "
    @usenet: "For what it's worth, I was also unable to connect from PB to my target
system. (DHCP failing, network timeouts, could download NK.bin but not
connect to debug it etc.)
The solution was to isolate my system from the office network by
adding an additional network card to my PC, connected to a router, and
have the target system connected to the same router. 
(Router, not hub or switch, only to provide DHCP services to that
2-node networks. The router was configured to a different subnet so no
traffic to/from other office computers was redirected here)
Hope this helps,
R.W.
On Wed, 28 Nov 2007 12:00:00 -0800, mithi
<quote>
Roberto Waltman
[ Please reply to the group,
  return address is invalid ]"
    @mithi: "Thanks RW and sorry for not providing all details earlier only. i had 
connected my target with host PC directly also using cross cable, disabled 
the DHCP, assigned static IP address. Even then, I was in same state :-(
<quote>"
    @mithi: "Hi All,
Problem was in LAN91C driver, few settings in MAC registers are supposed to 
be read from EEPROM. In our board configuration, the EEPROM is put but the 
connections to ethernet chip are not setup. One of the registers to be loaded 
are for MAC address.
So no MAC address was being set for my device, and hence only 
broadcast/multicast traffic was received.
Thanks all for yours prompt and generous response. This was my first 
experience on this forum, and frankly I was positively surprised to see so 
many mails back.
cheers,
Mithi
<quote>"
    @pspacetobeynospam: "Just wait  ask a dumb question instead of one where all the basic 
information is in the original message, as was the case with this message! 
;-)
Paul T.
"mithi" <email_address> wrote in message 
news:<email_address>
<quote>"
{'source': 'USENET', 'other_information': '{"reply_count": 8, "forum_name": "microsoft.public.windowsce.embedded.20140610.mbox"}', 'file': 'data/output/usenet-microsoft.public.parquet'}