Re: Debug works, Release hangs


I am certain I am building my image (in PB) with KITL disabled. Debug
messages mentioning KITL are from the bootloader.
Does the bootloader need to disable KITL somehow? I thought that was only a
switch in the main image, and I am doing a sysgen after changing the settings.
Are there Build Options I need to change between Debug and Release builds
besides "Enable KITL" and "Enable CE Target Control Support"? The Debug
build I check them, the Release I uncheck them.

I am building an image with CE and an application, which all works fine as a
debug version, and runs out of flash.

"Bruce Eitman (eMVP)" wrote:

> Huh? Maybe you should tell us what you are doing and what is going wrong?
> Looks like maybe you have been vague. I thought that you were working with
> Platform Builder to create an OS image for Windows CE. Sounds like you are
> doing application development.
>
> One thing to check based on this output and still assuming that you are
> using PB, disable KITL.
>
> --
> Bruce Eitman (eMVP)
> Senior Engineer
> beitman AT applieddata DOT net
>
> Applied Data Systems
> www.applieddata.net
> An ISO 9001:2000 Registered Company
> Microsoft WEP Gold-level Member
>
>
> "photon209" <photon209@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:815A4A1F-B90A-438A-8DD7-BFE3849CC768@xxxxxxxxxxxxxxxx
> > I'm not positive what you mean by Startup, but I placed a RETAILMSG atthe
> > very start of WinMain in our application. Below is what's spat out on the
> > debug serial port. Is Startup someplace earlier?
> >
> > -ed
> >
> >
> >
> >
> > Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built
> > Apr 8
> > 2005 17:32:57
> >
> > BootloaderMain: Restart from Power-up Reset
> > BootloaderMain: Download Command:0x0
> > BootloaderMain: Download Address:0x0
> > BootloaderMain: Download Length:0x0
> > BootloaderMain: Download Flash Image
> > Microsoft Windows CE Loader 2.0 for AMD DBAu1000 Built Apr 11 2005 at
> 11:52:14
> > BootloaderMain: System ready!
> > BootloaderMain: Preparing for download...
> > INFO: Predownload....
> > OEMPreDownload: Boot configuration found at 0x9fc60000
> > 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...
> > BLFlashDownload: Checking Primary Image Signature at 0x9e000040
> > BLFlashDownload: Primary Image Signature Found
> > BLFlashDownload: Primary Image Checksum = 0x1f270ecc
> > BLFlashDownload: Primary Image Calculated Checksum = 0x1f270ecc
> > BLFlashDownload: Primary Image Checksum Valid
> >
> > ROMHDR (pTOC = 0x9e71bd04) ---------------------
> > DLL First : 0x01f401f4
> > DLL Last : 0x02000000
> > Physical First : 0x80001000
> > Physical Last : 0x8071e274
> > Num Modules : 84
> > RAM Start : 0x8071f000
> > RAM Free : 0x80760000
> > RAM End : 0x83fff800
> > Num Copy Entries : 6
> > Copy Entries Offset : 0x8022dee4
> > Prof Symbol Length : 0x00000000
> > Prof Symbol Offset : 0x00000000
> > Num Files : 97
> > Kernel Flags : 0x00000000
> > FileSys RAM Percent : 0x80808080
> > Driver Glob Start : 0x00000000
> > Driver Glob Length : 0x00000000
> > CPU : 0x0166
> > MiscFlags : 0x0002
> > Extensions : 0x80002020
> > Tracking Mem Start : 0x00000000
> > Tracking Mem Length : 0x00000000
> > BLFlashDownload: Copy from FLASH:0x9e000000 to RAM:0x80001000
> LEN:0x0071d274
> > BLFlashDownload: Done
> > OEMPreDownload: Return = BL_JUMP
> > OEMLaunch: OEMLaunch(0x00000000,0x00000000,0x00000000,0x00000000)
> > OEMLaunch: pArgs->kitl.flags = 0x00000005
> > OEMLaunch: pArgs->kitl.devLoc = 0x00000000
> > OEMLaunch: pArgs->kitl.mac = 00:0d:cf:ff:ff:f6
> > OEMLaunch: pArgs->kitl.ipAddress = 0.0.0.0
> > OEMLaunch: pArgs->kitl.ipMask = 0.0.0.0
> > OEMLaunch: pArgs->kitl.ipRoute = 0.0.0.0
> > OEMLaunch: Windows CE .NET Launch address = 0x80001000
> > Windows CE Kernel for MIPS Built on Jun 24 2004 at 18:24:50
> > OEMIoControl: Unsupported Code 0x10100b4 - device 0x0101 func 45
> >
> >
> > then nothing more.....
> >
> > "Bruce Eitman (eMVP)" wrote:
> >
> > > Are you even getting to your Startup?
> > >
> > > --
> > > Bruce Eitman (eMVP)
> > > Senior Engineer
> > > beitman AT applieddata DOT net
> > >
> > > Applied Data Systems
> > > www.applieddata.net
> > > An ISO 9001:2000 Registered Company
> > > Microsoft WEP Gold-level Member
> > >
> > >
> > > "photon209" <photon209@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:63FC66CB-9FC3-489E-97BA-A108ADFBE525@xxxxxxxxxxxxxxxx
> > > >
> > > > I think there may be some other issue. A RETAILMSG right at the start
> of
> > > my
> > > > application code doesn't get printed, so I don't think it's even
> starting
> > > my
> > > > code.
> > > >
> > > > I assume variable declarations like "char g_rtcInit = FALSE;" are
> > > > initialized, but I don't think I've made any assumptions about
> variables
> > > > being zero without me expressly setting them.
> > > >
> > > >
> > > >
> > > > "Bruce Eitman (eMVP)" wrote:
> > > >
> > > > > It should work, but if you are using a variable that you expect the
> > > compiler
> > > > > to init to zero, that isn't going to happen in the retail build.
> > > RETAILMSG
> > > > > could be your friend in figuring this out.
> > > > >
> > > > > --
> > > > > Bruce Eitman (eMVP)
> > > > > Senior Engineer
> > > > > beitman AT applieddata DOT net
> > > > >
> > > > > Applied Data Systems
> > > > > www.applieddata.net
> > > > > An ISO 9001:2000 Registered Company
> > > > > Microsoft WEP Gold-level Member
> > > > >
> > > > >
> > > > > "photon209" <photon209@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > news:002CA722-330A-4FD9-87F0-0D67F34EF831@xxxxxxxxxxxxxxxx
> > > > > >
> > > > > > Any basic settings I may be missing that may cause the Release
> build
> > > to
> > > > > > hang, when the debug build works fine?
> > > > > >
> > > > > > I've tried just changing just the Build Type on the General Tab in
> > > > > > Platform->Settings to see if that would work. The code loads from
> > > flash,
> > > > > but
> > > > > > stops right after the Win CE Kernal message.
> > > > > >
> > > > > > I have KITL disabled, and have had the Debug version run from
> flash
> > > (no
> > > > > PB)
> > > > > > with no problems.
> > > > > >
> > > > > > Is there something I'm missing?
> > > > > >
> > > > > > -ed
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>
.

Relevant Pages

  • Re: just cut the kitl cord and my ethernet stopped working
    ... an ip address that was passed along to the debug ethernet connection. ... (I do know it isn't the same one as the bootloader ... Ship version of the image removes KITL support and other debug stuff. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Redirecting debug messages from PB/lan to serial
    ... >I think you can keep the KITL, DEBUG version and so on. ... >> release configuration. ... >>> I need to send this image to the BIOS folks who don't have PB and would ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Connecting to device for debugging
    ... Before starting the CE kernel, the bootloader sets some parameters passed to ... Some of them refers to the ethernet settings that should be used ... The KITL connection is driven by 2 things: ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Debugging Interrupt Vector Tables (IVTs)
    ... A more useful question would be centred on why you want to "debug IVT". ... able to debug using the debugger without loosing any control if i debug ... within the bootloader /application. ...
    (comp.os.linux.embedded)
  • Re: problem in downloading nk.bin
    ... Sorry, but that's no debug output, that's just the bootloader's ... bootloader, or do you simply mean you've compiled and flashed it? ... target stops sending UDP packet and the development workstation also ... RESERVED1 80001000 0000F000 RESERVED ...
    (microsoft.public.windowsce.platbuilder)