RE: TFTP I/O Error

["Jim Eastman" <Jim.Eastman@pro-dex.com>]

Eric,

 

These are the startup messages I received.

 

-----------------------------------------

Welcome to rtems-4.10.0(PowerPC/Generic (classic FPU)/mvme5500) on MVME5500-0163

-----------------------------------------

Now BSP_mem_size = 0x1FE00000

Marvell GT64260B (Discovery I) hostbridge detected at bus0 slot0

BSP unlisted vendor, Bus0 Slot10 DeviceID 0x263388

TUNDRA PCI-VME bridge detected at bus1 slot0

Marvell GT64260B (Discovery I) hostbridge detected at bus8 slot0

BSP unlisted vendor, Bus8 Slot10 DeviceID 0x10088086

Universe II PCI-VME bridge detected at 0x82000000, IRQ 12

Universe Master Ports:

Port  VME-Addr   Size       PCI-Adrs   Mode:

0:    0x20000000 0x0E000000 0x90000000 A32, D64 [MBLT], Dat, Sup

1:    0x00000000 0x00FF0000 0x9F000000 A24, D64 [MBLT], Dat, Sup

2:    0x00000000 0x00010000 0x9FFF0000 A16, D64, Dat, Sup

Universe Slave Ports:

Port  VME-Addr   Size       PCI-Adrs   Mode:

0:    0x90000000 0x1FE00000 0x00000000 A32, Pgm, Dat, Sup, Usr, PWEN, PREN

Overriding main IRQ line PCI info with 76

Registering /dev/console as minor 0 (==/dev/ttyS0)

 

***** Initializing network *****

Startup.

Attaching MVME5500 1GHz NIC1

RTEMS-mvme5500 BSP Copyright (c) 2004,2005,2008, Brookhaven National Lab., Shuchen Kate Feng

***** Initializing TFTP *****

 

***** Starting EPICS application *****

Can't open /TFTP/10.80.60.112/epics/mvme5500/st.cmd: I/O error

 

 

 

And here is what netstat 2 shows:

 

************ INTERFACE STATISTICS ************

***** wmG1 *****

Ethernet Address: 00:01:AF:30:50:77

Address:10.80.60.142    Broadcast Address:10.80.255.255   Net mask:255.255.0.0

Flags: Up Broadcast Running Simplex Multicast

Send queue limit:50   length:0    Dropped:0

    Ghost Interrupts:0

       Rx Interrupts:460

     Receive Packets:25

     Receive Overrun:0

     Receive  errors:0

   Rx sequence error:0

      Rx /C/ ordered:0

    Rx Length Errors:0

       Tx Interrupts:16

   Transmitt Packets:0

   Transmitt  errors:0

         Active Txqs:0

          collisions:0

          Crc Errors:0

  Link Status Change:1

***** lo0 *****

Address:127.0.0.1       Net mask:255.0.0.0

Flags: Up Loopback Running Multicast

Send queue limit:50   length:0    Dropped:0

 

************ MBUF STATISTICS ************

mbufs:8192    clusters: 512    free: 256

drops:   0       waits:   0  drains:   0

      free:7935          data:257         header:0           socket:0

       pcb:0           rtable:0           htable:0           atable:0

    soname:0           soopts:0           ftable:0           rights:0

    ifaddr:0          control:0          oobdata:0

 

Destination     Gateway/Mask/Hw    Flags     Refs     Use Expire Interface

default         10.80.60.20        UGS         1        0      0 wmG1

10.80.0.0       255.255.0.0        U           0        0      1 wmG1

10.80.60.20     00:90:7F:22:83:48  UHL         2        0   1571 wmG1

10.80.60.142    00:01:AF:30:50:77  UHL         0       10      0 lo0

71.245.107.83   10.80.60.20        UGH         1        7      0 wmG1

127.0.0.1       127.0.0.1          UH          0        0      0 lo0

************ IP Statistics ************

             total packets received          96

  packets rcvd for unreachable dest           6

 datagrams delivered to upper level          90

    total ip packets generated here          17

 

************ ICMP Statistics ************

              Calls to icmp_error()          10

                 ICMP panic avoided          10

 

************ UDP Statistics ************

                total input packets          90

                  no socket on port          10

     of above, arrived as broadcast          73

               total output packets          17

 

************ TCP Statistics ************

 

 

Thanks!

 

Regards,

Jim Eastman

 

 

---

From: Eric Norum [mailto:wenorum@lbl.gov]
Sent: 18 February 2011 17:36
To: Jim Eastman
Cc: EPICS Tech Talk
Subject: Re: TFTP I/O Error

 

What does  'netstat 2' show?  Does it show the right network configuration?

Also, could you post more of the startup messages?  That might give a little more insight.

 

On Feb 18, 2011, at 4:57 PM, Jim Eastman wrote:

Hello all,

 

I'm trying to get an EPICS test app going on RTEMS on an MVME5500 board, and I'm encountering a problem when trying to get files from a TFTP server.

 

"Can't open /TFTP/10.80.60.112/epics/mvme5500/st.cmd: I/O error"

 

My TFTP server logs don't show any attempt at this connection.

 

I'm using RTEMS 4.10 and EPICS 3.14.12. I am building the apps with the -DOMIT_NFS_SUPPORT flag set in a MINGW environment on a Windows 7 machine with RTEMS-mvme5500 set as the target arch.

 

I am also able to download that file (and others) from the tftp server while still in the MOTLOAD prompt on the mvme board.

 

I have the following GEVs set on the mvme board:

 

mot-/dev/enet1-cipa=10.80.60.142

mot-/dev/enet1-sipa=10.80.60.112

mot-/dev/enet1-snma=255.255.0.0

mot-/dev/enet1-gipa=10.80.60.20

rtems-client-name=mvme5500

epics-script=epics/mvme5500/st.cmd

rtems-dns-server=10.80.60.12

rtems-dns-domainname=pro-dex.com

epics-ntpserver=71.245.107.83

 

The networking when the application loads seems to be working fine, as I'm able to get time from the NTP server.

 

I'm not running a BOOTP server, and so I hardcoded these network parameters into bsp_driver_config and rtems_bsdnet_config  in rtems_netconfig.c

 

Any assistance in this problem would be greatly appreciated. Thank you very much.

 

Regards,

Jim Eastman

This e-mail and any attachment(s) are from Pro-Dex, Inc. and may contain information that is confidential or privileged. If you are not the intended recipient, do not read, copy or distribute the e-mail or any attachments. Instead, please notify the sender at the phone number indicated above and delete the e-mail and any attachments. Thank you.

 

-- 
Eric Norum
wenorum@lbl.gov

 

This e-mail and any attachment(s) are from Pro-Dex, Inc. and may contain information that is confidential or privileged. If you are not the intended recipient, do not read, copy or distribute the e-mail or any attachments. Instead, please notify the sender at the phone number indicated above and delete the e-mail and any attachments. Thank you.