Re: platform builder 4.2 debugger cannot connect to target

Hi,

Thanks for your response, Paul.

I have a 10 M Extension Ethernet card. I am using an EMBEST PXA255DB
Development platform. Not sure what a VMini network adapter is, how
can I find out whether this is part of the image? The board has a
network card and I have added the network driver to the image.

Here are the debug components in PB platform settings:

Enable CE Target Control Support --- yes
Enable Eboot Space in Memory --- yes
Enable Event Tracking during Boot --- no
Enable Full Kernel Mode --- yes
Enable Image for Flash --- yes
Enable Images Larger than 32 MB --- yes
Enable Kernel Debugger --- yes
Enable KITL --- yes
Enable Profiling --- no
Flush Events to Release Directory --- no

In addition, the following environment variables are defined:
BSP_LUBBOCK 1
PLAT_CIMSUN 1

I captured the serial port output during the download and boot up.
During the bootup process, I get the following message:

0x82cbe024: ERROR:
d:\mckendric\private\winceos\coreos\nk\kernel\kwin32.c line 649:
0x82cbe024: ConnectDebugger failed

Guess something is wrong, could you help. (I am attaching the sequence
of debug messages output to the serial port below).

Thanks for your help.
Harish

# InitSpecifiedEthDevice(): Checking for CS8900 Ethernet controller...
Entering CS8900DBG_Init().
dwEthernetIOBase = 0xBE300300
CS8900: MAC Address: 0:10:1:10:2:10
INFO: Probe: CS8900 is detected.
CS8900 Ethernet controller initialized.
pDriverGlobals->eth.EbootDevice.(0xA3DC8806 : 0x00000003)
Device identification: CEB255528
InitDHCP():: Calling ProcessDHCP()
ProcessDHCP()::DHCP_INIT
Waiting for DHCP assignment...
ProcessDHCP()::DHCP IP Address Resolved as 172.16.4.135, netmask:
255.255.255.0
Lease time: 28800 seconds
No ARP response in 2 seconds, assuming ownership of 172.16.4.135
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
Locked Down Link 1
Src IP 172.16.4.135 Port 0800 Dest IP 172.16.4.123 Port 060D
EthDown::TFTPD_OPEN::boot.bin
Downloading .BIN file
Downloading operating system image for flash target.
Image start: 0x98380000 length: 0x01C5B124 cache location: 0x800C0000
...................................................................................................................................................................................................Got
EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
Network Transfer Complete


Verify checksums...
Checksums verified correct.
# Main.c : fileType = BIN
# Main.c : fileType = FLASHTARGET
Found pTOC signature in downloaded image.
Preparing to write 0x1C5B124 bytes to flash from RAM address 0x800C0000
FStartAddr = 0xB8380000 , FCacheAddr = 0xA00C0000.
Erasing Flash B8380000 to B9FFFFFF: Please wait ...
...................................................................................................................
Performing erase verification ...
Flash erasing complete.

Now programming Flash ...
..................................................................................................................
Comparing Flash vs RAM image ...
Flash programmed successfully!
Storing image launch address to flash...
StoreEBootCFG.

Erasing Flash B8340000 to B837FFFF: Please wait ...
..
Performing erase verification ...
Flash erasing complete.
Found pTOC signature.
Download successful! Jumping to image at 98381000h...


Found pTOC signature.
ROMHDR at Address 99FD8ED0h
RomHdr.ulRAMStart=800C0000h RomHdr.physfirst=98380000h.
Verify checksums...
Checksums verified correct.
pDriverGlobals->eth.EdbgFlags( 0xA3DC8806 : 0x00000003)...
Download successful! Jumping to image at 98381000h...
OEMInitDebugSerial.

******************************************************

******************************************************

******************************************************

******************************************************

******************************************************

OEMInitDebugSerial using UART2

Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 13 2003 at
22:44:13

ProcessorType=02d0 Revision=6

sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable =
98381d90

Booting Windows CE version 4.20 for (ARM)

&pTOC = 9838a2bc, pTOC = 99fd8ed0, pTOC->ulRamFree = 800f3000, MemForPT
= 00000000



Old or invalid version stamp in kernel structures - starting clean!

Configuring: Primary pages: 11208, Secondary pages: 0, Filesystem pages
= 5604



Booting kernel with clean memory configuration:

Memory Sections:

[0] : start: 800f4000, extension: 00003000, length: 02bc8000

Sp=ffffc7cc

ARMInit done.

Windows CE KernelInit

Updated eptr->e32_vsize to = 000ab000

Scheduling the first thread.

0x82cbe024: KernelInit2: pCurThread=82cbe024 hCurThread=02cbe262
hCurProc=02cbe002, KernelInit = 983a3a00

0x82cbe024: Detecting VFP...0x82cbe024: VFP Not Found!
0x82cbe024: Updated eptr->e32_vsize to = 00016000

0x82cbe024: ERROR:
d:\mckendric\private\winceos\coreos\nk\kernel\kwin32.c line 649:
0x82cbe024: ConnectDebugger failed



Paul G. Tobey [eMVP] wrote:
Do you have the VMini network adapter in your image? It sounds like,
although you can connect to the device via KITL, you haven't included a
method for the OS to see that there's some sort of an Ethernet adapter, so
you have no one to respond to PING, etc.

What debug components do you have selected in the project settings in PB or
with IMGxyz environment variables?

Paul T.

"catspaw" <hsubbaram@xxxxxxxxx> wrote in message
news:1168379146.872344.8280@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello All,

I have a problem in starting the kernel debugger from platform builder
4.2. I am using the ethernet for downloading and kernel transport. My
PC is running windows xp professional, and the target is running wince
4.2.

Both the PC and the board are connected to a hub. I can see messages
go back and forth while downloading. However, I cannot ping the board
from my PC after the image is downloaded and the platform is up and
running.

I also cannot download an application from EVC 4.2.

When I try connecting to the target, I get this message:
"Kernel debugger is waiting to connect with target."

It never connects, so I disconnect. At this point, the following
message is output:
Kernel debugger failed to connect with target (KDBG open stream
failed).
Debugger could not initialize connection.

I am doing something wrong, can someone offer suggestions.

Thanks in advance.

Harry


.

Relevant Pages

  • Re: platform builder 4.2 debugger cannot connect to target
    ... Kernel Transport to Serial, ... to init KITL for Ethernet, not serial as it's doing now. ... I captured the serial port output during the download and boot up. ... Debugger could not initialize connection. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: failing to boot from mfsroot.gz
    ... > I have a 4.8 system that booted from flash using a kernel.gz and ... The ethernet parts were not fully supported by the fxp driver ... > but tells me that proc is out of sync with the kernel. ... To unsubscribe, ...
    (freebsd-questions)
  • Re: network problem when boot from flash,
    ... Trusting you, that the image is the same, then you are saying that Ethernet ... KITL is not working when the image is in flash, ... loader is initializing the Ethernet controller when you download, ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Trying to setup Linux on AT91RM9200EK
    ... >- Please tell us how did you configured your>kernel, ... I do have U BOOT already burned on flash at 20000000 address. ... I download the code through U Boot and ...
    (comp.os.linux.embedded)
  • Re: Trying to setup Linux on AT91RM9200EK
    ... >- Please tell us how did you configured your>kernel, ... I do have U BOOT already burned on flash at 20000000 address. ... I download the code through U Boot and ...
    (comp.os.linux.embedded)