Calling device3->clear() will strobe clear_tx_seqnum, but it is not a direct mapping. It also resets the upstream and downstream node connections, If you need trigger the reset at specific times, it would probably be easier to add your own reset settings register.
On Tue, Aug 27, 2019 at 10:55 AM Rob Kossler <[email protected]> wrote: > Thanks Jonathon. How about if I re-wire an rfnoc graph? Does that assert > clear_tx_seqnum? Does the UHD device3->clear() function map directly or > indirectly to this signal? > Rob > > On Mon, Aug 26, 2019 at 9:49 PM Jonathon Pendlum < > [email protected]> wrote: > >> Hi Rob, >> >> Originally clear_tx_seqnum was only for resetting AXI Wrapper, but it >> evolved into a user reset as well since it is asserted every time your UHD >> app starts. ce_rst is only asserted at power up. >> >> Jonathon >> >> On Tue, Aug 27, 2019 at 2:29 AM Rob Kossler via USRP-users < >> [email protected]> wrote: >> >>> Can anyone explain the meaning of the signals ce_rst and >>> clear_tx_seqnum? It is not clear to me what would cause either of them to >>> go High. Should I expect ce_rst to be strobed each time I launch my C++ >>> app that calls UHD? I had previously thought so, but now I have reason to >>> doubt. >>> >>> Thanks. >>> Rob >>> _______________________________________________ >>> USRP-users mailing list >>> [email protected] >>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >>> >>
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
