Re: How to Disable Ethernet

Yes, you can use the serial port as an alternative method of getting debug.
Download over serial is *very* slow, though. As I said, if you need to
download over Ethernet, you must have two adapters.

If you want to send messages over serial and don't need to debug, which
might be true, depending on what you're starting from driver-wise, yes, you
can disable KITL debugging and just read all of the messages that come out.
How, exactly, you choose that vs. Ethernet depends on your BSP.

To disable KITL debugging, open the Platform | Settings... menu item. Make
sure that the root item in the tree view at the left edge of the dialog is
selected, not some subsidiary item. Choose the Build Options tab. Uncheck
Enable KITL and Enable Kernel Debugger.

Paul T.

"jeffs" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0fb601c55285$dca3af90$a401280a@xxxxxxxxxx
> Can't I debug the driver using messages over the serial
> port (or run KITL over the serial port - albiet it would be
> painfully slow)? If this is the case, how do I make sure
> KITL is disabled. I dont think I want to disable on the
> fly, I think I want to disable in the build. -Jeff
>
>
>>-----Original Message-----
>>Right. You can't have KITL running and use your driver at
> the same time
>>(interrupt and state sharing wouldn't allow that).
> However, that doesn't
>>mean that they were disabling on-the-fly in a running system!
>>
>>Yes, you *do* need to develop the driver for the final
> product, but, in
>>order to debug that driver, you have to have two Ethernet
> ports so that you
>>can run the debugger over one via KITL and test the other one.
>>
>>Paul T.
>>
>>"jeffs" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message
>>news:0f5c01c5527a$ddd74e90$a401280a@xxxxxxxxxx
>>> Hi Paul,
>>>
>>> Wow, I am very confused. I thought I read that people were
>>> developing drivers for the ethernet (single ethernet port
>>> systems) but they first had to disable KITL. You then
>>> reroute your debug messages to the serial port since KITL
>>> is no longer available for debugging. We are trying to
>>> develop a controller with a single port that can access the
>>> internet. My understanding from other posts is you want to
>>> avoid using VMINI and the built in ethernet driver because
>>> it is very inefficient (slow). You need to develop your
>>> own NDIS driver for the actual final product.
>>>
>>> Thanks for the help, -Jeff
>>>
>>>
>>>>-----Original Message-----
>>>>That's just not the way it's supposed to work. If you
>>> want to use Ethernet
>>>>for download, you don't load your driver for the Ethernet,
>>> you load VMini.
>>>>There's a page in the 4.2 help called Ethernet Connection
>>> Options that talks
>>>>about using a single Ethernet connection for both download
>>> and ordinary
>>>>networking. I have not done that, but your OAL needs to
>>> support it, too, as
>>>>I read the documentation. There are just two ways to do
>>> things, when you're
>>>>using Ethernet for download:
>>>>
>>>>1. Two Ethernet adapters, one for download, one for the
> CE OS.
>>>>2. VMini and sharing of the Ethernet between KITL and the
>>> CE OS (you
>>>>wouldn't have a separate driver for the adapter installed,
>>> in this case).
>>>>
>>>>Paul T.
>>>>
>>>>"jeffs" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>>> message
>>>>news:129101c55266$02a9a020$a601280a@xxxxxxxxxx
>>>>> Thanks Paul,
>>>>>
>>>>> I dont mind living with it but I dont know how to make my
>>>>> driver behave correctly with it. It receives constant
>>>>> interrupts which are not intended for it (the
> interrupt and
>>>>> mask do not overlap). How should I handle this? I have
>>>>> been struggling with this for 2 weeks. I am porting the
>>>>> 91C96 driver to winCE 4.2 and the OS just gets stuck
>>>>> calling this ISR over & over. The interrupt is
> disabled in
>>>>> OEMInterruptHandler. It is reenabled/cleared at the
> end of
>>>>> the interruptHandler per what I have read in the mesage
>>>>> archives. In addition, I verify the hardware interrupt is
>>>>> completely cleared (no pending hardware interrupt)
> prior to
>>>>> leaving the interrupt handler. I also changed the SYSINTR
>>>>> value to a unique value (it no longer uses SYSINT_SMSC).
>>>>>
>>>>> Any help would be greatly appreciated. I can not find any
>>>>> formal documentation on this anywhere.
>>>>>
>>>>> -Jeff
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>Disable it? Program the OS into flash or wherever it will
>>>>> be permanently
>>>>>>stored and remove the KILT component from the OS. If you
>>>>> have to use
>>>>>>Ethernet to download, you're going to have to live with
>>>>> sharing the port...
>>>>>>
>>>>>>Paul T.
>>>>>>
>>>>>>"jeffs" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>>>>> message
>>>>>>news:126501c55262$caea6a00$a601280a@xxxxxxxxxx
>>>>>>> Hi Paul,
>>>>>>>
>>>>>>> How can I be sure that KITL is no longer accessing it?
>>>>>>> When I run my driver, I get interrupts from the
> 91C96 that
>>>>>>> should not be occuring (i.e. the interrupt does not
> match
>>>>>>> the mask). If I add a 10 second delay to the end of my
>>>>>>> InterruptHandler, no interrupts occur during that time.
>>>>>>> However, immediately upon return from the
> InterruptHandler
>>>>>>> a new interrupt is generated. There must be some other
>>>>>>> code that is accessing the 91C96 that I have not
> properly
>>>>>>> turned off.
>>>>>>>
>>>>>>> Thanks for the help! -Jeff
>>>>>>>
>>>>>>>>-----Original Message-----
>>>>>>>>If the cable is connected, there's a reasonable chance
>>>>>>> that you'll get
>>>>>>>>network traffic. Are you sure you're not seeing
> broadcast
>>>>>>> packets from
>>>>>>>>other machines on your network getting to your
> Windows CE
>>>>>>> device?
>>>>>>>>
>>>>>>>>Is the device configured for DHCP? Maybe it's trying to
>>>>>>> get an IP address
>>>>>>>>from a DHCP server?
>>>>>>>>
>>>>>>>>Other 'things' in the system aren't going to access the
>>>>>>> chip directly, once
>>>>>>>>you've removed KITL. Everything will go through the
>>>>>>> driver. That doesn't
>>>>>>>>mean that many network services won't be sending and
>>>>>>> receiving data, though.
>>>>>>>>
>>>>>>>>Paul T.
>>>>>>>>
>>>>>>>>"jeffs" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
>>>>>>> message
>>>>>>>>news:0c7a01c55203$37f77170$a401280a@xxxxxxxxxx
>>>>>>>>>I am adding an NDIS driver to a PXA255 board. OS is
>>> winCE
>>>>>>>>> 4.2 I want to make sure that nothing else
> accesses the
>>>>>>>>> 91C96 ethernet chip other than my driver. To do
> this I
>>>>>>>>> modified "OEMKitlInit" to only return FALSE to disable
>>>>>>>>> KITL. In addition, under platform settings->build
>>> options
>>>>>>>>> I unchecked "KITL" & "CE Target Control support".
>>>>>>>>>
>>>>>>>>> With KITL supposedly turned off and no ethernet
> drivers
>>>>>>>>> added to the build I am still seeing constant access
>>>>> to the
>>>>>>>>> 91C96 chip. The TX light is constantly going & the
>>>>>>>>> interrupt is constantly going.
>>>>>>>>>
>>>>>>>>> QUESTION : what else is accessing the 91C96? Have I
>>>>>>>>> properly disabled KITL?
>>>>>>>>>
>>>>>>>>> The following environment variables are also set:
>>>>>>>>> BSP_NOSHAREETH=1
>>>>>>>>> KERNELNOSHAREETH=1
>>>>>>>>> BSP_NOSERIAL=1
>>>>>>>>>
>>>>>>>>> Thanks in advance for any help -Jeff
>>>>>>>>
>>>>>>>>
>>>>>>>>.
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>.
>>>>>>
>>>>
>>>>
>>>>.
>>>>
>>
>>
>>.
>>


.

Relevant Pages

  • Re: Serial driver changes from v5 to v7
    ... Better to have a "robust" printcap entry. ... I didn't mean that you are the only one who can debug a serial port ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Debugging through UART0
    ... There is no way to share serial port between serial driver ... and debug output stuff. ... for the same UART port (ie. UART0). ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Can i use FFUART as Debug and Application serial port?
    ... You can't have a registry entry for the same port as a normal serial port ... Capturing the debug messages that are coming out that FFUART port would ... For your test with the BT serial port, display is getting what? ...
    (microsoft.public.windowsce.platbuilder)
  • Re: WIndows CE Emulator and COM port
    ... an OS image containing KITL, thus the COM1: port is unusable. ... "Serial Port 1" mapping will map the serial port ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: Cant open Serial port
    ... serial port is opened, then start the debug output again when it closes. ... are you actually loading a serial driver ... After boot, I find my test program, double click it to run. ...
    (microsoft.public.windowsce.platbuilder)