Re: RTEMS 5.3 libbsd, networking issue for 100mbps link (1Gbps is fine)

2023-07-18 Thread Chris Johns 
On 18/7/2023 8:21 pm, Karol Gliwa wrote:
> Hi Guys,
> 
>  
> 
> I have following problem with networking on Zynq running RTEMS 5.3 + libbsd +
> BSP zynq_zedboard of according version.
> 
> I had to patch the libbsd to support some network PHY for the boards I use.
> 
>  
> 
> Whenever I connect the device to 1Gbit interface, and the link is negotiated 
> to
> 1Gbit everything seems working just fine. I can PING the board and 
> successfully
> connect to TCP/IP socket (custom test echo server basing on the examples int 
> the
> rtems-libbsd repository + sockets).
> 
>  
> 
> When I connect the board to 100Mbit interface (another usb dongle) it seems to
> establish the link fine, but I cannot ping the board nor connect to the 
> socket.
> I replicated this behavior with at least three different 1Gbit interfaces 
> (works
> each time) and two 100Mbit dongles (not working). I confirmed that behavior
> using PYNQ Z1 board and also with our other custom device.
> 
>  
> 
> Additionally, I had an opportunity to test our custom board with another 
> 'hello
> world' echo server that came from my colleges that use Xilin'x Vitis + LwIP
> (bare metal application) and that one has been working in every link speed
> configuration.
> 
>  
> 
> It seems to me that the problem my reside in the RTEMS software part or 
> drivers
> (or my compilation or configuration) and not in the HW since I could confirm
> it's working with LwIP for all configs... Unfortunately, I have little
> experience with networking in general and was not able to solve that issue on 
> my
> own.
> 
>  
> 
> I attach the RTEMS shell output of `ifconfig -a` executed on PYNQ Z1 when
> connected to 1Gbit eth device (PING working):
> 
>  
> 
> '''
> 
> SHLL [/] # ifconfig  cgem0 192.168.10.207 netmask 255.255.255.0
> 
> SHLL [/] # ifconfig -a   
> 
> cgem0: flags=8843 metric 0 mtu 1500
> 
>     options=80008
> 
>     ether 0e:b0:ba:5e:ba:11
> 
>     inet6 fe80::cb0:baff:fe5e:ba11%cgem0 prefixlen 64 scopeid 0x1
> 
>     inet 192.168.10.207 netmask 0xff00 broadcast 192.168.10.255
> 
>     nd6 options=21
> 
>     media: Ethernet autoselect (1000baseT )
> 
>     status: active
> 
> lo0: flags=8049 metric 0 mtu 16384
> 
>     options=680003
> 
>     inet 127.0.0.1 netmask 0xff00
> 
>     inet6 ::1 prefixlen 128
> 
>     inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
> 
>     nd6 options=21
> 
>     groups: lo
> 
> '''
> 
>  
> 
>  
> 
> Then hot switch to 100Mbit usb eth card (PING not working):
> 
> '''
> 
> SHLL [/] # info: cgem0: link state changed to DOWN
> 
> cgem0: cgem_mediachange: could not set ref clk0 to 2500.
> 
> info: cgem0: link state changed to UP
> 
> SHLL [/] # ifconfig  cgem0 172.19.1.207 netmask 255.255.255.0 
> 
> SHLL [/] # ifconfig -a 
> 
> cgem0: flags=8843 metric 0 mtu 1500
> 
>     options=80008
> 
>     ether 0e:b0:ba:5e:ba:11
> 
>     inet6 fe80::cb0:baff:fe5e:ba11%cgem0 prefixlen 64 scopeid 0x1
> 
>     inet 172.19.1.207 netmask 0xff00 broadcast 172.19.1.255
> 
>     nd6 options=21
> 
>     media: Ethernet autoselect (100baseTX )
> 
>     status: active
> 
> lo0: flags=8049 metric 0 mtu 16384
> 
>     options=680003
> 
>     inet 127.0.0.1 netmask 0xff00
> 
>     inet6 ::1 prefixlen 128
> 
>     inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
> 
>     nd6 options=21
> 
>     groups: lo
> 
> '''
> 
>  
> 
>  
> 
>  
> 
> Do You have any idea of what may be causing the issue here? Thanks for all 
> help
> in advance.

Are the clocks to the PHY being correctly set and the driver knows the 
frequency.

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

