buffer overrun on raspberry pi

160 views
Skip to first unread message

Demian Ouspensky

unread,
Jul 8, 2015, 12:51:36 PM7/8/15
to gr-...@googlegroups.com
Hi, as discussed in this thread on github: https://github.com/ptrkrysik/gr-gsm/issues/72

So, I'm getting a buffer overrun apparently when I run airprobe_rt.py.  My exact sample rate reads 200000.052982 Hz, and I just get a continual 0000000000 being written to the terminal.  Can you explain the process of how I get this running?

Many thanks.

Piotr Krysik

unread,
Jul 8, 2015, 1:11:58 PM7/8/15
to gr-...@googlegroups.com
W dniu 08.07.2015 o 18:51, Demian Ouspensky pisze:
Hi,

After these zeros you get buffer overrun?
I don't know if Rasbery PI is stron enough to run current gr-gsm's
airprobe. Did you try to save some samples to a file and then process
them with airprobe_file.py?

--
Best Regards,
Piotr Krysik

Demian Ouspensky

unread,
Jul 8, 2015, 1:43:39 PM7/8/15
to gr-...@googlegroups.com, ptrk...@gmail.com
Ah, that would be a real shame if so - I haven't saved any to file yet, what arguments would you suggest to get a few useful samples to process?

Piotr Krysik

unread,
Jul 8, 2015, 3:27:52 PM7/8/15
to gr-...@googlegroups.com
W dniu 08.07.2015 o 19:43, Demian Ouspensky pisze:
I've posted short description and a tool for capturing raw signal here:
https://groups.google.com/forum/#!topic/gr-gsm/1C7LQCOgLEY

neoje...@gmail.com

unread,
Nov 13, 2015, 6:03:54 PM11/13/15
to gr-gsm
hi im having the same issue with my RPI i have set it up on a pc and it works great but on RPI 2 B+ it runs and shows the GUI and even shows the signal but starts putting out 000000000000000000 the sec i start it up i have been looking at the difference  on the two the one on the RPI said using "volk machine : neon_hardfp_orc" and on my amd 64 laptop it said "volk machine :sse4_a_64_orc" any help would be great

Tomcsányi Domonkos

unread,
Nov 14, 2015, 4:33:28 AM11/14/15
to neoje...@gmail.com, gr-gsm
The zeroes definitely mean buffer overrun. I think the Rpi is just simply not powerful enough. Maybe try to disable the GUI (you mean I guess the FFT/waterfall) to make the program less resource-hungry and see if that helps.

Cheers,
Domi

--
Otrzymujesz tę wiadomość, bo subskrybujesz grupę „gr-gsm” w Grupach dyskusyjnych Google.
Aby anulować subskrypcję tej grupy i przestać otrzymywać od niej wiadomości, wyślij e-maila na gr-gsm+un...@googlegroups.com.
Aby opublikować wpis w tej grupie, wyślij e-maila na gr-...@googlegroups.com.
Aby wyświetlić tę dyskusję w internecie, otwórz https://groups.google.com/d/msgid/gr-gsm/f56a3044-ac13-45fc-b026-76d878e9362a%40googlegroups.com.
Więcej opcji znajdziesz na https://groups.google.com/d/optout.

iron...@gmail.com

unread,
Jun 20, 2017, 4:47:04 AM6/20/17
to gr-gsm, neoje...@gmail.com
Hi, the problem seems has not to been resolved yet with or without GUI.
I'm running the grgsm_livemon on my BPI M2U (Raspbian OS) and I have the O's in the output from time to time (look screenshot).

Perhaps it relates to computer performance, but the processor is busy only on 80% or less (load average approximately 2.7).
Information about the hardware, system and installed software:
Hardware:
AllWinner R40 4x1500MHz (ARM Cortex-A7)
2G DDR3 SDRAM

System:
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"

Software:
GNU Radio Companion 3.7.10 installed from jessie-backports
gr-gsm installed from master branch using Installation on RaspberryPi 3 Wiki Guide.


How can I tune the gr-gsm for best performance?

What is the minimal hardware requirements for gr-gsm?


Thanks for any help.

Regards,
Olexandr

субота, 14 листопада 2015 р. 11:33:28 UTC+2 користувач Domonkos Tomcsanyi написав:

