Re: 5.0 - adding driver/file prevents boot by Bruce
Bruce
Sat Apr 12 06:26:21 PDT 2008
That is getting way further than you had indicated. You need to debug your
nLED driver. If you are using the registry settings from common, starts
very early in the boot process.
--
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
"Joel Winarske" <joel.winarske@gmail.com> wrote in message
news:3c666664-36e0-4c5c-aed0-5ba98a4d627e@b9g2000prh.googlegroups.com...
Without this file included in NK.bin I eventually see:
0x8facf370: This device has booted 1 times !!!
With this file included the debug output is:
Windows CE Kernel for Hitachi SH Built on Feb 8 2007 at 23:35:46
SH-4 Kernel
CCR=0105
+OEMInit
OEMTimerFreq = 003f93e1, SHxCount1MS = 00001046, nMaxSchedMSec =
0007dd95, SHxMa
xTicks = 7fffe6be
+SHxInitTimer
-SHxInitTimer
+OALInterruptInit
+OALIntrMapInit
-OALIntrMapInit
Set Interrupt Level Control Register.
INTC_ICR0 =0x80000000
INTC_ICR1 =0x00000000
INTC_INTPRI=0x00000000
INTC_ICR0 =0x80000000
INTC_ICR1 =0x00000000
INTPRI =0x70000000
INT2PRI0 =0x02020202
INT2PRI1 =0x02020202
INT2PRI2 =0x16160000
INT2PRI3 =0x001c0600
INT2PRI4 =0x161c0000
INT2PRI6 =0x16000016
INT2PRI7 =0x16160000
INT2PRI8 =0x16161600
INT2PRI9 =0x08001414
INT2PRI10=0x00000000
INT2PRI11=0x00000000
INT2PRI12=0x00001008
Interrupt Level Control Register setup done.
Set Interrupt Mask Register.
INTMSK0 =0xff000000
INTMSK1 =0xff000000
INTMSK2 =0x00000000
INTMSK0 =0xff000000
INTMSK1 =0xff000000
INTMSK2 =0xfffefffe
INTC2A0 =0x00000008
INTC2A1 =0x00000000
INT2MSKR =0xfdfffffe
INT2MSKR1 =0xffffffff
mask all interrupts done.
Calling HookInterrupt.
HookInterrupt Done.
-OALInterruptInit
-OEMInit
Using Paging Pool, size = 0x0fdfc000, Addr = 0x8c4f4000, gpPoolArr =
0x9c2f0000
Error Reporting Memory Reserved, dump size = 00020000
Booting Windows CE version 5.00 for (SH-4)
&pTOC = 8c1083fc, pTOC = 8c46f38c, pTOC->ulRamFree = 8c4f4000,
MemForPT = 0fefa0
00
Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 997105, Secondary pages: 0, Filesystem
pages = 65536
Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 00000000, extension: 00000000,
On Apr 11, 3:39 pm, "Bruce Eitman [eMVP]"
<beitman.nos...@applieddata.net.nospam> wrote:
> I don't think that it is image size, it looks like the image size is okay
> and AUTOSIZE is on. Image size was my first thought when I read your post.
>
> Some debug output might be of value. If the boot process in fact stops as
> early as the you say then it shouldn't have even loaded any drivers yet.
> On
> the other hand, if it gets far enough to load your driver then the driver
> may have problems. While you are at it, add some debug messages to your
> driver so you can tell if it is loading.
>
> --
> 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
>
> "Joel Winarske" <joel.winar...@gmail.com> wrote in message
>
> news:66ef81f2-8572-4322-ada1-a4b5f6f450e2@q27g2000prf.googlegroups.com...
>
>
>
> > When I add certain files to the OS image the image will no longer
> > boot. For example when I add my Notification LED driver the kernel
> > stops booting at the point of listing memory section. I remove the
> > NLED driver and rebuild and deploy, and it boots fine. It boots fine
> > with serial and ethernet drivers. If I only select the NLED driver,
> > and not the serial or Ethernet the kernel will stop at the same
> > place. Why wouldn't it stop with the Ethernet or Serial drivers? A
> > file is a file is a file right?
>
> > I need to be clear, it halts at kernel initialization with this
> > additional file. Without it the kernel boot fine without error. It
> > seems the NK.bin image is confused somehow.
>
> > Any ideas?
>
> > Joel
>
> > ; 8C00.0000 -+
> > ; | ARGS (4KB)
> > ; 8C00.1000 -+
> > ; |
> > ; | OS (NK) Code
> > ; |
> > ;------------+ **auto-size**
> > ; |
> > ; | OS (NK) RAM
> > ; |
> > ; |
> > ; |
> > ; |
> > ; |
> > ; 9000.0000 -+ 64MB - Top of Bootloader/Kern Init Stack
>
> > MEMORY
>
> > ; Name Start Size Type
> > ; ------- -------- -------- ----
> > RSVD 8C000000 000FF000 RESERVED
> > ARGS 8C0FF000 00001000 RESERVED
> > NK 8C100000 00A00000 RAMIMAGE
> > RAM 8CB00000 03500000 RAM
>
> > CONFIG
>
> > AUTOSIZE=ON
>
> > ViewBin... nk.bin
> > Image Start = 0x8C100000, length = 0x0035D260
> > Start address = 0x8C100004
> > Checking record #22 for potential TOC (ROMOFFSET = 0x00000000)
> > Found pTOC = 0x8c3165b4
> > ROMOFFSET = 0x00000000
> > Done.
>
> > From platform.bib:
>
> > ;
> > -----------------------------------------------------------------------------
> > IF BSP_SH7763_SERIAL
> > scif.dll $(_FLATRELEASEDIR)\scif.dll NK SH
> > ENDIF BSP_SH7763_SERIAL
> > ;
> > -----------------------------------------------------------------------------
>
> > ;
> > -----------------------------------------------------------------------------
> > IF BSP_SH7763_GETHER
> > celan.dll $(_FLATRELEASEDIR)\celan.dll NK SH
> > ENDIF BSP_NIC_GETHER
> > ;
> > -----------------------------------------------------------------------------
>
> > ;
> > -----------------------------------------------------------------------------
> > ; Notification LED Driver
> > IF BSP_SH7763_NLED
> > nleddrvr.dll $(_FLATRELEASEDIR)\nleddrvr.dll NK SH
> > ENDIF BSP_SH7763_NLED
> > ;
> > ------------------------------------------------------------------------------
> > Hide quoted text -
>
> - Show quoted text -