| Welcome, Guest |
You have to register before you can post on our site.
|
| Latest Threads |
Mobian image for the Pine...
Forum: Mobian on PinePhone
Last Post: Korfou
04-27-2026, 09:57 AM
» Replies: 2
» Views: 209
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
04-19-2026, 12:56 PM
» Replies: 13
» Views: 15,060
|
Pine Time dead
Forum: General Discussion on PineTime
Last Post: chris.burmajster
04-18-2026, 10:08 AM
» Replies: 0
» Views: 207
|
Booting Issues
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:17 PM
» Replies: 24
» Views: 19,606
|
App launcher shows tiny i...
Forum: PineNote Software
Last Post: vlagged
04-17-2026, 04:12 PM
» Replies: 1
» Views: 1,133
|
my pinecil v2 is not work...
Forum: General Discussion on Pinecil
Last Post: jagrav
04-17-2026, 06:28 AM
» Replies: 0
» Views: 140
|
Freezes and kernel panics...
Forum: Linux on RockPro64
Last Post: prahal
04-15-2026, 06:48 PM
» Replies: 4
» Views: 1,479
|
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
04-06-2026, 08:44 AM
» Replies: 0
» Views: 328
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 9,325
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 461
|
|
|
| getting second serial port available |
|
Posted by: gadgetguy - 11-10-2023, 12:05 AM - Forum: General Discussion on PINE A64-LTS / SOPINE
- Replies (1)
|
 |
I'm trying to get the second serial port working (/dev/ttyS2) on a PINE64-LTS board.
I created and edited the DTS file as @martinayotte posted a while back (https://forum.pine64.org/showthread.php?...ight=ttyS2).
But it didn't seem to work. I am using a logic analyzer to monitor the signals and getting NO data. I am using a simple C program to open and write to the port. the write reports its writing data.
in /boot/dtb/allwinner I modified the "-lts.dtb" file
-rw-r--r-- 1 root root 41859 Feb 17 2023 sun50i-a64-pine64.dtb
-rw-rw-r-- 1 root root 41973 Nov 1 13:20 sun50i-a64-pine64-lts.dtb
-rw-r--r-- 1 root root 41909 Feb 17 2023 sun50i-a64-pine64-lts-dtb-backup
-rw-r--r-- 1 root root 41981 Feb 17 2023 sun50i-a64-pine64-plus.dtb
Is there a way to confirm
a) which DTB file the system is actually using, or
b) that the "okay" on that serial port is enabling the mux mapping for those pins?
Thanks in advance.
|
|
|
|
| Pinebook Pro charging issues |
|
Posted by: tomekdev - 11-09-2023, 01:35 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (1)
|
 |
Hello everyone,
I have recently bought second-hand Pinebook Pro. I am using ARM platform for many years already (ASUS Chromebook C201PA with Devuan Linux as daily driver). Pinebook Pro brought my attention because of it's privacy features, great community support, RK3399 onboard (my chromebook has RK3288), case with alloy-magnesium, high resolution display and it looks modern and solid. I have installed Devuan Linux and it worked well with some workarounds (change sleep mode from deep to s2idle, my own custom background daemon for backlight management).
Pinebook Pro recently started having problems with charging. Through USB-C almoast always it is really charging (battery voltage rises by around 0.2-0.3V when plugged in as shown by command "sensors"). However sometimes the voltage does not change even though red LED is on. When I plug in barrell charger battery voltage never rises even though red LED is on. Earlier (one week before) battery used to charge normally through barrell or USB-C. Does anyone have any suggestions what is the problem in hardware? I have tried to perform some measurements for voltages on PCB but I didn't have enough time to investigate deeper and didn't find anything.
It's a shame that so promising device has dumb hardware issues (weak USB-A port unable to power HDD, high-pitch noise, exploding sound from speakers when audio codec goes to sleep mode regardless the volume, extremely slow charging, problems with charging, incorrect battery temperature reporting). I have come up with an idea that if I would not be able to solve charging issue, I will replace the motherboard with modified Orange Pi 3B accompanied by my custom PCB for I/O (USB ports, SD card slot and so on). What do you think about it?
|
|
|
|
| How is it going Pine64.org? |
|
Posted by: Corfromleuven - 11-09-2023, 04:57 AM - Forum: General
- Replies (2)
|
 |
Dear all, I try to regularly check the pine64.org blog page for community updates. Since the ironic august post about you guys keeping us waiting there seems to be no new community updates posted at all. Also the forum pages seem way out of date. What is happening? Is Pine64.org still alive?
|
|
|
|
| PPP now used as main device. |
|
Posted by: DaForest - 11-08-2023, 11:09 AM - Forum: General Discussion of PinePhone Pro
- Replies (3)
|
 |
Good day folks,
I now use my PPP as a daily device. This replaces my Blackberry Classic as a main device.
The only true requirement is the wired headset which is something most of us do regardless.
Arch Linux Phosh 2023-09-25 version.
To fix the dark theme issue I installed xdg-desktop-portal-gnome
sudo pacman -S xdg-desktop-portal-gnome
|
|
|
|
| Can't boot from eMMc with Armbian 23.8 Bookworm |
|
Posted by: francoispawlus - 11-07-2023, 02:50 AM - Forum: Linux on PINE A64-LTS / SOPINE
- Replies (1)
|
 |
Hello team!
I try to evaluate the platform based on:
- Sopine Baseboard model A
- Sopine A64 compute module
- Armbian 23.8 Bookworm
There is no issue with SDCard boot.
But when I try to boot the same image from eMMC (32G), the process stopped when the kernel start.
Here is an extract of the log from the serial console:
Please go to the last line to see the last operation.
Code: [10:40:49:671] U-Boot SPL 2023.07.02-armbian (Aug 31 2023 - 08:27:25 +0000)
[10:40:49:695] DRAM: 2048 MiB
[10:40:49:695] Trying to boot from MMC2
[10:40:50:402] NOTICE: BL31: v2.9(debug):armbian
[10:40:50:402] NOTICE: BL31: Built : 08:27:02, Aug 31 2023
[10:40:50:402] NOTICE: BL31: Detected Allwinner A64/H64/R18 SoC (1689)
[10:40:50:402] NOTICE: BL31: Found U-Boot DTB at 0x20ab818, model: SoPine with baseboard
[10:40:50:402] INFO: ARM GICv2 driver initialized
[10:40:50:402] INFO: Configuring SPC Controller
[10:40:50:402] INFO: PMIC: Probing AXP803 on RSB
[10:40:50:402] INFO: PMIC: dcdc1 voltage: 3.300V
[10:40:50:402] INFO: PMIC: dcdc5 voltage: 1.200V
[10:40:50:402] INFO: PMIC: dcdc6 voltage: 1.100V
[10:40:50:402] INFO: PMIC: dldo1 voltage: 3.300V
[10:40:50:402] INFO: PMIC: dldo2 voltage: 3.300V
[10:40:50:448] INFO: PMIC: dldo4 voltage: 3.300V
[10:40:50:448] INFO: PMIC: fldo1 voltage: 1.200V
[10:40:50:448] INFO: PMIC: Enabling DC SW
[10:40:50:448] INFO: BL31: Platform setup done
[10:40:50:448] INFO: BL31: Initializing runtime services
[10:40:50:448] INFO: BL31: cortex_a53: CPU workaround for 843419 was applied
[10:40:50:448] INFO: BL31: cortex_a53: CPU workaround for 855873 was applied
[10:40:50:448] INFO: BL31: cortex_a53: CPU workaround for 1530924 was applied
[10:40:50:448] SCP/INF: Crust v0.5.10000
[10:40:50:448] INFO: PSCI: Suspend is available via SCPI
[10:40:50:448] INFO: BL31: Preparing for EL3 exit to normal world
[10:40:50:468] INFO: Entry point address = 0x4a000000
[10:40:50:468] INFO: SPSR = 0x3c9
[10:40:50:961] ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19
[10:40:50:961]
[10:40:50:961]
[10:40:50:961] U-Boot 2023.07.02-armbian (Aug 31 2023 - 08:27:25 +0000) Allwinner Technology
[10:40:50:961]
[10:40:50:961] CPU: Allwinner A64 (SUN50I)
[10:40:50:961] Model: SoPine with baseboard
[10:40:50:961] DRAM: 2 GiB
[10:40:51:022] Core: 73 devices, 22 uclasses, devicetree: separate
[10:40:51:022] WDT: Not starting watchdog@1c20ca0
[10:40:51:022] MMC: mmc@1c0f000: 0, mmc@1c11000: 1
[10:40:51:045] Loading Environment from FAT... Unable to use mmc 1:1...
[10:40:52:787] In: serial
[10:40:52:787] Out: serial
[10:40:52:787] Err: serial
[10:40:52:803] Net: eth0: ethernet@1c30000
[10:40:52:843] MMC: no card present
[10:40:52:843] ** Bad device specification mmc 0 **
[10:40:52:843] Couldn't find partition mmc 0
[10:40:52:843] MMC: no card present
[10:40:52:843] ** Bad device specification mmc 0 **
[10:40:52:843] Couldn't find partition mmc 0
[10:40:52:843] starting USB...
[10:40:52:843] Bus usb@1c1a000: sun4i_usb_phy phy@1c19400: External vbus detected, not enabling our own vbus
[10:40:52:881] USB EHCI 1.00
[10:40:52:881] Bus usb@1c1a400: USB OHCI 1.0
[10:40:52:897] Bus usb@1c1b000: USB EHCI 1.00
[10:40:52:924] Bus usb@1c1b400: USB OHCI 1.0
[10:40:52:924] scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
[10:40:54:067] scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
[10:40:55:194] scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
[10:40:56:329] scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
[10:40:57:468] scanning usb for storage devices... 0 Storage Device(s) found
[10:40:57:468] Autoboot in 1 seconds, press <Space> to stop
[10:40:58:507] switch to partitions #0, OK
[10:40:58:523] mmc1(part 0) is current device
[10:40:58:523] Scanning mmc 1:1...
[10:40:58:555] Found U-Boot script /boot/boot.scr
[10:40:58:602] 3259 bytes read in 5 ms (635.7 KiB/s)
[10:40:58:602] ## Executing script at 4fc00000
[10:40:58:602] U-boot loaded from eMMC or secondary SD
[10:40:58:602] Boot script loaded from mmc
[10:40:58:602] 155 bytes read in 4 ms (37.1 KiB/s)
[10:40:58:602] MMC: no card present
[10:40:58:602] ** Bad device specification mmc 0 **
[10:40:58:642] 41715 bytes read in 11 ms (3.6 MiB/s)
[10:40:58:642] Working FDT set to 4fa00000
[10:40:58:642] 3821 bytes read in 5 ms (746.1 KiB/s)
[10:40:58:642] Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
[10:40:58:642] ## Executing script at 45000000
[10:40:59:041] 18215274 bytes read in 395 ms (44 MiB/s)
[10:40:59:533] 22390792 bytes read in 476 ms (44.9 MiB/s)
[10:40:59:533] Moving Image from 0x40080000 to 0x40200000, end=417d0000
[10:40:59:733] ## Loading init Ramdisk from Legacy Image at 4ff00000 ...
[10:40:59:733] Image Name: uInitrd
[10:40:59:733] Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
[10:40:59:733] Data Size: 18215210 Bytes = 17.4 MiB
[10:40:59:733] Load Address: 00000000
[10:40:59:733] Entry Point: 00000000
[10:40:59:733] Verifying Checksum ... OK
[10:40:59:861] ## Flattened Device Tree blob at 4fa00000
[10:40:59:861] Booting using the fdt blob at 0x4fa00000
[10:40:59:882] Working FDT set to 4fa00000
[10:40:59:882] Loading Ramdisk to 48ea0000, end 49fff12a ... OK
[10:40:59:912] Loading Device Tree to 0000000048e2d000, end 0000000048e9ffff ... OK
[10:40:59:912] Working FDT set to 48e2d000
[10:41:00:344]
[10:41:00:344] Starting kernel ...
[10:41:00:344]
[10:41:03:989] <0x1b>[2J<0x1b>[3J<0x1b>[-1;-1fdone.
[10:41:04:014] Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
[10:41:04:014] Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
It would be helpfull if somebody have any idea to solved this .
thanks for the support,
BR
|
|
|
|
| Messed Up Modem |
|
Posted by: dorkydev - 11-05-2023, 11:26 AM - Forum: PinePhone Pro Hardware
- Replies (13)
|
 |
One of the gold prongs is missing off the board, and it's extremely finicky picking up a sim now or if one is picked up it eventually drops signal.
Currently, there is no cheaper way to get a new modem, is there? Unless I found a cheaper pinephone altogether on ebay used and removed it myself and replaced it.
Basically I had a micro inside a mini and that grove caught hold of the prongs one time and snagged up and out from the board, really wish we could just upgrade the slot all the way from a mini to a standard micro.
|
|
|
|
|