Can´t connect to Windows Mobile Gerätecenter

  • Hello,


    Today I got a NETDCU14 for testing as replacement of the currently used NETDCU10


    But with the NETDCU14 I can not connect to the WINDOWS-Mobile Gerätecenter.


    With NETDCU10 I have no problem. (Same hardware platform).


    Do I have to make any additional settings on NETDCU14 ?


    (NDCUCFG over RS232 is working correctly).



    Best regards


    Manfred Geugelin


    In the meantime the board is not working any more.
    I removed the registry key LCD because the LCD-display we are using was not working on NETDCU14 and so I made the same settings as on NETDCU10
    (Samsung -> Mode100) but after doing this the system is not working any longer.


    // here is the debug output


    Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Aug 27 2012 17:23:31<\r><\n>
    Microsoft Windows CE Bootloader for NetDCU14 Built Aug 30 2012<\r><\n>
    Portions copyright (c) 2012 F&S Elektronik Systeme GmbH<\r><\n>
    Boot Loader, Version 1.8<\r><\n>
    NBoot, Version VN15<\r><\n>
    HW rev. 1.10<\r><\n>
    <\r><\n>
    HW-Watchdog: ON<\r><\n>
    System ready!<\r><\n>
    Preparing for download...<\r><\n>
    Press >S< to step into monitor...<\r><\n>
    AUTO BOOT enabled <\r><\n>
    Kernel (3026kB) read from flash disk started finished in 0 milliseconds<\r><\n>
    INFO: OEMLaunch: Jumping to Physical Address 0x4002B9DCh (Virtual Address 0x0h)...<\r><\n>
    <\r><\n>
    <\r><\n>
    Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 7 2012 at 17:38:46<\r><\n>
    [OAL] ++OEMInit()<\r><\n>
    INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb<\r><\n>
    OAL Log enable : 1 <\r><\n>
    OAL Log mask : 3 <\r><\n>
    <\n>******** System Clock Info **********<\r><\n>
    [OAL] APLL_CLK : 1000000000 Hz<\r><\n>
    [OAL] MPLL_CLK : 667000000 Hz<\r><\n>
    [OAL] EPLL_CLK : 96000000 Hz<\r><\n>
    [OAL] VPLL_CLK : 54000000 Hz<\r><\n>
    <\n>[OAL] ARM_CLK : 1000000000 Hz<\r><\n>
    [OAL] HCLK_MSYS : 200000000 Hz<\r><\n>
    [OAL] PCLK_MSYS : 100000000 Hz<\r><\n>
    [OAL] HCLK_DSYS : 166750000 Hz<\r><\n>
    [OAL] PCLK_DSYS : 83375000 Hz<\r><\n>
    [OAL] HCLK_PSYS : 133400000 Hz<\r><\n>
    [OAL] PCLK_PSYS : 66700000 Hz<\r><\n>
    ******** System Clock Info **********<\r><\n>
    <\n>******** NKForceCleanBoot Change for Release **********<\r><\n>
    <\n>OEM:-------------------------------------------<\r><\n>
    OEM: Normal Boot!!<\r><\n>
    OEM:-------------------------------------------<\r><\n>
    <\r><\n>
    NetDCU14 V0.80 - Firmware Init<\r><\n>
    Copyright (c) 2012 F&S Elektronik Systeme GmbH<\r><\n>
    Build: Aug 30 2012/15:42:18<\r><\n>
    [OAL] 2NDLAN Enabled<\r><\n>
    HW-WATCHDOG: ENABLED<\r><\n>
    FMD: NAND ID:0xf192 --> EON: 1GBit (128MB)<\r><\n>
    FMD: Block 0 to 6 are locked for boot loader<\r><\n>
    [OAL] RestartReason: Reset<\r><\n>
    [OAL] VidMemBase: 0x27000000<\r><\n>
    FMD: NAND ID:0xf192 --> EON: 1GBit (128MB)<\r><\n>
    FMD: Block 0 to 6 are locked for boot loader<\r><\n>
    PM-NETDCU: STARTED<\r><\n>
    BE2: Version 1.2, ActiveKey = Drivers\Active\01<\r><\n>
    DMSG: DrvWAITInitialize<\r><\n>
    PWC: Version 1.0, ActiveKey = Drivers\Active\02<\r><\n>
    I2C: Version 3.2, ActiveKey = Drivers\Active\03<\r><\n>
    OHCI: Version 1.0, ActiveKey = Drivers\BuiltIn\OHCI<\r><\n>
    PSS: Version 1.1, ActiveKey = Drivers\Active\12<\r><\n>
    [VDE:ERR] SVE_initialize_RAW_camera_driver() : \Drivers\Display\LCD\ Cannot Read RegistryKey : UseAsPost(NULL)<\r><\n>
    [VDE:ERR] SVE_initialize_RAW_camera_driver() : Try to use Default Setting Driver CAM2:, But it can not work<\r><\n>
    [VDE:ERR] SVE_initialize_RAW_WB_camera_driver() : \Drivers\Display\LCD\ Cannot Read RegistryKey : UseForWB(NULL)<\r><\n>
    [VDE:ERR] SVE_initialize_RAW_WB_camera_driver() : Try to use Default Setting Driver CAM3:, But it can not work<\r><\n>
    ::AttachDevice SUCCESS_HS:2000<\n>AX88796: Version 01.06, ActiveKey = Comm\ETHNETA<\r><\n>
    ENC624J600: Version 01.00, ActiveKey = Comm\ETHNETNR<\r><\n>
    AX88796: Version 01.06, ActiveKey = Comm\ETHNETB<\r><\n>
    NI2C: Version 3.2, ActiveKey = Drivers\Active\22<\r><\n>
    UART: Version 1.3, Key = Drivers\Active\23<\r><\n>
    BE2: Version 1.2, ActiveKey = Drivers\Active\24<\r><\n>
    CID: Version 2.10, ActiveKey = Drivers\Active\25<\r><\n>
    CID: Version 2.10, ActiveKey = Drivers\Active\26<\r><\n>
    ::AttachDevice SUCCESS_HS:2000<\n>CMM: Version 1.3, ActiveKey = Drivers\Active\27<\r><\n>
    SDMMCCh0: Version 1.5, ActiveKey = Drivers\Active\28<\r><\n>
    FSKBDHID: Version 1.0, ActiveKey = Drivers\Active\32<\r><\n>
    SDMMCCh0: Card removed!<\r><\n>
    ::AttachDevice SUCCESS_HS:2000<\n>Attach moutouchHID<\r><\n>
    TVD: Version 1.4, ActiveKey = Drivers\Active\46<\r><\n>
    MFC: Version 1.0, ActiveKey = Drivers\Active\49<\r><\n>
    MFC power on<\r><\n>
    MFC power off<\r><\n>
    BCS: Version 1.2, ActiveKey = Drivers\Active\50<\r><\n>
    DIO: Version 2.3, ActiveKey = Drivers\Active\51<\r><\n>
    LCD: Version 1.4, ActiveKey = Drivers\Display\LCD<\r><\n>
    LCD: Read registry settings from Drivers\Display\LCD<\r><\n>
    LCD: Display-Mode 1, Name SVGA standard display<\r><\n>
    Incorrect information dwi.dwNumMemWindows:0, dwi.memWindows[0].dwBase:0x0, dwi.memWindows[0].dwLen:0x0, Check Registry Key:\Drivers\Display\LCD\<\r><\n>
    [DISPDRV:ERR] --SMDKDisp::AllocResource : Failed, ioPhysicalBase(0x0)<\r><\n>
    [DISPDRV:ERR] SMDKDisp::SMDKDisp() : AllocResource() Fail<\r><\n>
    Exception 'Data Abort' (4): Thread-Id=04cb0006(pth=99a84664), Proc-Id=00400002(pprc=80439308) 'NK.EXE', VM-active=01e20002(pprc=9fdbe15c) 'udevice.exe'<\r><\n>
    PC=c0082dc8(k.coredll.dll+0x00052dc8) RA=c0b63704(display.dll+0x00013704) SP=d324f670, BVA=00000000<\r><\n>
    Exception 'Data Abort' (4): Thread-Id=04cb0006(pth=99a84664), Proc-Id=00400002(pprc=80439308) 'NK.EXE', VM-active=01e20002(pprc=9fdbe15c) 'udevice.exe'<\r><\n>
    PC=c036b738(gwes.dll+0x0005b738) RA=c036b720(gwes.dll+0x0005b720) SP=d324fdd8, BVA=00000104<\r><\n>



    Do you have an image for the board to download on the NETDCU14. (I can not found any
    downloads for NETDCU14)


    Best regards


    Manfred Geugelin

  • Hello,
    key for register LCD is HKLM/drivers/display/lcd/mode<xxx>.
    Best would be to erase registry (from bootloader). Afterwards the board should boot normal. Then register LCD again. If the problem persits please post your settings.

  • Hello,
    if ActiveSync/Mobile Device Center does not work at all, the following setting may "resolve" the problem:

    Code
    1. [HKLM\Drivers\Builtin\USBFN]
    2. "speed"=dword:1

    refer device driver documentation for details.
    In terms of "ndcucfg":

    Code
    1. reg open \Drivers\Builtin\USBFN
    2. reg set value speed dword 1
    3. reg save
  • Hello,


    Thanks for the information. The board is booting now correctly but the "Windows Mobile Gerätecenter" is still not working.


    I have set the speed value to 1.


    Here are the registry settings of the USBFN Key


    OK -> reg enum value \<\r><\n>
    00 "speed"=dword:1 \<\r><\n>
    01 "Dll"=string:usbfn.dll \<\r><\n>
    02 "Prefix"=string:UFN \<\r><\n>
    03 "Order"=dword:64 \<\r><\n>
    04 "Priority256"=dword:100 \<\r><\n>
    05 "Irq"=dword:92 \<\r><\n>
    06 "BusIoctl"=dword:2752584 \<\r><\n>
    07 "IClass"=multi:{E2BDC372-598F-4619-BC50-54B3F7848D35}=%b;{6F40791D-300E-44E4-BC38-E0E63CA8375C}=%b \<\r><\n>
    08 "Flags"=dword:16777216 \<\r><\n>
    09 "LoadAsyncEvent"=string:SYSTEM/ShellAPIReady \<\r><\n>


    When I use the NETDCU10 on same hardware interface "Windows Mobile GeräteCenter" is working correctly.


    Another question is how to set registry to work with LCD.


    On NETDCU10 we used the following registry settings


    reg open \drivers\display\Samsung
    reg create key mode100
    reg set value name string "Sharp LQ057V3"
    reg set value EFW dword 8
    reg set value BFW dword 24
    reg set value msignal dword 2
    reg set value rows dword 480
    reg set value LPP dword 480
    reg set value width dword 115
    reg set value height dword 86
    reg set value contrastenable dword 0
    reg set value contrastvalue dword 0
    reg set value type dword 6
    reg set value config dword 0x00700000
    reg set value columns dword 640
    reg set value PPL dword 640
    reg set value HSW dword 96
    reg set value bpp dword 16
    reg set value lcdclk dword 25
    reg set value VSW dword 8
    reg set value BLW dword 44
    reg set value ELW dword 16
    reg set value EnableCursor dword 1
    reg set value rotate dword 2
    display mode set 100
    reg save
    reboot hardware


    So on NETDCU14 I have to create a key with mode100 and insert the setting in this key
    is this correct ?




    best regards


    Manfred

  • Hello,


    LCD:

    Code
    1. reg create key mode100
    2. reg open \drivers\display\LCD
    3. ...


    this sould work. Does it?


    USB:
    please contact our HW department.

    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.

  • Is USB device not working at all (error message when connecting) or is just Active Sync not working?
    If the NetDCU14 is detected (USB Plug with green check mark symbol is shown in taskbar,Microsoft USB Sync displayed in Device Manager, NetDCUUSBLoader works) then you must delete the Microsoft USB Sync device in the Device Manager and connect the NetDCU14 again.
    Then it should work.
    If the NetDCU14 is not detected at all, then check your baseboard for for USB compliant routing.
    Also check if pin 1 of the USB connector is connected to NetDCU14 J7 pin 25. This connection is needed for proper operation.

    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.

  • I had the same problem, when trying to connect to Microsoft ActiveSync using the NetDCU14 USB device port. I was able to solve the issue by reducing the speed to 12MBit/s and by connecting the USB-Detect Pin (J7 25) to the 5V supply (Pin 1) of the device port. However, this means that the NetDCU14 is not compatible to our existing NetDCU10 hardware system. Because NetDCU10 did not use this USB-Detect input on the slave port. Is it possible to deactivate this detect pin of the NetDCU14 to make it compatible with our old design? If not, this means we would have to reroute two PCBs to get the 5V connection to the USB plug...

  • All new processors need 5V on the USB detect pin for proper function.
    It is not possible to use USB Device without this pin.

    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.