Thanks Ron,

However, I too think GIT is Arcane :-) ...

Doing that (git checkout v3.15.0.0 -b tmp) creates a new local err... branch, repo... called tmp.

How do I get the contents of the requested branch/tag up onto my machine?
It's not a branch, doing a git pull results in...
"
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=origin/<branch> tmp
"
Originally cloning the UHD repo results in one being on the Master branch, i.e.
 "git clone https://github.com/EttusResearch/uhd.git";
so how does one revert back to an earlier release please?

Hope you can help, sorry for my noob git knowledge!

Cheers,
Dave






On 12/09/2020 00:02, Ron Economos via USRP-users wrote:

Yes, it's not a problem. If you don't want to see the message, use:

git checkout v3.15.0.0 -b tmp

Also, you should never use the master branch of UHD. It's really a development branch and could be unstable. Always use a release tag.

To see all the release tags:

git tag

Ron

On 9/11/20 10:38, Marcus D Leech via USRP-users wrote:
That should be fine.

GIT is arcane. Others have more facility with it than I.

Sent from my iPhone

On Sep 11, 2020, at 12:07 PM, David Evans via USRP-users <usrp-users@lists.ettus.com> wrote:

 Thanks Marcus,

Sorry,, I know this isn't the place, but when i check out a version I get "detached head...". I also don't want to check anything back in, do I ignore this (I've never understood what detached head means, even after looking it up!).

Cheers,
Dave

On 10/09/2020 16:43, Marcus D. Leech via USRP-users wrote:
On 09/10/2020 08:55 AM, David Evans via USRP-users wrote:
Hi,
I have just installed the latest "master" branch of UHD (4.0.0.0).

If an overrun occurs during sampling, sampling does not continue thereafter. I noticed this with uhd_fft, which hangs with rates over 8MHz, and also rx_samples_to_file:

./rx_samples_to_file --freq 900000000 --rate 40000000

Creating the usrp device with: ...
[INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-34-g2655b0aa
[INFO] [B200] Detected Device: B200mini
[INFO] [B200] Operating over USB 3.
[INFO] [B200] Initialize CODEC control...
[INFO] [B200] Initialize Radio control...
[INFO] [B200] Performing register loopback test...
[INFO] [B200] Register loopback test passed
[INFO] [B200] Setting master clock rate selection to 'automatic'.
[INFO] [B200] Asking for clock rate 16.000000 MHz...
[INFO] [B200] Actually got clock rate 16.000000 MHz.
Using Device: Single USRP:
  Device: B-Series Device
  Mboard 0: B200mini
  RX Channel: 0
    RX DSP: 0
    RX Dboard: A
    RX Subdev: FE-RX1
  TX Channel: 0
    TX DSP: 0
    TX Dboard: A
    TX Subdev: FE-TX1

Setting RX Rate: 40.000000 Msps...
[INFO] [B200] Asking for clock rate 40.000000 MHz...
[INFO] [B200] Actually got clock rate 40.000000 MHz.
Actual RX Rate: 40.000000 Msps...

Setting RX Freq: 900.000000 MHz...
Setting RX LO Offset: 0.000000 MHz...
Actual RX Freq: 900.000000 MHz...

Waiting for "lo_locked": ++++++++++ locked.

Press Ctrl + C to stop streaming...
OGot an overflow indication. Please consider the following:
  Your write medium must sustain a rate of 160.000000MB/s.
  Dropped samples will not be written to the file.
  Please modify this example for your purposes.
  This message will not appear again.
*Timeout while streaming*

Done!

Any ideas please?
Should I be using the master branch, if not how do I checkout a stable branch ?

Thanks,
Dave


You can get a list of tagged versions using:

git tag

Try again with:

git checkout   v3.15.0.0

Sometimes when the overruns are persistent and at very high rates, the software is unable to recover, because so much information has been   dropped, any recovery procedure would be roughly as drastic as having to re-start.



_______________________________________________
USRP-users mailing list
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

_______________________________________________
USRP-users mailing list
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

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

Reply via email to