White Rabbit issueshttps://ohwr.org/project/white-rabbit/issues2019-08-01T12:07:45Zhttps://ohwr.org/project/white-rabbit/issues/35MB40201VX-000U-A99 EOL2019-08-01T12:07:45ZMariusz MrozMB40201VX-000U-A99 EOLSunon MB40201VX-000U-A99 fan is EOL (see EOL notice:
[EOL_Notice_20160706.pdf](/uploads/e50e1692a4202e66b1d5449b1739ecb7/EOL_Notice_20160706.pdf)
Recommended replacement type: MF40201VX-1000U-A99
Please confirm that this PN can be used as a replacement.https://ohwr.org/project/white-rabbit/issues/23V3 failsafe recovery button2019-02-12T08:15:15ZTomasz WlostowskiV3 failsafe recovery buttonAdd an extra button connected to one of the CPU's GPIO pins. Pressing
this button and powering up the switch will cause the internal
bootloader to enter failsafe/recovery mode.https://ohwr.org/project/white-rabbit/issues/3SFP and FIBER should be able to support unique choise for all ports2019-02-12T08:15:03ZTjeerd PinkertSFP and FIBER should be able to support unique choise for all portsJust for the record, and maybe the 5.1 release...
The configurations:
CONFIG\_SFP00\_PARAMS .. CONFIG\_SFP09\_PARAMS
and
CONFIG\_FIBER00\_PARAMS .. CONFIG\_FIBER03\_PARAMS
should support at least 18 different parts for a fully calibrated
switch.https://ohwr.org/project/white-rabbit/issues/2Round trip error when two nodes under one WR switch reset simulataneously2019-02-12T08:15:02Zli hongmingRound trip error when two nodes under one WR switch reset simulataneouslyhttps://ohwr.org/project/white-rabbit/issues/1SCB V3.4 fail to boot at +5 degrees and below when plugged onto Backplane20sf...2019-02-12T08:15:02ZPeter JansweijerSCB V3.4 fail to boot at +5 degrees and below when plugged onto Backplane20sfp_v2.0During the HALT test at IFIC Valencia it was found that the combination
of the backplane20sfp\_v2.0 + SCB v3.4 failed booting at temperatures
below +5 degrees.
*This issue is due to a combination of circumstances:**
- Backplane20sfp has a CP2015 UART \[1\] which powers-up in "suspend"
(see \[1\], paragraph 5) when no USB cable is attached. IO is
configured in GPIO mode which measn that the TXD output is
configured as input and the ARM DBG\_RXD line is floating.
- The ARM apparently can't handle the floating RxD (see also \[2\],
paragraph 10.5). Either a defined '1' (non-asserted RS232) or a '0'
will satisfy the ARM.
-----
*Solution:**
Put a pull-up (4K7) at the CP2105 TXD outputs to avoid floating lines
during "suspend" and signal "non-asserted RS232".
-----
*Other observations:**
- **The SCB V3.4 should have taken care of a defined DBG\_RXD input,
i.e. in a future version there should be a pull-up on the SCB
board.**
- The SCB v3.4 works fine in combination with the
miniBackplane\_SFP\_V3\_3 \[3\] since on the miniBackplane CP2102
devices are used at 3V3 and their outputs are made 2V5 (ARM VDDIOP0)
compliant using a resistor divider, hence effectively having a
pull-down when the CP2102 powers-up in "suspend" mode. Therefor the
ARM DBG\_RXD is defined and the SCB never fails boot when plugged
onto a miniBackplane.
- Apparently temperature influences the leakage current on the ARM
and/or CP2105 thus influencing the floating voltage.
-----
\[1\] https://www.silabs.com/documents/public/data-sheets/CP2105.pdf
\[2\]
http://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-6438-32-bit-ARM926-Embedded-Microprocessor-SAM9G45_Datasheet.pdf
\[3\]
https://www.ohwr.org/project/wr-switch-hw/blob/master/circuit_board/wrs_v3/Docs_PDF/miniBackplane_SFP_V3_3.pdf