| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,925
» Latest member: Kuletlou
» Forum threads: 16,330
» Forum posts: 117,424
Full Statistics
|
| Latest Threads |
Best Stainless Steel Cook...
Forum: General
Last Post: Briar4
03-22-2026, 11:38 AM
» Replies: 0
» Views: 53
|
Best Stainless Steel Cook...
Forum: General
Last Post: Briar4
03-22-2026, 11:36 AM
» Replies: 0
» Views: 42
|
Pinebook problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
03-18-2026, 08:58 AM
» Replies: 2
» Views: 4,606
|
Pine a64+ power supply
Forum: General Discussion on PINE A64(+)
Last Post: davidspencer
03-18-2026, 01:02 AM
» Replies: 0
» Views: 127
|
Private / self-hosted "Cl...
Forum: General Discussion on PinePhone
Last Post: cyberb123
03-17-2026, 11:57 AM
» Replies: 8
» Views: 7,135
|
Automatic screen rotation
Forum: PineTab Software
Last Post: Raik
03-17-2026, 01:49 AM
» Replies: 32
» Views: 29,798
|
Prohibit Pinecil from goi...
Forum: Pinecil Software
Last Post: snorkel
03-13-2026, 01:56 AM
» Replies: 2
» Views: 206
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
03-12-2026, 04:49 AM
» Replies: 2
» Views: 608
|
Looking for PineTime user...
Forum: General
Last Post: Mitrax
03-11-2026, 02:50 PM
» Replies: 2
» Views: 385
|
reset wifi hardware/drive...
Forum: Mobian on PinePhone
Last Post: baptx
03-10-2026, 04:43 PM
» Replies: 5
» Views: 5,066
|
|
|
| Cap Error or Bad Memory |
|
Posted by: GuyNoIRQ - 03-22-2021, 08:18 PM - Forum: RockPro64 Hardware and Accessories
- Replies (5)
|
 |
