Hi Marcus,

Thanks for the reply.

I believe this is not a power problem as the B210 was fed with an external
power.
The problem still thrives, any further suggestions are more than welcomed.

BR,
Steve

On Thu, Jun 24, 2021 at 7:28 PM Marcus D. Leech <patchvonbr...@gmail.com>
wrote:

> On 06/24/2021 02:31 AM, shachar J. brown wrote:
>
> Hi everyone,
>
> I am trying to run the given tx_samples_from_file example.
> Unfortunately, I keep receiving the uhd::usb_error, approximately 5-30
> minutes into the run.
>
> *Technical specs:*
> USRP: B210.
> Host: Intel Nuc, Core i7, 8th gen.
> OS: Ubuntu 20
> UHD Version: 4.1.0
> USB Controler: XHCI (USB3).
>
>
> *Error print: *
> [ERROR] [TX-STREAM] The tx_stream timed out sending 5000 samples (4080
> sent).
> [ERROR] [UHD] An unexpected exception was caught in a task loop.The task
> loop will now exit, things may not work.EnvironmentError: IOError: usb rx8
> transfer status: LIBUSB_TRANSFER_NO_DEVICE
> terminate called after throwing an instance of 'uhd::usb_error'
>   what():  RuntimeError: USBError -4: usb tx4 submit failed:
> LIBUSB_ERROR_NO_DEVICE
> Aborted (core dumped)
>
>
> *dmesg output: *
> [19924.922965] usb 4-2: USB disconnect, device number 7
> [19925.195595] usb 4-2: new SuperSpeed Gen 1 USB device number 8 using
> xhci_hcd
> [19925.217437] usb 4-2: LPM exit latency is zeroed, disabling LPM.
> [19925.220417] usb 4-2: New USB device found, idVendor=2500,
> idProduct=0020, bcdDevice= 0.00
> [19925.220422] usb 4-2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [19925.220426] usb 4-2: Product: USRP B200
> [19925.220429] usb 4-2: Manufacturer: Ettus Research LLC
> [19925.220431] usb 4-2: SerialNumber: 31F80A2
>
> Is anyone familiar with this fault?
> I would appreciate any help on the matter.
>
> Thanks in advance,
> Steve
>
>
> My guess is that your NUC USB controller is unhappy with power
> consumption.    Are you using external power on the B2xx, or relying
>   on USB3 power?
>
> Also, several years ago, there was an interaction between certain
> controllers and kernel power-saving features that caused the
>   controller to disconnect stuff even if it was being used.  But I can't
> for the live of me remember which driver parameter one
>   had to change to fix this.  It has been several years since this was a
> problem.
>
>
> _______________________________________________
> USRP-users mailing list -- usrp-users@lists.ettus.com
> To unsubscribe send an email to 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