Cinaed Simson

unread,
Jun 22, 2017, 4:43:54 PM6/22/17
to gr-...@googlegroups.com
On 06/20/2017 01:47 AM, iron...@gmail.com wrote:
> Hi, the problem seems has not to been resolved yet with or without GUI.
> I'm running the grgsm_livemon on my BPI M2U (Raspbian OS) and I have the
> O's in the output from time to time (look screenshot
> <https://user-images.githubusercontent.com/4047895/27171374-f2fad1ba-51b9-11e7-9c6c-1bc06777e961.png>).
>
> Perhaps it relates to computer performance, but the processor is busy
> only on 80% or less (load average approximately 2.7).
> Information about the hardware, system and installed software:
> Hardware:
> |AllWinner R40 4x1500MHz (ARM Cortex-A7)|
> |2G DDR3 SDRAM|
>
> System:
> |PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"|
> |NAME="Raspbian GNU/Linux"|
> |VERSION_ID="8"|
> |VERSION="8 (jessie)"|
>
> Software:
> |GNU Radio Companion 3.7.10| installed from |jessie-backports|
> |gr-gsm| installed from master branch using |Installation on RaspberryPi
> 3| Wiki Guide.
>
>
> How can I tune the gr-gsm for best performance?

Are you using the GPIO pins on the rpi3 to receive or do you have a SDR
attached to the rpi3 with USB cable?

If you have an SDR attached to the rpi3, then post the gnuradio flow graph.

Also, this is off topic for gr-gsm - you should post the flow graph on
the gnuradio mailing list.

-- Cinaed
>> <https://groups.google.com/forum/#%21topic/gr-gsm/1C7LQCOgLEY>
>>
>> --
>> Best Regards,
>> Piotr Krysik
>>
>>
>> --
>> Otrzymujesz tę wiadomość, bo subskrybujesz grupę „gr-gsm” w
>> Grupach dyskusyjnych Google.
>> Aby anulować subskrypcję tej grupy i przestać otrzymywać od niej
>> wiadomości, wyślij e-maila na gr-gsm+un...@googlegroups.com.
>> Aby opublikować wpis w tej grupie, wyślij e-maila na
>> gr-...@googlegroups.com.
>> Aby wyświetlić tę dyskusję w internecie, otwórz
>> https://groups.google.com/d/msgid/gr-gsm/f56a3044-ac13-45fc-b026-76d878e9362a%40googlegroups.com
>> <https://groups.google.com/d/msgid/gr-gsm/f56a3044-ac13-45fc-b026-76d878e9362a%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> Więcej opcji znajdziesz na https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
> --
> You received this message because you are subscribed to the Google
> Groups "gr-gsm" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to gr-gsm+un...@googlegroups.com
> <mailto:gr-gsm+un...@googlegroups.com>.
> To post to this group, send email to gr-...@googlegroups.com
> <mailto:gr-...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/gr-gsm/8090c118-286b-4570-b87b-7579c377cfd5%40googlegroups.com
> <https://groups.google.com/d/msgid/gr-gsm/8090c118-286b-4570-b87b-7579c377cfd5%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

Piotr Krysik

unread,
Jul 8, 2017, 12:30:50 AM7/8/17
to gr-...@googlegroups.com
W dniu 20.06.2017 o 10:47, iron...@gmail.com pisze:
> Hi, the problem seems has not to been resolved yet with or without GUI.
> I'm running the grgsm_livemon on my BPI M2U (Raspbian OS) and I have the
> O's in the output from time to time (look screenshot
> <https://user-images.githubusercontent.com/4047895/27171374-f2fad1ba-51b9-11e7-9c6c-1bc06777e961.png>).
>
This looks like the computer isn't fast enough to process all data.

> How can I tune the gr-gsm for best performance?
You can try to decrease oversampling ratio (from 4 to 2). Probably
avoiding resampling might help as it consumes considerable chunk of
processor's time.

I can't think of other simple/quick solutions. If the problem load
caused by GSM Receiver block it would require optimization of it for
SIMD operations for your processor.

> What is the minimal hardware requirements for gr-gsm?
Answer to this question wasn't figured out by anyone yet.

Best Regards,
Piotr Krysik
Reply all
Reply to author
Forward
0 new messages