Re: Fail to load symbols for ..._SERIAL.DL by olol
olol
Wed Oct 27 09:10:46 CDT 2004
Thank you, Randal and Bruce.
"Randal Leeson" <randylrandyl@yahoo.com> wrote in message
news:ad2vn09167ulbm3mulqrqclm3ka1lhl49h@4ax.com...
> The attach debug message will not be seen if the init zone is not
> enabled (check the mmd.c file dpCurSettings initialization). You can
> change the default zones in the MDD, or by using the
> HKEY_CURRENT_USER\Pegasus\Zones registry entries on your desktop
> machine.
I have set a entry in HKEY_CURRENT_USER\Pegasus\Zones
with Value name"XSC1BD_SERIAL" and value data 0xffdf.
I googled from the newsgroup, but I don't know the exact meaning of this
value.
> If you are using serial debugging the most common cause of a lock up
> when the serial driver loads is that the driver is reprogramming the
> serial port that is being used for download. If this is the problem
> you could either change the serial driver to not load for the UART
> channel used as the debug serial port for DEBUG builds or you could
> remove the registry entries that load the serial driver for the UART
> used as the debug serial port for DEBUG builds.
I will check this, thank you.
But remove which registry? I am a newbie with a few concept on it :(
But strangely, it occasionally startup successfully. but just occasionally.
I don't know what happened to it. I think I have changed nothing, just
retried.
>
> I'm not sure what your question about the two MDDs is. There is the
> original COM_MDD and the newer model COM_MDD2. A serial driver would
> be based on only one.
>
I have found it. in the SOURCE file, there is a conditional statement to
include the
right one. when verion of PB >= 4.0 , MDD2 will be used.
Thanks again!
> Randal Leeson
>
> On Thu, 21 Oct 2004 13:54:13 +0800, "olol" <coocoo@citiz.net> wrote:
>
>>
>>
>>My OS image startup process is stalled on loading symbols for _SERIAL.DL
>>the latest messages from debug output window are:
>>========================================================================================================
>>4294773656 PID:23c4948e TID:23c76eb6 0x83c49000:
>>DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial) entered
>>4294773670 PID:23c4948e TID:23c76eb6 0x83c49000: >>> Loading module
>>xsc1bd_serial.dll at address 0x02EC0000-0x02EE4000 (RW data at
>>0x01F46000-0x01F46608)
>>Loaded symbols for 'D:\MYWORK\LINDA\RELDIR\SITSANGDEBUG\XSC1BD_SERIAL.DLL'
>>=========================================================================================================
>>
>>The serial driver was cloned from lubbock.
>>
>>the PDD source should be
>>D:\WINCE420\PLATFORM\Sitsang\drivers\SERIAL\XSC1_SER16550\
>>and ...\SERIAL\XSC1_SerialPdd\
>>
>>MDD source should be
>>D:\WINCE420\PUBLIC\COMMON\OAK\DRIVERS\SERIAL\COM_MDD
>>and ..\SERIAL\COM_MDD2
>>
>>
>>Am I right? I am not sure why there are two MDD's ?
>>
>>
>>In the DllEntry of MDD file ((SerialDllEntry() of MDD; DllEntry() of
>>MDD2))
>>
>>there is a statement:
>>---------------------------------------------
>>{
>> if ( dwReason == DLL_PROCESS_ATTACH ) {
>> DEBUGREGISTER(hinstDll);
>> DEBUGMSG (ZONE_INIT, (TEXT("serial port process attach\r\n")));
>>---------------------------------------------
>>
>>But why I can not see the debug messagae "serial port process attach";
>>
>>What should winCE do before call into DllEntry?
>>
>>
>>
>>Thanks a lot!!
>>
>>
>