| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
OS installation/flash que...
Forum: PostmarketOS on PinePhone
Last Post: biketool
1 hour ago
» Replies: 6
» Views: 2,228
|
Front infrared flash cont...
Forum: PostmarketOS on PinePhone
Last Post: biketool
1 hour ago
» Replies: 15
» Views: 13,432
|
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: biketool
Yesterday, 09:23 AM
» Replies: 1
» Views: 52
|
PinePhone modem keeps "di...
Forum: PinePhone Hardware
Last Post: RobinHayes
12-12-2025, 05:23 AM
» Replies: 18
» Views: 14,828
|
No phone call audio, logs...
Forum: PinePhone Pro Hardware
Last Post: biketool
12-12-2025, 05:00 AM
» Replies: 9
» Views: 521
|
PinePhone USB-C port and ...
Forum: PinePhone Hardware
Last Post: jakfish
12-11-2025, 08:57 AM
» Replies: 5
» Views: 6,081
|
Is Danctnix about to get ...
Forum: PineTab Software
Last Post: biketool
12-11-2025, 06:19 AM
» Replies: 0
» Views: 84
|
7 inch touch panel patche...
Forum: Linux on PINE A64-LTS / SOPINE
Last Post: Learnincurve
12-11-2025, 02:54 AM
» Replies: 1
» Views: 178
|
default login & password,...
Forum: Getting Started
Last Post: kiloseven
12-11-2025, 12:11 AM
» Replies: 1
» Views: 91
|
Pine A64+ lost 7" screen ...
Forum: General Discussion on PINE A64(+)
Last Post: Learnincurve
12-10-2025, 09:03 AM
» Replies: 0
» Views: 122
|
|
|
| Need help compiling android for pine a64 + |
|
Posted by: YeeticusMaximus22 - 12-12-2025, 09:53 AM - Forum: Android on Pine A64(+)
- Replies (1)
|
 |
My goal is to compile android for a64+ with the usb simcom76xx drivers included, but I can't even get it to compile stock. I have tried several guides, several ubuntu versions as host os, various things. and the 8.1 sdk seems to be missing files (such as .dts) at first glance, on top of no compile instructions. How do?
|
|
|
|
| Pine A64+ lost 7" screen functionality after kernel 6.1 |
|
Posted by: Learnincurve - 12-10-2025, 09:03 AM - Forum: General Discussion on PINE A64(+)
- No Replies
|
 |
Hi,
I was successfully running Armbian on my Pine A64+ board, using the 7" touch screen from 2016, first using the Longsleep kernel, with mainline kernels from 2021.
See https://forum.pine64.org/showthread.php?tid=3482 thread for more details.
Regular Armbian upgrades were fine until around the beginning of this year - Armbian kernel 6.1.104 (02/02/2025).
But a kernel version somewhere beween that and the next currently available Armbian kernel 6.6.750 (03/02/25) has broken the output to the touchscreen.
I haven't been able top source intermediate kernels and device trees, so can't say exactly where the change happened that broke the output.
Rolling back to 6.1.104 fixes the display with no other changes.
I don't see any changes in logging boutput related to mipi-dsi or display and don't have access to a serial connection to view the early boot process, so am stuck.
Does anyone else still use this board with the 7" touchsceen and have they been able to run it with a kernel later than 6.1.x?
I'd be very interested to know what changed and how to fix it without freezing the kernel.
|
|
|
|
| PineTab2 spec for ddr and |
|
Posted by: rth - 12-09-2025, 08:28 PM - Forum: PineTab Hardware
- No Replies
|
 |
