Thanks Rob.

I have registered the issue in https://github.com/EttusResearch/uhd/issues/367 
and nagged their support email.

Andreas.

From: Rob Kossler <rkoss...@nd.edu>
Sent: 25. august 2020 15:59
To: Bertheussen, Andreas <andreas.bertheus...@kongsberg.com>
Cc: usrp-users <usrp-users@lists.ettus.com>
Subject: Re: [USRP-users] Issues with multi-usrp and UHD

Hi Andreas,
You might want to verify that benchmark_rate also misbehaves if you use 
"--ref=external --pps=external". I wasn't able to do this because I don't have 
an external reference handy. Regarding reporting of the bug, you could do so 
with gihub as you suggested, but I have been lazy in the past and just sent an 
email to "supp...@ettus.com<mailto:supp...@ettus.com>". This generally just 
causes them to create the issue.

Regarding UHD logging, take a look at this 
link<https://urldefense.com/v3/__https:/files.ettus.com/manual/log_8hpp.html*loghpp_logging__;Iw!!L8f3-wPVSng!S9U4pGFMepWOhBZhYhMgM4Eo2h_07u38lX5tJPAyLiWoNH0NpuAgOZuZcxpPHq1XSw3UQgcn0A$>.
 Below are the commands I used in Ubuntu prior to running the program.  This 
capability should work with any program that uses UHD including your custom 
program. For my own custom program, I also use the UHD logging commands in my 
source code such as UHD_LOGGER_INFO() and UHD_LOGGER_DEBUG() to print messages 
to the user rather than using std::cout.

export UHD_LOG_LEVEL=trace
export UHD_LOG_CONSOLE_LEVEL=trace
export UHD_LOG_FILE_LEVEL=trace
export UHD_LOG_FILE=uhd.log

Rob

On Tue, Aug 25, 2020 at 8:21 AM 
<andreas.bertheus...@kongsberg.com<mailto:andreas.bertheus...@kongsberg.com>> 
wrote:
Rob

I ran benchmark_rate --args=="addr0=192.168.10.2,addr1=192.168.110.2" --tx_rate 
5e6 --tx_channels="0,2"
And I observed the same issue I described earlier – mostly that ether channels 
0,1   or channels  2,3, or very rarely channels 0,2 get enabled.
When I add “skip_dram=1” to args, the channel mapping is correct! It is prone 
to underruns but now I can proceed a bit further with my UHD software.

How did you make the trace log? And did you do it to my program or to the 
benchmark_rate program?

It is definitely a severe issue I would expect to be fixed, so I will report 
it. Is creating a Github issue the proper avenue?

Many thanks for helping track this down, Rob!

Regards,
Andreas.


________________________________

CONFIDENTIALITY
This e-mail and any attachment contain KONGSBERG information which may be 
proprietary, confidential or subject to export regulations, and is only meant 
for the intended recipient(s). Any disclosure, copying, distribution or use is 
prohibited, if not otherwise explicitly agreed with KONGSBERG. If received in 
error, please delete it immediately from your system and notify the sender 
properly.
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Reply via email to