HP Ipaq PXA310

[Rob]

Hi,

A client has a HP Ipaq with a marvell PXA310 processor. (Mobile6)

Am I right in assuming I can build a driver for this using PXA270

proc-family, under CE5.0 ? (The client refers to CE5.2, not familiar with

that)



Kind regards,

Rob.

www.robtso.nl

 

[Valter Minute [eMVP]]

On 3/18/2010 9:13 AM, Rob wrote:

> Hi,

> A client has a HP Ipaq with a marvell PXA310 processor. (Mobile6)

> Am I right in assuming I can build a driver for this using PXA270

> proc-family, under CE5.0 ? (The client refers to CE5.2, not familiar with

> that)



Wich kind of driver do you need to implement?

If it's a driver for a device controlled by a bus (SD, USB) you'll use

OS calls to access it and so it should be quite portable (I said should

because the underlying drivers should be bug free ).

If it's some kind of integrated peripheral even if the controller is the

same on both architectures you should consider that some configuration

may change (clocks, I/O pins used etc.) and even if you can develop and

debug most of your code on the 270 you may need to do some extra work

(without the help of PB debugger!) to make your driver run on the other

platform.



--

Valter Minute (eMVP)

Training, support and development for Windows CE:

www.fortechembeddedlabs.it

My embedded programming and cooking blog:

www.geekswithblogs.net/WindowsEmbeddedCookbook

Windows Embedded support forums in Italian:

http://social.msdn.microsoft.com/Forums/it-IT/windowsembeddedit/threads

(the reply address of this message is invalid)

 

[Rob]

Hi,

I know about those considerations...

But are my basic assumptions correct ?



Is this target actually an ARM device, and is Mobile6 indeed compatible with

CE5 ?

or are there other issues ?



Kind regards,

Rob.







"Valter Minute [eMVP]" wrote:



> On 3/18/2010 9:13 AM, Rob wrote:

> > Hi,

> > A client has a HP Ipaq with a marvell PXA310 processor. (Mobile6)

> > Am I right in assuming I can build a driver for this using PXA270

> > proc-family, under CE5.0 ? (The client refers to CE5.2, not familiar with

> > that)

>

> Wich kind of driver do you need to implement?

> If it's a driver for a device controlled by a bus (SD, USB) you'll use

> OS calls to access it and so it should be quite portable (I said should

> because the underlying drivers should be bug free ).

> If it's some kind of integrated peripheral even if the controller is the

> same on both architectures you should consider that some configuration

> may change (clocks, I/O pins used etc.) and even if you can develop and

> debug most of your code on the 270 you may need to do some extra work

> (without the help of PB debugger!) to make your driver run on the other

> platform.

>

> --

> Valter Minute (eMVP)

> Training, support and development for Windows CE:

> www.fortechembeddedlabs.it

> My embedded programming and cooking blog:

> www.geekswithblogs.net/WindowsEmbeddedCookbook

> Windows Embedded support forums in Italian:

> http://social.msdn.microsoft.com/Forums/it-IT/windowsembeddedit/threads

> (the reply address of this message is invalid)

> .

>

 

[Valter Minute [eMVP]]

On 3/18/2010 11:21 AM, Rob wrote:

> Hi,

> I know about those considerations...

> But are my basic assumptions correct ?

>

> Is this target actually an ARM device, and is Mobile6 indeed compatible with

> CE5 ?

> or are there other issues ?



The assumptions are correct. Mobile 6 is based on CE 5 and all Mobile 6

devices are ARM based (that's not true for older version of the platform

like PocketPC).

The kernel and basic services are the same, the shell is completely

different but this should not be an issue for a driver that has no UI.



--

Valter Minute (eMVP)

Training, support and development for Windows CE:

www.fortechembeddedlabs.it

My embedded programming and cooking blog:

www.geekswithblogs.net/WindowsEmbeddedCookbook

Windows Embedded support forums in Italian:

