usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

Re: [USRP-users] building ise project file on windows

JB
Josh Blum
Fri, Aug 19, 2011 9:33 PM

On 08/19/2011 02:13 PM, Nemanja Trecakov wrote:

Sorry, I tried the command 'gmake'(not 'gnumake') in command promt while in top\usrp2 folder in order to build the image.
Is this the correct way to run gnumake?

On linux, i type "make proj" in the top level directory to make the ise
project file. I'm not sure what the binary is called when you install
gnumake. What files were installed on you system? Best guesses: make,
gmake, or gnumake

-josh

  1. When I installed gnumake, I got a binary in C:\Program Files\GnuWin32\bin called 'make'. However, when I write 'make' in the command promt, I get this:

C:\USRP2_fpga_NEMO\usrp2\top\USRP2>make
'make' is not recognized as an internal or external command,
operable program or batch file.

Well, is make.exe in your %PATH%?

  1. I have tried again with 'gmake' command to make project, but I get the same error as before - 'head' is not recognized and no rule to make target.

The head error should be ok to have. Its a test for ise version to
determine file extension. Since it fails it will default to xise

C:\USRP2_fpga_NEMO\usrp2\top\USRP2>gmake proj
'head' is not recognized as an internal or external command,
operable program or batch file.
gmake: *** No rule to make target C:/USRP2_fpga_NEMO/usrp2/top/USRP2/C:/USRP2_f pga_NEMO/usrp2/fifo/buffer_int.v', needed by C:/USRP2_fpga_NEMO/usrp2/top/USRP2
/build/u2_rev3.xise'.  Stop.

Looks like a prefix is getting appended to a full/non-relative path. Its
got to be an issue in this line and lines like it in the Makefiles.srcs
files:

FIFO_SRCS = $(abspath $(addprefix $(BASE_DIR)/../fifo/, \

-josh

On 08/19/2011 02:13 PM, Nemanja Trecakov wrote: > > >>> >>> Sorry, I tried the command 'gmake'(not 'gnumake') in command promt while in top\usrp2 folder in order to build the image. >>> Is this the correct way to run gnumake? >>> >> >> On linux, i type "make proj" in the top level directory to make the ise >> project file. I'm not sure what the binary is called when you install >> gnumake. What files were installed on you system? Best guesses: make, >> gmake, or gnumake >> >> -josh > > 1) When I installed gnumake, I got a binary in C:\Program Files\GnuWin32\bin called 'make'. However, when I write 'make' in the command promt, I get this: > > C:\USRP2_fpga_NEMO\usrp2\top\USRP2>make > 'make' is not recognized as an internal or external command, > operable program or batch file. > > Well, is make.exe in your %PATH%? > 2) I have tried again with 'gmake' command to make project, but I get the same error as before - 'head' is not recognized and no rule to make target. > The head error should be ok to have. Its a test for ise version to determine file extension. Since it fails it will default to xise > C:\USRP2_fpga_NEMO\usrp2\top\USRP2>gmake proj > 'head' is not recognized as an internal or external command, > operable program or batch file. > gmake: *** No rule to make target `C:/USRP2_fpga_NEMO/usrp2/top/USRP2/C:/USRP2_f > pga_NEMO/usrp2/fifo/buffer_int.v', needed by `C:/USRP2_fpga_NEMO/usrp2/top/USRP2 > /build/u2_rev3.xise'. Stop. > Looks like a prefix is getting appended to a full/non-relative path. Its got to be an issue in this line and lines like it in the Makefiles.srcs files: FIFO_SRCS = $(abspath $(addprefix $(BASE_DIR)/../fifo/, \ -josh
KZ
Kyle Zhou
Sat, Aug 20, 2011 2:15 PM

I tried to use usrp1 on my macbook with uhd driver.
Installed the latest uhd with images 003.002.002
uhd_find_device works, loading firmware ok and returning the serial no.
how ever uhd_usrp_probe failed to probe the device, loading fpga seems ok, but after that it hanged up.
An interesting thing I noticed is once the fpga is loaded, the usrp1 becomes unrecognized by the mac.
uhd_find_device no longer finds the device after that.
Seems to me fpga image is the cause?

I tried to use usrp1 on my macbook with uhd driver. Installed the latest uhd with images 003.002.002 uhd_find_device works, loading firmware ok and returning the serial no. how ever uhd_usrp_probe failed to probe the device, loading fpga seems ok, but after that it hanged up. An interesting thing I noticed is once the fpga is loaded, the usrp1 becomes unrecognized by the mac. uhd_find_device no longer finds the device after that. Seems to me fpga image is the cause?
KZ
Kyle Zhou
Mon, Aug 22, 2011 12:28 PM

On 21/08/2011, at 12:15 AM, Kyle Zhou wrote:

I tried to use usrp1 on my macbook with uhd driver.
Installed the latest uhd with images 003.002.002
uhd_find_device works, loading firmware ok and returning the serial no.
how ever uhd_usrp_probe failed to probe the device, loading fpga seems ok, but after that it hanged up.
An interesting thing I noticed is once the fpga is loaded, the usrp1 becomes unrecognized by the mac.
uhd_find_device no longer finds the device after that.
Seems to me fpga image is the cause?


Following the above problem, I dug a bit deeper and found out the problem only happens when I have two  daughterboards plugged in at the same time, DBSRX on RX A and TVRX on RX B.
If I remove either of them, things are all good.
This is ok since I do not need two boards at any one time. But just need to leave the box uncovered to change boards from time to time.
It is interesting that libusrp works well with the same hardware (two boards installed).

On 21/08/2011, at 12:15 AM, Kyle Zhou wrote: > I tried to use usrp1 on my macbook with uhd driver. > Installed the latest uhd with images 003.002.002 > uhd_find_device works, loading firmware ok and returning the serial no. > how ever uhd_usrp_probe failed to probe the device, loading fpga seems ok, but after that it hanged up. > An interesting thing I noticed is once the fpga is loaded, the usrp1 becomes unrecognized by the mac. > uhd_find_device no longer finds the device after that. > Seems to me fpga image is the cause? > _______________________________________________ Following the above problem, I dug a bit deeper and found out the problem only happens when I have two daughterboards plugged in at the same time, DBSRX on RX A and TVRX on RX B. If I remove either of them, things are all good. This is ok since I do not need two boards at any one time. But just need to leave the box uncovered to change boards from time to time. It is interesting that libusrp works well with the same hardware (two boards installed).