DEBUGCHK failed in file problem

Tutorials Win: Microsoft Windows Forum

Hi All,

I am working on WINCE 6.0 BSP development. I have developed BSP for
MC9328MXL
I have built DEBUG version with KITL and Kernel Debugger enabled while
building.
while booting I am facing problem.
Can anyone please help me regarding DEBUGCHK failed in file problem
that I get while debugging
Below is the debug information I get on my platform builder



4294767296 PID:400002 TID:b60002 Ceddk!CalibrateStallCounter: Could
not find stall counter
4294767296 PID:400002 TID:b60002 Ceddk!BeginCalibration: min(96001)
max(106667)
4294767296 PID:400002 TID:b60002 Ceddk!BeginCalibration: Elapsed is
101121
4294767296 PID:400002 TID:b60002 Ceddk!BeginCalibration: Delay is 14
4294767296 PID:400002 TID:b60002 +PmInit
4294767296 PID:400002 TID:b60002 -PmInit: returning 1
4294767296 PID:400002 TID:b60002 DEVICE!DevloadInit
4294767296 PID:400002 TID:b60002 DEVICE!InitDevices: Root Key is
Drivers\BuiltIn.
4294767296 PID:400002 TID:b60002 DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2
4294767296 PID:400002 TID:b60002 DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2
4294767296 PID:400002 TID:b60002 OSAXST1: >>> Loading Module
'busenum.dll' (0x83F676B4) at address 0xC0470000-0xC047B000 in Process
'NK.EXE' (0x809B1AA0)
PB Debugger Loaded symbols for 'E:\WINCE600\OSDESIGNS
\TINY_KITL_WORKNG_DBG\TINY_KITL_WORKNG_DBG\RELDIR\MC9328_ARMV4I_DEBUG
\BUSENUM.DLL'
4294767296 PID:400002 TID:650002 FILESYS: SignalStarted loop = 1
4294767296 PID:400002 TID:650002 FILESYS: Launching gwes.dll
4294767296 PID:400002 TID:650002 OSAXST1: >>> Loading Module
'gwes.dll' (0x83F678D0) at address 0xC0250000-0xC0416000 in Process
'NK.EXE' (0x809B1AA0)
PB Debugger Loaded symbols for 'E:\WINCE600\OSDESIGNS
\TINY_KITL_WORKNG_DBG\TINY_KITL_WORKNG_DBG\RELDIR\MC9328_ARMV4I_DEBUG
\GWES.DLL'
4294767296 PID:400002 TID:650002 Filesys: Loaded gwes.dll
4294767296 PID:400002 TID:650002 FILESYS: Done launching apps
4294767296 PID:400002 TID:650002 -DEVICE!DevloadPostInit
4294767296 PID:400002 TID:650002 This device has booted 1 times !!!
4294767296 PID:400002 TID:d40002 Ceddk!CalibrateStallCounter: Enter
4294767296 PID:400002 TID:d40002 Ceddk!CalibrateStallCounter: Stall
counter loaded from registry(14)
4294767296 PID:400002 TID:d40002 System Default HKL value set to
00000409
4294767296 PID:400002 TID:d40002 Grow Gdi handle table from 0 to 64
4294767296 PID:400002 TID:d40002 LogFontFromRegistry(SYSTEM\GDI
\SysFnt), lfHeight = -12
4294767296 PID:400002 TID:d40002 *** FAILED TO FIND SPECIFIED DISPLAY
DRIVER! ***
4294767296 PID:400002 TID:d40002 *** ATTEMPTING TO LOAD DISPLAY DRIVER
DDI.DLL! ***
4294767296 PID:400002 TID:d40002 *** COULD NOT LOAD DISPLAY DRIVER
(DDI.DLL)! ***
4294767296 PID:400002 TID:d40002 *** ATTEMPTING TO LOAD DISPLAY DRIVER
DDI_NOP.DLL! ***
4294767296 PID:400002 TID:d40002 *** COULD NOT LOAD DISPLAY DRIVER
(DDI_NOP.DLL)! ***
4294767296 PID:400002 TID:d40002 *** GWES FAILED TO LOAD A DISPLAY
DRIVER!!! PREPARE FOR MAYHEM!!! ***
4294767296 PID:400002 TID:d40002 Unknown: DEBUGCHK failed in file C:
\ymzki\private\winceos\COREOS\gwe\mgdi\base\.\gdi.cpp at line 2635

