Re: One more strange thing happens....
- From: "K. S. Huang" <ksh_AT_bsquare_DOT_com>
- Date: Mon, 26 Mar 2007 13:28:48 +0800
Which section do you put the DLL record in common.bib?
For records belong to MODULES section, romimage will check the processor
type while in FILES section it just by-pass.
I just wonder if your ddi_vgx.dll is always for x86 system, but when you
adding in common.bib, it was put in the bottom of the file so that it is
just resides in FILES section, so that MAKEIMG will work but booting failed.
You may use the DUMPBIN /headers ddi_vgx.dll in release folder to confirm
the CPU type of your DLL first.
"Eike" <Eike@xxxxxxxxxxxxxxxxxxxxxxxxx> ¼¶¼g©ó¶l¥ó·s»D:8B62867E-E4DE-437B-8263-F03CEF8A560E@xxxxxxxxxxxxxxxx
By the way, another strange thing happens, which I can not figure out.
If I write
IF BSP_DISPLAY_SMIVGX
ddi_vgx.dll $(_FLATRELEASEDIR)\ddi_vgx.dll NK SH
ENDIF BSP_DISPLAY_SMIVGX
into the "common.bib" everything works fine. But if I add these lines
(exact
in the same way) in the "platform.bib" instead of the common.bib, then the
following error occurs when trying to build the image:
Error: Module ddi_vgx.dll built for I386, kernel built for Thumb
Fatal error hit, exiting...
makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec).
makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec).
That's kind of strange, because the DLL is correct, without any doubt.
Well, I just let the lines in the common.bib and I don't think that has to
do with my main problem, but who knows....
.
- References:
- Prev by Date: Re: Must I call function NKForceCleanBoot() in OEMInit()?
- Next by Date: Re: serial port problem : no Rx Interrupt
- Previous by thread: Re: IXDP425 Can not load any display driver, especially the SM 5
- Next by thread: Re: Some problems about address mapping in windows ce5.0
- Index(es):
Relevant Pages
|
