Is it possible to contact the PicoCOMA5 via JTAG?
If it is possible, how can this be permanently prevented?
Posts by Ralf
-
-
-
Hello,
already with the default settings of the new driver the problem of the wrong evaluations seems to be solved.
Nevertheless, I will extend my test program for the touch driver and try different settings.
Thanks for the support.
-
-
We are increasingly getting complaints from our customers that the touch often gives wrong results. So my question, do you know the problem and if so, how can we improve that? We use the PicoCOMA5 with the Windows 7 CE operating system. Attached is a screenshot of a small test application. In this application, the incorrect results of touches are recorded. In this example the button was pressed 200 times. This resulted in 16 incorrect measurements! Advanced info: We use a 5.7 inch Display "URT UMSH8227MD" and a resitive 4 wire touch.
-
Hello,
our IT administrator has informed me that the driver is working now. Thank you for your support.
-
Until now, we only worked on the PC with Windows 7 . With this OS we installed our Kernels to the PicoCOMA5 via the programs DCUTerm and NetDCU-USB-Loader. Everything worked fine. But now, we changed our PC to Windows 10. Unfortunately, after the command “du” in the DCUTerm program the “LED”-symbol don't switch to green. Our Administrator think, that Windows 10 does not support the USB-driver because of the signature. Do you have any new drivers for the USB-Loader? The last version of the program we have is V2.4.1.0.
-
Thank you for your support. I have found the mistake. Now it works.
-
Hello,
I have changed the value to 2000 ms and 5000 ms. But always the same problem. I also have set the debug value of I2C3: to 255. Here the result:
<0>
Microsoft Windows CE Bootloader Common Library Version 1.2 Built Sep 10 2014 19:51:25
Microsoft Windows CE Bootloader for PicoCOMA5 Built Sep 10 2014
Portions copyright (c) 2012 F&S Elektronik Systeme GmbH
Boot Loader, Version 1.1
NBoot, Version VN11
HW rev. 1.20HW-Watchdog: ON
System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
Kernel (3302kB) read from flash disk started finished in 592 milliseconds
INFO: OEMLaunch: Jumping to Physical Address 0x8010A1E0h (Virtual Address 0x0h)...Jumping to Kernel @ 0x8010A1E0
Windows CE Kernel for ARM (Thumb Enabled)
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xbPicoCOMA5 V2.01 - Firmware Init
Copyright (c) 2013 F&S Elektronik Systeme GmbH
Build: Apr 15 2015/10:45:28
FMD: NAND ID:0x1da9095 --> Spansion: 2GBit (256MB)
FMD: Block 0 to 16 are locked for boot loader
I2C: Version 2.5
OAL: MACB Disabled
OAL: RestartReason=RESETB
FMD: NAND ID:0x1da9095 --> Spansion: 2GBit (256MB)
FMD: Block 0 to 16 are locked for boot loader
FSPART: FS partition driver loaded
BINFS: RegisterVolume - Mounted volume '\BINFS'
F3S_FSD: Checking serial number...
F3S_FSD: Failsafe Flash File System - V2.11
FMD: NAND ID:0x1da9095 --> Spansion: 2GBit (256MB)
FMD: Block 0 to 16 are locked for boot loader
F3S_FSD: Volume successfully mounted at FFSDISK (size=182 MB)!
PM-NETDCU: STARTED
BE2: Version 1.4, ActiveKey = Drivers\Active\03
NI2C: Version 1.0, ActiveKey = Drivers\Active\13
NI2C: Priority256 = 0x00000067 = 103 (Default)
NI2C: ClockFreq = 0x00061a80 = 400000
NI2C: DeviceArrayIndex = 0x00000003 = 3
NI2C: IntPullUp = 0x00000001 = 1
NI2C: DrvStrength = 0xffffffff = 4294967295 (Default)
NI2C: RepeatedStarts = 0x00000001 = 1
NI2C: ClkToggleNumber = 0x00000008 = 8
NI2C: I2CBusCheck = 0x00000001 = 1
NI2C: -GetRegistryData()
NI2C3: +CheckI2CLines
NI2C3: -CheckI2CLines
NI2C3: I2C_Init: MUX Pad Control Register[21]=0x00000001
NI2C3: I2C_Init: MUX Pad Control Register[20]=0x00000001
ENET: Version 01.03, ActiveKey = Comm\ETHNETA
BE2: Version 1.4, ActiveKey = Drivers\Active\16
NI2C: +I2C_Init(0xc4469240)
NI2C: Version 1.0, ActiveKey = Drivers\Active\17
NI2C: Alloc memory size=636
NI2C: +GetRegistryData()
NI2C: Debug = 0x000000ff = 255 (Default)
NI2C: Priority256 = 0x00000067 = 103 (Default)
NI2C: ClockFreq = 0x00030d40 = 200000
NI2C: DeviceArrayIndex = 0x00000001 = 1
NI2C: IntPullUp = 0x00000000 = 0
NI2C: DrvStrength = 0xffffffff = 4294967295 (Default)
NI2C: RepeatedStarts = 0x00000001 = 1
NI2C: ClkToggleNumber = 0x00000008 = 8
NI2C: I2CBusCheck = 0x00000001 = 1
NI2C: -GetRegistryData()
NI2C1: +CheckI2CLines
NI2C1: -CheckI2CLines
NI2C1: I2C_Init: MUX Pad Control Register[39]=0x00000001
NI2C1: I2C_Init: MUX Pad Control Register[38]=0x00000001
UART: Version 1.16, Key = Drivers\Active\18
UART: Version 1.16, Key = Drivers\Active\19
UART1: Port disabled. Serial debug is on !
AIN: Version 1.2, ActiveKey = Drivers\Active\21
PWM: Version 1.2, ActiveKey = Drivers\Active\22
EXTRTC: Version 1.1, ActiveKey = Drivers\Active\23
NI2C3: +I2C_Open()
NI2C3: [5168] 0xccbbdb00: Device opened
NI2C3: -I2C_Open()
I2C: Version 4.2, ActiveKey = Drivers\Active\24
WAV: Version 2.3, ActiveKey = Drivers\Active\26
BCS: Version 1.4, ActiveKey = Drivers\Active\36
NSPI: Version 3.0, ActiveKey = Drivers\Active\37
DIO: Version 2.8, ActiveKey = Drivers\Active\38
LCD: Version 1.9, ActiveKey = Drivers\Display\LCD
LCD: Read registry settings from Drivers\Display\LCD
LCD: Display-Mode 100, Name URT UMSH8227MD
TchProxy: touch driver cann't be loaded. Check touch driver registry settings. -
Following problem.
We want to exchange the PicoCOM4 with a PicoCOMA5. After I have changed the modules and registry settings the most parts works. The only thing that is not working is the resistive touch.
So far, we control the PicoCOM4 via a four wire touch which is integrated in the URT UMSH8227MD display. For the operation with the PicoCOMA5 I wanted to use the "fs_tchproxy.dll" touch driver, but there is not started at all.
The last entry in the log-file is "TchProxy: touch driver cann't be loaded. Check touch driver registry settings." I have already checked but I can't find the mistake. This are my registry setting:[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"MaxCalError"=dword:7
"TouchSamples"=dword:3
"CalibrationData"="1046,1055 529,1386 523,686 1561,714 1569,1393"; how long touch proxy will wait for touch driver to load
[HKEY_LOCAL_MACHINE\SYSTEM\GWE\TouchProxy]
"tchcaldll"="fs_tchcaldll.dll"
"DriverLoadTimeoutMs"=dword:64 ; 100 msec[HKEY_LOCAL_MACHINE\SYSTEM\GWE\UserInput]
"TouchInputTimeout"=dword:3E8 ; 1 secondEntry of Log-File:
<-2>
Microsoft Windows CE Bootloader Common Library Version 1.2 Built Sep 10 2014 19:51:25
Microsoft Windows CE Bootloader for PicoCOMA5 Built Sep 10 2014
Portions copyright (c) 2012 F&S Elektronik Systeme GmbH
Boot Loader, Version 1.1
NBoot, Version VN11
HW rev. 1.20HW-Watchdog: ON
System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
Kernel (3302kB) read from flash disk started finished in 592 milliseconds
INFO: OEMLaunch: Jumping to Physical Address 0x8010A1E0h (Virtual Address 0x0h)...Jumping to Kernel @ 0x8010A1E0
Windows CE Kernel for ARM (Thumb Enabled)
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xbPicoCOMA5 V2.01 - Firmware Init
Copyright (c) 2013 F&S Elektronik Systeme GmbH
Build: Apr 15 2015/10:45:28
FMD: NAND ID:0x1da9095 --> Spansion: 2GBit (256MB)
FMD: Block 0 to 16 are locked for boot loader
I2C: Version 2.5
ERROR: OEMSetRealTime: NKSystemTimeToFileTime failed.
OAL: MACB Disabled
OAL: RestartReason=RESETB
FMD: NAND ID:0x1da9095 --> Spansion: 2GBit (256MB)
FMD: Block 0 to 16 are locked for boot loader
FSPART: FS partition driver loaded
BINFS: RegisterVolume - Mounted volume '\BINFS'
F3S_FSD: Checking serial number...
F3S_FSD: Failsafe Flash File System - V2.11
FMD: NAND ID:0x1da9095 --> Spansion: 2GBit (256MB)
FMD: Block 0 to 16 are locked for boot loader
F3S_FSD: Volume successfully mounted at FFSDISK (size=182 MB)!
PM-NETDCU: STARTED
BE2: Version 1.4, ActiveKey = Drivers\Active\03
NI2C: Version 1.0, ActiveKey = Drivers\Active\13
ENET: Version 01.03, ActiveKey = Comm\ETHNETA
BE2: Version 1.4, ActiveKey = Drivers\Active\16
NI2C: Version 1.0, ActiveKey = Drivers\Active\17
UART: Version 1.16, Key = Drivers\Active\18
UART1: Port disabled. Serial debug is on !
UART: Version 1.16, Key = Drivers\Active\19
AIN: Version 1.2, ActiveKey = Drivers\Active\21
PWM: Version 1.2, ActiveKey = Drivers\Active\22
EXTRTC: Version 1.1, ActiveKey = Drivers\Active\23
I2C: Version 4.2, ActiveKey = Drivers\Active\24
WAV: Version 2.3, ActiveKey = Drivers\Active\26
BCS: Version 1.4, ActiveKey = Drivers\Active\36
NSPI: Version 3.0, ActiveKey = Drivers\Active\37
DIO: Version 2.8, ActiveKey = Drivers\Active\38
LCD: Version 1.9, ActiveKey = Drivers\Display\LCD
LCD: Read registry settings from Drivers\Display\LCD
LCD: Display-Mode 100, Name URT UMSH8227MD
TchProxy: touch driver cann't be loaded. Check touch driver registry settings. -
Hello,
OK, thanks for help.
I will check if it also works in Compact 7. -
Hello,
your workaround for a quick solution works and we had the same idea before. Thanks.
But what about your next step to solve this problems?
Do you think, that microsoft make a patch of CE7? -
Hello,
we found a memory leak in the OS of windows compact 7. If we change very often the system time with the function:
[DllImport("coredll.dll", SetLastError = true)]
private static extern bool SetLocalTime(ref SYSTEMDATETIME lpSystemTime);the program memory will decrease until to hang up the software. We found a entry in the internet about this problem:
https://social.msdn.microsoft.…-wec7?forum=winembmngdapp
I have searched through the wohle QFEs of microsoft, but I can't find any entries of this problem.
Now my questions:
Do you know this problem?
How we can solve it? May be you have a workaround for this? -
Hello,
if we are using several PicoCOMA5 in our LAN and some of the moduls have the same IP-Adress, they will not appear a message.
I have checked with the NETDCU8. With that modul it will appear the message: "Windows CE Networking: The system has detected a conflict...."Which steps can I do to solve this problem?
-
Hello,
now it works. Thank you.
-
Hello,
we set the priority value from 1 to 250. But always the same.
-
-
Hello,
we have problems with our used resistive touch and now we are looking for the reasons.
For example: If we push and hold the touch on the blank desktop and drawing a border, they will not show this border as a fixed picture, no the border toggle the position about ten, twelve pixels all the time.
In the document “WINCE_FSVYBRID_DeviceDriver”, we can find a list of entries for the driver "fs_touch_sx865x.dll". But when we check the entries with a registry-editor, we see a lot of more values. We changed some values but the result always the same. Have you any help for us?Additional our driver settings:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch_SX865x]
"SampleRate"=dword:00000190
"TouchSamples"=dword:00000001
"Prefix"="tch"
"Dll"="fs_touch_sx865x.dll"
"Order"=dword:00000020
"Index"=dword:00000001
"Flags"=dword:00000008
"IClass"=hex(7):\
7b,32,35,31,32,31,34,34,32,2d,30,38,63,61,2d,34,38,64,64,2d,39,31,63,63,2d,\
62,66,63,39,66,37,39,30,30,32,37,63,7d,00,7b,61,33,32,39,34,32,62,37,2d,39,\
32,30,63,2d,34,38,36,62,2d,62,30,65,36,2d,39,32,61,37,30,32,61,39,39,62,33,\
35,7d,00,00
"Priority256"=dword:0000006d
"SysIntr"=dword:00000000
"SWCalibration"=dword:00000001
"InvertY"=dword:00000001
"InvertX"=dword:00000001
"Threshold"=dword:00000320
"ChangeIO"=dword:00000063
"ResetIO"=dword:00000062
"I2CDevAddr"=dword:00000090
"I2CDevice"="i2c3:"[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\I2C3]
"ClockFreq"=dword:00061a80
"Prefix"="I2C"
"Dll"="fs_ni2c.dll"
"Order"=dword:00000017
"Index"=dword:00000003
"DeviceArrayIndex"=dword:00000003
"FriendlyName"="Native I2C driver display con."
"RepeatedStarts"=dword:00000001
"IntPullUp"=dword:00000001Regards
Ralf -
-