usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

List of all possible "--args=..." parameters

V
Vladimir
Fri, Aug 5, 2016 12:10 PM

Hello!

Is there any single place where one could look for a list of device arguments that can be passed in --arg=... CL param [= to usrp_make() func]? From time to time I encounter one or the other of those here and there, but never succeeded to find them all in one place. If there isn't, can you please collect them in some convenient way?

Particularly, I'm interesting if I can speed up the initial uhd_usrp_make(), specifying exact details of my hw config, for usrp_make() not to waste time on various auto-detection procedures. For example, if I don't have GPSDO, can I pass any parameter in device_args instructing not to search for it? Since I notice that it takes some time of approx. 1 second. What else (except IP and device type) can I specify to speed up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE connection?

It would be great to have in such a list other interesting things as well, eg master clock setting, things like  self_cal_adc_delay and similar 'fine tuning' stuff.

Thank you!
Vladimir

Hello! Is there any single place where one could look for a list of device arguments that can be passed in --arg=... CL param [= to usrp_make() func]? From time to time I encounter one or the other of those here and there, but never succeeded to find them all in one place. If there isn't, can you please collect them in some convenient way? Particularly, I'm interesting if I can speed up the initial uhd_usrp_make(), specifying exact details of my hw config, for usrp_make() not to waste time on various auto-detection procedures. For example, if I don't have GPSDO, can I pass any parameter in device_args instructing not to search for it? Since I notice that it takes some time of approx. 1 second. What else (except IP and device type) can I specify to speed up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE connection? It would be great to have in such a list other interesting things as well, eg master clock setting, things like self_cal_adc_delay and similar 'fine tuning' stuff. Thank you! Vladimir
V
Vladimir
Fri, Aug 5, 2016 12:28 PM