Hi all for the past couple months I've been having some stability issues with my RockPro64 NAS. It would just seem to hang and require physical power cycle to get back online. About a week ago it seems to have given up the ghost.
This evening I hooked up an ftdi232 so I could look at the serial console as it attempts to boot, and I'm getting output similar to below pretty consistently, but with slight variations. I'm not so deep in the weeds with SBC init procedures to make too much sense of this, but "Cap error!" seems to indicate to me that there may be a faulty capacitor somewhere on my board, and the failure to read a given memory address seems to indicate that it may be a capacitor related to the ram chips. My question is, is there a good way for me to test and identify which if any capacitor may have gone bad so I can try to re-solder a new one on? If its the ram I'll resign myself to tossing the board as I don't have a reflow station, and the wife would kill me if I tried to use the oven to do that. I have a basic multimeter, and a cheapo oscilloscope from aliexpress if those tools may help drill into what I may need to replace here.
I'd really like to bring this little computer back to life if its not too much headache. This thing lasted me less than 2 years. For $80 I expected a lot better components and QC. I have an early 1st gen Raspberry Pi that's still chooching at 19 years old.
Code: Version 1.19 20190305
In
channel 0
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x0
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x80
MR4=0x2
MR5=0x0
MR8=0x0
MR12=0x2
MR14=0x0
MR18=0x0
MR19=0x0
MR24=0x0
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
Channel 0: LPDDR4,800MHz
W FF != R
Cap error!
Channel 1: LPDDR4,800MHz
Col error!!!
Cap error!
ERR
Code: Version 1.19 20190305
In
channel 0
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
Channel 0: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
Channel 1: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
256B stride
read addr 0x40008000 = 0x40010000
ERR
Code: Version 1.19 20190305
In
channel 0
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x0
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x0
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x80
MR4=0x2
MR5=0x0
MR8=0x0
MR12=0x2
MR14=0x2
MR18=0x0
MR19=0x0
MR24=0x0
MR25=0x0
CS = 1
MR0=0x18
MR4=0x82
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x82
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
Channel 0: LPDDR4,800MHz
W FF != R
Cap error!
Channel 1: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
no stride
read addr 0x8000 = 0xFFFF8000
ERR
Code: Version 1.19 20190305
In
channel 0
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x0
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 400MHz 0,1
channel 0
CS = 0
MR0=0x98
MR4=0x2
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x0
MR4=0x82
MR5=0x0
MR8=0x0
MR12=0x0
MR14=0x2
MR18=0x0
MR19=0x0
MR24=0x0
MR25=0x0
channel 1
CS = 0
MR0=0x98
MR4=0x82
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
CS = 1
MR0=0x18
MR4=0x3
MR5=0xFF
MR8=0x8
MR12=0x72
MR14=0x72
MR18=0x0
MR19=0x0
MR24=0x8
MR25=0x0
channel 0 training pass!
channel 1 training pass!
change freq to 800MHz 1,0
Channel 0: LPDDR4,800MHz
W FF != R
Cap error!
Channel 1: LPDDR4,800MHz
Bus Width=32 Col=10 Bank=8 Row=15/15 CS=2 Die Bus-Width=16 Size=2048MB
no stride
ch 0 ddrconfig = 0x101, ddrsize = 0x2020
pmugrf_os_reg[2] = 0x2AA1E000, stride = 0x18
OUT
U-Boot SPL board iq"Synchronous Abort" handler, esr 0x9600qSynchronous Abort" handler, esr 0x02000000ELR: adac
LR: 4308
x 0: 0000000000000030 x 1: 00000000000ELR: adac
LR: 4268
x 0: 0000000000000030 x 1: 00000000000"Synchronous Abort" handler, esr 0x96000"Synchronous Abort" handler, esr 0x02000000
"Synchronous Abort" handler, esr 0x96000""Synchronous Abort" handler, esr 0x86000000
ELR: 17ff0000531f3e00
LR: 3ecc
x 0: 0000000"Synchronous Abort" handler, esr 0x02000000"Synchronous Abort" handler, esr 0x86000qSynchronous Abort" handler, esr 0x02000000
ELR: 8de0
LR: 4308
x 0: 0000000000000030 x 1: 0000000000000000
x 2: 00000000ff1a0014 x 3: 0000000000000030
x 4: 00000000003f9df8 x 5: 0000000000000000
x 6: 0000000000000001 x 7: 07f822e0003fb310
x 8: 00000000ff8c1edc x 9: 0000000000000000
x10: 0000000000000000 x11: 000000000000000c
x12: 0000000080000000 x13: 000000000000000f
x14: 00000qSynchronous Abort" handler, esr 0x02000000"Synchronous Abort" handler, esr 0x02000000"Synchronous Abort" handler, esr 0x02000000ELR: adac
LR: 3ecc
x 0: 000000000000000a x 1: 0000000000000000
x 2: 0000000000003e00 x 3: 0000000000000030
x 4: 0000000000003e00 x 5: 0000000000000000
x 6: 0000000000000001 x 7: 000000000000000"Synchronous Abort" handler, esr 0x02000000
ELR: adac
LR: 4308
x 0: 0000000000000061 x 1: 0000000000""Synchronous Abort" handler, esr 0x0200000"Synchronous Abort" handler, esr 0x02000000ELR: adac
"Synchronous Abort" han"Synchronous Abort" handler, esr 0x02000000
"Synchronous Abort" handler, esr 0x0200qSynchronous Abort" handler, esr 0x02000000qSynchronous Abort" handler, esr 0x02000000"Synchronous Abort" handler, esr 0x02000000
"Synchronous Abort" handler, esr 0x02000000
"Synchronous Abort" handler, esr 0x02000000
"Synchronous Abort" handler, esr 0x02000000
"Synchronous Abort" handler, esr 0x02000000
"Synchronous Abort" handler, esr 0x02000000
"Synchronous Abort" handle"Synchronous Abort" handler, esr 0x02000000"Synchronous Abort" handler, esr 0x02000000"Synchronous Abort" handler, esr 0x02000000"
|
|
|
|
| Installing Mobian --> "Resizing file system" forever |
|
Posted by: Anna - 03-22-2021, 03:42 PM - Forum: Mobian on PinePhone
- Replies (13)
|
 |