http://social.msdn.microsoft.com/Forums/it-IT/windowsembeddedit/threads

(the reply address of this message is invalid)

 

[Rob]

Ok, thanks thats good to hear.

Any suggestions why the "Unidentified USB Device" would pop up ?

is that also the case when the Vendor/device ID's dont match ?

Or this GUID that is in the regsettings for the device ?

It's been a while since I looked at the internals of the USB stack....



Kind regards,

Rob.

www.robtso.nl









"Valter Minute [eMVP]" wrote:



> On 3/18/2010 11:21 AM, Rob wrote:

> > Hi,

> > I know about those considerations...

> > But are my basic assumptions correct ?

> >

> > Is this target actually an ARM device, and is Mobile6 indeed compatible with

> > CE5 ?

> > or are there other issues ?

>

> The assumptions are correct. Mobile 6 is based on CE 5 and all Mobile 6

> devices are ARM based (that's not true for older version of the platform

> like PocketPC).

> The kernel and basic services are the same, the shell is completely

> different but this should not be an issue for a driver that has no UI.

>

> --

> Valter Minute (eMVP)

> Training, support and development for Windows CE:

> www.fortechembeddedlabs.it

> My embedded programming and cooking blog:

> www.geekswithblogs.net/WindowsEmbeddedCookbook

> Windows Embedded support forums in Italian:

> http://social.msdn.microsoft.com/Forums/it-IT/windowsembeddedit/threads

> (the reply address of this message is invalid)

> .

>

 

[Bruce Eitman [eMVP]]

Rob:



Where does the Unidentified USB Device" pop up? When does it pop up?



--

Bruce Eitman (eMVP)

Senior Engineer

Bruce.Eitman AT Eurotech DOT com

My BLOG http://geekswithblogs.net/bruceeitman



Eurotech Inc.

www.Eurotech.com



"Rob" wrote in message

news:41CB60DC-41F7-4F8B-A0F4-013213CAB300@microsoft.com...

> Ok, thanks thats good to hear.

> Any suggestions why the "Unidentified USB Device" would pop up ?

> is that also the case when the Vendor/device ID's dont match ?

> Or this GUID that is in the regsettings for the device ?

> It's been a while since I looked at the internals of the USB stack....

>

> Kind regards,

> Rob.

> www.robtso.nl

>

>

>

>

> "Valter Minute [eMVP]" wrote:

>

>> On 3/18/2010 11:21 AM, Rob wrote:

>> > Hi,

>> > I know about those considerations...

>> > But are my basic assumptions correct ?

>> >

>> > Is this target actually an ARM device, and is Mobile6 indeed compatible

>> > with

>> > CE5 ?

>> > or are there other issues ?

>>

>> The assumptions are correct. Mobile 6 is based on CE 5 and all Mobile 6

>> devices are ARM based (that's not true for older version of the platform

>> like PocketPC).

>> The kernel and basic services are the same, the shell is completely

>> different but this should not be an issue for a driver that has no UI.

>>

>> --

>> Valter Minute (eMVP)

>> Training, support and development for Windows CE:

>> www.fortechembeddedlabs.it

>> My embedded programming and cooking blog:

>> www.geekswithblogs.net/WindowsEmbeddedCookbook

>> Windows Embedded support forums in Italian:

>> http://social.msdn.microsoft.com/Forums/it-IT/windowsembeddedit/threads

>> (the reply address of this message is invalid)

>> .

>>

 

[Valter Minute [eMVP]]

On 3/18/2010 5:09 PM, Rob wrote:

> Ok, thanks thats good to hear.

> Any suggestions why the "Unidentified USB Device" would pop up ?

> is that also the case when the Vendor/device ID's dont match ?

> Or this GUID that is in the regsettings for the device ?

> It's been a while since I looked at the internals of the USB stack....



Usually this happens when the USB host and stack recognized the device

(it returned its IDs and replied to the initial USB "handshake") but the

