Re: OEMWriteDebugString problem
- From: "Bruce Eitman \(eMVP\)" <beitmannospam@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 3 Aug 2005 08:23:52 -0400
I mean rebuild the code of interest. Not knowing specifically what your
code looks like it would be difficult for me to mean anything else, but your
problem is in the kernel, so that is what I said.
Since usually the selection of debug port is based on a variable, it is
entirely possible that the bootloader and kernel are using different ports,
even if they are using the exact same file when building. It is up to you
to verify this, please don't assume something like that they are when you
are clearly having a problem which could indicate that your assumption is
not correct. Looking at the .COD files mentioned earlier would be good.
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"ms" <ms@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23cD5hE7lFHA.576@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks Bruce, when you say rebuild the kernel do you mean - rebuild the
> private source to create nk.lib
> or do you mean rebuild the OAL oal.lib.
>
> As i understood OEMInitDebugSerial sets up the serial port and there is
> only
> one implementation of this
> which the bootloader and kernel can call, aswell as only one
> implementation
> of OEMWriteDebugstring
> so i can't see how they could be using different ports.
>
> Regards
>
> "Bruce Eitman (eMVP)" <beitmannospam@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> in
> message news:uHcKOc3lFHA.572@xxxxxxxxxxxxxxxxxxxxxxx
>> Opps, that should read
>>
>> First, set WINCECOD
>>
>> --
>> Bruce Eitman (eMVP)
>> Senior Engineer
>> beitman AT applieddata DOT net
>>
>> Applied Data Systems
>> www.applieddata.net
>> An ISO 9001:2000 Registered Company
>> Microsoft WEP Gold-level Member
>>
>>
>> "Bruce Eitman (eMVP)" <beitmannospam@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote
> in
>> message news:ek6oNb3lFHA.1464@xxxxxxxxxxxxxxxxxxxxxxx
>> > First, set WINCEREL and rebuild the kernel. In the obj folder will be
>> > .COD files which contain the C code as well as the assembly code that
>> > it
>> > creates. Looking at these files will tell you a lot about what is
>> > happening.
>> >
>> > Next, is it possible that the bootloader and the kernel are using
>> > different ports?
>> >
>> > --
>> > Bruce Eitman (eMVP)
>> > Senior Engineer
>> > beitman AT applieddata DOT net
>> >
>> > Applied Data Systems
>> > www.applieddata.net
>> > An ISO 9001:2000 Registered Company
>> > Microsoft WEP Gold-level Member
>> >
>> >
>> >
>>
>>
>
>
.
- Follow-Ups:
- Re: OEMWriteDebugString problem
- From: ms
- Re: OEMWriteDebugString problem
- References:
- OEMWriteDebugString problem
- From: ms
- Re: OEMWriteDebugString problem
- From: ms
- Re: OEMWriteDebugString problem
- From: Bruce Eitman \(eMVP\)
- Re: OEMWriteDebugString problem
- From: Bruce Eitman \(eMVP\)
- Re: OEMWriteDebugString problem
- From: ms
- OEMWriteDebugString problem
- Prev by Date: PSM support for Windows CE 4.2 on an IXP425-based SBC
- Next by Date: Re: How can I disable Off button ???
- Previous by thread: Re: OEMWriteDebugString problem
- Next by thread: Re: OEMWriteDebugString problem
- Index(es):