Does the USB cable to the mini-B connector on the spec board have to be connected all the time? Or is it only required at some point during the installation?
We strongly suggest you to keep the USB cable to the mini-B connector at
this moment, because it is the easiest way to configure the SPEC (wrpc
Some other solutions exists but we would not recommend them for
Do I need to connect the external power supply connector when used in a PCIe slot?
No the power supply is not necessary while connecting through the PCIe
slot. The board gets its power from the PCIe card edge connector. This
exernal connector is only used in stand-alone applications where the
card is not plugged into a PCIe slot.
Starting Kit Software
I don't see the interface using ifconfig
Please check if you see them using :
if you see them by using the `-a` option you just need to bring them
up as it is explained in wr-starting-kit.pdf.
Which kernel version is supported
To compile you must have at least the 2.6.36 kernel. We recommend you to
use the latest version of your distribution.
It is possible to use the 2.6.34 version but by modifying the includes
Unfortunatly, kernel 2.6.32 (RHEL 6.x, CentOS 6.x & SL 6.x) is not
officialy supported by spec-sw, you can try to compile the backport-rubi-131119 branch. The driver should work but you will not
get any timestamp as kernel 2.6.32 does not support it.
This means that you need to remove the jumper (SW1) near the SFP port.
If the jumper has been removed and you still have this error this mean
that the SPEC has not been properly setup during the manufacturing
process. Please contact you provider to obtain more details on how you
wrc# calibration force Enabling ptracker channel: 0LNK: PLL: SPLL_Init: running as Slave, 1 ref channels, 2 out channels
And the calibration is doing an infinite loop.
Calibration is only available for slave and you need to be connected to
a working PTP master master (SPEC in master mode or the
switch) to be completed.
To configure your SPEC as a working PTP master, just execute in
the wrpc shell of the other board:
wrc# sfp matchwrc# mode masterwrc# ptp start
If you have blocked your two boards in calibration mode and they stay in
this mode even after rebooting and reloading firmware/gateware you might
need to format the
The starting kit is based on Ubuntu. How can I use it with Scientific Linux?
The commands to execute in order to update the kernel using scientific
linux (you need at least the 2.6.36 to compile the starting kit) are:
You can have more information on how to do this by browsing the ELRepo
After this you should reboot your PC with the new kernel source and
start from section 3.4 in wr-starting-kit-v1.0.pdf
Is it possible to use the DIO without being connected to WR?
Actually the dio core capabilities needs to be synced to a WR master to
work. You will not be able to use the wr-dio-pps nor the wr-dio-cmd pulse without a White Rabbit
When the wr-nic card boots and reach free-running master mode, there is no PPS output. Is it normal?
That's correct in fact.
At boot up, you card check for a WR master on the link, if you link
failed or not WR master is found, your card switch to free-running
master mode and PPS output is disable because no PPS output is better
than wrong PPS output: your node would start producing random 1-PPS
signal because it will be generated from free-running oscillator.
If it is your desire (for testing purpose) to have your node to be
free-running master you have to clearly configure it to this mode using
the command #wrc> mode maser and then you have your 1-PPS output
from free-running oscillator.
In basic configuration your Master SPEC can use its internal
free-running oscillator as a time
reference. However, you can also discipline your Master SPEC with
external 10 MHz and 1-PPS
signal by connecting them to the appropriate LEMO connectors of FMC-DIO
Then in the wrc console just execute the following commands:
wrc# mode gmwrc# ptp start
For more information about grandmaster mode you can take a look at:
This document has been written for the WR switch, but
timing/accuracy/stability requirements are same for the SPECs.