Re: 5.0 - adding driver/file prevents boot
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Fri, 11 Apr 2008 15:19:34 -0400
OS image get too large? Take a close look at the output from makeimg. If
you see something about skipping records, you have a problem with image
size.
--
Dean Ramsier - eMVP
BSQUARE Corporation
"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
;
-----------------------------------------------------------------------------
.
- References:
- 5.0 - adding driver/file prevents boot
- From: Joel Winarske
- 5.0 - adding driver/file prevents boot
- Prev by Date: Re: WaitForAPIReady CE 6.0
- Next by Date: Re: CE6.0 KITL Problem....
- 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
|
