Re: Can One Make an XPe Device Appear As a Firewire Device?

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Benjamin Madsen (bmadsen_at_massie-labs.com)
Date: 10/13/04 

Date: Wed, 13 Oct 2004 18:00:24 GMT

I'm not sure if I want to emulate a certain type of device that exists
on the market right now. We're use xpe on a PC104 stack to control a
couple of imaging devices and a few of our own electronic modules. We
then need the PC104 stack to communicate to a host PC (also running
xpe), but I don't want to use TCP/IP to do it as the host PC will also
be talking to a public network for inter-system communications (Note
that by system I mean pair of Host PC and PC104 device stack).

I realize that it is probably less work to just manage the networking in
a controlled fashion, but I'd like it to be elegant enough that I can
tell my customer to just plug the device into their network and go. If
I use TCP/IP over firewire, I have to make an exception to the
"plug-and-play" statement.

Regardless, the device drivers is the way to do this. Now I just have
to figure out if it's worth doing at all. The other newsgroup is the
place for me to look. Thanks all...

-Ben

Note: In a brief search, I think I found a starting point:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/buses/hh/buses/1394-configrom_c96ec262-5546-4489-adce-5c768b7997a0.xml.asp

Slobodan Brcin (eMVP) wrote:
> Hi Benjamin,
>
> You can do that, but I don't think that except network (supported by default) you can create any other device type from user mode.
> You will have to write drivers for this job :(
> Unfortunately this is beyond of scope of this NG and you should try in some of driver programming related NG like:
> microsoft.public.development.device.drivers
>
> Anyhow like Konstantin said if you make driver that can work on XP Prof then you can use it on XPe without any modifications.
>
> Regards,
> Slobodan
> PS:
> What device type do you want to emulate?
>
>
> "Benjamin Madsen" <bmadsen@massie-labs.com> wrote in message news:CSXad.2439$gy1.1635@newsread1.news.pas.earthlink.net...
>
>>I realize that this is exposing my VERY limited knowledge of firewire
>>architecture and WDM driver architecture, but the question came up and I
>>figure I'd ask anyway...
>>
>>Is it possible to make an XP Embedded device appear as a Firewire device
>>to a connected XP Pro (or other OS) machine? If so, how would one go
>>about doing this? Is there some kind of SDK that would do this? Maybe
>>even just a How-To?
>>
>>Thanks,
>>Ben Madsen
>>Embedded Systems Engineer
>>Massie Laboratories, Inc.
>><bmadsen@massie-labs.com>

Relevant Pages

  • CE 5.0 network stack
    ... Does someone here know of any stability issue with Win CE 5.0 network ... PID:a609d4c2 TID:5b3ef32 Fatal Stack Error, ... There is no dynamic memory allocation in the driver. ... Is there any way to dig deeper into the crash site .. ...
    (microsoft.public.windowsce.embedded)
  • Re: MAC ADDRESS being reported at 0000000
    ... I meant that you should use arp on computer that is connected trough network to computer with XPe, but now it is not important. ... If you write pure program (driver) that executes in kernel space it can trough NDIS interface use and access network, ...
    (microsoft.public.windowsxp.embedded)
  • RE: Packet Blocking a.k.a. BlackICE
    ... BlackICE Defender has the equivalent of an intermediate driver. ... the same place in the stack. ... just one step above the network. ... (Which means, for example, that TDI ...
    (Focus-IDS)
  • Re: Sleep() issue
    ... I also hope that you setting THREAD_PRIORITY_TIME_CRITICAL priority level ... XPe system. ... In my XP Pro system there is probably much more activity then the kernel ... I suppose you don't have the source code of the driver you are ...
    (microsoft.public.windowsxp.embedded)
  • Re: Sleep() issue
    ... Since you are running the thread in time critical priority I wouldn't expect the 10-15 jitter from the Sleepcall unless there ... Well, I suppose you don't have the source code of the driver you are referring to, right? ... Try to run the following code sniplet on your hardware and see if you get different results on XP and XPe: ... Also hope you test the same code under XPe and XP Pro on the same hardware. ...
    (microsoft.public.windowsxp.embedded)