I have not developed LCD driver for the board yet. Is this anything
related to LCD driver?
Please anyone know about this help me.


Thanks,
Chitra
Top

Re: DEBUGCHK failed in file problem by Dean

Dean
Wed Oct 31 05:57:05 PDT 2007

The messages aren't very subtle, are they? Yes, the problem is you don't
have a display driver. Unless you have configured the OS for a headless
build, a display driver is absolutely required. If you aren't ever going to
need one, then change your OS config to a headless build. If you just
haven't gotten there yet, you can include the NULL display driver. The NULL
driver will not talk to hardware, but it does present everything gwes needs
to be happy.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Chitra" <chitrar25@yahoo.co.in> wrote in message
news:1193824273.398040.221590@z24g2000prh.googlegroups.com...
> Hi All,
>
> I am working on WINCE 6.0 BSP development. I have developed BSP for
> MC9328MXL
> I have built DEBUG version with KITL and Kernel Debugger enabled while
> building.
> while booting I am facing problem.
> Can anyone please help me regarding DEBUGCHK failed in file problem
> that I get while debugging
> Below is the debug information I get on my platform builder
>
>
>
> 4294767296 PID:400002 TID:b60002 Ceddk!CalibrateStallCounter: Could
> not find stall counter
> 4294767296 PID:400002 TID:b60002 Ceddk!BeginCalibration: min(96001)
> max(106667)
> 4294767296 PID:400002 TID:b60002 Ceddk!BeginCalibration: Elapsed is
> 101121
> 4294767296 PID:400002 TID:b60002 Ceddk!BeginCalibration: Delay is 14
> 4294767296 PID:400002 TID:b60002 +PmInit
> 4294767296 PID:400002 TID:b60002 -PmInit: returning 1
> 4294767296 PID:400002 TID:b60002 DEVICE!DevloadInit
> 4294767296 PID:400002 TID:b60002 DEVICE!InitDevices: Root Key is
> Drivers\BuiltIn.
> 4294767296 PID:400002 TID:b60002 DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2
> 4294767296 PID:400002 TID:b60002 DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2
> 4294767296 PID:400002 TID:b60002 OSAXST1: >>> Loading Module
> 'busenum.dll' (0x83F676B4) at address 0xC0470000-0xC047B000 in Process
> 'NK.EXE' (0x809B1AA0)
> PB Debugger Loaded symbols for 'E:\WINCE600\OSDESIGNS
> \TINY_KITL_WORKNG_DBG\TINY_KITL_WORKNG_DBG\RELDIR\MC9328_ARMV4I_DEBUG
> \BUSENUM.DLL'
> 4294767296 PID:400002 TID:650002 FILESYS: SignalStarted loop = 1
> 4294767296 PID:400002 TID:650002 FILESYS: Launching gwes.dll
> 4294767296 PID:400002 TID:650002 OSAXST1: >>> Loading Module
> 'gwes.dll' (0x83F678D0) at address 0xC0250000-0xC0416000 in Process
> 'NK.EXE' (0x809B1AA0)
> PB Debugger Loaded symbols for 'E:\WINCE600\OSDESIGNS
> \TINY_KITL_WORKNG_DBG\TINY_KITL_WORKNG_DBG\RELDIR\MC9328_ARMV4I_DEBUG
> \GWES.DLL'
> 4294767296 PID:400002 TID:650002 Filesys: Loaded gwes.dll
> 4294767296 PID:400002 TID:650002 FILESYS: Done launching apps
> 4294767296 PID:400002 TID:650002 -DEVICE!DevloadPostInit
> 4294767296 PID:400002 TID:650002 This device has booted 1 times !!!
> 4294767296 PID:400002 TID:d40002 Ceddk!CalibrateStallCounter: Enter
> 4294767296 PID:400002 TID:d40002 Ceddk!CalibrateStallCounter: Stall
> counter loaded from registry(14)
> 4294767296 PID:400002 TID:d40002 System Default HKL value set to
> 00000409
> 4294767296 PID:400002 TID:d40002 Grow Gdi handle table from 0 to 64
> 4294767296 PID:400002 TID:d40002 LogFontFromRegistry(SYSTEM\GDI
> \SysFnt), lfHeight = -12
> 4294767296 PID:400002 TID:d40002 *** FAILED TO FIND SPECIFIED DISPLAY
> DRIVER! ***
> 4294767296 PID:400002 TID:d40002 *** ATTEMPTING TO LOAD DISPLAY DRIVER
> DDI.DLL! ***
> 4294767296 PID:400002 TID:d40002 *** COULD NOT LOAD DISPLAY DRIVER
> (DDI.DLL)! ***
> 4294767296 PID:400002 TID:d40002 *** ATTEMPTING TO LOAD DISPLAY DRIVER
> DDI_NOP.DLL! ***
> 4294767296 PID:400002 TID:d40002 *** COULD NOT LOAD DISPLAY DRIVER
> (DDI_NOP.DLL)! ***
> 4294767296 PID:400002 TID:d40002 *** GWES FAILED TO LOAD A DISPLAY
> DRIVER!!! PREPARE FOR MAYHEM!!! ***
> 4294767296 PID:400002 TID:d40002 Unknown: DEBUGCHK failed in file C:
> \ymzki\private\winceos\COREOS\gwe\mgdi\base\.\gdi.cpp at line 2635
>
> I have not developed LCD driver for the board yet. Is this anything
> related to LCD driver?
> Please anyone know about this help me.
>
>
> Thanks,
> Chitra
>


