Error using rtems network legacy on MVME3100

[Heinz Junkes]

For the Legacy stack you have to define MBUFS in rtems_bsdnet_config.

Example from EPICS:


os/CONFIG.Common.RTEMS-mvme3100:ARCH_DEP_CFLAGS += -DRTEMS_NETWORK_CONFIG_MBUF_SPACE=2048


struct rtems_bsdnet_config rtems_bsdnet_config = {
    FIRST_DRIVER_CONFIG,   /* Link to next interface */
    MY_DO_BOOTP,           /* How to find network config */
    10,                    /* If 0 then the network daemons will run at a */
                           /*   priority just less than the lowest-priority */
                           /*   EPICS scan thread. */
                           /* If non-zero then the network daemons will run */
                           /*   at this *RTEMS* priority */
    RTEMS_NETWORK_CONFIG_MBUF_SPACE*1024,
    RTEMS_NETWORK_CONFIG_CLUSTER_SPACE*1024,
    NULL,                  /* Host name */
    MY_DOMAINNAME,         /* Domain name */
};

HTH,
Heinz



> On 22. Jun 2023, at 23:21, Zainab Olalekan <zolaleka at uccs.edu> wrote:
> 
> Hi everyone, 
> 
> I am having issues running rtems network legacy on the MVME3100 board. The configuration setup and output are below.  Could you advise on how to resolve this problem? Thank you.
> 
> 
> NET_CFG_IFACE =tse1
> NET_CFG_BOOT_PROT = dhcp
> NET_CFG_SELF_IP = xx.xx.xx.xx
> NET_CFG_NETMASK = 255.xx.xx.xx
> NET_CFG_MAC_ADDR = xx:xx:xx:xx:xx:xx
> NET_CFG_GATEWAY_IP = 0.0.0.0
> NET_CFG_DOMAINNAME = localnet
> 
> 
> Welcome to rtems-6.0.0 (PowerPC/Generic (no FPU)/mvme3100)
> BSP: mvme3100, CVS Release ($Name$)
> CPU 0x8020 - rev 0x20
> Additionnal boot options are H
> Initial system stack at 117070
> Going to start PCI buses scanning and initialization
> Board Type: MVME3100-1152 (S/N E1726C0)
> External (=PCI Bus) Clock Freq   :   66666666 Hz
> Core Complex Bus (CCB) Clock Freq:  333333330 Hz
> CPU Clock Freq:                     133333332 Hz
> Ethernet 0                  EC:9E:CD:19:B3:53
> Ethernet 1                  EC:9E:CD:19:B3:54
> Ethernet 2                  EC:9E:CD:19:B3:55
> Number of PCI buses found is : 2
> BUS:SLOT:FUN  VENDOR-DEV_ID: COMMAND STATUS BASE_ADDR0 BASE_ADDR1 IRQ_PIN -> IRQ_LINE
>   0:0x00:0    0x1057-0x0008:  0x0006 0x20b0 0x80000000 0x00000000       0 ->   0 (=0x00)
>   0:0x11:0    0x10e3-0x0148:  0x0146 0x02b0 0x80100004 0x00000000       1 ->   0 (=0x00)
>   0:0x12:0    0x10b5-0x6520:  0x0147 0x02b0 0x00000000 0x00000000       0 ->   0 (=0x00)
>   0:0x14:0    0x1095-0x3124:  0x01c7 0x02b0 0x80300004 0x00000000       1 ->   2 (=0x02)
> Memory:                             268435456 bytes
> Cleared PCI errors: pci_stat was 0x20b0
> OpenPIC Version 1.2 (1 CPUs and 56 IRQ sources) at 0x3775135744
> OpenPIC Vendor 0 (Unknown), Device 0 (Unknown), Stepping 0
> OpenPIC timer frequency is 41666666 Hz
> MSR is 0x00001000, TCR 0x04000000
> -----------------------------------------
> Exit from bspstart
> Tundra Tsi148 PCI-VME bridge detected at 0x80100000, IRQ 0
> Tsi148 Outbound Ports:
> Port  VME-Addr   Size       PCI-Adrs   Mode:
> 0:    0x20000000 0x0e000000 0xc0000000 A32, SUP, D32, SCT
> 1:    0x00000000 0x00ff0000 0xcf000000 A24, SUP, D32, SCT
> 2:    0x00000000 0x00010000 0xcfff0000 A16, SUP, D32, SCT
> 7:    0x00000000 0x01000000 0xce000000 CSR, SUP, D32, SCT
> Tsi148 Inbound Ports:
> Port  VME-Addr   Size       PCI-Adrs   Mode:
> 0:    0xc0000000 0x10000000 0x00000000 A32, PGM, DAT, SUP, USR, MBLT, BLT
> vmeTsi148 IRQ manager: looking for registers on VME...
> Trying to find CSR on VME...
> vmeTsi148 - IRQ manager using VME CSR to flush FIFO
> libi2c: Claiming driver slot failed (rtems status code 5)
> Initializing I2C library failed
> Registering /dev/console as minor 0 (==/dev/ttyS0)
> 
> 
> *** BEGIN OF TEST TELNETD 2 ***
> *** TEST VERSION: 6.0.0.b2967081e5daa673141d714a2e53280898dce566
> *** TEST STATE: EXPECTED_PASS
> *** TEST BUILD: RTEMS_POSIX_API
> *** TEST TOOLS: 12.2.1 20230425 (RTEMS 6, RSB 3c8c2ce38a8fe0a622f88fb3422d1f8fa609609b, Newlib 9ae9eef)
> tsec1: (tsec ethernet) Your application has not enough mbuf clusters
>                       configured for this driver.
> Can't bring tse1 up: No such device or address
>  an't set default route: Network is
>  unr[e aRchTaEblMe
> c./.S. /stehsutsuittdeso/wtelnent d02]/init.
>  : 6R3T rv E=M= 0S
>  version: 6.0.0.b2967081e5daa673141d714a2e53280898dce566
> RTEMS tools: 12.2.1 20230425 (RTEMS 6, RSB 3c8c2ce38a8fe0a622f88fb3422d1f8fa609609b, Newlib 9ae9eef)
> executing thread ID: 0x0a010001
> executing thread name: UI1
> 
> 
> 
> 
> Best Regards,
> Zainab Olalekan
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users