Re: Using Embedded VisualC to debug a driver
From: Yannick Chamming's [eMVP] (ychammings_nospam_at_adeset.com)
Date: 02/24/05
- Next message: andrerev: "Configurable IP Address"
- Previous message: hcl: "Re: lan91c111 NdisMInitializeWrapper() error"
- In reply to: Dr Stuart Galt: "Using Embedded VisualC to debug a driver"
- Next in thread: Steve Maillet \(eMVP\): "Re: Using Embedded VisualC to debug a driver"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 24 Feb 2005 07:51:17 +0100
you should probably have a look at the "sources" file of the driver which is
the equivalent of a makefile for PB (defines include paths, linked lib and
so on).
As a driver is a standard dll, I think you should recreate an empty dll
project under eVC, try to include all source code files (.c and .h files) in
the project and insert all build settings from the "sources" file to the
settings of your project.
BR
Yannick
-- ---------------------------------------------------------------- Yannick Chamming's (eMVP) ADENEO (ADESET) Windows Embedded Manager ychammings AT adeset DOT com> http://www.adeset.com Tél : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- "Dr Stuart Galt" <stuartgalt73@hotmail.com> wrote in message news:O9qqNIiGFHA.3724@TK2MSFTNGP10.phx.gbl... > I'm currently having problems with a Philips USB host chip connected to my > Prolificx Eagle 250 ARM4 (Intel XScale) WinCE system. > > Philips have provided the source code for the host chip driver and this gets > built into the WinCE image by Prolificx, who then pass the image to us for > programming the board with. > > However, we are having problems that are specific to our hardware setup and > Philips have suggested breakpointing a specific CPP file and debugging from > there. Obviously, we cant do this with the image as it is (at least, that's > what I believe to be the case). > > Prolificx have suggested that it may be possible to have the driver code run > within Embedded Visual C as part of our test application and debug it from > there, rather than use the pre-compiled driver that comes as part of the > image. However, they are unaware of exactly how to do this or if it is > actually possible to actually do so. > > Does anyone know how to do this, or if it is actually possible? > >
- Next message: andrerev: "Configurable IP Address"
- Previous message: hcl: "Re: lan91c111 NdisMInitializeWrapper() error"
- In reply to: Dr Stuart Galt: "Using Embedded VisualC to debug a driver"
- Next in thread: Steve Maillet \(eMVP\): "Re: Using Embedded VisualC to debug a driver"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|