Hi Rob,

Thank you for your feedback !

I am relieved to learn that I'm not the only user experience issues using WR 
with N32x boards.
Where did you find out that Ettus is presently looking into WR issues ?
I'm asking because I can see a different thread from 2019 
(http://ettus.80997.x6.nabble.com/USRP-users-N320-XQ-image-issue-using-sfp0-as-time-source-td13973.html)
Which as far as I can see, no fix is implemented in uhd:master.

BTW, I work with uhd4.0 - commit cf570707a2.
We tried 2 different N320 boards, both resulted in the same behavior.

Best,

Julián

===================================
Julián Mariano Burella Pérez
M.Sc.Eng. TIN, Embedded Systems
Collaborateur Ra&D HES
Prof.:          +41 24 557 62 84
julian.burellape...@heig-vd.ch<mailto:julian.burellape...@heig-vd.ch>
Haute École d'Ingénierie et de Gestion du Canton de Vaud
Route de Cheseaux 1 - CP 521 - 1401 Yverdon-les-Bains
===================================
________________________________
De : Rob Kossler <rkoss...@nd.edu>
Envoyé : jeudi, 6 mai 2021 15:41:11
À : Burella Pérez Julián Mariano
Cc : usrp-users@lists.ettus.com
Objet : Re: [USRP-users] [N320] Using white rabbit with OPNT Master Switch

Hi Julián,
I am also getting these same errors and have been unsuccessful getting WR 
working on either 3.15 or 4.0.  I have asked this list to see if anyone is 
presently using WR successfully, but have not had any replies.  I know that 
Ettus is presently looking into WR issues.
Rob


On Thu, May 6, 2021 at 8:57 AM Burella Pérez Julián Mariano 
<julian.burellape...@heig-vd.ch<mailto:julian.burellape...@heig-vd.ch>> wrote:
Hello,

We have a setup where we're trying to sync a N320 (bitstream WX) using White 
rabbit with a OPNT Timing Switch as Master configured as Free Running Master.


+------------------------+                        +---------------------+
|                                 |             SFP0  |                         
    |
| OPNT Timing Switch   |---------------- |        N320             |
|                                 |                        |                    
         |
+------------------------+                        +---------------------+


We are trying to run test program `test_pps_input` in order to see if PPS is 
working as expected.
When running without any argument, the PPS is correctly detected, I suppose it 
is because it uses as time source `internal`.
Then when I try to use `sfp0` as a time source, I observed 2 different 
behaviors:

Command run: ./test_pps_input --args="clock_source=internal,time_source=sfp0" 
--source=sfp0

1. I get the following message:

[ERROR] [RPC] TDC Failed to reset.
[INFO] [MPM.Rhodium-0.init.LMK04828] LMK initialized and locked!
[ERROR] [MPM.Sync-0] TDC Failed to Reset! Check your clocks! Status: 0x0
[ERROR] [MPM.RPCServer] init() failed with error: TDC Failed to reset.
Error: RuntimeError: Error during RPC call to `init'. Error message: TDC Failed 
to reset.

And after this message, the PPS led does not blink anymore.

2.
If I then run again the test after failing previously, this time I don't get 
any error message but a exception is thrown because no PPS was detected.

We know that the OPNT Timing switch works when used with a OPNT node, where we 
get PPS and 10MHz signals.

Do you think that there could be an issue when N320 and OPNT Switch try to sync 
together, or do you have any idea of what I could explore ?

Thank you in advance for any help you can provide me with.

Best,
Julián
_______________________________________________
USRP-users mailing list -- 
usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com>
To unsubscribe send an email to 
usrp-users-le...@lists.ettus.com<mailto:usrp-users-le...@lists.ettus.com>
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to