Go to previous topic
Go to next topic
Last Post 16 Aug 2004 08:08 PM by  scottpitcher
Problems with LOLO Boot scripts that use network interface
 1 Replies
Author Messages
JadePhoenix
New Member
New Member
Posts:


--
20 Jul 2004 02:12 AM
    Greetings,

    while testing the "LOLO boot script" feature i seem to have problems to get remote boot (image via TFTP) to work ...

    I doesnt matter if i use static or dynamic (DHCP) config.

    Quote:

    echo "LOLO ifconfig sm0 198.120.75.7 255.255.255.0 198.120.75.252 ; ifconfig sm0 up ; exit\n" /dev/serial_eeprom


    Quote:

    losh> Àlosh> ifconfig sm0 198.120.75.7 255.255.255.0 198.120.75.252 ; ifconfig
    sm0 up ; exit
    MAC Address: 00:08:ee:00:50:74
    MAC Address: 00:08:ee:00:50:74

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

    © Copyright 2002-2003, Logic Product Development, Inc.
    All Rights Reserved.
    Version 1.2.0
    *****************************************************************

    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> ifconfig

    sm0: up 100M full-duplex (425)
    sm0: mac: 0:8:ee:0:50:74 ip: 198.120.75.7
    mask: 255.255.255.0 gw: 198.120.75.252
    losh> ping 198.120.75.6
    Pinging 198.120.75.6 1 times from 198.120.75.7
    Timeout Trying to Allocate for Send
    MIR_REG: 0x4
    INTERRUPT_REG: 0xb107
    CPLD MASK REG: 0xe
    Was allocating 0x30 bytes
    losh> ping 198.120.75.6
    Pinging 198.120.75.6 1 times from 198.120.75.7
    Timeout Trying to Allocate for Send
    MIR_REG: 0x4
    INTERRUPT_REG: 0xb117
    CPLD MASK REG: 0xe
    Was allocating 0x30 bytes
    losh> ping 198.120.75.6
    Pinging 198.120.75.6 1 times from 198.120.75.7
    Timeout Trying to Allocate for Send
    MIR_REG: 0x4
    INTERRUPT_REG: 0xb117
    CPLD MASK REG: 0xe
    Was allocating 0x30 bytes
    losh> ping 127.0.0.1
    Pinging 127.0.0.1 1 times from 198.120.75.7
    Timeout Trying to Allocate for Send
    MIR_REG: 0x4
    INTERRUPT_REG: 0xb117
    CPLD MASK REG: 0xe
    Was allocating 0x30 bytes


    I even put some delays after "ifconfig" with "sleep" or used explicit "ifconfig sm0 up" but the network interface doesnt work.
    Either i get errors (timeout) or the whole LOLO thing crashed with fatal error (occurred sometimes).

    When i cleared LOLO script using " " /dev/serial_eeprom and use manual method like "ifconfig sm0 dhcp" or static one all works fine.
    I can ping hosts and download images from tftp server.

    I suspect there might be some early initialization/race condition problems?
    I use latest ver 1.2.0.

    Has someone gotten automatic TFTP boot via LOLO to work?
    Please post a script if so.

    Thanks in advance
    scottpitcher
    New Member
    New Member
    Posts:


    --
    16 Aug 2004 08:08 PM
    Quote:


    while testing the "LOLO boot script" feature i seem to have problems to get remote boot (image via TFTP) to work ...

    I doesnt matter if i use static or dynamic (DHCP) config.


    I use the following command line:

    ifconfig sm0 192.168.3.10 255.255.255.0 192.168.3.1 ; ifconfig sm0 up; load elf /tftp/192.168.3.1:/vmlinux; exec video=pl110 console=ttyAM1,115200 noinitrd root=/dev/nfs rw nfsroot=192.168.3.1:/tftpboot/rootfs ip=192.168.3.10


    This seems to work reliably.

    I have however had a few inexplicable failures. A few weeks ago we had a power failure for a few minutes. For the remainder of the afternoon the board refused to use the network interface, and any attempt to engage in activity on this interface would result in a lolo crash and register dump. Eventually a 10 minute power cycle brought the board back to normal. I was not able to reproduce this fault.

    I am more wary of lolo now. I was using dhcp for a while and generally it works but stick with static now.


    Regards,
    Scott

    Forums NXP SOMs and Development Kits LH79520 Card Engine and Development Kit
    ---