Hi Heinz,
Thanks for the hardware tests. It's great to see the tests running
successfully on hardware!
Best regards,
Vijay
On Wed, Mar 3, 2021 at 1:34 PM junkes <junkes at fhi-berlin.mpg.de> wrote:
>
> Hallo Vijay,
> You don't have to apologize. I am glad that you are doing this. And now
> it works perfectly.
>
> Even on the Hardware:
>
> Copyright(C)2008-2009,Emerson Network Power-Embedded Computing,Inc.
> All Rights Reserved
> Copyright Motorola Inc. 1999-2007, All Rights Reserved
> MOTLoad RTOS Version 2.0, PAL Version 2.3 RM01
> Fri Jan 23 14:47:54 MST 2009
>
> MPU-Type =MPC74x7
> MPU-Int Clock Speed =1266MHz
> MPU-Ext Clock Speed =133MHz
> MPU-Int Cache(L2) Enabled, 512KB, L2CR =C0000000
> MPU-Ext Cache(L3) Enabled, 2MB, 211MHz, L3CR =DC026300
>
> PCI bus instance 0 =64 bit, 133 Mhz, PCI-X
> PCI bus instance 1 =64 bit, PCI
>
> Reset/Boot Vector =Flash1
>
> Local Memory Found =20000000 (&536870912)
> User Download Buffer =006B7000:008B6FFF
>
> MVME6100> tftpGet -s141.14.128.9 -c141.14.128.12 -a04000000 -fticker.exe
> Network Loading from: /dev/enet0
> Loading File: ticker.exe
> Load Address: 04000000
> Download Buffer Size = User Defined
>
> Client IP Address = 141.14.128.12
> Server IP Address = 141.14.128.9
> Gateway IP Address = 141.14.128.253
> Subnet IP Address Mask = 255.255.255.0
>
> Network File Load in Progress...
>
> Bytes Received =&252200, Bytes Loaded =&252200
> Bytes/Second =&252200, Elapsed Time =1 Second(s)
> -----------------------------------------
> config addr is 0xf1000cf8
> config data is 0xf1000cfc
> Welcome to RTEMS rtems-6.0.0 (PowerPC/Generic (classic FPU)/beatnik)
> CPU: MPC7457
> Board Type: MVME6100-0163 (S/N E173D27)
> Bus Clock Freq: 133333333 Hz
> CPU Clock Freq: 1266666654 Hz
> Memory: 536870912 bytes
> -----------------------------------------
> Now BSP_mem_size = 0x1fe00000
> Configuration.work_space_size = 2120
> Page table setup finished; will activate it NOW...
> Going to start PCI buses scanning and initialization
> Number of PCI buses found is : 3
> MSR 0x2003032
> Exit from bspstart
> unable to find the universe in pci config space
> Tundra Tsi148 PCI-VME bridge detected at 0x81100000, IRQ 84
> Tsi148 Outbound Ports:
> Port VME-Addr Size PCI-Adrs Mode:
> 0: 0x20000000 0x0e000000 0x90000000 A32, SUP, D32, SCT
> 1: 0x00000000 0x00ff0000 0x9f000000 A24, SUP, D32, SCT
> 2: 0x00000000 0x00010000 0x9fff0000 A16, SUP, D32, SCT
> 7: 0x00000000 0x01000000 0x9e000000 CSR, SUP, D32, SCT
> Tsi148 Inbound Ports:
> Port VME-Addr Size PCI-Adrs Mode:
> 0: 0x90000000 0x1fe00000 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
>
>
> *** BEGIN OF TEST NETWORKING 1 ***
> *** TEST VERSION: 6.0.0.4fa5e77ba3a00f8ac61251b6c049c98102583d57
> *** TEST STATE: EXPECTED_PASS
> *** TEST BUILD: RTEMS_POSIX_API
> *** TEST TOOLS: 10.2.1 20210205 (RTEMS 6, RSB
> 61dcadee0825867ebe51f9f367430ef75b8fe9c0, Newlib d4a756f)
> Try AF_INET6
> force node name
> force service name
> get node only
> get service only
> get node and service
> get node and service with maximum number of characters for IP
>
> *** END OF TEST NETWORKING 1 ***
>
> fatal source: RTEMS_FATAL_SOURCE_EXIT
> bsp_fatal_extension(): RTEMS terminated -- no way back to MotLoad so I
> reset the card
> Printing a stack trace for your convenience :-)
>
> 0x00017368--> 0x00017368--> 0x00122684--> 0x00100928--> 0x00099556
> 0x00016936--> 0x00014728--> 0x00113540--> 0x00113364
>
>
>
> Copyright(C)2008-2009,Emerson Network Power-Embedded Computing,Inc.
> All Rights Reserved
> Copyright Motorola Inc. 1999-2007, All Rights Reserved
> MOTLoad RTOS Version 2.0, PAL Version 2.3 RM01
> Fri Jan 23 14:47:54 MST 2009
>
> MPU-Type =MPC74x7
> MPU-Int Clock Speed =1266MHz
> MPU-Ext Clock Speed =133MHz
> MPU-Int Cache(L2) Enabled, 512KB, L2CR =C0000000
> MPU-Ext Cache(L3) Enabled, 2MB, 211MHz, L3CR =DC026300
>
> PCI bus instance 0 =64 bit, 133 Mhz, PCI-X
> PCI bus instance 1 =64 bit, PCI
>
> Reset/Boot Vector =Flash1
>
> Local Memory Found =20000000 (&536870912)
> User Download Buffer =006B7000:008B6FFF
>
> MVME6100> tftpGet -s141.14.128.9 -c141.14.128.12 -a04000000 -fticker.exe
> Network Loading from: /dev/enet0
> Loading File: ticker.exe
> Load Address: 04000000
> Download Buffer Size = User Defined
>
> Client IP Address = 141.14.128.12
> Server IP Address = 141.14.128.9
> Gateway IP Address = 141.14.128.253
> Subnet IP Address Mask = 255.255.255.0
>
> Network File Load in Progress...
>
> Bytes Received =&502732, Bytes Loaded =&502732
> Bytes/Second =&502732, Elapsed Time =1 Second(s)
> MVME6100> ne-----------------------------------------
> config addr is 0xf1000cf8
> config data is 0xf1000cfc
> Welcome to RTEMS rtems-6.0.0 (PowerPC/Generic (classic FPU)/beatnik)
> CPU: MPC7457
> Board Type: MVME6100-0163 (S/N E173D27)
> Bus Clock Freq: 133333333 Hz
> CPU Clock Freq: 1266666654 Hz
> Memory: 536870912 bytes
> -----------------------------------------
> Now BSP_mem_size = 0x1fe00000
> Configuration.work_space_size = 80000
> Page table setup finished; will activate it NOW...
> Going to start PCI buses scanning and initialization
> Number of PCI buses found is : 3
> MSR 0x2003032
> Exit from bspstart
> unable to find the universe in pci config space
> Tundra Tsi148 PCI-VME bridge detected at 0x81100000, IRQ 84
> Tsi148 Outbound Ports:
> Port VME-Addr Size PCI-Adrs Mode:
> 0: 0x20000000 0x0e000000 0x90000000 A32, SUP, D32, SCT
> 1: 0x00000000 0x00ff0000 0x9f000000 A24, SUP, D32, SCT
> 2: 0x00000000 0x00010000 0x9fff0000 A16, SUP, D32, SCT
> 7: 0x00000000 0x01000000 0x9e000000 CSR, SUP, D32, SCT
> Tsi148 Inbound Ports:
> Port VME-Addr Size PCI-Adrs Mode:
> 0: 0x90000000 0x1fe00000 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
>
>
> *** BEGIN OF TEST LOOPBACK ***
> *** TEST VERSION: 6.0.0.4fa5e77ba3a00f8ac61251b6c049c98102583d57
> *** TEST STATE: EXPECTED_PASS
> *** TEST BUILD: RTEMS_POSIX_API
> *** TEST TOOLS: 10.2.1 20210205 (RTEMS 6, RSB
> 61dcadee0825867ebe51f9f367430ef75b8fe9c0, Newlib d4a756f)
> "Network" initializing!
> "Network" initialized!
> Try running client with no server present.
> Should fail with `connection refused'.
> Connect to server.
> Can't connect to server: Connection refused
> Client closing connection.
>
> Start server.
>
> Try running client with server present.
> Connect to server.
> Can't connect to server: Connection refused
> Client closing connection.
> Client task terminating.
> Create socket.
> Bind socket.
>
> Try running two clients.
> Connect to server.
> Connect to server.
> ACCEPTED:2130706433
> ACCEPTED:2130706433
> Write 22-byte message to server.
> Write 22-byte message to server.
> Read 43 from server: Server received 22 (Hi there, server (2).)
> Read 43 from server: Server received 22 (Hi there, server (3).)
> Client closing connection.
> Client task terminating.
> Worker task terminating.
> Client closing connection.
> Client task terminating.
> Worker task terminating.
>
> Try running three clients.
> Connect to server.
> Connect to server.
> Connect to server.
> ACCEPTED:2130706433
> ACCEPTED:2130706433
> ACCEPTED:2130706433
> Write 22-byte message to server.
> Write 22-byte message to server.
> Write 22-byte message to server.
> Read 43 from server: Server received 22 (Hi there, server (4).)
> Read 43 from server: Server received 22 (Hi there, server (5).)
> Read 43 from server: Server received 22 (Hi there, server (6).)
> Client closing connection.
> Client task terminating.
> Worker task terminating.
> Client closing connection.
> Client task terminating.
> Worker task terminating.
> Client closing connection.
> Client task terminating.
> Worker task terminating.
>
> *** END OF TEST LOOPBACK ***
>
> fatal source: RTEMS_FATAL_SOURCE_EXIT
> bsp_fatal_extension(): RTEMS terminated -- no way back to MotLoad so I
> reset the card
> Printing a stack trace for your convenience :-)
>
> 0x00224388--> 0x00224388--> 0x00334484--> 0x00311900--> 0x00310528
> 0x00289968--> 0x00348388--> 0x00013652--> 0x00325192--> 0x00325016
>
>
>
> Copyright(C)2008-2009,Emerson Network Power-Embedded Computing,Inc.
>
> Danke!
> Heinz
>
>
>
>
>
> On 2021-03-03 21:03, Vijay Kumar Banerjee wrote:
> > On Wed, Mar 3, 2021 at 12:37 PM junkes <junkes at fhi-berlin.mpg.de>
> > wrote:
> >>
> >> Hi Vijay,
> >> I tried it again:
> >>
> > Hi Heinz,
> >
> > I'm really sorry that the build crashed again. I missed the telnetd.h
> > file probably because it was somewhere in my build prefix from one of
> > the rtems builds. I have pushed a fix on the rtems repo and the
> > rtems-net-legacy repo. This time I was more thorough and used a new
> > prefix location, I believe it won't break this time.
> >
> > Thank you for helping with the testing. I really appreciate it.
> >
> >
> > Best regards,
> > Vijay
> >
> >> # building kernel
> >> #git clone git://git.rtems.org/rtems.git kernel
> >> git clone git://git.rtems.org/vijay/rtems.git kernel
> >> cd kernel
> >> git checkout devel-no-libnet
> >>
> >> # build and install bsp
> >> # 1. Test with waf
> >> #-e "s|RTEMS_NETWORKING = False|RTEMS_NETWORKING = True|" \
> >> ./waf bsp_defaults --rtems-bsps=powerpc/beatnik > config.ini
> >> sed -i \
> >> -e "s|RTEMS_POSIX_API = False|RTEMS_POSIX_API = True|" \
> >> -e "s|BUILD_TESTS = False|BUILD_TESTS = True|" \
> >> config.ini
> >> ./waf configure --prefix=/home/junkes/MVME6100_testing/rtems/6
> >> ./waf
> >> ./waf install
> >>
> >> cd ..
> >>
> >> # building extra legacy net
> >> git clone git://git.rtems.org/vijay/rtems-net-legacy.git legacyNet
> >> cd legacyNet
> >> git submodule init
> >> git submodule update
> >>
> >> ./waf configure --prefix=/home/junkes/MVME6100_testing/rtems/6
> >>
> >> ./waf build --rtems-archs=powerpc --rtems-bsps=beatnik
> >>
> >>
> >> Much better, but still a missing file?
> >>
> >> [125/235] Compiling libc/res_mkquery.c
> >> [126/235] Compiling libc/inet_lnaof.c
> >> [127/235] Compiling librpc/src/xdr/xdr_array.c
> >> ../../telnetd/check_passwd.c:70:10: fatal error: rtems/telnetd.h: No
> >> such file or directory
> >> 70 | #include <rtems/telnetd.h>
> >> | ^~~~~~~~~~~~~~~~~
> >> compilation terminated.
> >>
> >> ../../telnetd/telnetd.c:57:10: fatal error: rtems/telnetd.h: No such
> >> file or directory
> >> 57 | #include <rtems/telnetd.h>
> >> | ^~~~~~~~~~~~~~~~~
> >> compilation terminated.
> >>
> >> Waf: Leaving directory
> >> `/home/junkes/MVME6100_testing/legacyNet/build/powerpc-rtems6-beatnik'
> >> Build failed
> >> -> task in 'network_objects' failed with exit status 1 (run with -v
> >> to
> >> display more information)
> >> -> task in 'network_objects' failed with exit status 1 (run with -v
> >> to
> >> display more information)
> >>
> >> Heinz
- Replies:
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
- References:
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Joel Sherrill via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
- Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
- Navigate by Date:
- Prev:
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Vijay Kumar Banerjee via Core-talk
- Next:
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository Chris Johns via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
- Next:
Re: Announcement: Legacy libnetworking will be removed from RTEMS and will be placed in a separate repository junkes via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
|