Hi Josh,
thanks for your answer. Anyway if the UHD makes trouble because of the USRP2 than I decided to build my own UHD.dll from source code with MSVC 2008. I set in CMake environment that I don't want to include USRP2 stuff into the UHD driver (it won't look for USRP2 devices only for USRP1 devices on USB). I installed BOOST. I compiled the UHD, I got the DLL and utils files (uhd_usrp_probe and uhd_find_devices), I copied the DLL to location C:\program files (x86)\uhd\bin and the LIB file to location C:\program files (x86)\uhd\lib (both from D:\uhd\host\build\lib\Release\) but it's not working, so the problem is due to paths. I downloaded UHD source code to D:\uhd. Maybe I set wrong some parameters in CMake.
Do you have any idea regarding this?
Thanks,
Mark.
From: Josh Blum <address@hidden>
To: Mark Colin <address@hidden>
Cc: address@hidden
Sent: Thu, April 28, 2011 9:05:44 AM
Subject: Re: Error when using UHD, GRC
On 04/27/2011 02:34 PM, Mark Colin wrote:
> Hi,
>
> OK, the uhd_find_devices --args="type=usrp1" is working, there's no device
> discovery error message, but when I tried to run the uhd_usrp_probe
> --args="type=usrp1" the uhd_usrp_probe broke down giving a nice error message:
>
> "uhd_usrp_probe.exe has encountered a problem and needs to close. We are sorry
> for the inconvenience."
>
The last time I saw this, was
when I learned that the libusb callbacks
needed to be defined w/ a different calling convention. If you got UHD
from this installer then I don't know the problem:
http://www.ettus.com/downloads/uhd_releases/003_000_001/UHD-003.000.001-win32-with-LIBUSB_CALL-fix.exe
> If I disconnect from the Internet (I have internet connection on PPPOE) then I
> don't get any error when running uhd_find_devices.exe instead when I
> run uhd_usrp_probe.exe I get the mentioned error. I even tried to disable Local
> Area Network, and VirtualBox Network, but the error is there.
>
If I read your message right, then it seems that the interaction between
PPPOE and UHD may be the culprit. But it wasnt consistent between find
and probe? but I would expect them to behave identically.
> I tried many packet sniffer (TCP, UDP) programs but there's no data transfer (I
> couldn't find any packet sent by UHD)
when running uhd_usrp_probe
> --args="type=usrp1" therefore it might be some error in the test
> program uhd_usrp_probe before sending out any packet.
>
It may be the act of opening up a socket on that interface for broadcast.
>
> What could be the problem?
>
Windows is that nosey neighbor who always manages to get into your house
at those awkward moments; even though you know you locked the door.
-Josh