sh1ntomi wrote:
> Thanks Paul and Chicks.
>
> I have not soldered GPIO pins to the Zero2W but I am using Pimoroni's
> hammer header pin and I suspect this could be the issue?!
>
> For now I have connected a ZeroWh I had lying around. This seems to be
> working fine for both the RasPiOS and pCP
sh1ntomi wrote:
> Thanks Paul and Chicks.
>
>
>
> For now I have connected a ZeroWh I had lying around. This seems to be
> working fine for both the RasPiOS and pCP options. I am trying to get
> another Zero2W ready (hopefully with soldering - I have to admit I am
> not good at soldering
Thanks Paul and Chicks.
I have not soldered GPIO pins to the Zero2W but I am using Pimoroni's
hammer header pin and I suspect this could be the issue?!
For now I have connected a ZeroWh I had lying around. This seems to be
working fine for both the RasPiOS and pCP options. I am trying to get
The latest 5.15 kernels actually have new vc4 based hyperpixel overlays,
but your settings seem to make sense, even though you have a duplicated
dpi_output_format. I think the latter is the one that gets used by the
firmware.
I looked at at my 02W, and I have not even put a header on it
paul- wrote:
> Just curious, have you check to see if the screen works with RaspiOS and
> the 02W? I have a 02W, but just lacking time to try it out on my HP4.
Working fine here on Zero 2W running RaspiOS Buster. Haven't tried
upgrading to latest release of RaspiOS.
piTouch™ w/JustBoom
Just curious, have you check to see if the screen works with RaspiOS and
the 02W? I have a 02W, but just lacking time to try it out on my HP4.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
paul- wrote:
> Are you using the correct config.txt settings for the board, as pi4's
> use different settings that pi0-3?
Hi,
Yes, these are two different installations (SD cards) and different
config.txt. I used Raspi OS for the P14B to verify the issue is not with
the screen. For the Pi
Are you using the correct config.txt settings for the board, as pi4's
use different settings that pi0-3?
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
paul- wrote:
> The touch is connected to GPIO, and the display device is there.
>
> Check the tweaks page on the pCP interface to make sure Jivelite is
> using fb0
>
> You might try adding to your config.txt
>
> dtoverlay=vc4-kms-v3d
>
> And comment out the gpu_mem line
Thanks Paul.
The touch is connected to GPIO, and the display device is there.
Check the tweaks page on the pCP interface to make sure Jivelite is
using fb0
You might try adding to your config.txt
dtoverlay=vc4-kms-v3d
And comment out the gpu_mem line
piCorePlayer a small player for the Raspberry Pi in
paul- wrote:
> dmesg might be helpful.
>
> Is there a framebuffer device created?
Hi Paul,
Thanks.
I see fb0 is created:
tc@pCP:~$ ls -l /dev/fb*
crw-rw1 root staff 29, 0 Jan 1 1970 /dev/fb0
dmesg might be helpful.
Is there a framebuffer device created?
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Hi
I am trying to get Jivelite working on Pi Zero 2w and a Hyperpixel
rectangular touchscreen. I followed the steps at
https://github.com/piCorePlayer/hyperpixel4 by ssh (no HDMI).
All I get is a glowing screen with no startup screen or jivelite display
perhaps similar to @thewebgal. I have
I found the bug! Directions said to install the Hyperpixel settings at
the bottom of the config.txt file - but it actually goes between 2
comment lines just before the very bottom.
Once I figured that out, I had the basics, and with some fine tuning,
its running great!
36464
36465
Working through the steps to setup pCP and LMS on a raspberry Pi 4.
No problem creating the Sd card, no problems ssh-ing into the system.
I've gotten that working, but have not gotten the hyperPixel 4 display
working with it.
I can connect via Wifi and a browser, but the display never does
Just wanted to say a big thank you for pCP and the Hyperpixel4 work. I
now have pCP and a Hyperpixel4 that didn't work out on another project
in service as my study music player.
Many thanks.
stuaburt's Profile:
Cheers both that's cracked it!
I was getting there in that I spoted the typo but not the backup
Thanks
garym999's Profile: http://forums.slimdevices.com/member.php?userid=4943
View this thread:
Its funny how your brain just reads right over the typo. Even reading
your message, It took 3 reads to find the typo
/mnt/mmcblk0p2/tce/hp4-init is the correct location.
"pcp bu" is a shortcut to backup
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage:
Hi simon,
your message has just come in as i was finding this out. Well the
/mnt/mmcblk0p2/tce/hp4-init p2 part.
I'll carry on now as per your steps and see how it goes
garym999's Profile:
After typing in the right extension it still did not work for me.
I then looked at the diagnostics in the pi and checked I'd followed the
instructions correctly from github
I eventually discovered that this was incorrect
/mnt/mmcblk0p1/tce/hp4-init
it was
/mnt/mmcblk0p2/tce/hp4-init
I then
Forget jivelite for a second. Lets check the screen setup/init
process. (Make sure you did step 4)
Code:
Add /mnt/mmcblk0p1/tce/hp4-init to /opt/bootlocal.sh (Add it before pCP
startup)
If you did this out of sequence(i.e. after
Did you keep the ssh/console session dialogue?
If yes you could post it here.
Otherwise ... post the contents of
/mnt/mmcblk0p1/config.txt
Might be able to spot a difference between what you have and what is in
GitHub.
Paul Webster
http://dabdig.blogspot.com
Author Radio France (FIP etc)
Hi Paul, You know its going to be fat fingers!..
I have followed your step by step guide on GitHub but cannot get the
display to work. I have confirmed that the display works on Raspbian
with Pimoroni's drivers on the Pi 2B but can't get anything out of it
under pCP 6 & Jivelite.
Any thoughts
That's a typo, the extension is pigpio.tcz
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
(https://www.paypal.com/cgi-bin/webscr?cmd=_donations=U7JHY5WYHCNRU=GB_code=USD=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted)
if
paul- wrote:
> Its because it is not an extension. The howto is listed on the github
> page.
Are you referring to this
7.Backlight
>From the pCP Extension interface install the extension pigpiod.tcz
If you are I did the following
I found the ip address of my pi zero w (player only, LMS not
Its because it is not an extension. The howto is listed on the github
page.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
paul- wrote:
> I might move it to my octopi setup just have to find or design a
> nice control case.
>
> Anyway, I did update some instructions for pCP, I have not tested with a
> rpi4 yet.
>
> https://github.com/piCorePlayer/hyperpixel4
This extension is not available from the pCP
You would have to use an i2c bus based GPIO extender.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Hi all,
When PcP includes LMS I like solutions with switch-off button to avoid
brutal shutdowns. Also it is quite an elegant solution to start the
device, instead of getting to the wall to plug/unplug etc.
I guess this is still possible to use a GPIO power button with this
display? PcP in its
I might move it to my octopi setup just have to find or design a
nice control case.
Anyway, I did update some instructions for pCP
https://github.com/piCorePlayer/hyperpixel4
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please
Perhaps the Hyperpixel's are best considered for controllers. I picked
up the 3.5 version a while back, but came to the conclusion that I
didn't want to give up my HiFiBerry's and pHat DAC's. Works great for
controller/display only.
Nope. I2S is not available. Only USB or the Pi onboard audio.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
Hi Paul, could the screen sit on top of an audio dac as this one ?
http://iqaudio.co.uk/hats/8-pi-dac.html
or do they use the same pins for communication?
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: 'https://www.picoreplayer.org' (https://www.picoreplayer.org/)
I agree, I just liked the form factor of the display, and not needing
any Odd connectors/cables to connect the display to the rpi.
piCorePlayer a small player for the Raspberry Pi in RAM.
Homepage: https://www.picoreplayer.org
Please 'donate'
paul- wrote:
>
> Cons:
> > > >
- This literally uses most of the GPIO header for the graphic
> connection. The connection is direct to the rpi GPU. It runs the
> GPIO in dpi mode. The only Free GPIO are 18 and 26
- This means you cannot use a i2S Hat board for sound, but Rpi
35 matches
Mail list logo
