Software for White Rabbit PTP Core issueshttps://ohwr.org/project/wrpc-sw/issues2024-03-28T13:54:55Zhttps://ohwr.org/project/wrpc-sw/issues/63configs in the configs directory are out of sync with available options in Kc...2024-03-28T13:54:55ZAdam Wujekconfigs in the configs directory are out of sync with available options in Kconfigconfigs in the configs directory are out of sync with available options in Kconfighttps://ohwr.org/project/wrpc-sw/issues/62Bring back removed AUX_DIAG in Kconfig2024-03-28T13:47:18ZAdam WujekBring back removed AUX_DIAG in KconfigAUX_DIAG is needed to be able to enable SNMP_AUX_DIAG.
AUX_DIAG was removed in the commit:
https://ohwr.org/project/wrpc-sw/commit/df529bbb `Kconfig, configs: remove AUX_DIAG (unused)`https://ohwr.org/project/wrpc-sw/issues/61PLL not locking causing WR degradation to PTP2024-01-31T22:21:32ZAdam WujekPLL not locking causing WR degradation to PTPIn about 1 out of 5-10 restarts of WRPC the PLL is not locking.
With the timeout set to 15sec, if PLL locking takes too long, the timer times out and re-triggers PLL lock. The second lock is successful. In the dev version of WRPC, when the `WR_S_LOCK_TIMEOUT_MS` was increased from 15 to 60 seconds, then the WR handshaking fails and WR link is degraded to PTP (later promotion to WR is not possible).
Changing `WR_M_LOCK_TIMEOUT_MS` on the master side (to e.g. 60) also fixes the problem, but it is not possible to guarantee that the WRS uses the increased value. Which will cause problems with backward compatibility.https://ohwr.org/project/wrpc-sw/issues/60include wr-cores version in the ver command2023-03-08T00:09:35ZAdam Wujekinclude wr-cores version in the ver commandwr-cores version is probably not available to lm32/RISC-Vhttps://ohwr.org/project/wrpc-sw/issues/59P2P mechanism does not compile/fit (ISPCS2022 tests)2022-12-16T09:46:13ZMaciej LipinskiP2P mechanism does not compile/fit (ISPCS2022 tests)see PPSi issue: https://ohwr.org/project/ppsi/issues/41https://ohwr.org/project/wrpc-sw/issues/57Board-specific SFP access2021-11-03T15:24:04ZMarek GumiĆskiBoard-specific SFP accessI request a method of preparing a board-specific funcions: sfp_present and sfp_read_part_id (currently defined in dev/sfp.c).
The preferred method would be to enable defining them in boards/boardname/board.c.
I'm working on support of a board that requires setting up a few i2c muxes to access sfp via i2c.
On the same board sfp present is accessable via i2c-gpio extender.https://ohwr.org/project/wrpc-sw/issues/56Warning: tx not terminated infinite mcr=0x10015002021-09-17T02:10:01ZAdam WujekWarning: tx not terminated infinite mcr=0x1001500Sometimes after the fiber is re-connected I saw messages like:
```
Warning: tx not terminated infinite mcr=0x1001500
Warning: tx timestamp never became available
```
or
```
Warning: tx not terminated infinite mcr=0x1001400
Warning: tx timestamp never became available
```https://ohwr.org/project/wrpc-sw/issues/55two tasks to check the link up in development version2021-07-08T14:21:40ZAdam Wujektwo tasks to check the link up in development versionIn the development version of WRPC there are two tasks to check if the link is up. It looks like there was some work done to support multiple links. The task `check-link` (the old one) does check only one link. The task `netif` checks multiple links.https://ohwr.org/project/wrpc-sw/issues/54no BOOTP after link down/up2021-09-24T01:10:07ZAdam Wujekno BOOTP after link down/upIf IP is dynamic, IP is not requested after link down, link up.Adam WujekAdam Wujekhttps://ohwr.org/project/wrpc-sw/issues/53Send VLAN ID via LLDP2021-09-24T01:10:07ZAdam WujekSend VLAN ID via LLDPSend VLAN ID in LLDP frame. Example reported by 3Com switch:
```
[lldpcli] # show neighbors details
-------------------------------------------------------------------------------
LLDP neighbors:
-------------------------------------------------------------------------------
Interface: eth0, via: LLDP, RID: 1, Time: 0 day, 03:45:43
Chassis:
ChassisID: mac xx:xx:xx:xx:xx:xx
SysName: 3Com
SysDescr: 3Com Baseline Switch
Capability: Bridge, on
Capability: Router, on
Port:
PortID: ifname GigabitEthernet1/0/3
PortDescr: GigabitEthernet1/0/3 Interface
TTL: 120
VLAN: 10 pvid: yes VLAN 0010
PPVID: supported: yes, enabled: no
-------------------------------------------------------------------------------
```Adam WujekAdam Wujekhttps://ohwr.org/project/wrpc-sw/issues/52WRS stuck in UNCALIBRAT/IDLE after accuracy changed2021-09-30T13:09:03ZAdam WujekWRS stuck in UNCALIBRAT/IDLE after accuracy changedwhen wrpc is master with the following parameters:
```
wrc# ptp
running; e2e master
prio1 = 128
prio2 = 128
domain = 0
clock class = 193
clock accuracy = 32
clock allan variance = 50973
time source = 160
```
If command ``ptp accuracy 31`` is executed a WRS stays in UNCALIBRAT/IDLE state. The change of other clock parameters (class, allan tsource causes the same effect.
May be a false positive bug.https://ohwr.org/project/wrpc-sw/issues/51Add advanced PPSI parameters to Kconfig and add a command to wrpc to configur...2021-09-24T01:10:07ZAdam WujekAdd advanced PPSI parameters to Kconfig and add a command to wrpc to configure themparameters like:
* priority1/2
* clock class
* domain numberhttps://ohwr.org/project/wrpc-sw/issues/50Add CONFIG_NO_PTPDUMP to Kconfig2021-09-24T01:10:07ZAdam WujekAdd CONFIG_NO_PTPDUMP to Kconfighttps://ohwr.org/project/wrpc-sw/issues/49add command to print sfp info (and monitoring)2021-05-31T23:43:31ZAdam Wujekadd command to print sfp info (and monitoring)https://ohwr.org/project/wrpc-sw/issues/48Improve wrpc-dump to support WRPC related info2021-05-17T14:18:14ZAdam WujekImprove wrpc-dump to support WRPC related infoImprove `wrpc-dump` to support WRPC related info. Right now `wrpc-dump` supports only the dump of ppsi memory.https://ohwr.org/project/wrpc-sw/issues/47Implement DHCP2021-03-11T11:39:27ZIlia SlepnevImplement DHCPPlease consider implementing DHCP.
BOOTP is problematic with dhcp-relay in L3 routed networks and BOOTP is not supported by some switch vendors:
> Cisco Nexus 9000 Series switches do not support the relaying of bootp packets. However, the switches do support bootp packets that are Layer 2 switched.https://ohwr.org/project/wrpc-sw/issues/46Reduce the size of WRPC2021-05-17T14:16:34ZAdam WujekReduce the size of WRPCWith the new PPSI (used in WRS v6.0), the footprint of WRPC is bigger than the available memory (128KB). There was some work done in this area, this issue is to keep track of it.
The size at the beginning of the WP1b was 139968 Bytes, the size was reduced to 125596 Bytes (by 14372 Bytes) with possible further reduction to 123640 (total reduction by 16328 Bytes) if `Single port`, `One instance per port` and `One foreign master` options are selected in PPSI's config. Additionally, it was identified that the use of RISCV can reduce the footprint by 7844B.
Also following can reduce the size (tested not for the latest commit):
* Use newer compiler for RISCV (10.2.0 instead of 7.3.0), reduction ~1.5KB
* Use Compressed Instructions in RISCV, reduction ~27KB
* Use LTO (Link Time Optimization) for RISCV, reduction ~5KB.
If all of the above are used, the footprint can be reduced by more than 40KB, from ~125KB down to ~85KB (or even less).
The attached file contains the detailed information about size reduction of WRPC.
[Size_report.ods](/uploads/d85f04ae54bc0675455a6e3dc2d318d3/Size_report.ods)https://ohwr.org/project/wrpc-sw/issues/45implement OIDs in SNMP to identify node2020-10-29T16:25:22ZAdam Wujekimplement OIDs in SNMP to identify nodeImplement OIDs like:
```
RFC1213-MIB::sysDescr.0 = STRING: "Linux ctdwa-774-cwrstest2 3.16.38 #1 Thu Oct 29 17:14:48 CET 2020 armv5tejl"
RFC1213-MIB::sysObjectID.0 = OID: NET-SNMP-TC::linux
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (653) 0:00:06.53
RFC1213-MIB::sysContact.0 = STRING: "root@localhost"
RFC1213-MIB::sysName.0 = STRING: "ctdwa-774-cwrstest2"
RFC1213-MIB::sysLocation.0 = STRING: "Unknown"
```
Make following settable:
```
RFC1213-MIB::sysContact.0
RFC1213-MIB::sysLocation.0
```https://ohwr.org/project/wrpc-sw/issues/43make network services (syslog, lldp, etc.) aware of multiple interfaces2020-10-07T15:54:29ZGrzegorz Danilukmake network services (syslog, lldp, etc.) aware of multiple interfacesFunctions to configure these should take netif structure object as argument.wrpc-v5.0Grzegorz DanilukGrzegorz Danilukhttps://ohwr.org/project/wrpc-sw/issues/42add storage support for multiple MAC addresses (multiple ports)2020-10-07T15:54:37ZGrzegorz Danilukadd storage support for multiple MAC addresses (multiple ports)Required e.g. for LLRF where the board has several endpoints (only one used for WR, the other used e.g. for BTrain traffic).wrpc-v5.0Grzegorz DanilukGrzegorz Daniluk