To install Mobian on an SD card I, all I theoretically have to do is to download mobian-pinephone-phosh-20210314.img.gz, write it to the card, put the card into the phone and start it, right?
However, when I do that, the "resizing file system during initial boot" screen is there for quite a long time (30 minutes maybe) and afterwards the screen turns black (not pitch black though, the display remains switched on) and that's it.
I have used two different 64 GB cards (a new Sandisk Extreme and and old Sandisk Ultra). I tried
Code: sudo zcat mobian-pinephone-phosh-20210314.img.gz | sudo dd of=/dev/mmcblk0 bs=1M
and I tried BalenaEtcher.
What am I doing wrong?
|
|
|
|
| Motion Eye OS |
|
Posted by: Will Welker - 03-22-2021, 03:23 PM - Forum: General Discussion on PineCube
- Replies (5)
|
 |
Has anybody run motion eye on the cube?
Also can you write an image to an SD card and boot with it like the Pinephone or a Raspberry Pi?
I have tried motioneyeos-pine64-20200606.img.xz and I was hoping to get it to connect to my network so I could avoid the serial-terminal process.
I haven't found any basic instructions to get this up and running.
|
|
|
|
| About killswitches |
|
Posted by: Mtravel - 03-22-2021, 03:13 PM - Forum: PinePhone Hardware
- Replies (1)
|
 |
Hello everyone
I'm new to this forum and joined here to follow the development of Sailfish OS on Pinephone and the utilization of killswitches that appear to be very unpractical location wise. So is there any modification available to allow the killswitches be used without removing the whole back cover? Like some sort of switcher slider in the cover or something? Or is the only option to burn or drill a hole to the cover oneself If you want to keep the mic off always when not having a call?
Thanks
|
|
|
|
| ? about streaming cdma |
|
Posted by: rvh - 03-22-2021, 12:20 PM - Forum: General Discussion on PinePhone
- Replies (2)
|
 |
in my area cdma is the only service that works. i cant find any carrier that supports my modom. my verizon sim works (mostly) but i cant stream on it. so im wondering if that because i cant register my imei? if anyone knows of a carrier that will, plese respond.
|
|
|
|
| Session start fails, need to reinstall? |
|
Posted by: Avron - 03-22-2021, 09:26 AM - Forum: Mobian on PinePhone
- Replies (5)
|
 |
I posted the same question 5 days ago in "getting started" but perhaps it wasn't the right place.
I received my pinephone with mobian 5 days ago. After playing around and failing to update anything with the software update app, I saw I needed to do that via the command line and using dist-upgrade.
I did that but during the upgrade, as I was touching the screen to avoid the screensaver, I touched the battery icon and the phone immediately wet off. As I powered it up again, I could enter the password to decipher but after seing mobian and the logo, I have a graphical message saying that something went wrong in the session start and I need to try again, but f I power off and on again the same occurs.
Is there any solution apart from reinstalling mobian?
While the phone is connected to my PC running Trisquel, there is no device for it so I guess the only solution to reinstall mobian is to first install mobian on a SD card and after I have a working phone, I can try to access the eMMC to install mobian there again, but I am not sure whether that can be the installer at https://images.mobian-project.org/pinephone/installer/ that is copied to the eMMC directly or not (in order to install the FS ciphered).
|
|
|
|
| Back cover plastic woes |
|
Posted by: mteagles1942 - 03-22-2021, 08:29 AM - Forum: PinePhone Hardware
- Replies (6)
|
 |
I finally received my phone and the second day I apparently snapped the thin plastic in between the volume and power buttons. When the back cover was removed the buttons fell off. With a careful hand I was able to put it back together and buttons are working, however now I am afraid to take the cover off again when needed.
I could go on blah blah. My only question is does anyone know of a ETA on back cover https://pine64.com/product/pinephone-bac...46c16e2e66 availability?
thanks everybody
|
|
|
|
|