Оn the same subject: can I instruct usrp_make() to skip any calibration/tests for the second channel (or even turn it off or tell it in some other way that I'm not using it), if I know that I'm planning to use only one (eg RX2) channel in this run? I mean if it's at all effective in minimizing the initialization time.

Vladimir

Пятница,  5 августа 2016, 15:10 +03:00 от Vladimir www2008_2@mail.ru:

Hello!

Is there any single place where one could look for a list of device arguments that can be passed in --arg=... CL param [= to usrp_make() func]? From time to time I encounter one or the other of those here and there, but never succeeded to find them all in one place. If there isn't, can you please collect them in some convenient way?

Particularly, I'm interesting if I can speed up the initial uhd_usrp_make(), specifying exact details of my hw config, for usrp_make() not to waste time on various auto-detection procedures. For example, if I don't have GPSDO, can I pass any parameter in device_args instructing not to search for it? Since I notice that it takes some time of approx. 1 second. What else (except IP and device type) can I specify to speed up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE connection?

It would be great to have in such a list other interesting things as well, eg master clock setting, things like  self_cal_adc_delay and similar 'fine tuning' stuff.

Thank you!
Vladimir

Оn the same subject: can I instruct usrp_make() to skip any calibration/tests for the second channel (or even turn it off or tell it in some other way that I'm not using it), if I know that I'm planning to use only one (eg RX2) channel in this run? I mean if it's at all effective in minimizing the initialization time. Vladimir >Пятница, 5 августа 2016, 15:10 +03:00 от Vladimir <www2008_2@mail.ru>: > >Hello! > >Is there any single place where one could look for a list of device arguments that can be passed in --arg=... CL param [= to usrp_make() func]? From time to time I encounter one or the other of those here and there, but never succeeded to find them all in one place. If there isn't, can you please collect them in some convenient way? > >Particularly, I'm interesting if I can speed up the initial uhd_usrp_make(), specifying exact details of my hw config, for usrp_make() not to waste time on various auto-detection procedures. For example, if I don't have GPSDO, can I pass any parameter in device_args instructing not to search for it? Since I notice that it takes some time of approx. 1 second. What else (except IP and device type) can I specify to speed up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE connection? > >It would be great to have in such a list other interesting things as well, eg master clock setting, things like self_cal_adc_delay and similar 'fine tuning' stuff. > >Thank you! >Vladimir
V
Vladimir
Mon, Aug 8, 2016 3:08 PM

Can anybody from Ettus at least say couple words on the reason of ignoring the question about cutting device start up time? Doesn't it make any sense? Even if this is impossible/requiring development efforts, please confirm it.

Surprising silence for this usually responsive list...

Vladimir

Пятница,  5 августа 2016, 15:28 +03:00 от Vladimir via USRP-users usrp-users@lists.ettus.com:

Оn the same subject: can I instruct usrp_make() to skip any calibration/tests for the second channel (or even turn it off or tell it in some other way that I'm not using it), if I know that I'm planning to use only one (eg RX2) channel in this run? I mean if it's at all effective in minimizing the initialization time.

Vladimir

Пятница,  5 августа 2016, 15:10 +03:00 от Vladimir < www2008_2@mail.ru >:

Hello!

Is there any single place where one could look for a list of device arguments that can be passed in --arg=... CL param [= to usrp_make() func]? From time to time I encounter one or the other of those here and there, but never succeeded to find them all in one place. If there isn't, can you please collect them in some convenient way?

Particularly, I'm interesting if I can speed up the initial uhd_usrp_make(), specifying exact details of my hw config, for usrp_make() not to waste time on various auto-detection procedures. For example, if I don't have GPSDO, can I pass any parameter in device_args instructing not to search for it? Since I notice that it takes some time of approx. 1 second. What else (except IP and device type) can I specify to speed up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE connection?

It would be great to have in such a list other interesting things as well, eg master clock setting, things like  self_cal_adc_delay and similar 'fine tuning' stuff.

Thank you!
Vladimir



Can anybody from Ettus at least say couple words on the reason of ignoring the question about cutting device start up time? Doesn't it make any sense? Even if this is impossible/requiring development efforts, please confirm it. Surprising silence for this usually responsive list... Vladimir >Пятница, 5 августа 2016, 15:28 +03:00 от Vladimir via USRP-users <usrp-users@lists.ettus.com>: > >Оn the same subject: can I instruct usrp_make() to skip any calibration/tests for the second channel (or even turn it off or tell it in some other way that I'm not using it), if I know that I'm planning to use only one (eg RX2) channel in this run? I mean if it's at all effective in minimizing the initialization time. > >Vladimir > > >>Пятница, 5 августа 2016, 15:10 +03:00 от Vladimir < www2008_2@mail.ru >: >> >>Hello! >> >>Is there any single place where one could look for a list of device arguments that can be passed in --arg=... CL param [= to usrp_make() func]? From time to time I encounter one or the other of those here and there, but never succeeded to find them all in one place. If there isn't, can you please collect them in some convenient way? >> >>Particularly, I'm interesting if I can speed up the initial uhd_usrp_make(), specifying exact details of my hw config, for usrp_make() not to waste time on various auto-detection procedures. For example, if I don't have GPSDO, can I pass any parameter in device_args instructing not to search for it? Since I notice that it takes some time of approx. 1 second. What else (except IP and device type) can I specify to speed up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE connection? >> >>It would be great to have in such a list other interesting things as well, eg master clock setting, things like self_cal_adc_delay and similar 'fine tuning' stuff. >> >>Thank you! >>Vladimir > > > >_______________________________________________ >USRP-users mailing list >USRP-users@lists.ettus.com >http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com 
M
mleech@ripnet.com
Mon, Aug 8, 2016 3:17 PM

This must have slipped past, sorry about that Vladimir.

The most effective thing is to always specify an explicit device
identifier in --args, which will bypass the discovery phase.  But in
terms of subsystem-by-subsystem bypass of initialization sequences,
there's nothing in support of that.

I'm guessing that you're asking this because you have a flow that you
want to "trigger", have it come up, do its job, and then exit.  And you
want this process to be as fast as possible.

Your best approach may be to have a flow running all the time, and use
some kind of external signalling to have it become "active" when you
need it.

On 2016-08-08 11:08, Vladimir via USRP-users wrote:

Can anybody from Ettus at least say couple words on the reason of ignoring the question about cutting device start up time? Doesn't it make any sense? Even if this is impossible/requiring development efforts, please confirm it.

Surprising silence for this usually responsive list...

Vladimir

Пятница, 5 августа 2016, 15:28 +03:00 от Vladimir via USRP-users usrp-users@lists.ettus.com:

Оn the same subject: can I instruct usrp_make() to skip any calibration/tests for the second channel (or even turn it off or tell it in some other way that I'm not using it), if I know that I'm planning to use only one (eg RX2) channel in this run? I mean if it's at all effective in minimizing the initialization time.

Vladimir

Пятница, 5 августа 2016, 15:10 +03:00 от Vladimir <www2008_2@mail.ru [1]>:

Hello!

Is there any single place where one could look for a list of device arguments that can be passed in --arg=... CL param [= to usrp_make() func]? From time to time I encounter one or the other of those here and there, but never succeeded to find them all in one place. If there isn't, can you please collect them in some convenient way?

Particularly, I'm interesting if I can speed up the initial uhd_usrp_make(), specifying exact details of my hw config, for usrp_make() not to waste time on various auto-detection procedures. For example, if I don't have GPSDO, can I pass any parameter in device_args instructing not to search for it? Since I notice that it takes some time of approx. 1 second. What else (except IP and device type) can I specify to speed up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE connection?

It would be great to have in such a list other interesting things as well, eg master clock setting, things like self_cal_adc_delay and similar 'fine tuning' stuff.

Thank you!
Vladimir


USRP-users mailing list
USRP-users@lists.ettus.com [2]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

This must have slipped past, sorry about that Vladimir. The most effective thing is to always specify an explicit device identifier in --args, which will bypass the discovery phase. But in terms of subsystem-by-subsystem bypass of initialization sequences, there's nothing in support of that. I'm guessing that you're asking this because you have a flow that you want to "trigger", have it come up, do its job, and then exit. And you want this process to be as fast as possible. Your best approach may be to have a flow running all the time, and use some kind of external signalling to have it become "active" when you need it. On 2016-08-08 11:08, Vladimir via USRP-users wrote: > Can anybody from Ettus at least say couple words on the reason of ignoring the question about cutting device start up time? Doesn't it make any sense? Even if this is impossible/requiring development efforts, please confirm it. > > Surprising silence for this usually responsive list... > > Vladimir > > Пятница, 5 августа 2016, 15:28 +03:00 от Vladimir via USRP-users <usrp-users@lists.ettus.com>: > > Оn the same subject: can I instruct usrp_make() to skip any calibration/tests for the second channel (or even turn it off or tell it in some other way that I'm not using it), if I know that I'm planning to use only one (eg RX2) channel in this run? I mean if it's at all effective in minimizing the initialization time. > > Vladimir > > Пятница, 5 августа 2016, 15:10 +03:00 от Vladimir <www2008_2@mail.ru [1]>: > > Hello! > > Is there any single place where one could look for a list of device arguments that can be passed in --arg=... CL param [= to usrp_make() func]? From time to time I encounter one or the other of those here and there, but never succeeded to find them all in one place. If there isn't, can you please collect them in some convenient way? > > Particularly, I'm interesting if I can speed up the initial uhd_usrp_make(), specifying exact details of my hw config, for usrp_make() not to waste time on various auto-detection procedures. For example, if I don't have GPSDO, can I pass any parameter in device_args instructing not to search for it? Since I notice that it takes some time of approx. 1 second. What else (except IP and device type) can I specify to speed up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE connection? > > It would be great to have in such a list other interesting things as well, eg master clock setting, things like self_cal_adc_delay and similar 'fine tuning' stuff. > > Thank you! > Vladimir > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com [2] > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com _______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com [2] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com Links: ------ [1] https://e.mail.ru/mailto:www2008_2@mail.ru [2] https://e.mail.ru/mailto:USRP-users@lists.ettus.com
MM
Marcus Müller
Mon, Aug 8, 2016 3:17 PM

Hi Vladimir,
sorry for being so silent on this; I meant to reply, and just forgot
about it.

So, no, we don't have a comprehensive table of options; just the common
options we list in [1]. Having such a table would be a good idea,
though, I agree.

Regarding speeding up the detection:

The most speedup will probably be attainable via
"type=x300,addr=IP.ADDRESS.OF.DEVICE" ; we don't really have much other
options. You could try to disable the "disable_adc_self_test" flag, but
I don't think that will gain much time.

Disabling GPSDO detection would actually be pretty easy to do; adding an
option to [3] would do that, but there's nothing in place to allow you
to disable it right now.

Best regards,
Marcus

[1] http://files.ettus.com/manual/page_configuration.html
[2]
https://github.com/EttusResearch/uhd/blob/master/host/lib/usrp/x300/x300_impl.cpp#L932
[3]
https://github.com/EttusResearch/uhd/blob/master/host/lib/usrp/x300/x300_impl.cpp#L856

On 08/08/2016 05:08 PM, Vladimir via USRP-users wrote:

Can anybody from Ettus at least say couple words on the reason of
ignoring the question about cutting device start up time? Doesn't it
make any sense? Even if this is impossible/requiring development
efforts, please confirm it.

Surprising silence for this usually responsive list...

Vladimir

 Пятница, 5 августа 2016, 15:28 +03:00 от Vladimir via USRP-users
 <usrp-users@lists.ettus.com>:

 Оn the same subject: can I instruct usrp_make() to skip any
 calibration/tests for the second channel (or even turn it off or
 tell it in some other way that I'm not using it), if I know that
 I'm planning to use only one (eg RX2) channel in this run? I mean
 if it's at all effective in minimizing the initialization time.

 Vladimir


     Пятница, 5 августа 2016, 15:10 +03:00 от Vladimir
     <www2008_2@mail.ru <mailto:www2008_2@mail.ru>>:

     Hello!

     Is there any single place where one could look for a list of
     device arguments that can be passed in --arg=... CL param [=
     to usrp_make() func]? From time to time I encounter one or the
     other of those here and there, but never succeeded to find
     them all in one place. If there isn't, can you please collect
     them in some convenient way?

     Particularly, I'm interesting if I can speed up the initial
     uhd_usrp_make(), specifying exact details of my hw config, for
     usrp_make() not to waste time on various auto-detection
     procedures. For example, if I don't have GPSDO, can I pass any
     parameter in device_args instructing not to search for it?
     Since I notice that it takes some time of approx. 1 second.
     What else (except IP and device type) can I specify to speed
     up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE
     connection?

     It would be great to have in such a list other interesting
     things as well, eg master clock setting, things like
     self_cal_adc_delay and similar 'fine tuning' stuff.

     Thank you!
     Vladimir




 _______________________________________________
 USRP-users mailing list
 USRP-users@lists.ettus.com <mailto:USRP-users@lists.ettus.com>
 http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com




USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Hi Vladimir, sorry for being so silent on this; I meant to reply, and just forgot about it. So, no, we don't have a comprehensive table of options; just the common options we list in [1]. Having such a table would be a good idea, though, I agree. Regarding speeding up the detection: The most speedup will probably be attainable via "type=x300,addr=IP.ADDRESS.OF.DEVICE" ; we don't really have much other options. You could try to disable the "disable_adc_self_test" flag, but I don't think that will gain much time. Disabling GPSDO detection would actually be pretty easy to do; adding an option to [3] would do that, but there's nothing in place to allow you to disable it right now. Best regards, Marcus [1] http://files.ettus.com/manual/page_configuration.html [2] https://github.com/EttusResearch/uhd/blob/master/host/lib/usrp/x300/x300_impl.cpp#L932 [3] https://github.com/EttusResearch/uhd/blob/master/host/lib/usrp/x300/x300_impl.cpp#L856 On 08/08/2016 05:08 PM, Vladimir via USRP-users wrote: > Can anybody from Ettus at least say couple words on the reason of > ignoring the question about cutting device start up time? Doesn't it > make any sense? Even if this is impossible/requiring development > efforts, please confirm it. > > Surprising silence for this usually responsive list... > > Vladimir > > Пятница, 5 августа 2016, 15:28 +03:00 от Vladimir via USRP-users > <usrp-users@lists.ettus.com>: > > Оn the same subject: can I instruct usrp_make() to skip any > calibration/tests for the second channel (or even turn it off or > tell it in some other way that I'm not using it), if I know that > I'm planning to use only one (eg RX2) channel in this run? I mean > if it's at all effective in minimizing the initialization time. > > Vladimir > > > Пятница, 5 августа 2016, 15:10 +03:00 от Vladimir > <www2008_2@mail.ru <mailto:www2008_2@mail.ru>>: > > Hello! > > Is there any single place where one could look for a list of > device arguments that can be passed in --arg=... CL param [= > to usrp_make() func]? From time to time I encounter one or the > other of those here and there, but never succeeded to find > them all in one place. If there isn't, can you please collect > them in some convenient way? > > Particularly, I'm interesting if I can speed up the initial > uhd_usrp_make(), specifying exact details of my hw config, for > usrp_make() not to waste time on various auto-detection > procedures. For example, if I don't have GPSDO, can I pass any > parameter in device_args instructing not to search for it? > Since I notice that it takes some time of approx. 1 second. > What else (except IP and device type) can I specify to speed > up initialization, if I use X300 + 1 UBX, w/o GPSDO over 10GBE > connection? > > It would be great to have in such a list other interesting > things as well, eg master clock setting, things like > self_cal_adc_delay and similar 'fine tuning' stuff. > > Thank you! > Vladimir > > > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com <mailto:USRP-users@lists.ettus.com> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > > > >  > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com