This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Cannot connect to DM3730 Device with Telnet

Other Parts Discussed in Thread: DM3730, OMAP3530

Hello,

I have DM3730 board with ARM_A8 BSP and WinCE 6 R3.  I created an image with KITL and VMINI disabled.  The build is successfully downled to flash through Ethernet using LAN9221 on board.  After booting to the desktop, I ping the board at address 192.168.0.3 from my development PC and get reply.  However, when I telnet to the same address, I got the message below:

Connecting To 192.168.0.3...Could not open connection to the host, on port 23: Connect failed

Would anyone please tell me what I am missing?  Why does "ping' work but not "telnet"?

Thanks,

Luan

  • Hi Luan,

    What are the registry settings. ALso in the OS Design have you selected requried catalog items for Telnet (SYSGEN_TELNETD) ?

    Regards,

    GSR

  • Thanks GSR for replying.

    The OS image has KITL and VMINI disabled (BSP_NOSHAREETH=1).  My custom board boots from flash and does not have a display so it is not easy to find out what the actual IpAddress is.  I disabled DHCP and set static IP address to 192.168.0.3.  The registry for the ethernet from reginit.ini is below

    ;===============================================================================
    ; @CESYSGEN IF CE_MODULES_VMINI
    ; @CESYSGEN ENDIF CE_MODULES_VMINI


    ; NDIS SMSC driver
    ; --> Entering C:\WINCE600\platform\Adenio2\src\drivers\SMSC9118\smsc9118.reg
    ; All rights reserved ADENEO EMBEDDED 2010
    ; @CESYSGEN IF CE_MODULES_NDIS
    ;-------------------------------------------------------------------------------
    [HKEY_LOCAL_MACHINE\Comm\SMSC9118]
        "DisplayName"="SMSC11X Ethernet Driver"
        "Group"="NDIS"
        "ImagePath"="Smsc9118.dll"

    [HKEY_LOCAL_MACHINE\Comm\SMSC9118\Linkage]
        "Route"=multi_sz:"SMSC91181"

    [HKEY_LOCAL_MACHINE\Comm\SMSC91181]
        "DisplayName"="SMSC11X Ethernet Driver"
        "Group"="NDIS"
        "ImagePath"="Smsc9118.dll"

    [HKEY_LOCAL_MACHINE\Comm\SMSC91181\Parms]
        "BusNumber"=dword:0
        "BusType"=dword:0
     "SysIntr"=dword:10    ; FIXED in the OAL to SYSINTR_FIRMWARE + 0
        "IoBaseAddress"=dword:15000000  ; ETHERNET_BASE (Physical Addr)
        "PhyAddress"=dword:20           ; PHY address (0x20:Auto, 0xFF:Internal)
        "RxDMAMode"=dword:0             ; 1-DMA, 0-PIO
        "TxDMAMode"=dword:0             ; 1-DMA, 0-PIO
        "FlowControl"=dword:1           ; 1-Enabled, 0-Disabled
        ; LinkMode will replace Duplex, Speed and FlowControl
        ; bit7: RESERVED, bit6: ANEG, bit5: ASymmetric Pause, bit4: Symmetric Pause
        ; bit3: 100FD, bit2: 100HD, bit1: 10FD, bit0: 10HD
        "LinkMode"=dword:7F
        ; Setting Auto-Mdix Status
        ; 0: Override strap, Disable Auto Mdix, straight cable
        ; 1: Override strap, Disable Auto Mdix, CrossOver cable
        ; 2: Override strap, Enable Auto Mdix
        ; Others or No Keyword: AutoMdix controlled by strap
        "AutoMdix"=dword:4
        ; INT_CFG value applied following HW_CFG_SRST_.  Note valid settings below:
         "IntCfg"=dword:0               ; bit4:IRQ_POL, bit0:IRQ_TYP (11/10/1/0)
        ;----------------------------------------------------------------------
        ; Following 3 keys use following value
        ;   2 = NdisDeviceStateD1 (WOL)
        ;   3 = NdisDeviceStateD2 (Energy Detect)
        ;   4 = NdisDeviceStateD3 (Full Power Down)
        ; NOTE
        ; Parm starts from 2 to 4 because NDIS enumerates as follows
        ;   typedef enum _NDIS_DEVICE_POWER_STATE
        ;   {
        ;       NdisDeviceStateUnspecified = 0,
        ;       NdisDeviceStateD0,
        ;       NdisDeviceStateD1,
        ;       NdisDeviceStateD2,
        ;       NdisDeviceStateD3,
        ;       NdisDeviceStateMaximum
        ;   } NDIS_DEVICE_POWER_STATE, *PNDIS_DEVICE_POWER_STATE;
        ; 
        ; See NDIS Powermanagement Comment in PUBLIC\COMMON\OAK\FILES\COMMON.REG
         "MinLinkChangeWakeUp"=dword:4
         "MinMagicPacketWakeUp"=dword:4
         "MinPatternWakeUp"=dword:4
        ;----------------------------------------------------------------------

    [HKEY_LOCAL_MACHINE\Comm\SMSC91181\Parms\TcpIp]
        "EnableDHCP"=dword:0
     "IpAddress"="192.168.0.3"
        "Subnetmask"="255.255.255.0"
        "DefaultGateway"="192.168.0.249"
        "UseZeroBroadcast"=dword:0

    I have "Telnet Server" included in the Catalog and the registry shows as below:

    ; @CESYSGEN IF SERVERS_MODULES_TELNETD
    [HKEY_LOCAL_MACHINE\Services\TELNETD\Accept\TCP-23]
       ; TCP port 23, default Telnet Port
       "SockAddr"=hex:02,00,00,17,00,00,00,00,00,00,00,00,00,00,00,00

    ; @CESYSGEN IF CE_MODULES_TCPIP6
    ; @CESYSGEN ENDIF CE_MODULES_TCPIP6

    ; Used for starting telnet server up at initialization (TEL0:)
    [HKEY_LOCAL_MACHINE\Services\TELNETD]
       "ServiceContext"=dword:1
       "FriendlyName"="Telnet"
       "Dll"="TELNETD.Dll"
       "Order"=dword:9
       "Keep"=dword:1
       "Prefix"="TEL"
       "Index"=dword:0

    ; Used when creating a new telnet session (TEL(1-9):)
    [HKEY_LOCAL_MACHINE\Services\TELNETD\NewSession]
       "ServiceContext"=dword:1
       "FriendlyName"="Telnet"
       "Dll"="TELNETD.Dll"
       "Order"=dword:9
       "Keep"=dword:1
       "Prefix"="TEL"
    ;  "Index"=dword:0 ; Set by telnet server dynamically


    ; @CESYSGEN IF CE_MODULES_EVENTLOG
    ; @CESYSGEN ENDIF CE_MODULES_EVENTLOG
      
    ; @CESYSGEN ENDIF SERVERS_MODULES_TELNETD

    My goal is to be able to debug application with VS2005/2008 using ethernet connection.  My board is headless, so I think I need to use telnet to execute CoreCon programs from command prompt before connecting Visual Studio to the target.  Please let me know if I am missing any registry settings.  I appreciate any suggestions that you can give me regarding application debugging.

    Luan

  • Try to add the below registry settings and check once.

    [HKEY_LOCAL_MACHINE\COMM\TELNETD]

    "UseAuthentication"=dword:0   ;Authentication is not required

    "IsEnabled"=dword:1                            ;Set to 1 to enable Telnet Server and to 0 to disable.

    Regards,

    GSR

  • Hi,

    Please let me know if you are able to fix it or facing any other issue?

    Regards,

    GSR

  • Hi GSR,

    Thank you very much for asking.  I checked the registry and it already has

    [HKEY_LOCAL_MACHINE\COMM\TELNETD]
    "UseAuthentication"=dword:0   ;Authentication is not required
    "IsEnabled"=dword:1                            ;Set to 1 to enable Telnet Server and to 0 to disable.

    so I checked out the OMAP3530 EVM.  The EVM has EC7 OS image built with KITL disabled and NDIS SMSC driver included.  After the EVM booting to the desktop, I sucessfully ping and telnet the EVM from my development PC.

    I am doing the same for my custom board but for some reason both ping and telnet do not work with CE7.  With CE6, I was able to ping but not telnet.

    The only difference between my board and the EVM is that my board uses LAN9221 for the Ethernet Controller instead of LAN9220 as on the EVM.  Since I am able to download the image through the Ethernet so I don't think it is a hardware problem.  I am clueless at this time and would appreciate any pointers from you.

    Thanks again,

    Luan

  • Hi Luan,

    Did you do the diff between both the kernel images by opening them in Visual Studio.

    If there are any differences w.r.t. registry or any missing components you can easily identify by doing so.

    Regards,

    GSR