Something may have changedits so hard to keep up with testing. But
in pCP6.1 the RPI4 used a 64bit kernel with 32 bit userspace. In this
configuration, onboard audio did not work with mmap turned on. However
USB and i2s cards worked fine.
in pCP7, in 64bit system, it does now appear
paul- wrote:
> Squeezelite uses mmap by defaultthere are some cases with a 64bit
> kernel, where it doesnt work. Ive not been very successful setting
> their automatically.
Should I interpret your comment to mean that perhaps the fact 7.0.0
worked fine out of the box with mmap=1 when
Squeezelite uses mmap by defaultthere are some cases with a 64bit
kernel, where it doesnt work. Ive not been very successful setting
their automatically.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Just been doing a few more experiments.
Using piCorePlayer 6.1.0, I finally discovered that the critical step is
to change the fourth option on the ALSA output setting to 0. After
restarting squeezelite, everything just works, including the GPIO
toggling. No reboot required. Once I discovered
Headphones is the correct output for onboard audio in pCP7
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Jeff07971 wrote:
> I ALWAYS resize the fs to full sdcard capacity before doing anything
I did try that at one point, but it didn't seem to help.
Jeff07971 wrote:
> Maybe its ANY operation rather than changing O/P device
I guess that's possible.
Jeff07971 wrote:
> Edit2: I Used
Hi Cliveb
Glad you got it working, if by a long winded process !
However
> So it would seem that switching the audio output device is the crucial
> step that gets everything going.
> (I speculate that the reason others say "it just works" is perhaps
> because they had already set their output
OK, today the GPIO pin suddenly started working as desired, but I had no
idea which of the many things I fiddled with had done the trick.
So I've spent a lot of time experimenting, being very methodical to try
and find out what fixed it.
Here's what I found. Bear in mind this is on a RPi4
Just done some more experiments and wonder if the results might be at
all informative.
On the Pi4, I started with both the gpio-poweroff tweak and the
squeezelite power on/off option switched off.
I never touched the gpio-poweroff tweak during these tests.
Logged in via SSH, I checked the
paul- wrote:
> Turning the gpio-poweroff on then off would put things back in the
> default state. There is nothing special that needs to be done. However
> if two drivers are trying to claim the same GPIO, then things are
> unpredictable.
OK, thanks.
Q: is the gpio-poweroff option another
Turning the gpio-poweroff on then off would put things back in the
default state. There is nothing special that needs to be done. However
if two drivers are trying to claim the same GPIO, then things are
unpredictable.
You've mentioned a pi2 and a pi4, I really think you've been swapping
OK, there are some developments...
First of all, when browsing around I discovered this on the Tweaks
page:
32642
I wondered if this had anything to do with things, so I tried activating
the gpio-poweroff tweak (setting the pin to 13) and rebooted. But it
didn't seem to do anything.
I
cliveb wrote:
> This one:
>
> Stays at 3.27V at all times. (3.25V on the Pi4 I was trying before).
Its OK I thought that the pin might not be actively driven low, I tried
with my DMM and verified that it actaully is.
@Paul- Another command to be added to the "toolbox" !
@Cliveb What server
How many players do you have on your LMS, are you sure you are selecting
the correct player when toggling power?
There are 2 command line tools provided with pcp.
pcp-gpio (which will let you do simple things like toggle and output or
read an input.)
readall.sh (This is a simple shell script
Jeff07971 wrote:
> Just tried it on my Pi4 works and toggles fine, what meter are you using
> ?
>
> 32639
This one:
32641
Stays at 3.27V at all times. (3.25V on the Pi4 I was trying before).
+---+
|Filename: meter.jpg
cliveb wrote:
> I've just tried on a Pi2 with the same results: GPIO 13 remains high at
> all times.
> I must be missing something that's glaringly obvious.
Just tried it on my Pi4 works and toggles fine, what meter are you using
?
32639
Jeff07971 wrote:
> I Doubt it its fairly foolproof !
>
> I don't have any Pi4's as players, I'll burn a card and test on a Pi4
>
> Jeff
I've just tried on a Pi2 with the same results: GPIO 13 remains high at
all times.
I must be missing something that's glaringly obvious.
Transporter ->
cliveb wrote:
> OK, thanks.
> I've done exactly what you suggest and GPIO 13 (pin #33) stays
> obstinately on 3.25V whether the player is on or off.
> Have I done something stupid?
>
I Doubt it its fairly foolproof !
I don't have any Pi4's as players, I'll burn a card and test on a Pi4
Jeff
Jeff07971 wrote:
> Apart from setting the GPIO and the Active State (High or Low) in the
> Web settings page nothing else needs to be done.
>
> I use GPIO13 as its right next to 0v and I know its not used by my
> Hifiberry Hat
>
> Jeff
OK, thanks.
I've done exactly what you suggest and GPIO
cliveb wrote:
> OK, thanks. So GPIO 13 is physical pin #33.
> I don't have any HAT installed. This is a fresh piCorePlayer install
> with nothing added.
> Should the Squeezelite power on/off setting just work, or do I need to
> enable it somehow?
>
> Incidentally, is there a recommendation for
paul- wrote:
> BCM pin numbering. Which is the numbering almost everything uses.
> https://pinout.xyz/ Almost nowhere in software is physical pin numbering
> used.
>
> Are you sure nothing else is using GPIO 13? D9 you have a DAC Hat
> installed?
OK, thanks. So GPIO 13 is physical pin
> 1. The help for the setting says: "Squeezelite will toggle this GPIO
> when the Power On/Off button is pressed"
> I interpret this to mean that when I click the power button for the
> picoreplayer in the LMS web interface (and by extension, if I switch the
> player on/off using a Duet
BCM pin numbering. Which is the numbering almost everything uses.
https://pinout.xyz/
Almost nowhere is physical pin numbering used.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Jeff07971 wrote:
> Hi Cliveb,
>
> You don't actually have to do any scripting to do this its built into
> pCP (SL actually)
>
> I use Powerswitch3 for my SB3's and pCP built in for my pCP based
> players
>
> All drive 16A SSR's directly
>
> Jeff
>
> 32631
>
Well, my apologies for not
I think you made the best solution a lot more obvious than I did. :)
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forums.slimdevices.com/showthread.php?t=113507
cliveb wrote:
> Not sure which forum I should ask this in: here, 3rd party software,
> DIY?
>
> Anyhow, I'm setting out on a project to develop a plugin that will
> toggle a GPIO pin on a pi running piCorePlayer.
> This is to replicate the behaviour of the old PowerSwitchII plugin on
>
piCore/Tiny Core uses Extensions, see pCP GUI [Main page] >
[Extensions].
This kind of thing has already been done many times.
You can access GPIO directly from userspace or use one of the many
libraries.
wiringPi is depreciated.
In /home/tc there are a couple of scripts to look at.
You could do all that with a shell script. But assuming you want
python. It is available, as well as the python rpio package.
Take a look at the extension page from the main menu.
If you don't find what you are looking for, ask. We don't package
everything, but alot of commonly used stuff
28 matches
Mail list logo