Re: HEADS UP: git repo WRONG push landed.

2023-07-18 Thread Chris Johns 
Amar as edited the repo. You can read his post here ..

https://lists.rtems.org/pipermail/devel/2023-July/075819.html

Chris

On 19/7/2023 12:13 am, Brett Sterling wrote:
> The easiest way to do this is to revert and push.  'unpushing' is not
> recommended :-)
> 
> Brett
> 
> *From:* users  on behalf of Karel Gardas
> 
> *Sent:* Tuesday, July 18, 2023 7:58 AM
> *To:* users@rtems.org 
> *Subject:* HEADS UP: git repo WRONG push landed.
>  
> [You don't often get email from karel.gar...@centrum.cz. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification
>  ]
> 
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you recognize the sender and know the content
> is safe.
> 
> 
>    Dear RTEMS users,
> 
> if you are using RTEMS git repo, please do not pull now. Wrong patches
> landed in the main RTEMS git.rtems.org and they needs to be removed.
> 
> Thanks for your patience!
> Karel
> 
> 
>  Forwarded Message 
> Subject: HEADS UP: git repo WRONG push landed.
> Date: Tue, 18 Jul 2023 15:40:11 +0200
> From: Karel Gardas 
> To: rtems-de...@rtems.org 
> 
> 
>    Folks,
> 
> I've completely screwed up and pushed wrong repository to the git.rtems.org.
> 
> I don't know how that happen as this should land on github.com...
> 
> So please do not commit anything for now, I'll try to lookup help on
> discord.com and see what can be done to unpush...
> 
> Thanks and really sorry for this mess...
> 
> Karel
> ___
> devel mailing list
> de...@rtems.org
> https://usg02.safelinks.protection.office365.us/?url=http%3A%2F%2Flists.rtems.org%2Fmailman%2Flistinfo%2Fdevel=05%7C01%7C%7Cdf082186a2e94e7469a508db87972228%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638252855427392820%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=KaysoMVjUZ3z52kLfaNS1xmwbdN5Y3YmOQLPiYCUHlI%3D=0
>  
> 
> ___
> users mailing list
> users@rtems.org
> https://usg02.safelinks.protection.office365.us/?url=http%3A%2F%2Flists.rtems.org%2Fmailman%2Flistinfo%2Fusers=05%7C01%7C%7Cdf082186a2e94e7469a508db87972228%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638252855427392820%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=hcdP78m3VZM%2BhIPEluZSxF45bbuMfkuWqBGByQxtMSs%3D=0
>  
> 
> 
> ___
> 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: HEADS UP: git repo WRONG push landed.

2023-07-18 Thread Brett Sterling 
The easiest way to do this is to revert and push.  'unpushing' is not 
recommended :-)

Brett

From: users  on behalf of Karel Gardas 

Sent: Tuesday, July 18, 2023 7:58 AM
To: users@rtems.org 
Subject: HEADS UP: git repo WRONG push landed.

