[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Details on Ettus E100?

From: Matt Ettus
Subject: Re: [Discuss-gnuradio] Details on Ettus E100?
Date: Tue, 14 Dec 2010 09:32:05 -0800
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20101027 Fedora/3.0.10-1.fc12 Lightning/1.0b2pre Thunderbird/3.0.10

On 12/14/2010 08:34 AM, Douglas Geiger wrote:
  Thanks Matt - that's very helpful. Interesting in that the Gumstix
configures the FPGA. I see the fpga-downloader program in
host/lib/usrp/usrp_e100 that does the work, and presumably with the
stock linux distribution you're shipping it has the image file in some
default location, and it looks like the uhd driver calls a magic
find_image_path function to find it.


Are you all working on an
E-Series Application Note like the rather nice ones already existent
for the USRP1/2/N-series? Perhaps you could include some notes for
those of us who would want to create a custom distro image for our
E100's.Do you plan to share/host a repository of the default distro
loaded on the Gumstix? Are you using Angstrom to build that image?

We have based our distro on Angstron and OpenEmbedded. The vast majority of packages come from the standard repositories, and we have our UHD and kernel driver work added to that.

As a side note it looks like there is no aeMB/microblaze loaded in the
fpga for the e100 (at least not in the fpga/usrp2/top/u1e directory,
which I assume is the correct place to look), so no firmware file to
create/load - which also presumably leaves more room for DSP work,

There is no aeMB so there is no firmware in the sense that we have on the USRP2. The OMAP fulfills that role because it has direct low-latency bus access to the FPGA. The FPGA can directly interrupt the CPU as well.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]