Problems by exchange PicoCOM4 with PicoCOMA5

      Problems by exchange PicoCOM4 with PicoCOMA5

      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 second

      Entry 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.20

      HW-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: 0xb

      PicoCOMA5 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.
      Best regards

      Ralf Zanner
      Hello,

      did you already increase ""DriverLoadTimeoutMs" e.g. to 2000ms?
      Any details by enabel Debug=255 for I2C3?
      F&S Elektronik Systeme GmbH
      As this is an international forum, please try to post in English.
      Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.
      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.20

      HW-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: 0xb

      PicoCOMA5 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.
      Best regards

      Ralf Zanner