system was not able to find an entry under \HKLM\Drivers\USB\LoadClients

that matches the device IDs or its class (it first check IDs and

release, then class to allow you to load a device-specific driver also

for devices that implement a class that is supported by CE).

This may happen also when the USBDeviceAttach function of the driver has

not "accepted" to handle it (not setting the accept flag to TRUE). Why

this may happen is quite device specific.

If you provide the DLL name for your driver the driver is loaded

correctly? In this case I would suspect a registry configuration

problem. If you checked that the keys are correctly configured, it may

be USBDeviceAttach failing to correctly recognize/initialize the device.

This happens on your PXA board or on the WM device?



--

Valter Minute (eMVP)

Training, support and development for Windows CE:

www.fortechembeddedlabs.it

My embedded programming and cooking blog:

www.geekswithblogs.net/WindowsEmbeddedCookbook

Windows Embedded support forums in Italian:

http://social.msdn.microsoft.com/Forums/it-IT/windowsembeddedit/threads

(the reply address of this message is invalid)

 

[Rob]

Hi,

Thanks for the tips.

It happens on the WM device, when the client-device is connected.

I am not sure what client they are connecting exactly.

Is it possible for them to check what GUID the device reports ?

(my client is on the other side of the world, i have never seen their client

or host)

I am trying to figure out some options for very-very-remote-debugging -)



Kind regards,

Rob.

www.robtso.nl









"Valter Minute [eMVP]" wrote:



> On 3/18/2010 5:09 PM, Rob wrote:

> > Ok, thanks thats good to hear.

> > Any suggestions why the "Unidentified USB Device" would pop up ?

> > is that also the case when the Vendor/device ID's dont match ?

> > Or this GUID that is in the regsettings for the device ?

> > It's been a while since I looked at the internals of the USB stack....

>

> Usually this happens when the USB host and stack recognized the device

> (it returned its IDs and replied to the initial USB "handshake") but the

> system was not able to find an entry under \HKLM\Drivers\USB\LoadClients

> that matches the device IDs or its class (it first check IDs and

> release, then class to allow you to load a device-specific driver also

> for devices that implement a class that is supported by CE).

> This may happen also when the USBDeviceAttach function of the driver has

> not "accepted" to handle it (not setting the accept flag to TRUE). Why

> this may happen is quite device specific.

> If you provide the DLL name for your driver the driver is loaded

> correctly? In this case I would suspect a registry configuration

> problem. If you checked that the keys are correctly configured, it may

> be USBDeviceAttach failing to correctly recognize/initialize the device.

> This happens on your PXA board or on the WM device?

>

> --

> Valter Minute (eMVP)

> Training, support and development for Windows CE:

> www.fortechembeddedlabs.it

> My embedded programming and cooking blog:

> www.geekswithblogs.net/WindowsEmbeddedCookbook

> Windows Embedded support forums in Italian:

> http://social.msdn.microsoft.com/Forums/it-IT/windowsembeddedit/threads

> (the reply address of this message is invalid)

> .

>

 

[Valter Minute [eMVP]]

On 3/18/2010 9:13 PM, Rob wrote:

> Hi,

> Thanks for the tips.

> It happens on the WM device, when the client-device is connected.

> I am not sure what client they are connecting exactly.

> Is it possible for them to check what GUID the device reports ?

> (my client is on the other side of the world, i have never seen their client

> or host)

> I am trying to figure out some options for very-very-remote-debugging -)



There is no GUID. You need vendorid, devicedi and class. You can get

them by attaching the device to a PC and checking its properties in the

device manager.



--

Valter Minute (eMVP)

Training, support and development for Windows CE:

www.fortechembeddedlabs.it

My embedded programming and cooking blog:

www.geekswithblogs.net/WindowsEmbeddedCookbook

Windows Embedded support forums in Italian:

http://social.msdn.microsoft.com/Forums/it-IT/windowsembeddedit/threads

(the reply address of this message is invalid)