Top

Re: DEBUGCHK failed in file problem by Chitra

Chitra
Wed Oct 31 06:18:34 PDT 2007

Thanks for your reply.

Can I build for Small footprint Design template.


On Oct 31, 5:57 pm, "Dean Ramsier" <ramsiernos...@nospam.com> wrote:
> The messages aren't very subtle, are they? Yes, the problem is you don't
> have a display driver. Unless you have configured the OS for a headless
> build, a display driver is absolutely required. If you aren't ever going to
> need one, then change your OS config to a headless build. If you just
> haven't gotten there yet, you can include the NULL display driver. The NULL
> driver will not talk to hardware, but it does present everything gwes needs
> to be happy.
>
> --
> Dean Ramsier - eMVP
> BSQUARE Corporation
>
> "Chitra" <chitra...@yahoo.co.in> wrote in message
>
> news:1193824273.398040.221590@z24g2000prh.googlegroups.com...
>
>
>
> > Hi All,
>
> > I am working on WINCE 6.0 BSP development. I have developed BSP for
> > MC9328MXL
> > I have built DEBUG version with KITL and Kernel Debugger enabled while
> > building.
> > while booting I am facing problem.
> > Can anyone please help me regarding DEBUGCHK failed in file problem
> > that I get while debugging
> > Below is the debug information I get on my platform builder
>
> > 4294767296 PID:400002 TID:b60002 Ceddk!CalibrateStallCounter: Could
> > not find stall counter
> > 4294767296 PID:400002 TID:b60002 Ceddk!BeginCalibration: min(96001)
> > max(106667)
> > 4294767296 PID:400002 TID:b60002 Ceddk!BeginCalibration: Elapsed is
> > 101121
> > 4294767296 PID:400002 TID:b60002 Ceddk!BeginCalibration: Delay is 14
> > 4294767296 PID:400002 TID:b60002 +PmInit
> > 4294767296 PID:400002 TID:b60002 -PmInit: returning 1
> > 4294767296 PID:400002 TID:b60002 DEVICE!DevloadInit
> > 4294767296 PID:400002 TID:b60002 DEVICE!InitDevices: Root Key is
> > Drivers\BuiltIn.
> > 4294767296 PID:400002 TID:b60002 DEVICE!RegReadActivationValues
> > RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2
> > 4294767296 PID:400002 TID:b60002 DEVICE!RegReadActivationValues
> > RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2
> > 4294767296 PID:400002 TID:b60002 OSAXST1: >>> Loading Module
> > 'busenum.dll' (0x83F676B4) at address 0xC0470000-0xC047B000 in Process
> > 'NK.EXE' (0x809B1AA0)
> > PB Debugger Loaded symbols for 'E:\WINCE600\OSDESIGNS
> > \TINY_KITL_WORKNG_DBG\TINY_KITL_WORKNG_DBG\RELDIR\MC9328_ARMV4I_DEBUG
> > \BUSENUM.DLL'
> > 4294767296 PID:400002 TID:650002 FILESYS: SignalStarted loop = 1
> > 4294767296 PID:400002 TID:650002 FILESYS: Launching gwes.dll
> > 4294767296 PID:400002 TID:650002 OSAXST1: >>> Loading Module
> > 'gwes.dll' (0x83F678D0) at address 0xC0250000-0xC0416000 in Process
> > 'NK.EXE' (0x809B1AA0)
> > PB Debugger Loaded symbols for 'E:\WINCE600\OSDESIGNS
> > \TINY_KITL_WORKNG_DBG\TINY_KITL_WORKNG_DBG\RELDIR\MC9328_ARMV4I_DEBUG
> > \GWES.DLL'
> > 4294767296 PID:400002 TID:650002 Filesys: Loaded gwes.dll
> > 4294767296 PID:400002 TID:650002 FILESYS: Done launching apps
> > 4294767296 PID:400002 TID:650002 -DEVICE!DevloadPostInit
> > 4294767296 PID:400002 TID:650002 This device has booted 1 times !!!
> > 4294767296 PID:400002 TID:d40002 Ceddk!CalibrateStallCounter: Enter
> > 4294767296 PID:400002 TID:d40002 Ceddk!CalibrateStallCounter: Stall
> > counter loaded from registry(14)
> > 4294767296 PID:400002 TID:d40002 System Default HKL value set to
> > 00000409
> > 4294767296 PID:400002 TID:d40002 Grow Gdi handle table from 0 to 64
> > 4294767296 PID:400002 TID:d40002 LogFontFromRegistry(SYSTEM\GDI
> > \SysFnt), lfHeight = -12
> > 4294767296 PID:400002 TID:d40002 *** FAILED TO FIND SPECIFIED DISPLAY
> > DRIVER! ***
> > 4294767296 PID:400002 TID:d40002 *** ATTEMPTING TO LOAD DISPLAY DRIVER
> > DDI.DLL! ***
> > 4294767296 PID:400002 TID:d40002 *** COULD NOT LOAD DISPLAY DRIVER
> > (DDI.DLL)! ***
> > 4294767296 PID:400002 TID:d40002 *** ATTEMPTING TO LOAD DISPLAY DRIVER
> > DDI_NOP.DLL! ***
> > 4294767296 PID:400002 TID:d40002 *** COULD NOT LOAD DISPLAY DRIVER
> > (DDI_NOP.DLL)! ***
> > 4294767296 PID:400002 TID:d40002 *** GWES FAILED TO LOAD A DISPLAY
> > DRIVER!!! PREPARE FOR MAYHEM!!! ***
> > 4294767296 PID:400002 TID:d40002 Unknown: DEBUGCHK failed in file C:
> > \ymzki\private\winceos\COREOS\gwe\mgdi\base\.\gdi.cpp at line 2635
>
> > I have not developed LCD driver for the board yet. Is this anything
> > related to LCD driver?
> > Please anyone know about this help me.
>
> > Thanks,
> > Chitra- Hide quoted text -
>
> - Show quoted text -


Top