Re: 5.0 - adding driver/file prevents boot
- From: Joel Winarske <joel.winarske@xxxxxxxxx>
- Date: Tue, 15 Apr 2008 12:09:02 -0700 (PDT)
I figured it out. The problem was in my original post. Notice
BSP_NIC_GETHER does not match BSP_SH7763_GETHER?
Adding a driver that was below this was causing corruption of the
NK.bin file. So when I set BSP_SH7763_NLED it would build the driver
and include it in NK.bin, but the image startup would show memory
region 0 started at 0, and would then halt. Device Manager never had
a chance.
;
-----------------------------------------------------------------------------
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: about norflash file system problem
- Next by Date: .NET compact frmework 2.0 in catalog
- Previous by thread: Re: 5.0 - adding driver/file prevents boot
- Next by thread: about norflash file system problem
- Index(es):
Relevant Pages
|