Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
End Users
Pocket PCActiveSyncMultimediaEBooksWirelessSmartPhones
Developers
Windows MobileSmartPhonesWinCE ProgrammingVB for WinCEVC++ for WinCEPlatform BuilderTest Tools
PocketPC DirectoryFree SoftwareWeb Resources
Related Topics
PalmMobile PhonesMore Topics ...

Pocket PC Forum / Developers / Platform Builder / July 2008

Tip: Looking for answers? Try searching our database.

Develop a driver for Windows Mobile 6

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
GuiKami - 20 Jul 2008 17:58 GMT
Hi everyone

I'm creating a simple SDIO and I have to create a driver for it to use
in my PDA Dell Axim x50v with Windows Mobile 6.
I would aprecciate if someane describle the steps I have to follow to
create and install a driver on the Windows Mobile 6 using Visual
Studio 2005 and Windows Embedded CE 6.0.

Thanks in advance

Regards,
Guilherme Kami
make shi - 21 Jul 2008 16:24 GMT
The same way with Windows Mobile 6.

"GuiKami" <guikamifc@gmail.com>
??????:33292eb5-dfaf-4d16-9a21-83db42c056d7@2g2000hsn.googlegroups.com...
> Hi everyone
>
[quoted text clipped - 8 lines]
> Regards,
> Guilherme Kami
Bradley Remedios - 21 Jul 2008 16:38 GMT
> I'm creating a simple SDIO and I have to create a driver for it to use
> in my PDA Dell Axim x50v with Windows Mobile 6.
> I would aprecciate if someane describle the steps I have to follow to
> create and install a driver on the Windows Mobile 6 using Visual
> Studio 2005 and Windows Embedded CE 6.0.

I am not familiar with SDIO but if I would start by reading
http://msdn.microsoft.com/en-us/library/aa918430.aspx if I had to
write one.  Bruce Eitman also has a good article on writing Stream
Drivers here: http://geekswithblogs.net/BruceEitman/archive/2008/06/09/windows-ce-a-stream-int
erface-shell.aspx
.

Just so you know, Windows Mobile 6 is actually based on Windows
Embedded CE 5.0 not Windows Embedded CE 6.0.

Good Luck,
Brad.
Bradley Remedios - 21 Jul 2008 17:32 GMT
> > I'm creating a simple SDIO and I have to create a driver for it to use
> > in my PDA Dell Axim x50v with Windows Mobile 6.
[quoted text clipped - 8 lines]
> Just so you know, Windows Mobile 6 is actually based on Windows
> Embedded CE 5.0 not Windows Embedded CE 6.0.

The first link I posted is for CE 6.0.  Here is one for CE 5.0 sorry
for any confusion http://msdn.microsoft.com/en-us/library/ms923739.aspx
GuiKami - 22 Jul 2008 02:51 GMT
> > > I'm creating a simple SDIO and I have to create a driver for it to use
> > > in my PDA Dell Axim x50v with Windows Mobile 6.
[quoted text clipped - 11 lines]
> The first link I posted is for CE 6.0.  Here is one for CE 5.0 sorry
> for any confusionhttp://msdn.microsoft.com/en-us/library/ms923739.aspx

Hi Bradley

Thanks for your attention

I read those articles you indicatted and I saw the concepts of the sd
driver and the structure you have to build to develop a driver.
But one thing i
GuiKami - 22 Jul 2008 03:13 GMT
Hi Bradley

Thanks for your attention

Now I'll use The Windows Embedded CE 5.

I read those articles you recommended and I understood the concepts of
the SD card drivers and the structure you have to build to develop a
driver. I realized that I can develop my driver based on the existing
SD source with some modifications.

The article you recommended teaches how to configure the driver to
work on the OS you're developing, but I want it to work on the Windows
Mobile 6. I noticed that when I built the driver, one .obj file was
generated in the same folder. Now, I would like to know which driver
files do I have to copy to my PDA Dell Axim x50v and what settings
should I configure for it to work.
Could you help me again?

Regards,
Guilherme Kami
Bruce Eitman [eMVP] - 22 Jul 2008 03:41 GMT
The Microsoft page that Bradley directed you to included a link to the
registry settings for SD cards.  You will need to add similar, but
different, registry entries for your driver.  Review that page.  Keep in
mind that you may need to reset the device after adding the registry
settings.

What do you mean by "Now, I would like to know which driver files do I have
to copy to my PDA?"  If you don't know what you built, how would we?

Signature

Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

> Hi Bradley
>
[quoted text clipped - 17 lines]
> Regards,
> Guilherme Kami
GuiKami - 23 Jul 2008 01:15 GMT
Oh, I'm sorry.

I'm really naive in this subject and I wasn't explicit in my
question.
What I meant is that I don't know what you have to do after you
acomplish writing your driver source.
Do I have to do build it on Platform Builder and copy the files to the
somewhere in the WM and modify a .reg file?

Thanks for your help

Regards,
Guilherme Kami
Bruce Eitman [eMVP] - 23 Jul 2008 02:18 GMT
Is it safe to say that you do not work for Dell or one of their vendors?
But instead are developing a driver to distribute to others to use a device
you are buiding that inserts into the Axim?

Let's assume that I am right.  You need a way to get your driver and
registry setting into the device and insert your registry settings in the
registry.  Unfortunatly, this is outside of my expertise but I can point you
in the right direction.  CAB files are the typically way to do this, and
usually they are wrapped with an MSI that installs the CAB file on a PC so
that ActiveSync can send the CAB and run the cab file installer on the
device.

Signature

Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT EuroTech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

EuroTech Inc.
www.EuroTech.com

> Oh, I'm sorry.
>
[quoted text clipped - 9 lines]
> Regards,
> Guilherme Kami
GuiKami - 31 Jul 2008 21:20 GMT
Hi everybody again.

Thanks for all your help.

Now, I have another doubt.
As I read, the bus driver is responsible to do the first communication
with the SD and determine the appropriate client driver to load. To do
this, the bus driver has to access the CIS area and get the
CISTPL_MANFID.
Another thing I've read is that you have to use CMD52 for reading a
register. So I thought that it would be the first command the host
would use.
But in my tests, I only received the following commands from the host:
CMD5, CMD0, CMD1, CMD55.

Is that correct? Do I have to receive all this commands before the
command to get the Plug and Play information? Or does the host uses
another command to get that?

Thanks again.

Regards,
Guilherme Kami
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.