No ndcucfg on Com1 and problems connecting via usb

    We try to use the NetDCU14 as a replacement for the NetDCU8 on the same baseboard but so far I wasn't able to connect the board via usb and I also cannot get ndcucfg to work on Com1.


    During boot the debug-output says:
    NDCUCFG Open COM1: at 38400 Baud
    CreateFile() failed -> ERROR COM1:


    When I connect the board via usb the output says:
    USBFN: SDE: USB_HIGH detected
    [UFNPDD] RESET Exception


    When I change the ndcucfg configuration with
    reg open \Drivers\Builtin\USBFN
    reg set value speed dword 1
    reg save
    the following output appears:
    [UFNPDD] RESET Exception
    USBFN: SDE: USB_FULL detected


    Anything I could do now?

    Hello,

    Quote

    During boot the debug-output says:
    NDCUCFG Open COM1: at 38400 Baud
    CreateFile() failed -> ERROR COM1:

    Serial debug line and "ndcucfg" are using the same port on NetDCU14 in contast to NetDCU6/8. You have two possibilities to use "ndcucfg" via serial line:
    1. Disable serial debug output by boot loader command "O" ... . Or run "ndcucfg" on a command shell and enter "serial debug off".
    2. You can redirect "ndcucfg" to an other seriel line via registry entry HKLM\system\ndcucfg\port="COMx:".
    There is even a third possibility, you can redirct seria debug output by change nboot. We can deliver nboot on request.


    Did you refer http://www.forum.fs-net.de/viewtopic.php?f=59&t=3282, contribute from 6.11.2012?

    Quote

    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.

    When I disable serial debug output I finally get to ndcucfg which is great. Then I thought why not redirect ndcucfg to Com2 like it was on NetDCU8 and enable serial debug output again!
    Now I am getting:
    NDCUCFG Open COM2 at 38400 Baud
    CreateFile() failed -> ERROR COM2
    Is Com2 also blocked by something else?


    About USB-Connection: I was indeed referring to the thread about the usb problems. Does the registry setting set the USB Speed to 1.1 and if so, is there still a difference between NetDCU8 and NetDCU14 so the USB-Connection with our baseboard doesn't work?

    COM:
    please try "COM2:" instead of "COM2".


    USB:
    i mean especially the contribution from 6.11.2012. If you checked this and the problem persists then set speed to "1".
    If nothing helps contact our HW department (best would be to send your schematic).

    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.

    With "COM2:" it now works, thanks for the help.


    About the USB-Problem:
    When i connect via usb my pc always shows the message that the usb device could not be recognized and "unknown device".
    I also tried to download a kernel in bootloader but after typing DU i only get the message EOTG: USB DeInit 0xE59FF3D8. Is that normal?


    After changing the partitions in bootloader windows ce isn't booting up anymore so i tried to transfer a new kernel via eshell. Now i get the message
    BINFS:IOCTL_KLIB_SETROMDLLBASE (first = d3ac0000, last = 00180000) failed; error=87!!!
    in debug output. Did i install the wrong image?

    Hello,

    Quote


    After changing the partitions in bootloader windows ce isn't booting up anymore so i tried to transfer a new kernel via eshell. Now i get the message
    BINFS:IOCTL_KLIB_SETROMDLLBASE (first = d3ac0000, last = 00180000) failed; error=87!!!
    in debug output. Did i install the wrong image?

    Which kernel do you try to install?
    Can you post serial debug output for command "I" and all output after enter "DE"?

    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 was trying to install kernel XIPV210_CE6Core_121010.bin.
    Bootloader settings:


    NetDCU14 boot options valid : YES
    Start Download after reboot : no
    Download kernel to : FLASH
    Kernel load/store compression : OFF
    Size of area for OS image : 64 MB
    Size of FFSDISK : 64 MB
    Format of FFSDISK : FAT
    F3S serial number :
    Launch image after reboot : yes
    Output debug messages at serial port : yes
    Bootloader Network setting valid : YES
    -MAC Address : 0:5:51:xx:xx:xx
    -Use DHCP to get IP address: YES
    WindowsCE MAC address valid : yes
    -WindowsCE MAC Address : 0:5:51:xx:xx:xx


    After typing DE:


    HW-Watchdog: OFF
    ETH: MAC set to : 0:5:51:xx:xx:xx
    ETH: HWSetMCRegs: Set all to 0x00
    INFO: *** Device Name 'NetDCU1422023' ***
    INFO: *** Device Name 'NetDCU1422023' ***
    InitDHCP():: Calling ProcessDHCP()
    ProcessDHCP()::DHCP_INIT
    Got Response from DHCP server, IP address: 192.168.1.43


    ProcessDHCP()::DHCP IP Address Resolved as 192.168.1.43, netmask: 255.255.255.0
    Lease time: 691200 seconds
    Got Response from DHCP server, IP address: 192.168.1.43
    No ARP response in 2 seconds, assuming ownership of 192.168.1.43
    +EbootSendBootmeAndWaitForTftp
    Sent BOOTME to 255.255.255.255
    Sent BOOTME to 255.255.255.255
    Sent BOOTME to 255.255.255.255
    Sent BOOTME to 255.255.255.255
    Sent BOOTME to 255.255.255.255
    Sent BOOTME to 255.255.255.255
    Packet has the following data:
    boot.bin[NULL]octet[NULL]
    TFTP packet could have 1 name/value pairs
    Locked Down Link 1
    Src IP 192.168.1.43 Port 03D4 Dest IP 192.168.1.24 Port CC7C
    Default TFTP block size set to: 512 bytes
    There were no options detected in the TFTP
    EthDown::TFTPD_OPEN::boot.bin
    -EbootSendBootmeAndWaitForTftp


    Download file information:
    -------------------------------------------------------------------------------
    [0]: Address=0x80020000 Length=0x203B5B8 Name=
    INFO: Changed start address for to 0x80020000.
    -------------------------------------------------------------------------------
    1 files tranfered
    INFO: Write image at 0x80020000 size 0x0203b5b8 to NAND Flash
    Create partition for boot section ...
    Success
    Create partition for kernel section ...
    Success
    Create partition for FFSDISK section ...
    FindFreeSector: FreeSector is: 0x83 after processing part 0x20.
    FindFreeSector: FreeSector is: 0x80c1 after processing part 0x21.
    FindFreeSector: FreeSector is: 0xfe00 after processing part 0xf3.
    CreatePartition: can't find free sector.
    Failed
    ERROR: Can't create partition (type=0xB, size=0xFFFFFFFF)
    WriteRegionsToNandFlash
    INFO: [0] Found chain information (pChainInfo=0x801E5C20 Extensions=0x3).
    [Dump XIP Chain Summary]
    - pvAddr: 0x80400000
    - dwMaxLength : 16384
    - usOrder : 0x0
    - usFlags : 0x0
    - reserved : 0x0
    Writing single region/multi-region update, dwBINFSPartLength: 33797560
    INFO: BP_OpenPartition: dwBINFSPartLength =0x203B5B8).
    dwRegionStart=0x80020000).
    dwRegionLength=0x203B5B8).
    INFO: BP_SetDataPointer: Set data pointer in BINFS partition (offset=0x0).
    INFO: WriteRegionsToNandFlash: Write region to BINFS partition (start=0x80020000, length=0x203B5B8).
    Writing image to flash complete.
    AUTO-BOOT enabled
    All files flashed
    OEMReadData: 0x1CE4648
    Leaving DownloadImage()
    dwImageStart=0x80020000, dwImageLength=0x203b5b8, dwLaunchAddr=0x8002bafc
    OEMAfterDownload(dwAction=0x0)
    ROMHDR at Address 80020044h
    Got EDBG_CMD_JUMPIMG
    Got EDBG_CMD_CONFIG, flags:0x0000000F
    INFO: OEMLaunch: Jumping to Physical Address 0x4002BAFCh (Virtual Address 0x8002BAFCh)...



    Windows CE Kernel for ARM (Thumb Enabled) Built on May 7 2012 at 12:47:43
    [OAL] ++OEMInit()
    INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
    OAL Log enable : 1
    OAL Log mask : 3
    ******** System Clock Info **********
    [OAL] APLL_CLK : 1000000000 Hz
    [OAL] MPLL_CLK : 667000000 Hz
    [OAL] EPLL_CLK : 96000000 Hz
    [OAL] VPLL_CLK : 54000000 Hz
    [OAL] ARM_CLK : 1000000000 Hz
    [OAL] HCLK_MSYS : 200000000 Hz
    [OAL] PCLK_MSYS : 100000000 Hz
    [OAL] HCLK_DSYS : 166750000 Hz
    [OAL] PCLK_DSYS : 83375000 Hz
    [OAL] HCLK_PSYS : 133400000 Hz
    [OAL] PCLK_PSYS : 66700000 Hz
    ******** System Clock Info **********
    ******** NKForceCleanBoot Change for Release **********
    OEM:-------------------------------------------
    OEM: Normal Boot!!
    OEM:-------------------------------------------


    NetDCU14 V0.90 - Firmware Init
    Copyright (c) 2012 F&S Elektronik Systeme GmbH
    Build: Oct 10 2012/11:10:32
    FMD: NAND ID:0xf192 --> EON: 1GBit (128MB)
    FMD: Block 0 to 6 are locked for boot loader
    [OAL] MACB: Disabled
    [OAL] RestartReason: Reset
    [OAL] VidMemBase: 0x4f000000
    FMD: NAND ID:0xf192 --> EON: 1GBit (128MB)
    FMD: Block 0 to 6 are locked for boot loader
    BINFS:IOCTL_KLIB_SETROMDLLBASE (first = ceac0000, last = 00180000) failed; error=87!!!

    please install lastest NBoot, EBoot and kernel.


    nbootv210_17
    ebootv210_109
    XIPV210_CE6Core_121109

    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.

    You have the right kernel, but there are more recent kernel available.
    Please do repartitionize (other values) and try it again.
    If noting helps erase flash in nboot and install eboot (e.g. via serial line) and kernel again. Use latest versions.

    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.