Hi,
I want use a third party touch controller driver for the NetDCUA5.
The current driver i downloaded from the "Touch-Base" Website. This is a ARMV7 driver.
Run this driver on the NetDCUA5 Cortex-M4 processor under compact 2013 ?
thx
WEC2013 USB HID Device driver
-
-
ohhhh sorry, its a Cortex-A5 processor with compact 2013
-
Hello,
in general it should work! Note, that the driver have to be copied to flash memory to be persistent after a reboot. So possibly you have also to modify Registry settings from "\Windows\..." to "\ffsdisk\...".
-
ok nice
i copied the driver to \ffsdisk\StarTouch and modified the registry as follows
Display MoreCode- reg open \drivers\builtin\Touch_SX865X
- reg set val Flags dword 4
- ;
- reg open \drivers\builtin
- reg create key TBUPDD
- reg set val Dll string "ffsdisk\StarTouch\upddce.dll"
- reg set val Prefix string "TSD"
- reg set val Index dword 1
- reg set val Vid dword 9103
- reg set val Pid dword 1
- reg open \hardware\devicemap\touch
- reg del val CalibrationData
- reg set val DriverName string "ffsdisk\StarTouch\upddce.dll"
- ;
- reg open \drivers\usb\loadclients\default\default\
- reg create key 9103_1
- reg create key TBUPDDCEUSB
- reg set val Dll string "ffsdisk\StarTouch\tbupddceusb.dll"
- reg set val Order dword 64
- reg set val Index dword 1
- reg set val Prefix string "USB"
- reg save
- reboot
the "upddce.dll" driver is a native ce touch driver and the "tbupddceusb.dll" is the library for the USB interface
I want load this "upddce" driver with GWES.but the driver was not loaded, what is wrong ?
-
Hello,
is this "reg set val DriverName string "ffsdisk\StarTouch\upddce.dll"" really refered in the drivers reg file! driver should be loaded from USHD (like mouse or keyboard).
Any information from serial debug output?
-
Greetings,
I sure that the driver was refered to the reg file, I've experiment a little.
My reg file look as follows:Display MoreCode- rem
- rem // disable default touch driver
- rem
- reg open \drivers\builtin\touch_sx865x
- reg set val Flags dword 4
- rem
- rem // create new registry entry for UPDD Star Touch driver
- rem
- reg open \drivers\builtin\
- reg create key UPDD
- reg set val Dll string "\ffsdisk\StarTouch\upddce.dll"
- reg set val Index dword 0x1
- reg set val Order dword 0xff
- reg set val Vid dword 0x457
- reg set val Pid dword 0x1080
- reg set val "Packet Size" dword 0x40
- reg set val Prefix string "TSD"
- reg set val Settings string "\ffsdisk\StarTouch\tbupdd.ini"
- rem
- rem // open default devicemap touch driver
- rem // change driver name to upddce and erase current
- rem // calibration data
- rem
- reg open \hardware\devicemap\touch
- reg del val CalibrationData
- reg set val DriverName string "\ffsdisk\StarTouch\upddce.dll"
- rem
- rem // create new touch interface driver registry entry
- rem
- reg open \drivers\hid\loadclients\
- reg create key 1111_4224
- reg create key default
- reg create key default
- reg create key TBUPDDCEUSB
- reg set val Dll string "\ffsdisk\StarTouch\tbupddceusb.dll"
- reg set val Index dword 0x1
- reg set val Order dword 0xff
- reg set val Prefix string "HID"
- reg save
- reboot
Normaly must a HID driver registered at \drivers\hid\loadclients\ ... right ?
the debug output looks as follows:
Display MoreCode- Jumping to Kernel @ 0x8010BD69
- Windows CE Kernel for ARM (Thumb Enabled)
- INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
- HW-WATCHDOG: ENABLED
- NetDCUA5 V2.00 - Firmware Init
- Copyright (c) 2013 F&S Elektronik Systeme GmbH
- Build: Feb 19 2015/14:50:57
- FMD: NAND ID:0x2cf18095 --> MICRON: 1GBit (128MB)
- FMD: Block 0 to 16 are locked for boot loader
- OAL: Enable SCU
- I2C: Version 2.5
- INFO: No external RTC found!.
- OAL: RestartReason=Software
- OAL: Boot display enabled. Settings imported successfully.
- FMD: NAND ID:0x2cf18095 --> MICRON: 1GBit (128MB)
- FMD: Block 0 to 16 are locked for boot loader
- FSPART: FS partition driver loaded
- BINFS: RegisterVolume - Mounted volume '\BINFS'
- F3S_FSD: Failsafe Flash File System - V2.11
- FMD: NAND ID:0x2cf18095 --> MICRON: 1GBit (128MB)
- FMD: Block 0 to 16 are locked for boot loader
- F3S_FSD: Volume successfully mounted at FFSDISK (size=74 MB)!
- BE2: Version 1.4, ActiveKey = Drivers\Active\03
- NI2C: Version 1.0, ActiveKey = Drivers\Active\15
- BE2: Version 1.4, ActiveKey = Drivers\Active\16
- UART: Version 1.16, Key = Drivers\Active\17
- UART3 RS232 Configured
- UART: Version 1.16, Key = Drivers\Active\19
- UART2: Port disabled. Serial debug is on !
- UART: Version 1.16, Key = Drivers\Active\20
- CID: Version 2.7, ActiveKey = Drivers\Active\21
- CID: Version 2.7, ActiveKey = Drivers\Active\22
- ENET: Version 01.03, ActiveKey = Comm\ETHNETA
- AIN: Version 1.2, ActiveKey = Drivers\Active\24
- PWM: Version 1.2, ActiveKey = Drivers\Active\25
- EXTRTC: Version 1.1, ActiveKey = Drivers\Active\26
- EXTRTC: No external RTC detected
- I2C: Version 4.2, ActiveKey = Drivers\Active\27
- SDHC: Version 1.2, ActiveKey = Drivers\Active\28
- WAV: Version 2.3, ActiveKey = Drivers\Active\30
- ENET: Version 01.03, ActiveKey = Comm\ETHNETB
- BCS: Version 1.4, ActiveKey = Drivers\Active\38
- DIO: Version 2.8, ActiveKey = Drivers\Active\41
- SIO: Version 1.2, ActiveKey = Drivers\Active\42
- FRW: Version 1.1, ActiveKey = Drivers\Active\49
- LCD: Version 1.9, ActiveKey = Drivers\Display\LCD
- LCD: Read registry settings from Drivers\Display\LCD
- LCD: Display-Mode 20, Name Hitachi TX17D01VM2CP
- SE2: Version 1.3, ActiveKey = Drivers\Active\51
- NDCUCFG V 57 started. Platform: NetDCUA5
- NDCUCFG Open COM1: at 38400 Baud
- CreateFile() failed -> ERROR COM1:
- CheckAutoStart: Version 1.7, LaunchNum = 100
- SoftRTC disabled
- UsbHost : New Function [address(1) / layer(0)]
I think the new registered driver must show in the debug output window (TSD), if i plugged in the new USB device, right ?
