Re: Platform Builder Ignoring BOOTME message



Is the name of the device visible in the list of detected devices? If
yes, then PB is able to receive the BOOTME packets.
Probably there is error after that.

Also see the debug message on your device (which are sent out of the
debug Serial port).

On Sep 13, 2:08 pm, "Karel Danihelka"
<Karel.Danihe...@xxxxxxxxxxxxxxxxxxxx> wrote:
I would suggest look to firewall settings on host machine. It looks like
firewall blocks BOOTME packets from PB and/or reply to them.

Karel Danihelka
--
Kar...@xxxxxxxxxxxxxxxxxxxx (remove "online" from reply-to address)
This posting is provided "AS IS" with no warranties, and confers no rights.

"Roger Williamson" <RogerWilliam...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
messagenews:0FB5A522-2DDE-48E4-A491-3917E863E840@xxxxxxxxxxxxxxxx

I've configured my development board to send the BOOTME UDP packet along
the
Ethernet cable. It sends the message every second, and I can see the
packets
coming in on my computer.

The packet (picked up by Ethereal):
0000 ff ff ff ff ff ff 00 04 f3 00 a3 55 08 00 45 00 ........ ...U..E.
0010 00 5c 20 00 00 00 40 11 6f cb c0 a8 2a 1e ff ff .\ ...@. o...*...
0020 ff ff 03 d4 03 d4 00 48 75 4d 45 44 42 47 ff 01 .......H uMEDBG..
0030 20 00 01 00 00 04 f3 00 a3 55 c0 a8 2a 1e 43 43 ....... .U..*.CC
0040 58 50 5f 00 00 00 00 00 00 00 00 00 00 00 00 43 XP_..... .......C
0050 43 58 50 5f 34 31 38 31 33 00 00 00 00 00 00 00 CXP_4181 3.......
0060 41 02 00 00 00 00 00 00 00 00 A....... ..

The platform Builder: "Download Runtime Image to ..." window comes up, and
PB displays this message in the debug box:
Cannot access selected Device from service host.
The Kernel Debugger is waiting to connect with target.
Debugger could not initialize connection.
The Kernel Debugger has been disconnected successfully.

My development board sends a BOOTME message every second, and PB just flat
ignores the message, it seems.

I have a few theories:
1) The packet is incorrect
2) PB is looking at my other ethernet port (tested, it is not)
3) My configurations are wrong (I'm set to look at IP 192.168.42.30, the
device is 192.168.42.30)
4) My development board is broadcasting the packet wrong (I don't know if
255.255.255.255 is correct or even a sane broadcast IP)

Anyway,
Thanks for your help,
Roger


.



Relevant Pages

  • RE: Cisco IOS exploit (44020)
    ... Subject: Cisco IOS exploit ... various protocols and sends 19 packets ... DEBUG: Protocol: 53 ...
    (Bugtraq)
  • [Full-Disclosure] [Fwd: RE: Cisco IOS exploit (44020)]
    ... Subject: Cisco IOS exploit ... various protocols and sends 19 packets ... DEBUG: Protocol: 53 ...
    (Full-Disclosure)
  • RE: Cisco IOS exploit (44020)
    ... various protocols and sends 19 packets ... Cisco IOS device and is the TTL subtracted by 255. ... DEBUG: Protocol: 53 ...
    (Bugtraq)
  • Re: GMail [and other free email] and these lists?
    ... Under SunOS, I typically apply the multicast patches (available from ... this may result in some packets beingfragmented by routers just ... Using kadbkadb is the Sun kernel debugger. ... Patching variables9.2. ...
    (freebsd-questions)
  • Re: Platform Builder Ignoring BOOTME message
    ... beitman AT applieddata DOT net ... My debug port just asserts that the uboot is shooting out the packets ... those packets, and waiting for the runtime image to be uploaded into it. ...
    (microsoft.public.windowsce.platbuilder)