Re: 5.0 - adding driver/file prevents boot
- From: "Bruce Eitman [eMVP]" <beitman.nospam@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 11 Apr 2008 18:39:17 -0400
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.winarske@xxxxxxxxx> wrote in message
news:66ef81f2-8572-4322-ada1-a4b5f6f450e2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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
;
-----------------------------------------------------------------------------
.
- Follow-Ups:
- Re: 5.0 - adding driver/file prevents boot
- From: Joel Winarske
- Re: 5.0 - adding driver/file prevents boot
- References:
- 5.0 - adding driver/file prevents boot
- From: Joel Winarske
- 5.0 - adding driver/file prevents boot
- Prev by Date: Re: CreateSurface fails in Ddraw CETK test case 102(WINCE 6.0)
- Next by Date: Re: 5.0 - adding driver/file prevents boot
- Previous by thread: Re: 5.0 - adding driver/file prevents boot
- Next by thread: Re: 5.0 - adding driver/file prevents boot
- Index(es):
Relevant Pages
|
