OMAP2420 Kernel Debugging problem



Hi,

I'm porting Windows CE 6.0 on OMAP2420 SDP. I've used the H4SAMPLE BSP from
Microsoft. I've gave build and downloaded the image to the board via ethernet.

But i coulnt use the kernel debugger for debugging. The following are the
debug messages i received.

NAND X-Loader for OMAP2420 H4-Sample...
OSTToolBugFix: Skipped!


Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built
Feb 28 2006 12:17:23
Microsoft Windows CE EBOOT 1.0 for OMAP2420 H4-Sample. Built Feb 28 2006 at
12:19:54
INFO: Platform Init**
+OMAPLCDOpen

Screen Paint
-OMAPLCDOpen
System ready!
Preparing for download...
INFO: Predownload....
INFO: Boot configuration found
INFO: MAC found
Hit space to enter configuration menu 5...
Hit space to enter configuration menu 4...
Hit space to enter configuration menu 3...
Hit space to enter configuration menu 2...
Hit space to enter configuration menu 1...
LAN91Cxxx: Chip Id 4 Revision 9
INFO: Boot device uses MAC 10:20:30:40:50:61
+OALKitlCreateName('H4-', 0x2010:0x4030:0x6150, 0xa1baf784)
KITLID is 20509150
INFO: *** Device Name H4-205091500000 ***
InitDHCP():: Calling ProcessDHCP()
ProcessDHCP()::DHCP_INIT
Got Response from DHCP server, IP address: 172.29.38.23

ProcessDHCP()::DHCP IP Address Resolved as 172.29.38.23, netmask:
255.255.255.0
Lease time: 86640 seconds
Got Response from DHCP server, IP address: 172.29.38.23
No ARP response in 2 seconds, assuming ownership of 172.29.38.23
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Sent BOOTME to 255.255.255.255
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.29.38.23 Port 0800 Dest IP 172.29.38.153 Port 0C4C
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp
EbootInitEtherTransport Done
OEMMultiBINNotify: Download BIN file information:
-----------------------------------------------------------
[0]: Address=0x84000000 Length=0x0085c78c Base=0x80000000
-----------------------------------------------------------
DOWNLOAD_TYPE_RAM
rom_offset=0x0.
ROMHDR at Address 84000044h
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
INFO: Lauch Windows CE .NET by jumping to 0x800071e8...

MultiPort-II Debug Board Rev A.3.1 CPLD Rev B.A.3
Windows CE Kernel for ARM (Thumb Enabled) Built on Sep 6 2006 at 19:14:27
+OEMInit
OEMInit: DISABLING CLOCKS FOR FAC,HDQ
DeviceId................. H4-
pArgs->flags............. 0x35
pArgs->devLoc.IfcType.... 0
pArgs->devLoc.LogicalLoc. 0x8000300
pArgs->devLoc.PhysicalLoc 0x0
pArgs->devLoc.Pin........ 0
pArgs->ip4address........ 1
pDevice->Name............ s
pDevice->ifcType......... 0
pDevice->id.............. 0x8000300
pDevice->resource........ 0
pDevice->type............ 2
pDevice->pDriver......... 0x84869000
LAN91Cxxx: Chip Id 4 Revision 9
KITL: *** Device Name H4-14B7E079 ***
WARN: KITL will run in polling mode
KITL: DHCP get/renew device IP: 1
Connecting to Desktop
Connecting to Desktop .. resending
Connecting to Desktop .. resending
Connecting to Desktop .. resending
Connecting to Desktop .. resending
Connecting to Desktop .. resending
Connecting to Desktop .. resending
Connecting to Desktop .. resending
....

What should i do now. If i disable " Enable KITL on device boot". the image
is loading fine and i could be able to see the desktop screen. But i want to
use the kernel debugger.

Any suggestions welcome.

Regards,
Meenakshikumar S
.



Relevant Pages

  • Re: OMAP2420 Kernel Debugging problem
    ... But for Kernel, the funtion in name.c is taken. ... Connecting to Desktop .. ... Hit space to enter configuration menu 5... ...
    (microsoft.public.windowsce.platbuilder)
  • Re: WINCE 6.0 nk.bin Issue
    ... Now I have enabled KITL and build is Debug mode. ... PCI Device Configurations present)... ... Sent BOOTME to 255.255.255.255 ... This particular setting always throws Connecting to Desktop ..Resending ...
    (microsoft.public.windowsce.platbuilder)
  • Etehrnet Download issue
    ... Target PC:Pentium Machine with RealTek 8139 ethernet Card and with one COM Port. ... My Ethernet card is identified as CEPCRT4461 after nk.bin boots up and as CEPC4461 by eboot.bix code.This particular setting always throws Connecting to Desktop ..Resending mesages on HTerminal. ... PCI Device Configurations present)... ... Sent BOOTME to 255.255.255.255 ...
    (microsoft.public.windowsce.platbuilder)
  • Re: The PPP negotiation failed, coz serial loopback was detected
    ... Why are you not connecting to the net via that network ... Why are you bringing up eth0 at all? ... It's some helpful configuration that's screwed. ... The fact that pon can connect says the hardware is working. ...
    (alt.os.linux)
  • Re: Cisco VPN / Firewall configuration
    ... >>I'm connecting to the VPN server using NAT, as I have a firewall running ... > does not have the correct DNS server configured. ... From the Cisco 2000 VPN Concentrator Configuration page: ...
    (Fedora)

Loading