Re: Trying to get a Touch Screen driver loaded.
- From: "Bruce Eitman [eMVP]" <beitman.nospam@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 31 Jan 2008 10:01:14 -0500
I don't use the GUI much for building. So, I would open a build window, cd
to the touch driver. Then:
1. change code
2. build
3. makeimg
That is dependent on setting WINCEREL in the environment.
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"JeffB" <JeffB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DB3D6A07-3BF9-445B-805B-5676444DBD30@xxxxxxxxxxxxxxxx
Thanks, I have started reading about the build tools but don't fully
understand when to use one over the other.
Let's say I'm just updating the TouchScreen Driver. Which build tool
would
I use?
Can you guys recommend any books or tutorials?
"Bruce Eitman [eMVP]" wrote:
If you are waiting 45 minutes to build, then open help and get familiar
with
the build tools. You shouldn't need to take that long, I can go from
driver
change to download in a couple of minutes. To do so, you need to
understand
how the system builds.
Look for:
cebuild
sysgen
buildrel
makeimg
to get started.
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
"JeffB" <JeffB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B6425F30-C6CC-4D26-B326-0E4634EE8DC5@xxxxxxxxxxxxxxxx
I am very new at this so please bear with me.
I am trying to get a touch screen driver loaded an becoming very
frustrated.
Here is what I have in my .bib file
MODULES
; Name Path
Memory
Type
-------------- --------------------------------------------- -----------
USBTouch.dll c:\CEDB\USBTouch.dll NK SHK
TouchKit.exe c:\CEDB\TouchKit.exe NK S
DrawTest.exe c:\CEDB\drawtest.exe NK S
Calbration.exe c:\CEDB\calbration.exe NK S
UpdateEEPROM.exe c:\CEDB\UpdateEEPROM.exe NK S
and here are my registry entries.
[HKEY_LOCAL_MACHINE\Drivers\TouchKit]
"RBSIZE"=dword:800
[HKEY_LOCAL_MACHINE\Drivers\TouchKit]
"RBTIME"=dword:ffffff
[HKEY_LOCAL_MACHINE\Drivers\TouchKit]
"FLAGS"=dword:1
[HKEY_LOCAL_MACHINE\Drivers\TouchKit]
"BeepFrequence"=dword:1f4
[HKEY_LOCAL_MACHINE\Drivers\TouchKit]
"BeepTime"=dword:64
[HKEY_LOCAL_MACHINE\Drivers\TouchKit]
"ZFilterThreshold"=dword:800
[HKEY_LOCAL_MACHINE\Drivers\TouchKit]
"ZFilterBound"=dword:00100001
[HKEY_LOCAL_MACHINE\Drivers\TouchKit]
"SoundType"=dword:0
[HKEY_LOCAL_MACHINE\Drivers\TouchKit]
"NoPostRange"=dword:80
[HKEY_LOCAL_MACHINE\Drivers\USBTouch]
"DLL"="USBTouch.dll"
"Prefix"="TUB"
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\14371_1\0_0_0\255_255_255\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\14371_2\0_0_0\255_255_255\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\4660_1\0_0_0\255_255_255\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\3823_1\0_0_0\255_255_255\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\3823_2\0_0_0\255_255_255\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
;for Hid class
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\14371_1\Default\3\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\14371_2\Default\3\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\4660_1\Default\3\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\3823_1\Default\3\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
[HKEY_LOCAL_MACHINE\Drivers\USB\LoadClients\3823_2\Default\3\USB_TOUCH_Driver]
"DLL"="USBTouch.dll"
Here's the problem. I am running a debug build and with I connect the
TouchScreen connector the Devlopment computer pops up a window asking
the
location of "USBTouch.dll" (even though it is in the \Windows directory
on
the CE device). I tell it where to find the .dll on the development
machine.
Then is ask for the location of "devapi.c". I don't have this file,
don't
know why it is asking for it. All I can do is cancel and here is what
the
Debug Window shows:
147554 PID:400002 TID:21c0002 CHub(Root tier
0)::HubStatusChangeThread -
port 3, change = 0x0001, status = 0x0301
147688 PID:400002 TID:21c0002 CHub(Root tier
0)::HubStatusChangeThread -
device attached on port 3
147721 PID:400002 TID:21c0002 +CHub(Root tier 0)::AttachDevice - port =
3,
fIsLowSpeed = 1
147764 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0
147816 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0
147876 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0
148012 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST, failures =
0
148113 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0
148223 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0
148342 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures
=
0
148442 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0
148553 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0
148663 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures
=
0
148735 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0
148865 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0
148994 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - Select
Configuration 0 on DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE step
149073 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0
149162 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION, failures = 0
149259 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY,
failures
= 0
149365 PID:400002 TID:21c0002 CHub(Root tier 0)::AttachDevice - status
=
DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE,
failures =
0
149490 PID:400002 TID:21c0002 OSAXST1: >>> Loading Module
'usbtouch.dll'
(0x847854F8) at address 0xC0AC0000-0xC0AC7000 in Process 'NK.EXE'
(0x81ADBC80)
PB Debugger Loaded 'usbtouch.dll', no matching symbolic information
found.
149626 PID:400002 TID:21c0002 Kernel DLL 'usbtouch.dll' needs thread
creation/deletion notification
149661 PID:400002 TID:21c0002 +USBD:OpenPipe, EP: 0x81, MaxPkt: 8,
Type:
Interrupt
149704 PID:400002 TID:21c0002 CInterruptPipe::OpenPipe - setting the
poll
interval to 4 ms instead of 5 ms
149756 PID:400002 TID:21c0002 -USBD:OpenPipe success, hPipe = D07CD710
149817 PID:400002 TID:21c0002 Unknown: DEBUGCHK failed in file
C:\ymzki\private\winceos\COREOS\device\devcore\.\devapi.c at line 29
149903 PID:400002 TID:21c0002 Unknown: DEBUGCHK failed in file
C:\ymzki\private\winceos\COREOS\device\devcore\.\devapi.c at line 29
Now the debugger keeps stopping at line 29 of devapi.c
Please help, I just want to get the touch screen going. Not to mention
the
frustration at having to wait 45 minutes to build, rebuild, or whatever
everytime I want to change something.
Thanks.
.
- References:
- Trying to get a Touch Screen driver loaded.
- From: JeffB
- Re: Trying to get a Touch Screen driver loaded.
- From: Bruce Eitman [eMVP]
- Re: Trying to get a Touch Screen driver loaded.
- From: JeffB
- Trying to get a Touch Screen driver loaded.
- Prev by Date: Re: USB driver for device
- Next by Date: Re: aygshell.h missing in WinCE6.0 SDK
- Previous by thread: Re: Trying to get a Touch Screen driver loaded.
- Next by thread: .Net Compact Framework does not work in CE 6.0 ?
- Index(es):
Relevant Pages
|
