No worries, I got it working with the drivers from waveshare and some
help from this thread for setting up jivelite.
I still need to optimise the size of the skin, as the qvga square is
smaller than the display, despite being 240x240, same as the display.
---
jd68 wrote:
> Ok, understood. I am a beta tester. :D
>
> The scripts are great. It worked like a charm.
>
> But the README.md could be improved because at some points I was unsure
> what to do:
>
> in Step 2:
> instead of
> >
Code:
> > pcp_prepare_kernel_src -k -s
paul- wrote:
> The scripts should walk you through it. I'm trying to be vague, to see
> how it goes.
Ok, understood. I am a beta tester. :D
The scripts are great. It worked like a charm.
But the README.md could be improved because at some points I was unsure
what to do:
in Step 2:
instead
paul- wrote:
> There is no way to "update" between 32 and 64 bit.
Thought so. 32 bit running great. I suspect that I may find some
advantage to rescanning LMS in 64 bit, otherwise I can’t think of
any other advantages for me as I only use pCP for LMS.
Is there an other advantage to 64 Bit on
Some of the overlays have overrides, which means you can move the
function to a different pin. But obviously re-routing the electrical
connection is a bit harder. Take a look at the README in the overlay
folder as to what the specific overrides are for each.
That's why the DSI screen connecto
Insitu_update From 7.01 to 8.0 went well.
Been doing the Insitu_update since 6.0
Im on a RP3B. Did the Insitu_update do a 32 bit install? And if so,
is the only way to get to a 64bit with a full install?
Thanks for the great work.
Tony
SBTouch ♪ SBRadio ♬
paul- wrote:
> You have a pin conflict, The obvious one is the DAC mute vs screen
> backlight control.
>
> i2s Dac Hats use (pins 12, 35, 38 and 40) for the i2s sound interface.
> Some also use Pins 3&5 for the i2c line to control the DAC.
>
> Then you can look at the source for the device
Greg Erskine wrote:
> copy2fs is not of much use.
>
> It was initially added as an answer to the "supposedly" corrupt SD cards
> problem. But that problem didn't really occur on piCore, so it hasn't
> been implemented.
>
> You could completely run pCP in RAM, unmount /dev/mmcblk0p1 and do full
copy2fs is not of much use.
It was initially added as an answer to the "supposedly" corrupt SD cards
problem. But that problem didn't really occur on piCore, so it hasn't
been implemented.
You could completely run pCP in RAM, unmount /dev/mmcblk0p1 and do full
backups of the unmounted partition
Hi was wondering what the advantages of using the copy2fs option in
PCP8.0 are?
Have done a number of insitu upgrades and a couple of installations from
scratch all went perfectly thankyou very much.
gegen's Profile:
paul- wrote:
> Working with the developer at bluealsa
.. will see where this goes.
Thank you!
pi4 4gb picoreplayer with lms and squeezelite for usb inside an argon
one case
pi3b+ (7\" display, hifiberry dac+ pro) picoreplayer with
squeezlite/jivelite for hifiberry and bluetooth headphone ins
11 matches
Mail list logo
