Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Raspberry Pi 3 support #14

Closed
xmikos opened this issue Mar 1, 2016 · 7 comments
Closed

Raspberry Pi 3 support #14

xmikos opened this issue Mar 1, 2016 · 7 comments

Comments

@xmikos
Copy link
Contributor

xmikos commented Mar 1, 2016

This is more of a question than an issue - do you think rpitx should work without modifications on new Raspberry Pi 3? Or if not, are you planning to add support for it?

CPU in RPi3 runs on higher frequency, so maybe rpitx should work better for transmitting on higher frequencies too?

@F5OEO
Copy link
Owner

F5OEO commented Mar 1, 2016

I wait for my pi 3 to test. So I cant' tell if rpitx works or not.
About higher frequency, I have maybe some ticks to get higher even on Raspberry 2 but not yet tested.

@tgeorgiop
Copy link

Do you have any news about raspberry pi 3?

@primeshp
Copy link

I have verified its working with Pi 3. Any news of this working on Pi Zero. I could not make it work

@E3V3A
Copy link

E3V3A commented Apr 17, 2016

@primeshp Any ideas/tests regarding the upper freq limit for PWM? (The old rp2 has about 125 MHz according to BCM2835 datasheet.)

@OutsourcedGuru
Copy link

Works great on my Raspberry Pi 3 Model B, pin 12, Raspbian Jessie (pretty sure it's the Lite version without the GUI). I don't think I had to sudo raspi-config to change the Interfacing Options for this to work. Pretty sure I did a sudo apt-get update, however, even after the install script for rpitx (which I think includes one at the top).

I managed to get it to stream realtime from a USB-based microphone, noting that my Radio Shack digital mic shows up as plughw:1, transmitting mono on FM 87.9 Mhz:

arecord -D plughw:1 -f S16_LE -r 48000 /dev/stdout 2> /dev/null | ./pifm /dev/stdin /dev/stdout | sudo ./rpitx -m RF -i /dev/stdin -f 87900

@OutsourcedGuru
Copy link

And btw, this project next will be ported over to a Raspberry Pi Zero W after the initial shake-down test so I should know more after testing this at the venue first to their 548.5 Mz—tuned Sennheiser receiver.

@abiank
Copy link

abiank commented Jun 4, 2017

On my unmodified Rpi3 with the latest jessie full the "main" output frequency is a bit off. For example using the provided sample wav file:

sudo ./rpitx -m RF -i fm.ft -f 429000 -l
rpitx Version 0.2 compiled Jun 4 2017 (F5OEO Evariste) running on Master PLL = 1000000000

Warning : Using harmonic 3
memory: 1024 MB
processor: Broadcom BCM2837
i2cDevice: /dev/i2c-1
model: Model B Pi 3
manufacturer: Sony
pcb revision: 2
warranty void: no
revision: a02082
peripheral base: 0x3f000000
Jessie
Using mbox device /dev/vcio.
3616000 Size NUM PAGES 883 PAGE_SIZE 4096
MASH 1 Freq PLL# 6
Calibrate : ppm=-7 DMA 175ns:1592ns
WaitNano=15908 F1=95331192.105386 TuneFrequency 95333298.665365 F2=95333410.915862 Initial Resolution(Hz)=2218.810476 ResolutionPWMF 24.653450 NbStep=90 DELAYStep=9
****** STARTING TRANSMIT ********

gives the following output as received by gqrx:

frequency is off

I ask for 429.000Mhz but I get the signal on 430.665500Mhz . The only thing that's remarkable about this pi3 is that it is connected to a non hdmi monitor; should i try another one?

I tried sudo -s echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor as suggested in issue #21 but it didn't help. Let me know if i can run any needed test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants