Re: Error using rtems network legacy on MVME3100

2023-06-26 Thread Joel Sherrill 
Hi


The message "sec1: (tsec ethernet) Your application has not enough mbuf
clusters configured for this driver." would normally indicate that you
don't have enough mbuf memory configured. See

https://git.rtems.org/network-demos/tree/networkconfig-mpc8313erdb.h

around line 88 for the parameters you likely need to increase.

If there is a minimum, it is in the network driver itself somewhere. Should
be under ./bsps/powerpc/mvme3100/

If this is a GigE interface, it is sometimes surprising how much buffering
you need.

--joel

On Thu, Jun 22, 2023 at 4:21 PM Zainab Olalekan  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   :    Hz
> Core Complex Bus (CCB) Clock Freq:  0 Hz
> CPU Clock Freq: 13332 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:00x1057-0x0008:  0x0006 0x20b0 0x8000 0x   0
> ->   0 (=0x00)
>   0:0x11:00x10e3-0x0148:  0x0146 0x02b0 0x8014 0x   1
> ->   0 (=0x00)
>   0:0x12:00x10b5-0x6520:  0x0147 0x02b0 0x 0x   0
> ->   0 (=0x00)
>   0:0x14:00x1095-0x3124:  0x01c7 0x02b0 0x8034 0x   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 4166 Hz
> MSR is 0x1000, TCR 0x0400
> -
> Exit from bspstart
> Tundra Tsi148 PCI-VME bridge detected at 0x8010, IRQ 0
> Tsi148 Outbound Ports:
> Port  VME-Addr   Size   PCI-Adrs   Mode:
> 0:0x2000 0x0e00 0xc000 A32, SUP, D32, SCT
> 1:0x 0x00ff 0xcf00 A24, SUP, D32, SCT
> 2:0x 0x0001 0xcfff A16, SUP, D32, SCT
> 7:0x 0x0100 0xce00 CSR, SUP, D32, SCT
> Tsi148 Inbound Ports:
> Port  VME-Addr   Size   PCI-Adrs   Mode:
> 0:0xc000 0x1000 0x 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@rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: Error using rtems network legacy on MVME3100

2023-06-26 Thread 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  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   :    Hz
> Core Complex Bus (CCB) Clock Freq:  0 Hz
> CPU Clock Freq: 13332 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:00x1057-0x0008:  0x0006 0x20b0 0x8000 0x   0 ->  
>  0 (=0x00)
>   0:0x11:00x10e3-0x0148:  0x0146 0x02b0 0x8014 0x   1 ->  
>  0 (=0x00)
>   0:0x12:00x10b5-0x6520:  0x0147 0x02b0 0x 0x   0 ->  
>  0 (=0x00)
>   0:0x14:00x1095-0x3124:  0x01c7 0x02b0 0x8034 0x   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 4166 Hz
> MSR is 0x1000, TCR 0x0400
> -
> Exit from bspstart
> Tundra Tsi148 PCI-VME bridge detected at 0x8010, IRQ 0
> Tsi148 Outbound Ports:
> Port  VME-Addr   Size   PCI-Adrs   Mode:
> 0:0x2000 0x0e00 0xc000 A32, SUP, D32, SCT
> 1:0x 0x00ff 0xcf00 A24, SUP, D32, SCT
> 2:0x 0x0001 0xcfff A16, SUP, D32, SCT
> 7:0x 0x0100 0xce00 CSR, SUP, D32, SCT
> Tsi148 Inbound Ports:
> Port  VME-Addr   Size   PCI-Adrs   Mode:
> 0:0xc000 0x1000 0x 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@rtems.org
> http://lists.rtems.org/mailman/listinfo/users


___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

Re: [EXTERNAL] Re: Error using rtems network legacy on MVME3100

2023-06-26 Thread Zainab Olalekan 
Increasing the size of the allocated memory worked. Thank you!

On Jun 23, 2023 08:20, Joel Sherrill  wrote:
Hi


The message "sec1: (tsec ethernet) Your application has not enough mbuf 
clusters configured for this driver." would normally indicate that you don't 
have enough mbuf memory configured. See

https://git.rtems.org/network-demos/tree/networkconfig-mpc8313erdb.h

around line 88 for the parameters you likely need to increase.

If there is a minimum, it is in the network driver itself somewhere. Should be 
under ./bsps/powerpc/mvme3100/

If this is a GigE interface, it is sometimes surprising how much buffering you 
need.

--joel

On Thu, Jun 22, 2023 at 4:21 PM Zainab Olalekan 
mailto:zolal...@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   :    Hz
Core Complex Bus (CCB) Clock Freq:  0 Hz
CPU Clock Freq: 13332 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:00x1057-0x0008:  0x0006 0x20b0 0x8000 0x   0 ->   
0 (=0x00)
  0:0x11:00x10e3-0x0148:  0x0146 0x02b0 0x8014 0x   1 ->   
0 (=0x00)
  0:0x12:00x10b5-0x6520:  0x0147 0x02b0 0x 0x   0 ->   
0 (=0x00)
  0:0x14:00x1095-0x3124:  0x01c7 0x02b0 0x8034 0x   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 4166 Hz
MSR is 0x1000, TCR 0x0400
-
Exit from bspstart
Tundra Tsi148 PCI-VME bridge detected at 0x8010, IRQ 0
Tsi148 Outbound Ports:
Port  VME-Addr   Size   PCI-Adrs   Mode:
0:0x2000 0x0e00 0xc000 A32, SUP, D32, SCT
1:0x 0x00ff 0xcf00 A24, SUP, D32, SCT
2:0x 0x0001 0xcfff A16, SUP, D32, SCT
7:0x 0x0100 0xce00 CSR, SUP, D32, SCT
Tsi148 Inbound Ports:
Port  VME-Addr   Size   PCI-Adrs   Mode:
0:0xc000 0x1000 0x 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@rtems.org
http://lists.rtems.org/mailman/listinfo/users


On Jun 23, 2023 08:20, Joel Sherrill  wrote:
Hi


The message "sec1: (tsec ethernet) Your application has not enough mbuf 
clusters configured for this driver." would normally indicate that you don't 
have enough mbuf memory configured. See

https://git.rtems.org/network-demos/tree/networkconfig-mpc8313erdb.h

around line 88 for the parameters you likely need to increase.

If there is a minimum, it is in the network driver itself somewhere. Should be 
under ./bsps/powerpc/mvme3100/

If this is a GigE interface, it is sometimes surprising how much buffering you 
need.

--joel

On Thu, Jun 22, 2023 at 4:21 PM Zainab Olalekan 
mailto:zolal...@uccs.edu>> wrote:
Hi everyone,

I am having issues running rtems network legacy on the MVME3100