RE: Fast IR NDIS Miniport Driver for Windows CE

Hi David,
Thanks for the reply.
I have got past this issue. I think it was some quick hacks in the send and
receive functions and may be with the total supported Irda speeds which i was
supporting to the OID_IRDA query.

What ever, i got it resolved and I am able to transfer the files in 4Mbps as
well.
But i still have some issues with the CETK test cases. All the connection
oriented CETK test cases just skip complaining that, SKIPPED: Unable to
establish connection to IRTestServer.

Here is the complete query, can you please advice?
-------------------------------
I have developed a Fast IR driver for ARM platform. I am able to transfer
The files between my desktop and development board. Though I am not able to
transfer bigger files (since I am not using DMA yet), I am successfully able
to transfer files of small size.

While trying to run the CETK test cases, I found that, all the connection
oriented test cases are skipping, and I am just getting the result as
SKIPPED: Unable to establish connection to IRTestServer.

Following is the procedure I follow.
I am running one board as server and I run the following commands
s services stop obx0:
s irapisrv22
It shows
Creating AF_IRDA endpoint
IRSRV waiting for connect...
Another board I am using as client and I am running the following commands
s services stop obx0:
s tux -o -d irapi22 -f cesh:irapitest.log

Following components are added SYSGEN_IRDA, SYSGEN_WINSOCK,
SYSGEN_OBEX_INBOX(file transfer)
I have got the same code, passing all the test cases. The only difference
is, more components are added to the platform, and power management is also
introduced.
Wrt to the code I didn't do any modifications.

Is there anything I missed out?
Any help will be greatly appreciated
-------------------------------



""David Kanz [MSFT]"" wrote:

All disconnected Irda communications occur at 9600 baud. This includes
discovery and connection establishment. If this convention were not
adherred to (i.e. start at 9600 baud), then no discovery could occur. Part
of connection establishment includes baud rate negotiation. The initiating
side advertises the baud rates he supports and the peer responds with the
baud rate to connect with.
One sticky point to remember when writing an Irda miniport is that you must
delay the command to change the hardware baud rate until after the last
9600 baud rate frame has been completely sent.

SNRM <9600, 115200, 4000000>
UA <4000000>

The UA packet must go out at 9600 baud.

David Kanz [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
| Thread-Topic: Fast IR NDIS Miniport Driver for Windows CE
| thread-index: AcYSyptmAwTKlrg8TwCOJHsEC3svNw==
| X-WBNR-Posting-Host: 203.91.193.6
| From: "=?Utf-8?B?c3VqaQ==?=" <suji@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Fast IR NDIS Miniport Driver for Windows CE
| Date: Fri, 6 Jan 2006 06:08:02 -0800
| Lines: 27
| Message-ID: <1F49371D-BCB9-4A25-8A74-EFB56D082BF4@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windowsce.embedded
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.windowsce.embedded:29610
| X-Tomcat-NG: microsoft.public.windowsce.embedded
|
| Hi,
|
| We are developing a Fast IR(FIR) Driver for Windows CE with support to
FIR
| and Slow IR(SIR).
|
| The switching between FIR or SIR is purely depending on the
| OID_IRDA_LINK_SPEED Object ID. Once we receive the Set information
request
| from NDIS, with OID as OID_IRDA_LINK_SPEED and a valid speed in the
| InformationBuffer. We check
| whether the InformationBuffer contain a valid supported speed, if
valid,
| we determine whether we really are in FIR or SIR.
|
| In the query function, with OID as OID_IRDA_SUPPORTED_SPEEDS, we are
| supporting the speed NDIS_IRDA_SPEED_4M which is FIR speed.
|
| We are working on NDIS 5.0.
|
| We are always getting the OID_IRDA_LINK_SPEED as 0x2580 which is 9600, so
| driver always set the speed as SIR speed and not FIR.
|
| Can anybody please suggest, how can we get a OID_IRDA_LINK_SPEED with
| NDIS_IRDA_SPEED_4M? what additional settings needed from OS components /
| Platform Settings? Or is it is something to do with the driver itself?
|
| Any help will be greatly appreciated.
| Regards,
| Sujith
|


.

Relevant Pages