search

markondej / fm_transmitter

Raspberry Pi as FM transmitter
1.32k stars 292 forks source link

Not working on Raspberry Pi 4 #80

Closed stk122 closed 5 years ago

stk122 commented 5 years ago

I make the setup of FM Transmitter like I do in my old Rpi2 and simply not work. The command start ok, with the message:

_"pi@RPI4stk122:~ $ sudo /home/pi/fm_transmitter/./fm_transmitter -r -b 200 -f 90.6 /home/pi/fmtransmitter/musica/todas.wav"

_Broadcasting at 90.6 MHz with 200 kHz bandwidth Playing: /home/pi/fmtransmitter/musica/todas.wav, 44100 Hz, 16 bits, stereo

But not sound recibed on radio. If I put the same command in Rpi2 works fine. I put a wire in the same GPIO PIN 4, I disable 1-Wire on raspi-config, disable another conflictive modules with "sudo rmmod w1-gpio" and "sudo rmmod w1-therm", but it continue not working.

Any way to fix it? I don't know what else to try.

markondej commented 5 years ago

There is a bug for RPi 4 - peripherals address is set to 0. This bug is located in Raspberry Pi's inner libraries (https://www.raspberrypi.org/documentation/hardware/raspberrypi/peripheral_addresses.md). I will try to bypass this problem and publish solution as soon as possible (tomorow).

I beleive this will be fixed out of box also in upcoming Raspbian distros as there is a fix on RPi userland repository: https://github.com/raspberrypi/userland/commit/17d2fdc1abd370e09ba7074753294c7976dd6b0d

markondej commented 5 years ago

Fixed, problem was already reported, see issue #78

stk122 commented 5 years ago

Completely solved, really thank you, I used this with my radio alarm clock all 2019 and works fine, better than Pi-FM or PiFMRds, with a lower CPU consumption (4%).

Good job. You deserve a beer ;)

markondej commented 5 years ago

Nice to hear that, cheers :)

vssj322 commented 4 years ago

Mine is also not working

Missingfiles2021 commented 1 year ago

I found out a solution: 1.Make sure you overclock your CPU at least above 50 % and it should not be left at idle.

  1. Do /sudo rmmod w1-gpio This might sound the opposite of what the others are saying, but I'm just hoping for an update or a patch from the Raspberry Pi 4 devs to diagnose or fix this problem. As for now I'm speculating that it is a bug.