Send USRP-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."
Today's Topics:
1. Fwd: GNURadio USRP Tablet (Jeevake Attapattu)
2. Re: E110 - Detects 63MB RAM in lieu of 512 MB (Marcus M?ller)
3. Re: Fwd: GNURadio USRP Tablet (Marcus M?ller)
4. Re: E110 - Detects 63MB RAM in lieu of 512 MB (Brais Ares)
5. Re: E110 - Detects 63MB RAM in lieu of 512 MB (Marcus M?ller)
6. Re: Fwd: GNURadio USRP Tablet (Timothy Schaffer)
7. Re: E110 - Detects 63MB RAM in lieu of 512 MB (Philip Balister)
8. Tx Streaming using 3.8.1 (Robert Kossler)
9. Re: Tx Streaming using 3.8.1 (Marcus M?ller)
10. Re: E110 - Detects 63MB RAM in lieu of 512 MB (Brais Ares)
11. FW: Fwd: GNURadio USRP Tablet (Ralph A. Schmid, dk5ras)
----------------------------------------------------------------------
Message: 1
Date: Tue, 16 Dec 2014 21:23:24 -0800
From: Jeevake Attapattu <[email protected]>
To: [email protected]
Subject: [USRP-users] Fwd: GNURadio USRP Tablet
Message-ID:
<CAOGtvEQ=i_cybonqc2ba5vhr3ztcpazxnbweszwjw_ojbq1...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
To whom it may concern,
My name is Jeevake. I am an senior undergraduate in electrical and computer
engineering. I plan on using the USRP B200 for my senior design project.
The end product needs to be portable. I intend on using a tablet to ensure
portability.
My question is; what kind of hard ware & software could i run GNURadio and
UHD with? Does it have to be a CISC processor? Will an android or Windows
RT work as a host OS?
Yours sincerely,
Jeevake Attapattu.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141216/b753b997/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 17 Dec 2014 18:13:48 +0100
From: Marcus M?ller <[email protected]>
To: Brais Ares <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] E110 - Detects 63MB RAM in lieu of 512 MB
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi Brais,
Philip asked me to ask you: could you share the contents of
/proc/cmdline, ie. the output of cat /proc/cmdline?
Greetings,
Marcus
On 12/17/2014 04:56 PM, Brais Ares wrote:
> Here you go, I used PuTTY instead:
>
> https://dl.dropboxusercontent.com/u/2696878/bootlog.txt
>
> It's weird because it seems to recognize the 512 MB DRAM when booting...
>
> Thank you again.
> Regards.
>
> 2014-12-17 16:06 GMT+01:00 Marcus M?ller <[email protected]
> <mailto:[email protected]>>:
>
> Hello Brais,
>
> uh oh. I'd ask to do one more thing: can you connect a PC to the
> serial console USB port [1] and boot the device, and give us the
> output (at least the beginning)?
> For that, you would run (assuming the serial converter in the E110
> appears as /dev/ttyUSB0 on your PC)
>
> screen -L /dev/ttyUSB0 115200,cs8,-ixon,-ixoff
>
> and get the screenlog.* of that run in the folder that you ran
> screen in. To exit screen, press ctrl+a, then k, then confirm.
>
>
> Greetings,
> Marcus
>
>
> [1]http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/FAQ#How-do-I-connect-through-the-console-port
>
> On 12/16/2014 11:39 PM, Brais Ares wrote:
>> Hello Marcus,
>>
>> In order to discard that possibility, apart from switching Overo
>> boards, I also tried to only switch SD cards. I've got one SD
>> Card working flawless in the other E110, but putting it into the
>> faulty usrp, RAM goes down to 61 MB as well.
>>
>> Regards,
>> Brais.
>>
>>
>> 2014-12-16 20:19 GMT+01:00 Marcus M?ller
>> <[email protected] <mailto:[email protected]>>:
>>
>> Hello Brais,
>>
>> have you tried putting a clean image on the SD card? This
>> could also be caused by something wrong with the way the
>> operating system is loaded.
>>
>> Greetings,
>> Marcus
>>
>> On 12/16/2014 08:05 PM, Brais Ares via USRP-users wrote:
>>> Sorry,
>>>
>>> All i said applied to USRPs E110.
>>>
>>> 2014-12-16 19:58 GMT+01:00 Brais Ares <[email protected]
>>> <mailto:[email protected]>>:
>>>
>>> Hello,
>>>
>>> I'm having trouble with one of my N210. It only detects
>>> 63 MB of RAM as you can see in this pic, when this value
>>> ought to be 512 MB:
>>>
>>> https://dl.dropboxusercontent.com/u/2696878/usrpram.jpg
>>>
>>> The RAM that's still left is not even enough to compile
>>> a small program so that gcc throws an error.
>>>
>>> I moved the small PCB where the SD Card and processor
>>> are to a healthy N210, and it's not healthy anymore, so
>>> the problem seems to be this small PCB.
>>>
>>> I would appreciate any advice about this.
>>>
>>> Regards,
>>> Brais.
>>>
>>> --
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> [email protected] <mailto:[email protected]>
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>>
>> _______________________________________________
>> USRP-users mailing list
>> [email protected] <mailto:[email protected]>
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>>
>>
>> --
>>
>
>
>
> --
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141217/d051d4a5/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 17 Dec 2014 18:35:22 +0100
From: Marcus M?ller <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Fwd: GNURadio USRP Tablet
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Hi Jeevake,
UHD runs on a lot of systems -- basically, as long as you have a proper
windows, a GNU/Linux environment or Mac OS X, you should be able to get
UHD to run. The processor architecture itself is of minor importance --
for example, UHD runs very well on our embedded devices, which sport ARM
processors.
GNU Radio is generally as portable. Anything that behaves a bit like a
POSIX-compliant OS should do, and Windows should, too. Most GNU Radio
devs are using Linux or OS X [1], and it will be easiest to get helpful
hints for these platforms. GNU Radio should run on any CPU architecture.
I don't want to talk too much about GNU Radio on Android, but it might
be something to be available in the future ;)
So, basically, you're not really very limited by the platform itself.
However, there are some consideration to be made:
USB3 is necessary for any sample rate >8MS/s. This limits the number of
viable Android tablets drastically. Also, not all USB3 controllers are
created equally. Some behave so strangely that you can't use the B200
them, others deliver limited maximum rates. See [2].
Also, and this is the larger aspect of the whole "which tablet to use":
You're going to do real time digital signal processing at megasample
rates. This means that your CPU simply *can't be powerful enough*. Ok,
if you're going to do 4MS/s without much latency constraints, doing
nothing but displaying a abs(FFT) every few seconds, your smartphone
might be powerful enough. But doing a 101-tap FIR at 16MS/s, followed by
some correlation detector, or whatever complex application you might
have in mind, requires serious processing power.
All in all: I'd start off with a desktop computer, build my application.
If it works, analyze CPU consumption, and choose a platform that easily
handles that load. Pay attention to the fact that GNU Radio is heavily
optimized for x86 with SIMD instructions (SSE and so on), and your
non-CISC platform might simply need more instructions to do the same thing.
Greetings,
Marcus
[1] very personal observation. I could be totally wrong.
[2]
http://www.ettus.com/kb/detail/usrp-b200-and-b210-usb-30-streaming-rate-benchmarks
On 12/17/2014 06:23 AM, Jeevake Attapattu via USRP-users wrote:
>
> To whom it may concern,
>
> My name is Jeevake. I am an senior undergraduate in electrical and
> computer engineering. I plan on using the USRP B200 for my senior
> design project. The end product needs to be portable. I intend on
> using a tablet to ensure portability.
>
> My question is; what kind of hard ware & software could i run GNURadio
> and UHD with? Does it have to be a CISC processor? Will an android or
> Windows RT work as a host OS?
>
> Yours sincerely,
> Jeevake Attapattu.
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141217/eeffa8ba/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 17 Dec 2014 18:38:42 +0100
From: Brais Ares <[email protected]>
To: Marcus M?ller <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] E110 - Detects 63MB RAM in lieu of 512 MB
Message-ID:
<CAJcStAj8Ua=6-emj1tz+fxcjxjspuakajwso5z+lcdqdf1b...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Here,
The flawed one returns:
> console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60
omapfb.debug=y mem=80M omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw
rootfstype=ext3 rootwait buddy=
The healthy one returns:
> console=ttyO2,115200n8 mpurate=720 vram=12M
omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2
rw rootfstype=ext3 rootwait
Thank you again.
Regards.
2014-12-17 18:13 GMT+01:00 Marcus M?ller <[email protected]>:
>
> Hi Brais,
> Philip asked me to ask you: could you share the contents of /proc/cmdline,
> ie. the output of cat /proc/cmdline?
>
> Greetings,
> Marcus
>
>
> On 12/17/2014 04:56 PM, Brais Ares wrote:
>
> Here you go, I used PuTTY instead:
>
> https://dl.dropboxusercontent.com/u/2696878/bootlog.txt
>
> It's weird because it seems to recognize the 512 MB DRAM when booting...
>
> Thank you again.
> Regards.
>
> 2014-12-17 16:06 GMT+01:00 Marcus M?ller <[email protected]>:
>>
>> Hello Brais,
>>
>> uh oh. I'd ask to do one more thing: can you connect a PC to the serial
>> console USB port [1] and boot the device, and give us the output (at least
>> the beginning)?
>> For that, you would run (assuming the serial converter in the E110
>> appears as /dev/ttyUSB0 on your PC)
>>
>> screen -L /dev/ttyUSB0 115200,cs8,-ixon,-ixoff
>>
>> and get the screenlog.* of that run in the folder that you ran screen in.
>> To exit screen, press ctrl+a, then k, then confirm.
>>
>>
>> Greetings,
>> Marcus
>>
>> [1]
>> http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/FAQ#How-do-I-connect-through-the-console-port
>>
>> On 12/16/2014 11:39 PM, Brais Ares wrote:
>>
>> Hello Marcus,
>>
>> In order to discard that possibility, apart from switching Overo boards,
>> I also tried to only switch SD cards. I've got one SD Card working flawless
>> in the other E110, but putting it into the faulty usrp, RAM goes down to 61
>> MB as well.
>>
>> Regards,
>> Brais.
>>
>>
>> 2014-12-16 20:19 GMT+01:00 Marcus M?ller <[email protected]>:
>>>
>>> Hello Brais,
>>>
>>> have you tried putting a clean image on the SD card? This could also be
>>> caused by something wrong with the way the operating system is loaded.
>>>
>>> Greetings,
>>> Marcus
>>>
>>> On 12/16/2014 08:05 PM, Brais Ares via USRP-users wrote:
>>>
>>> Sorry,
>>>
>>> All i said applied to USRPs E110.
>>>
>>> 2014-12-16 19:58 GMT+01:00 Brais Ares <[email protected]>:
>>>>
>>>> Hello,
>>>>
>>>> I'm having trouble with one of my N210. It only detects 63 MB of RAM
>>>> as you can see in this pic, when this value ought to be 512 MB:
>>>>
>>>> https://dl.dropboxusercontent.com/u/2696878/usrpram.jpg
>>>>
>>>> The RAM that's still left is not even enough to compile a small
>>>> program so that gcc throws an error.
>>>>
>>>> I moved the small PCB where the SD Card and processor are to a healthy
>>>> N210, and it's not healthy anymore, so the problem seems to be this small
>>>> PCB.
>>>>
>>>> I would appreciate any advice about this.
>>>>
>>>> Regards,
>>>> Brais.
>>>>
>>>> --
>>>>
>>>>
>>>
>>> --
>>>
>>>
>>>
>>> _______________________________________________
>>> USRP-users mailing
>>> [email protected]http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>>
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> [email protected]
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>>
>>
>> --
>>
>>
>>
>
> --
>
>
>
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141217/3e3f5931/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 17 Dec 2014 18:59:45 +0100
From: Marcus M?ller <[email protected]>
To: Brais Ares <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] E110 - Detects 63MB RAM in lieu of 512 MB
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi Brais,
I'm no expert in this, but the mem=80M looks suspicious.
I was under the impression that the problem was bound to the Overo (the
gumstick-sized board containing the CPU and SD card slot), but that boot
line should be coming from the installation on the SD Card, so I need to
confirm this:
the problem doesn't "stick" to a SD card image, but to the Overo itself,
right?
Greetings,
Marcus
On 12/17/2014 06:38 PM, Brais Ares wrote:
> Here,
>
> The flawed one returns:
> > console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60
> omapfb.debug=y mem=80M omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw
> rootfstype=ext3 rootwait buddy=
>
> The healthy one returns:
> > console=ttyO2,115200n8 mpurate=720 vram=12M
> omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi
> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
>
> Thank you again.
> Regards.
>
> 2014-12-17 18:13 GMT+01:00 Marcus M?ller <[email protected]
> <mailto:[email protected]>>:
>
> Hi Brais,
> Philip asked me to ask you: could you share the contents of
> /proc/cmdline, ie. the output of cat /proc/cmdline?
>
> Greetings,
> Marcus
>
>
> On 12/17/2014 04:56 PM, Brais Ares wrote:
>> Here you go, I used PuTTY instead:
>>
>> https://dl.dropboxusercontent.com/u/2696878/bootlog.txt
>>
>> It's weird because it seems to recognize the 512 MB DRAM when
>> booting...
>>
>> Thank you again.
>> Regards.
>>
>> 2014-12-17 16:06 GMT+01:00 Marcus M?ller
>> <[email protected] <mailto:[email protected]>>:
>>
>> Hello Brais,
>>
>> uh oh. I'd ask to do one more thing: can you connect a PC to
>> the serial console USB port [1] and boot the device, and give
>> us the output (at least the beginning)?
>> For that, you would run (assuming the serial converter in the
>> E110 appears as /dev/ttyUSB0 on your PC)
>>
>> screen -L /dev/ttyUSB0 115200,cs8,-ixon,-ixoff
>>
>> and get the screenlog.* of that run in the folder that you
>> ran screen in. To exit screen, press ctrl+a, then k, then
>> confirm.
>>
>>
>> Greetings,
>> Marcus
>>
>>
>> [1]http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/FAQ#How-do-I-connect-through-the-console-port
>>
>> On 12/16/2014 11:39 PM, Brais Ares wrote:
>>> Hello Marcus,
>>>
>>> In order to discard that possibility, apart from switching
>>> Overo boards, I also tried to only switch SD cards. I've got
>>> one SD Card working flawless in the other E110, but putting
>>> it into the faulty usrp, RAM goes down to 61 MB as well.
>>>
>>> Regards,
>>> Brais.
>>>
>>>
>>> 2014-12-16 20:19 GMT+01:00 Marcus M?ller
>>> <[email protected]
>>> <mailto:[email protected]>>:
>>>
>>> Hello Brais,
>>>
>>> have you tried putting a clean image on the SD card?
>>> This could also be caused by something wrong with the
>>> way the operating system is loaded.
>>>
>>> Greetings,
>>> Marcus
>>>
>>> On 12/16/2014 08:05 PM, Brais Ares via USRP-users wrote:
>>>> Sorry,
>>>>
>>>> All i said applied to USRPs E110.
>>>>
>>>> 2014-12-16 19:58 GMT+01:00 Brais Ares
>>>> <[email protected] <mailto:[email protected]>>:
>>>>
>>>> Hello,
>>>>
>>>> I'm having trouble with one of my N210. It only
>>>> detects 63 MB of RAM as you can see in this pic,
>>>> when this value ought to be 512 MB:
>>>>
>>>> https://dl.dropboxusercontent.com/u/2696878/usrpram.jpg
>>>>
>>>> The RAM that's still left is not even enough to
>>>> compile a small program so that gcc throws an error.
>>>>
>>>> I moved the small PCB where the SD Card and
>>>> processor are to a healthy N210, and it's not
>>>> healthy anymore, so the problem seems to be this
>>>> small PCB.
>>>>
>>>> I would appreciate any advice about this.
>>>>
>>>> Regards,
>>>> Brais.
>>>>
>>>> --
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> USRP-users mailing list
>>>> [email protected] <mailto:[email protected]>
>>>>
>>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>>
>>> _______________________________________________
>>> USRP-users mailing list
>>> [email protected]
>>> <mailto:[email protected]>
>>>
>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>
>>>
>>>
>>> --
>>>
>>
>>
>>
>> --
>>
>
>
>
> --
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141217/8f2b4253/attachment-0001.html>
------------------------------
Message: 6
Date: Wed, 17 Dec 2014 13:00:16 -0500
From: Timothy Schaffer <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Fwd: GNURadio USRP Tablet
Message-ID:
<CACx9bDrEvogqxFj=vqmic6de+9osesspkt49fkiwpwcmrsn...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hate to say it depends, but it depends on your application.
There's an excellent guide here:
http://discourse.criticalengineering.org/t/howto-gsm-base-station-with-the-beaglebone-black-debian-gnu-linux-and-a-usrp/56
which describes using a USRP B200 and a Beagle Bone Black to run OpenBTS.
It's not straightforward, but not too difficult, it is however much easier
(and faster) than on a raspberry pi.
If you're willing to write some HDL you could roll your own firmware and do
all the processing in the FPGA (there was just a thread about this
yesterday or the day prior) and then just use the tablet as a display.
Depending on your application, you might want to look into an Intel NUC
together with a touch screen. You can find NUCs with USB 3.0 to give you a
high sample rate if required, but it's small enough to be portable...not
sure what your definition of portable is though.
If you're set on a tablet there's a number of programs that already exist
for the RTL-SDRs that can connect to any android device via USB-OTG. This
would be limited to a single antenna receive only application however.
I hope this helps. Can you elaborate on your project if possible?
-Tim
On Wed, Dec 17, 2014 at 12:23 AM, Jeevake Attapattu via USRP-users <
[email protected]> wrote:
>
>
> To whom it may concern,
>
> My name is Jeevake. I am an senior undergraduate in electrical and
> computer engineering. I plan on using the USRP B200 for my senior design
> project. The end product needs to be portable. I intend on using a tablet
> to ensure portability.
>
> My question is; what kind of hard ware & software could i run GNURadio and
> UHD with? Does it have to be a CISC processor? Will an android or Windows
> RT work as a host OS?
>
> Yours sincerely,
> Jeevake Attapattu.
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141217/38ec8408/attachment-0001.html>
------------------------------
Message: 7
Date: Wed, 17 Dec 2014 14:41:12 -0500
From: Philip Balister <[email protected]>
To: Marcus M?ller <[email protected]>, Brais Ares
<[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] E110 - Detects 63MB RAM in lieu of 512 MB
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
On 12/17/2014 12:59 PM, Marcus M?ller via USRP-users wrote:
> Hi Brais,
>
> I'm no expert in this, but the mem=80M looks suspicious.
> I was under the impression that the problem was bound to the Overo (the
> gumstick-sized board containing the CPU and SD card slot), but that boot
> line should be coming from the installation on the SD Card, so I need to
> confirm this:
> the problem doesn't "stick" to a SD card image, but to the Overo itself,
> right?
OK, since you have an overo with NAND flash, u-boot is reading the
cmdline from NAND flash. It is likely someone was doing some DSP work
and used the mem= option to reserve memory for the DSP.
You can reset the u-boot environment by clearing the NAND memory where
the environment is stored.
See step 4 at:
http://gumstix.org/getting-started-guide/243-booting-your-gumstix-system.html
The default environment from the u-boot binary should then let you
access all RAM. Thanks for your patience as we worked through this.
Philip
>
> Greetings,
> Marcus
>
> On 12/17/2014 06:38 PM, Brais Ares wrote:
>> Here,
>>
>> The flawed one returns:
>>> console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60
>> omapfb.debug=y mem=80M omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw
>> rootfstype=ext3 rootwait buddy=
>>
>> The healthy one returns:
>>> console=ttyO2,115200n8 mpurate=720 vram=12M
>> omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi
>> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
>>
>> Thank you again.
>> Regards.
>>
>> 2014-12-17 18:13 GMT+01:00 Marcus M?ller <[email protected]
>> <mailto:[email protected]>>:
>>
>> Hi Brais,
>> Philip asked me to ask you: could you share the contents of
>> /proc/cmdline, ie. the output of cat /proc/cmdline?
>>
>> Greetings,
>> Marcus
>>
>>
>> On 12/17/2014 04:56 PM, Brais Ares wrote:
>>> Here you go, I used PuTTY instead:
>>>
>>> https://dl.dropboxusercontent.com/u/2696878/bootlog.txt
>>>
>>> It's weird because it seems to recognize the 512 MB DRAM when
>>> booting...
>>>
>>> Thank you again.
>>> Regards.
>>>
>>> 2014-12-17 16:06 GMT+01:00 Marcus M?ller
>>> <[email protected] <mailto:[email protected]>>:
>>>
>>> Hello Brais,
>>>
>>> uh oh. I'd ask to do one more thing: can you connect a PC to
>>> the serial console USB port [1] and boot the device, and give
>>> us the output (at least the beginning)?
>>> For that, you would run (assuming the serial converter in the
>>> E110 appears as /dev/ttyUSB0 on your PC)
>>>
>>> screen -L /dev/ttyUSB0 115200,cs8,-ixon,-ixoff
>>>
>>> and get the screenlog.* of that run in the folder that you
>>> ran screen in. To exit screen, press ctrl+a, then k, then
>>> confirm.
>>>
>>>
>>> Greetings,
>>> Marcus
>>>
>>>
>>> [1]http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/FAQ#How-do-I-connect-through-the-console-port
>>>
>>> On 12/16/2014 11:39 PM, Brais Ares wrote:
>>>> Hello Marcus,
>>>>
>>>> In order to discard that possibility, apart from switching
>>>> Overo boards, I also tried to only switch SD cards. I've got
>>>> one SD Card working flawless in the other E110, but putting
>>>> it into the faulty usrp, RAM goes down to 61 MB as well.
>>>>
>>>> Regards,
>>>> Brais.
>>>>
>>>>
>>>> 2014-12-16 20:19 GMT+01:00 Marcus M?ller
>>>> <[email protected]
>>>> <mailto:[email protected]>>:
>>>>
>>>> Hello Brais,
>>>>
>>>> have you tried putting a clean image on the SD card?
>>>> This could also be caused by something wrong with the
>>>> way the operating system is loaded.
>>>>
>>>> Greetings,
>>>> Marcus
>>>>
>>>> On 12/16/2014 08:05 PM, Brais Ares via USRP-users wrote:
>>>>> Sorry,
>>>>>
>>>>> All i said applied to USRPs E110.
>>>>>
>>>>> 2014-12-16 19:58 GMT+01:00 Brais Ares
>>>>> <[email protected] <mailto:[email protected]>>:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I'm having trouble with one of my N210. It only
>>>>> detects 63 MB of RAM as you can see in this pic,
>>>>> when this value ought to be 512 MB:
>>>>>
>>>>> https://dl.dropboxusercontent.com/u/2696878/usrpram.jpg
>>>>>
>>>>> The RAM that's still left is not even enough to
>>>>> compile a small program so that gcc throws an error.
>>>>>
>>>>> I moved the small PCB where the SD Card and
>>>>> processor are to a healthy N210, and it's not
>>>>> healthy anymore, so the problem seems to be this
>>>>> small PCB.
>>>>>
>>>>> I would appreciate any advice about this.
>>>>>
>>>>> Regards,
>>>>> Brais.
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> USRP-users mailing list
>>>>> [email protected] <mailto:[email protected]>
>>>>>
>>>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>>
>>>>
>>>> _______________________________________________
>>>> USRP-users mailing list
>>>> [email protected]
>>>> <mailto:[email protected]>
>>>>
>>>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>
>>>
>>>
>>> --
>>>
>>
>>
>>
>> --
>>
>
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 8
Date: Wed, 17 Dec 2014 15:46:48 -0500
From: Robert Kossler <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] Tx Streaming using 3.8.1
Message-ID:
<cab__htr4g-kvmfcf2b+nhrf08hzkc26tnde32mujqsz4fjg...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi,
With my X310 (CBX-120), I've noticed some unexpected behavior with version
3.8.1 driver/FPGA. I'm suspecting that this version made some changes with
respect to TX streaming levels. I have a "tx_samples_from_file" custom app
that repeatedly sends the same fixed length sequence (initially read from
the file). I seem to be getting both of the following:
1) higher output power
2) significant compression (non-linear output) unless I scale all the
values by about 0.5.
My plan was to role back to the previous version to confirm, but I confess
that I don't know the best way to do so. I'm not particularly adept with
either git or Linux in general. I presently compile from source after
doing a "git pull" on the master branch. What is the best/easiest way to
test versus a previous version?
Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141217/b5a960f8/attachment-0001.html>
------------------------------
Message: 9
Date: Wed, 17 Dec 2014 22:08:34 +0100
From: Marcus M?ller <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Tx Streaming using 3.8.1
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Hi Robert,
you can use "git checkout <tagname/branchname>" to get a specific
version of UHD; to get a list of tagnames, "git tag"; they correspond to
the official releases. You can go back to master by checking out master.
To get you can have as many build directories as you want, they don't
have to be called "build", by the way, so when switching back, you're
not re-building everything.
Greetings,
Marcus
On 12/17/2014 09:46 PM, Robert Kossler via USRP-users wrote:
> Hi,
> With my X310 (CBX-120), I've noticed some unexpected behavior with
> version 3.8.1 driver/FPGA. I'm suspecting that this version made some
> changes with respect to TX streaming levels. I have a
> "tx_samples_from_file" custom app that repeatedly sends the same fixed
> length sequence (initially read from the file). I seem to be getting
> both of the following:
> 1) higher output power
> 2) significant compression (non-linear output) unless I scale all the
> values by about 0.5.
>
> My plan was to role back to the previous version to confirm, but I
> confess that I don't know the best way to do so. I'm not particularly
> adept with either git or Linux in general. I presently compile from
> source after doing a "git pull" on the master branch. What is the
> best/easiest way to test versus a previous version?
>
> Rob
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141217/c539db19/attachment-0001.html>
------------------------------
Message: 10
Date: Thu, 18 Dec 2014 10:08:02 +0100
From: Brais Ares <[email protected]>
To: Philip Balister <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] E110 - Detects 63MB RAM in lieu of 512 MB
Message-ID:
<CAJcStAjc0U00KXuPOvxQ=dqzlkrp4wxbomwovh+7zqwh1o3...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Wow, it worked! We lent this USRP for a couple of years so someone else
must've been messing around with the NAND flash.
Thank you both once again. It's always a pleasure to use these email lists.
Greetings,
Brais.
2014-12-17 20:41 GMT+01:00 Philip Balister <[email protected]>:
>
> On 12/17/2014 12:59 PM, Marcus M?ller via USRP-users wrote:
> > Hi Brais,
> >
> > I'm no expert in this, but the mem=80M looks suspicious.
> > I was under the impression that the problem was bound to the Overo (the
> > gumstick-sized board containing the CPU and SD card slot), but that boot
> > line should be coming from the installation on the SD Card, so I need to
> > confirm this:
> > the problem doesn't "stick" to a SD card image, but to the Overo itself,
> > right?
>
> OK, since you have an overo with NAND flash, u-boot is reading the
> cmdline from NAND flash. It is likely someone was doing some DSP work
> and used the mem= option to reserve memory for the DSP.
>
> You can reset the u-boot environment by clearing the NAND memory where
> the environment is stored.
>
> See step 4 at:
>
>
> http://gumstix.org/getting-started-guide/243-booting-your-gumstix-system.html
>
> The default environment from the u-boot binary should then let you
> access all RAM. Thanks for your patience as we worked through this.
>
> Philip
>
>
> >
> > Greetings,
> > Marcus
> >
> > On 12/17/2014 06:38 PM, Brais Ares wrote:
> >> Here,
> >>
> >> The flawed one returns:
> >>> console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60
> >> omapfb.debug=y mem=80M omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw
> >> rootfstype=ext3 rootwait buddy=
> >>
> >> The healthy one returns:
> >>> console=ttyO2,115200n8 mpurate=720 vram=12M
> >> omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi
> >> root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
> >>
> >> Thank you again.
> >> Regards.
> >>
> >> 2014-12-17 18:13 GMT+01:00 Marcus M?ller <[email protected]
> >> <mailto:[email protected]>>:
> >>
> >> Hi Brais,
> >> Philip asked me to ask you: could you share the contents of
> >> /proc/cmdline, ie. the output of cat /proc/cmdline?
> >>
> >> Greetings,
> >> Marcus
> >>
> >>
> >> On 12/17/2014 04:56 PM, Brais Ares wrote:
> >>> Here you go, I used PuTTY instead:
> >>>
> >>> https://dl.dropboxusercontent.com/u/2696878/bootlog.txt
> >>>
> >>> It's weird because it seems to recognize the 512 MB DRAM when
> >>> booting...
> >>>
> >>> Thank you again.
> >>> Regards.
> >>>
> >>> 2014-12-17 16:06 GMT+01:00 Marcus M?ller
> >>> <[email protected] <mailto:[email protected]>>:
> >>>
> >>> Hello Brais,
> >>>
> >>> uh oh. I'd ask to do one more thing: can you connect a PC to
> >>> the serial console USB port [1] and boot the device, and give
> >>> us the output (at least the beginning)?
> >>> For that, you would run (assuming the serial converter in the
> >>> E110 appears as /dev/ttyUSB0 on your PC)
> >>>
> >>> screen -L /dev/ttyUSB0 115200,cs8,-ixon,-ixoff
> >>>
> >>> and get the screenlog.* of that run in the folder that you
> >>> ran screen in. To exit screen, press ctrl+a, then k, then
> >>> confirm.
> >>>
> >>>
> >>> Greetings,
> >>> Marcus
> >>>
> >>> [1]
> http://code.ettus.com/redmine/ettus/projects/usrpe1xx/wiki/FAQ#How-do-I-connect-through-the-console-port
> >>>
> >>> On 12/16/2014 11:39 PM, Brais Ares wrote:
> >>>> Hello Marcus,
> >>>>
> >>>> In order to discard that possibility, apart from switching
> >>>> Overo boards, I also tried to only switch SD cards. I've got
> >>>> one SD Card working flawless in the other E110, but putting
> >>>> it into the faulty usrp, RAM goes down to 61 MB as well.
> >>>>
> >>>> Regards,
> >>>> Brais.
> >>>>
> >>>>
> >>>> 2014-12-16 20:19 GMT+01:00 Marcus M?ller
> >>>> <[email protected]
> >>>> <mailto:[email protected]>>:
> >>>>
> >>>> Hello Brais,
> >>>>
> >>>> have you tried putting a clean image on the SD card?
> >>>> This could also be caused by something wrong with the
> >>>> way the operating system is loaded.
> >>>>
> >>>> Greetings,
> >>>> Marcus
> >>>>
> >>>> On 12/16/2014 08:05 PM, Brais Ares via USRP-users wrote:
> >>>>> Sorry,
> >>>>>
> >>>>> All i said applied to USRPs E110.
> >>>>>
> >>>>> 2014-12-16 19:58 GMT+01:00 Brais Ares
> >>>>> <[email protected] <mailto:[email protected]>>:
> >>>>>
> >>>>> Hello,
> >>>>>
> >>>>> I'm having trouble with one of my N210. It only
> >>>>> detects 63 MB of RAM as you can see in this pic,
> >>>>> when this value ought to be 512 MB:
> >>>>>
> >>>>>
> https://dl.dropboxusercontent.com/u/2696878/usrpram.jpg
> >>>>>
> >>>>> The RAM that's still left is not even enough to
> >>>>> compile a small program so that gcc throws an error.
> >>>>>
> >>>>> I moved the small PCB where the SD Card and
> >>>>> processor are to a healthy N210, and it's not
> >>>>> healthy anymore, so the problem seems to be this
> >>>>> small PCB.
> >>>>>
> >>>>> I would appreciate any advice about this.
> >>>>>
> >>>>> Regards,
> >>>>> Brais.
> >>>>>
> >>>>> --
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> USRP-users mailing list
> >>>>> [email protected] <mailto:
> [email protected]>
> >>>>>
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> USRP-users mailing list
> >>>> [email protected]
> >>>> <mailto:[email protected]>
> >>>>
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>>
> >>
> >>
> >>
> >> --
> >>
> >
> >
> >
> >
> > _______________________________________________
> > USRP-users mailing list
> > [email protected]
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
> >
>
>
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141218/6ea8a36e/attachment-0001.html>
------------------------------
Message: 11
Date: Thu, 18 Dec 2014 11:31:44 +0100
From: "Ralph A. Schmid, dk5ras" <[email protected]>
To: "'usrp-users'" <[email protected]>
Subject: [USRP-users] FW: Fwd: GNURadio USRP Tablet
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
I am using a MS Surface pro Windows 8.1 tablet with i7 CPU (so this is a
real PC in tablet shape), and Gnuradio has no problems in using up the CPU
power at 100%...
Ralph.
From: USRP-users [ <mailto:[email protected]>
mailto:[email protected]] On Behalf Of Marcus M?ller via
USRP-users
Sent: Wednesday, December 17, 2014 6:35 PM
To: <mailto:[email protected]> [email protected]
Subject: Re: [USRP-users] Fwd: GNURadio USRP Tablet
Hi Jeevake,
UHD runs on a lot of systems -- basically, as long as you have a proper
windows, a GNU/Linux environment or Mac OS X, you should be able to get UHD
to run. The processor architecture itself is of minor importance -- for
example, UHD runs very well on our embedded devices, which sport ARM
processors.
GNU Radio is generally as portable. Anything that behaves a bit like a
POSIX-compliant OS should do, and Windows should, too. Most GNU Radio devs
are using Linux or OS X [1], and it will be easiest to get helpful hints for
these platforms. GNU Radio should run on any CPU architecture. I don't want
to talk too much about GNU Radio on Android, but it might be something to be
available in the future ;)
So, basically, you're not really very limited by the platform itself.
However, there are some consideration to be made:
USB3 is necessary for any sample rate >8MS/s. This limits the number of
viable Android tablets drastically. Also, not all USB3 controllers are
created equally. Some behave so strangely that you can't use the B200 them,
others deliver limited maximum rates. See [2].
Also, and this is the larger aspect of the whole "which tablet to use":
You're going to do real time digital signal processing at megasample rates.
This means that your CPU simply *can't be powerful enough*. Ok, if you're
going to do 4MS/s without much latency constraints, doing nothing but
displaying a abs(FFT) every few seconds, your smartphone might be powerful
enough. But doing a 101-tap FIR at 16MS/s, followed by some correlation
detector, or whatever complex application you might have in mind, requires
serious processing power.
All in all: I'd start off with a desktop computer, build my application. If
it works, analyze CPU consumption, and choose a platform that easily handles
that load. Pay attention to the fact that GNU Radio is heavily optimized for
x86 with SIMD instructions (SSE and so on), and your non-CISC platform might
simply need more instructions to do the same thing.
Greetings,
Marcus
[1] very personal observation. I could be totally wrong.
[2]
http://www.ettus.com/kb/detail/usrp-b200-and-b210-usb-30-streaming-rate-benc
hmarks
On 12/17/2014 06:23 AM, Jeevake Attapattu via USRP-users wrote:
To whom it may concern,
My name is Jeevake. I am an senior undergraduate in electrical and computer
engineering. I plan on using the USRP B200 for my senior design project. The
end product needs to be portable. I intend on using a tablet to ensure
portability.
My question is; what kind of hard ware & software could i run GNURadio and
UHD with? Does it have to be a CISC processor? Will an android or Windows RT
work as a host OS?
Yours sincerely,
Jeevake Attapattu.
_______________________________________________
USRP-users mailing list
[email protected] <mailto:[email protected]>
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141218/a91869b9/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
End of USRP-users Digest, Vol 52, Issue 20
******************************************