I'm trying to build a U-Boot loader for PineTab2 (don't ask me why, I have no answer to this question).
However, it fails on step 2 - building atf. Without it, U-Boot returns an error
Code: [alarm@danctnix u-boot]$ make pinetab2-rk3566_defconfig
#
# configuration written to .config
#
[alarm@danctnix u-boot]$ make -j 4
scripts/kconfig/conf --syncconfig Kconfig
CFG u-boot.cfg
GEN include/autoconf.mk.dep
CFG spl/u-boot.cfg
GEN include/autoconf.mk
GEN spl/include/autoconf.mk
UPD include/generated/timestamp_autogenerated.h
ENVC include/generated/env.txt
ENVP include/generated/env.in
ENVT include/generated/environment.h
LDS u-boot.lds
CC common/version.o
AR common/built-in.a
CC env/common.o
AR env/built-in.a
LD u-boot
OBJCOPY u-boot.srec
OBJCOPY u-boot-nodtb.bin
RELOC u-boot-nodtb.bin
SYM u-boot.sym
CAT u-boot-dtb.bin
MKIMAGE u-boot.img
MKIMAGE u-boot-dtb.img
COPY u-boot.bin
CC spl/common/spl/spl.o
AR spl/common/spl/built-in.a
LD spl/u-boot-spl
OBJCOPY spl/u-boot-spl-nodtb.bin
SYM spl/u-boot-spl.sym
CAT spl/u-boot-spl-dtb.bin
COPY spl/u-boot-spl.bin
BINMAN .binman_stamp
[b]Image 'simple-bin' is missing external blobs and is non-functional: rockchip-tpl atf-bl31[/b]
/binman/simple-bin/mkimage/rockchip-tpl (rockchip-tpl):
An external TPL is required to initialize DRAM. Get the external TPL
binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source
for the external TPL binary is https://github.com/rockchip-linux/rkbin.
/binman/simple-bin/fit/images/@atf-SEQ/atf-bl31 (atf-bl31):
See the documentation for your board. You may need to build ARM Trusted
Firmware and build with BL31=/path/to/bl31.bin
[b]Image 'simple-bin' has faked external blobs and is non-functional: rockchip-tpl[/b]
[b]Image 'simple-bin' is missing optional external blobs but is still functional: tee-os[/b]
/binman/simple-bin/fit/images/@tee-SEQ/tee-os (tee-os):
See the documentation for your board. You may need to build Open Portable
Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin
[b]Image 'simple-bin-spi' is missing external blobs and is non-functional: rockchip-tpl atf-bl31[/b]
/binman/simple-bin-spi/mkimage/rockchip-tpl (rockchip-tpl):
An external TPL is required to initialize DRAM. Get the external TPL
binary and build with ROCKCHIP_TPL=/path/to/ddr.bin. One possible source
for the external TPL binary is https://github.com/rockchip-linux/rkbin.
/binman/simple-bin-spi/fit/images/@atf-SEQ/atf-bl31 (atf-bl31):
See the documentation for your board. You may need to build ARM Trusted
Firmware and build with BL31=/path/to/bl31.bin
[b]Image 'simple-bin-spi' has faked external blobs and is non-functional: rockchip-tpl[/b]
[b]Image 'simple-bin-spi' is missing optional external blobs but is still functional: tee-os[/b]
/binman/simple-bin-spi/fit/images/@tee-SEQ/tee-os (tee-os):
See the documentation for your board. You may need to build Open Portable
Trusted Execution Environment (OP-TEE) and build with TEE=/path/to/tee.bin
[b]Some images are invalid[/b]
make: *** [Makefile:1339: .binman_stamp] Error 103
Code: ls rkbin/bin/rk35/rk3566*
rkbin/bin/rk35/rk3566_ddr_1056MHz_D3_LP3_eyescan_v1.23.bin rkbin/bin/rk35/rk3566_ddr_1056MHz_ultra_v1.20.bin rkbin/bin/rk35/rk3566_ddr_528MHz_ultra_v1.10.bin rkbin/bin/rk35/rk3566_ddr_920MHz_ultra_v1.10.bin
rkbin/bin/rk35/rk3566_ddr_1056MHz_D4_LP4_4x_eyescan_v1.23.bin rkbin/bin/rk35/rk3566_ddr_1056MHz_v1.23.bin
rkbin/bin/rk35/rk3566_ddr_780MHz_ultra_v1.10.bin
rkbin/bin/rk35/rk3566_ddr_920MHz_v1.23.bin
Does anyone know what the DDR frequency is on the PineTab2?
Another question.
Can I use rk3568_bl31_v1.45.elf to build u-boot for rk3566?
Don't laugh too hard, I'm new on that
|
|
|
|
| default login & password, Pinebook Pro? |
|
Posted by: kiloseven - 12-08-2025, 07:17 PM - Forum: Getting Started
- Replies (1)
|
 |
Just received a gifted Pinebook Pro. Donor said "look in the forums" when I asked for the login & password.
May I please ask what are the default username and password?
TY.
UPDATE: rock/rock
--
73 & best regards de K7AAY CN85oj @503bartley.pdx.social @503bartley.bsky.social
|
|
|
|
Alpha One - no connectivity directly out of the box. |
|
Posted by: anoduck - 12-06-2025, 10:07 AM - Forum: Getting Started
- No Replies
|
 |
Purchased an Alpha One, took it out of the box, plugged in the Ethernet cord, inserted a blank SD Card, and plugged in the provided power cable. Noticed from the start, only one of the two ethernet port lights were lit, which indicates a faulty port. I created a brand new Cat6 Ethernet cable with shielded RJ45s, and tested it, to make sure the cable was not the issue. I then checked to see if the alpha one had acquired an IP Address, it indicated it did, but attempts to connect failed due to timing out. So then an ARP scan was performed to see if the board would respond to ARP, but it did not. I performed a ping test for redundancy, which timed out, then the Alpha One disappeared entirely from the network.
Repeated attempts to try to configure the network proved unsuccessful, until the decision to reflash the entire board with the official image was reached. This was performed to the letter as instructed by RockOS, here[url=https://docs.rockos.dev/en/docs/installation/][/url]. The result of which was fewer errors generated in syslog, but overall no change. Neither could the board obtain connectivity, nor could anything connect to it.
Current efforts are invested towards discovering whether the EMMC is defective, before moving on to other parts of the board itself. In my sixteen years of experience, I have yet to encounter a system I have been unable to get up and running, I do not plan for the AlphaOne to be the first, but there is little I can do when it appears the hardware itself arrives broken.
|
|
|
|
| camera not usable with trixie? |
|
Posted by: JChdeL - 12-05-2025, 01:45 AM - Forum: Mobian on PinePhone
- No Replies
|
 |
Hi,
I'm writing a custom pyqt6 app on my pinephone but I cannot access the camera.
In dmesg, I see
Quote:ov5640 0-004C: ov5640_write_reg: error: reg=3008, val=42
Does it mean no cam for pinephone running trixie?
Is it a workaround or a fix?
Have a nice day!
|
|
|
|
|