[You don't often get email from karel.gar...@centrum.cz. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.


   Dear RTEMS users,

if you are using RTEMS git repo, please do not pull now. Wrong patches
landed in the main RTEMS git.rtems.org and they needs to be removed.

Thanks for your patience!
Karel


 Forwarded Message 
Subject: HEADS UP: git repo WRONG push landed.
Date: Tue, 18 Jul 2023 15:40:11 +0200
From: Karel Gardas 
To: rtems-de...@rtems.org 


   Folks,

I've completely screwed up and pushed wrong repository to the git.rtems.org.

I don't know how that happen as this should land on github.com...

So please do not commit anything for now, I'll try to lookup help on
discord.com and see what can be done to unpush...

Thanks and really sorry for this mess...

Karel
___
devel mailing list
de...@rtems.org
https://usg02.safelinks.protection.office365.us/?url=http%3A%2F%2Flists.rtems.org%2Fmailman%2Flistinfo%2Fdevel=05%7C01%7C%7Cdf082186a2e94e7469a508db87972228%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638252855427392820%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=KaysoMVjUZ3z52kLfaNS1xmwbdN5Y3YmOQLPiYCUHlI%3D=0
___
users mailing list
users@rtems.org
https://usg02.safelinks.protection.office365.us/?url=http%3A%2F%2Flists.rtems.org%2Fmailman%2Flistinfo%2Fusers=05%7C01%7C%7Cdf082186a2e94e7469a508db87972228%7Cd761ffacf6be45b88f6f288a59577095%7C0%7C0%7C638252855427392820%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=hcdP78m3VZM%2BhIPEluZSxF45bbuMfkuWqBGByQxtMSs%3D=0
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users

HEADS UP: git repo WRONG push landed.

2023-07-18 Thread Karel Gardas 



  Dear RTEMS users,

if you are using RTEMS git repo, please do not pull now. Wrong patches 
landed in the main RTEMS git.rtems.org and they needs to be removed.


Thanks for your patience!
Karel


 Forwarded Message 
Subject: HEADS UP: git repo WRONG push landed.
Date: Tue, 18 Jul 2023 15:40:11 +0200
From: Karel Gardas 
To: rtems-de...@rtems.org 


  Folks,

I've completely screwed up and pushed wrong repository to the git.rtems.org.

I don't know how that happen as this should land on github.com...

So please do not commit anything for now, I'll try to lookup help on 
discord.com and see what can be done to unpush...


Thanks and really sorry for this mess...

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

RTEMS 5.3 libbsd, networking issue for 100mbps link (1Gbps is fine)

2023-07-18 Thread Karol Gliwa 
Hi Guys,

I have following problem with networking on Zynq running RTEMS 5.3 + libbsd + 
BSP zynq_zedboard of according version.
I had to patch the libbsd to support some network PHY for the boards I use.

Whenever I connect the device to 1Gbit interface, and the link is negotiated to 
1Gbit everything seems working just fine. I can PING the board and successfully 
connect to TCP/IP socket (custom test echo server basing on the examples int 
the rtems-libbsd repository + sockets).

When I connect the board to 100Mbit interface (another usb dongle) it seems to 
establish the link fine, but I cannot ping the board nor connect to the socket. 
I replicated this behavior with at least three different 1Gbit interfaces 
(works each time) and two 100Mbit dongles (not working). I confirmed that 
behavior using PYNQ Z1 board and also with our other custom device.

Additionally, I had an opportunity to test our custom board with another 'hello 
world' echo server that came from my colleges that use Xilin'x Vitis + LwIP 
(bare metal application) and that one has been working in every link speed 
configuration.

It seems to me that the problem my reside in the RTEMS software part or drivers 
(or my compilation or configuration) and not in the HW since I could confirm 
it's working with LwIP for all configs... Unfortunately, I have little 
experience with networking in general and was not able to solve that issue on 
my own.

I attach the RTEMS shell output of `ifconfig -a` executed on PYNQ Z1 when 
connected to 1Gbit eth device (PING working):

'''
SHLL [/] # ifconfig  cgem0 192.168.10.207 netmask 255.255.255.0
SHLL [/] # ifconfig -a
cgem0: flags=8843 metric 0 mtu 1500
options=80008
ether 0e:b0:ba:5e:ba:11
inet6 fe80::cb0:baff:fe5e:ba11%cgem0 prefixlen 64 scopeid 0x1
inet 192.168.10.207 netmask 0xff00 broadcast 192.168.10.255
nd6 options=21
media: Ethernet autoselect (1000baseT )
status: active
lo0: flags=8049 metric 0 mtu 16384
options=680003
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
nd6 options=21
groups: lo
'''


Then hot switch to 100Mbit usb eth card (PING not working):
'''
SHLL [/] # info: cgem0: link state changed to DOWN
cgem0: cgem_mediachange: could not set ref clk0 to 2500.
info: cgem0: link state changed to UP
SHLL [/] # ifconfig  cgem0 172.19.1.207 netmask 255.255.255.0
SHLL [/] # ifconfig -a
cgem0: flags=8843 metric 0 mtu 1500
options=80008
ether 0e:b0:ba:5e:ba:11
inet6 fe80::cb0:baff:fe5e:ba11%cgem0 prefixlen 64 scopeid 0x1
inet 172.19.1.207 netmask 0xff00 broadcast 172.19.1.255
nd6 options=21
media: Ethernet autoselect (100baseTX )
status: active
lo0: flags=8049 metric 0 mtu 16384
options=680003
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
nd6 options=21
groups: lo
'''



Do You have any idea of what may be causing the issue here? Thanks for all help 
in advance.

Karol G.



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