OS: Windows CE 6.0 R2
Updates: R2 Rollup, Jan-April 2008 Monthly Updates
Platform: ARM
Debug Build Options (Listed are Enabled):IMGEBOOT=1 IMGPROFILER=1
IMGRAM64=1
Total ROM Size: 56,156,288 bytes
Total .bin Size: 55,205,131 bytes

Recently while trying to debug another issue I went to load up a Debug
Build on my platform (I haven't really used a debug build at all since
I've done the Upgrade to R2.) and noticed that my image can no longer
successfully boot as it crashes during the initialization.

I didn't have either KITL or the Kernel Debugger loaded as I only
wanted the debug messages (and I'd have to use a Serial KITL as I'll
be doing tests that span a suspend and resume.)

After seeing the crash dump (and seeing nkprof) I decided to see if it
was the profiler that was causing the crash so I removed IMGPROFILER=1
from the Build Options and my Boot Crash seems to have gone away.
Although, I seem to be able to continue what I was working on I would
like to track down and fix this issue. Has anyone tried to use the
profiler with the Debug Build with R2 on an ARM platform? Has anyone
had any issues with it?

I have not used the profiler since installing R2 but have used it in
the Release Build with our platform prior to R2.

My config.bib basically has 2 MB assigned to the NK image and just
over 121MB assigned to the RAM. AUTOSIZE=ON and KERNELFIXUPS = ON.

The crash dump:

NK Kernel: DEBUGCHK failed in file C:\yzkiqfe\private\winceos\COREOS\nk
\kernel\nkprof\..\physmem.c at line 103

Faulted in KCall, pCurThread->dwStartAddr = c0784848, PageFreeCount =
000016b8!!
Original Context when thread faulted:
Exception 'Undefined Instruction'(1) Thread-Id=03820002(pth=85cdbdb0)
PC=c09b11f0 BVA=d0c5df40, dwInfo = 00000007
R0=d0c634f0 R1=d0c5eea4 R2=00000106 R3=00000001
R4=00004444 R5=00005555 R6=00006666 R7=00007777
R8=00008888 R9=00009999 R10=00001010 R11=00001111
R12=d0c5ee90 SP=d0c5dee4 Lr=c09ad694 Psr=2000001f
Context when faulted in KCall:
Exception 'Undefined Instruction'(1) Thread-Id=03820002(pth=ffffc124)
PC=8010d9a0 BVA=d0c5df40, dwInfo = 00000007
R0=0000de37 R1=03820002 R2=85cdbde8 R3=00000000
R4=d0c5eea4 R5=00000106 R6=00000001 R7=c09b11f0
R8=00008888 R9=00009999 R10=00001010 R11=00001111
R12=00000000 SP=ffffc274 Lr=8010d97c Psr=60000013

Thank you for any help,
Brad.

Re: Debug Crash when using Profiler (Windows CE 6.0 R2) by Bradley

Bradley
Thu Jun 12 17:04:31 PDT 2008

On Jun 12, 2:18 pm, Bradley Remedios <bremed...@gmail.com> wrote:
> OS: Windows CE 6.0 R2
> Updates: R2 Rollup, Jan-April 2008 Monthly Updates
> Platform: ARM
> Debug Build Options (Listed are Enabled):IMGEBOOT=1 IMGPROFILER=1
> IMGRAM64=1
> Total ROM Size: 56,156,288 bytes
> Total .bin Size: 55,205,131 bytes

I also forgot, my actual install order was:
1. Visual Studio 2005
2. Visual Studio 2005 SP1
3. Windows Embedded CE 6.0 Platform Builder 6.0
4. Windows Embedded CE 6.0 SP1
5. Windows Embedded CE 6.0 R2
6. WinCEPB60-R2-Update-Rollup-Armv4I.msi
7. WinCEPB60-R2-Update-Rollup-X86.msi
10. WinCEPB60-080131-2008M01-Armv4I.msi
11. WinCEPB60-080131-2008M01-X86.msi
12. WinCEPB60-080229-2008M02-Armv4I.msi
13. WinCEPB60-080229-2008M02-X86.msi
14. WinCEPB60-080331-2008M03-Armv4I.msi
15. WinCEPB60-080331-2008M03-X86.msi
16. WinCEPB60-080430-2008M04-Armv4I.msi
17. WinCEPB60-080430-2008M04-X86.msi

If you notice, I think that I overlooked the Cumulative Update install
that provides the QFE's for November and December, so I'll be going
back to install that after item 7 (will become 8 and 9 for ARM and
X86.)

Thank you,
Brad.

Re: Debug Crash when using Profiler (Windows CE 6.0 R2) by Bradley

Bradley
Fri Jun 13 15:44:00 PDT 2008

On Jun 12, 5:04 pm, Bradley Remedios <bremed...@gmail.com> wrote:
> On Jun 12, 2:18 pm, Bradley Remedios <bremed...@gmail.com> wrote:
>
> > OS: Windows CE 6.0 R2
> > Updates: R2 Rollup, Jan-April 2008 Monthly Updates
> > Platform: ARM
> > Debug Build Options (Listed are Enabled):IMGEBOOT=1 IMGPROFILER=1
> > IMGRAM64=1
> > Total ROM Size: 56,156,288 bytes
> > Total .bin Size: 55,205,131 bytes
>
> I also forgot, my actual install order was:
> 1. Visual Studio 2005
> 2. Visual Studio 2005 SP1
> 3. Windows Embedded CE 6.0 Platform Builder 6.0
> 4. Windows Embedded CE 6.0 SP1
> 5. Windows Embedded CE 6.0 R2
> 6. WinCEPB60-R2-Update-Rollup-Armv4I.msi
> 7. WinCEPB60-R2-Update-Rollup-X86.msi
> 10. WinCEPB60-080131-2008M01-Armv4I.msi
> 11. WinCEPB60-080131-2008M01-X86.msi
> 12. WinCEPB60-080229-2008M02-Armv4I.msi
> 13. WinCEPB60-080229-2008M02-X86.msi
> 14. WinCEPB60-080331-2008M03-Armv4I.msi
> 15. WinCEPB60-080331-2008M03-X86.msi
> 16. WinCEPB60-080430-2008M04-Armv4I.msi
> 17. WinCEPB60-080430-2008M04-X86.msi
>
> If you notice, I think that I overlooked the Cumulative Update install
> that provides the QFE's for November and December, so I'll be going
> back to install that after item 7 (will become 8 and 9 for ARM and
> X86.)

Having the Cumulative Update installed has made no difference to the
results of the debug build and profiler. CEUpdateCheck.exe also says
that I am only Missing May 2008 which I have not installed yet.

Regards,
Brad.