Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 24 Nov 2003 07:48 AM by  mikee@logicpd.com
Trouble Building_a_Webserver_with_the_LoCE_BSP.pdf
 5 Replies
Sort:
You are not authorized to post a reply.
Author Messages
cborax
New Member
New Member
Posts:


--
09 Nov 2003 07:02 PM
    Greetings,

    Has anyone had trouble with the white paper "Building_a_Webserver_with_the_LoCE_BSP.pdf" on the SDK-LH7A400-10 .

    The "losh> ifconfig sm0 dhcp" does work and the board does respond to a ping before I load CE.
    Once CE.NET 4.20 boots the board won't respond to a ping or my HTML browser .

    TELNETD won't start either.

    The only discrepancy I noticed is that
    losh> ifconfig reports :sm0: up 100M half-duplex (415)
    but the figure 18 in the pdf shows 100Mbits full-duplex

    Any suggestions?

    Thanks in advance,
    Craig
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    12 Nov 2003 09:55 AM
    cborax,

    Hello and thanks for your post. Currently, we are not aware of anyone else having difficulty building this project. We had several people inside Logic follow the directions in an attempt to make sure that we didn't miss any steps. However, that doesn't mean that we didn't.

    Could you please post a few more details about what you are seeing once the kernel comes up? Perhaps some screen shots of the serial-port output. I'd also like to know what components you included in your image and what string you passed to LoCE to boot the kernel.

    Thanks,
    --mikee
    cborax
    New Member
    New Member
    Posts:


    --
    15 Nov 2003 10:27 PM
    I have Windows CE.Net 4.2 and installed both the LOCE_A400_Beta_001 and the 002 .

    Here is the serial output from the session:

    *****************************************************************
    LogicLoader

    (c) Copyright 2002-2003, Logic Product Development, Inc.
    All Rights Reserved.
    Version 1.2.3
    *****************************************************************

    Available commands:
    load - download a binary image of type 'elf', or 'srec'
    burn - burns the already-loaded image into flash device 'device'
    erase - erases 'device' from start_address for length bytes
    jump - jump to a loaded image, or [address]
    exec - disable cache & ints, then jump to a loaded OS, or to [addr]
    source - execute a series of losh commands stored in <filename>
    w - write memory [of specified width] at addr
    x - examine memory with [width][format] at an addr for a [len]
    date - display the number of seconds since boot
    info - print information about: version, arch, mem, net, cpu
    help - print help for a single command or a group of commands.
    losh> bootme &
    Blosh> OOTME: no active network interfaces. Try ifconfig

    losh> ifconfig sm0 dhcp
    MAC Address: 00:08:ee:00:14:7e
    MAC Address: 00:08:ee:00:14:7e
    Starting DHCP on sm0
    losh> ifconfig

    sm0: up 100M half-duplex (415)
    sm0: mac: 0:8:ee:0:14:7e ip: 192.168.1.106
    mask: 255.255.255.0 gw: 192.168.1.1
    losh> bootme &
    losh>
    Device's name is LoCE_5246.
    Sent BOOTME
    Sent BOOTME
    Sent BOOTME
    Sent BOOTME
    Got a response from a host ip: 192.168.1.102 port: 3107
    Connecting to Platform Builder
    R

    image launch addr: 0xc00e1000
    Verifying checksums: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
    Checksums good.
    BOOTME: Got jump command

    losh> source /dev/serial_eeprom
    losh> exec dbg_serial:A400_UART:dbg_enet:91C111:dbg_enet_base:0x70000000:rtc:rtc
    _a400_int:share_eth:1
    kernel cmdline: 'dbg_serial:A400_UART:dbg_enet:91C111:dbg_enet_base:0x70000000:r
    tc:rtc_a400_int:share_eth:1:kitl:true:ip_addr:192.168.1.106' at c00c0100
    disabling mmu.
    LoCE start
    link_for_flash: 0
    Debug serial initialized. Using driver A400_UART
    Windows CE Kernel for ARM (Thumb Enabled) Built on Jul 25 2003 at 11:54:05
    ProcessorType=0922 Revision=0
    sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 800e1220


    ===================================================================

    WinCE firmware init (LoCE).
    Kernel Arguments: dbg_serial:A400_UART:dbg_enet:91C111:dbg_enet_base:0x70000000:
    rtc:rtc_a400_int:share_eth:1:kitl:true:ip_addr:192.168.1.106.

    image_size: 0xF00000
    ram_size: 0xC00000
    link_for_flash: 0

    ===================================================================

    Initializing interrupts.
    Interrupt initialization complete.
    Initializing system-tick.
    System-tick initialized.
    RTC initialized. Using driver rtc_a400_int
    Multiple XIP regions not defined or fixup failed.
    Initializing KITL.
    Remote host present.
    Debug enet initialized. Using driver 91C111
    Debug enet base read as 0x70000000
    Debug enet base mapped to virtual address 0xBFE00000.
    hooking platform interrupts... done
    OEMKitlInit()
    SmSC Ethernet controller detected: 0xBFE00000
    MAC Address: 00:08:EE:00:14:7E
    91C111: 100 Mbits half-duplex.
    +pckt_list_init(): 0x80002000 : 0x00002800

    Device Name: LoCE_5246, IP: 192.168.1.106, Port: 981

    KITL Buffers at 0x80005000 len 0x20000
    KITL Interrupt using SysIntr: 16.
    share_dbg_enet read as 0x00000001
    Initializing VBridge.
    VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
    Tx buffer [0xA102F0C0] to [0xA10330C0].
    Rx buffer [0xA102B0A0] to [0xA102F0A0].
    VBridge:: NK add MAC: [0-8-EE-0-14-7E]
    VBridge initialized.
    KITL Ethernet transport initialized
    Host connected.
    Host IP: 192.168.1.102, port 3106
    KeyIndex 0 = -1
    KeyIndex 1 = -1
    KeyIndex 2 = -1
    KeyIndex 3 = -1
    KeyIndex 4 = -1
    KeyIndex 5 = -4194305
    KeyIndex 6 = -4194305
    KeyIndex 7 = -1
    +KITLRegisterDfltClient, service:0
    +KITLRegisterDfltClient, service:1
    KITLGlobalState == 0x61
    KITL initialized.
    Firmware initialization complete.

    driver globals at 0x80000000.
    Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0
    ProcessAdminMsg: Receive Config message for service DBGMSG
    ProcessAdminMsg: Receive Config message for service PPSH
    ProcessAdminMsg: Receive Config message for service DBGMSG
    ProcessAdminMsg: Receive Config message for service PPSH
    ProcessAdminMsg: Receive Config message for service DBGMSG
    ARMInit done.
    +KITLRegisterDfltClient, service:2
    ProcessAdminMsg: Receive Config message for service KDBG
    ProcessAdminMsg: Receive Config message for service KDBG
    KITL: Leaving polling mode...
    KITL Checking client registrations
    +RegisterClientPart2: Id 0x00000000
    KITL Timer thread started, (hTh: 0x01BFFF86, pTh: 0x81BFCAF8)
    -RegisterClientPart2
    +RegisterClientPart2: Id 0x00000001
    -RegisterClientPart2
    KITL Creating IST
    KITL Interrupt thread started (hTh: 0xC1BEF9F2, pTh: 0x81BEF7B4), using SYSINTR
    16
    Enabling adapter ints...
    Enabling debug ethernet interrupts.
    Enabling SmSC 91C111 receive interrupt.[list=][/list][/list]
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    16 Nov 2003 09:06 PM
    Craig,

    It looks like your system is coming up just fine. From the serial output that you have listed, the Windows CE kernel is up and running and should be found at IP address: 192.168.1.106.

    Can you ping the device with your desktop at that address?

    Also, did you use the Remote Registry Editor tool to set the TELNETD registry entries as outlined in the white paper?

    Do you have an active connection through Platform Builder? By this I mean, are you seeing messages from the device show up in PB's output window, can you see the threads executing on the system, start programs, etc.?

    Regards,
    --mikee
    Anonymous
    Posts:


    --
    18 Nov 2003 09:45 AM
    Hello Craig,

    I've built the webserver here and was able to ping and telnet to it.

    Please try rebuilding the platform following Mr. Erickson's "Building a Web-Server with the LoCE BSP" White Paper. Make a list of the steps taken and post them to the discussion group. Perhaps a necessary instruction is unclear. If that is the case we will work to clarify.

    Best Regards,
    Andrew Wawra
    Logic Product Development
    mikee@logicpd.com
    New Member
    New Member
    Posts:


    --
    24 Nov 2003 07:48 AM
    Craig and I resolved this problem. For completion, I want to post the details publicly in case anyone else runs into the same trouble.

    The problem that Craig ran into stemmed from a bad assumption on my part concerning the behavior of common DHCP servers.

    Here at Logic, our DHCP server tends to always give the same IP address to a given MAC address. This means that when the LogicLoader (LoLo) initiates a DHCP session, it will be served IP address xx.xx.xx.xx. When the Windows CE kernel boots and initiates another DHCP session, it gets served the exact same IP address.

    When I wrote this document, I stated that users can look at the serial output from LoLo and then access their device from that IP address.

    In Craig's case, his DHCP server gives the LogicLoader IP address xx.xx.xx.xx. However, it gives the Windows CE kernel address yy.yy.yy.yy. Therefore, the output shown on the serial port is incorrect.

    Craig rightly deduced that he could use the Remote Registry Editor to view the Windows CE registry and figure out what IP address the CE kernel was using. Once he did that, he was able to successfully complete the rest of the steps outline in the whitepaper.

    We will update the whitepaper to correct this assumption and detail the usage of the Remote Registry Editor.

    Best regards,
    --mikee
    You are not authorized to post a reply.