Re: eboot and FFUART
- From: "Blake" <blake29.chang@xxxxxxxxx>
- Date: Thu, 29 Mar 2007 00:09:39 +0800
Hi osreeye,
You can check if there is any registry settings about FFUART in reginit.ini.
If yes, I think you have loaded a serial port driver for FFUART.
You cannot make a serial port being a COM port and a debug port at the same
time.
--
I hope it is useful ^_^
Best Regards,
Blake Chang
"soreeye" <soreeye@xxxxxxxxxxx> wrote in message
news:%23ML%23JzPcHHA.4656@xxxxxxxxxxxxxxxxxxxxxxx
How do we check that it is not loaded, at the eboot or wince portion?
If we don't load the driver, can we still use the FFUART for other
purpose?
K. S. Huang wrote:
Make sure your serial driver is *not* loaded for FFUART port or it will
conflict with the debug port.
"soreeye" <soreeye@xxxxxxxxxxx>
???????:ea%23pVrOcHHA.1220@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have the OS booted up successfully with the BTUART as the debug UART,
under mainstone III.
However, when I configure the FFUART as the debug UART under eboot menu,
the OS hangs at
"NDIS: PcmciaNeedsMapToScrap = 0"
or
"Loaded symbols for "......\VMINI.DLL"
Anyone can advise on where to look for the problem.
Thanks
.
- References:
- eboot and FFUART
- From: soreeye
- Re: eboot and FFUART
- From: K. S. Huang
- Re: eboot and FFUART
- From: soreeye
- eboot and FFUART
- Prev by Date: Re: SetTimeZoneInformation and file time stamps
- Next by Date: Re: Can't add driver to target image
- Previous by thread: Re: eboot and FFUART
- Next by thread: Re: Installable Interrupt on PCI
- Index(es):
Relevant Pages
|